From: FrancescoFioraEst Date: Mon, 4 Mar 2024 12:26:29 +0000 (+0000) Subject: Update dmaap references in policy documentation files X-Git-Tag: 4.1.2~10 X-Git-Url: https://gerrit.onap.org/r/gitweb?p=policy%2Fparent.git;a=commitdiff_plain;h=30ad30c5a31df96e35d2276d095a72b5e3954b39 Update dmaap references in policy documentation files Issue-ID: POLICY-4942 Change-Id: I08d9ab8e5028eab0a20999ce174d3a2fbad67967 Signed-off-by: FrancescoFioraEst --- diff --git a/docs/clamp/acm/acm-architecture.rst b/docs/clamp/acm/acm-architecture.rst index e1272419..c3e7d568 100644 --- a/docs/clamp/acm/acm-architecture.rst +++ b/docs/clamp/acm/acm-architecture.rst @@ -315,7 +315,7 @@ public and is used by the ACM GUI. It may also be used by any other client via t REST interface. The REST interface also allows the state of Automation Composition Instances to be changed. A user can change the state of Automation Composition Instances as described in the state transition diagram shown in section 2 above. The Instantiation component issues update and state change -messages via DMaaP/Kafka to participants so that they can update and manage the state of the Automation +messages via Kafka to participants so that they can update and manage the state of the Automation Composition Elements they are responsible for. The Instantiation component also implements persistence of Automation Composition Instances, automation composition elements, and their state changes. @@ -334,9 +334,9 @@ changes where state changes failed. A Participant is an executing component that partakes in automation compositions. More explicitly, a Participant is something that implements the Participant Instantiation and Participant -Monitoring messaging protocol over DMaaP/Kafka for Life Cycle management of Automation Composition Elements. +Monitoring messaging protocol over Kafka for Life Cycle management of Automation Composition Elements. A Participant runs Automation Composition Elements and manages and reports on their life cycle -following the instructions it gets from the ACM runtime in messages delivered over DMaaP/Kafka. +following the instructions it gets from the ACM runtime in messages delivered over Kafka. In the figure above, five participants are shown. A Configuration Persistence Participant manages Automation Composition Elements that interact with the `ONAP Configuration Persistence Service @@ -391,14 +391,14 @@ The system is designed to be inherently scalable. The ACM runtime is stateless, is preserved in the Instantiated Automation Composition inventory in the database. When the user requests an operation such as an undeploy, deploy, lock, or an unlock on a Automation Composition Instance, the ACM runtime broadcasts the request to participants over -DMaaP/Kafka and saves details of the request to the database. The ACM runtime does not directly +Kafka and saves details of the request to the database. The ACM runtime does not directly wait for responses to requests. -When a request is broadcast on DMaaP/Kafka, the request is asynchronously picked up by participants +When a request is broadcast on Kafka, the request is asynchronously picked up by participants of the types required for the Automation Composition Instance and those participants manage the life cycle of its automation composition elements. Periodically, each participant reports back on the status of operations it has picked up for the Automation Composition Elements it controls, together with -statistics on the Automation Composition Elements over DMaaP/Kafka. On reception of these participant messages, +statistics on the Automation Composition Elements over Kafka. On reception of these participant messages, the ACM runtime stores this information to its database. The participant to use on a automation composition can be selected from the registered participants diff --git a/docs/clamp/acm/acm-participant-guide.rst b/docs/clamp/acm/acm-participant-guide.rst index baf61d50..a98e66b8 100644 --- a/docs/clamp/acm/acm-participant-guide.rst +++ b/docs/clamp/acm/acm-participant-guide.rst @@ -42,7 +42,9 @@ and the same is configured for the 'ParticipantIntermediaryParameters' object in 1. participantId - A unique participant UUID that is used by the runtime to identify the participant. 2. ReportingTimeIntervalMs - Time inertval the participant should report the status/heartbeat to the runtime. 3. clampAutomationCompositionTopics - This property takes in the kafka topic names and servers for the intermediary module to use. - These values should be provided for both source and sink configs. The following example shows the topic parameters set for using DMaap. + These values should be provided for both source and sink configs. + (**Note**: In order to avoid a connection to Kafka when Unit Tests are running, set topicCommInfrastructure: NOOP in properties file for tests). + The following example shows the topic parameters set for using Kafka. .. code-block:: bash @@ -51,15 +53,15 @@ and the same is configured for the 'ParticipantIntermediaryParameters' object in - topic: POLICY-ACRUNTIME-PARTICIPANT servers: - - ${topicServer:localhost} - topicCommInfrastructure: dmaap + - ${topicServer:localhost}:9092 + topicCommInfrastructure: kafka fetchTimeout: 15000 topicSinks: - topic: POLICY-ACRUNTIME-PARTICIPANT servers: - - ${topicServer:localhost} - topicCommInfrastructure: dmaap + - ${topicServer:localhost}:9092 + topicCommInfrastructure: kafka 4. participantSupportedElementTypes - This property takes a list of typeName and typeVersion fields to define the types of AC elements the participant deals with. These are user defined name and version and the same should be defined for the AC elements that are included in the TOSCA based AC definitions. @@ -410,14 +412,14 @@ The following example shows the topic parameters and the additional 'myparameter topicSources: - topic: POLICY-ACRUNTIME-PARTICIPANT servers: - - ${topicServer:localhost} - topicCommInfrastructure: dmaap + - ${topicServer:localhost}:9092 + topicCommInfrastructure: kafka fetchTimeout: 15000 topicSinks: - topic: POLICY-ACRUNTIME-PARTICIPANT servers: - - ${topicServer:localhost} - topicCommInfrastructure: dmaap + - ${topicServer:localhost}:9092 + topicCommInfrastructure: kafka participantSupportedElementTypes: - typeName: org.onap.policy.clamp.acm.MyFirstAutomationCompositionElement diff --git a/docs/clamp/acm/acm-user-guide.rst b/docs/clamp/acm/acm-user-guide.rst index 842032eb..9bf668fe 100644 --- a/docs/clamp/acm/acm-user-guide.rst +++ b/docs/clamp/acm/acm-user-guide.rst @@ -150,7 +150,7 @@ operations on a high level before proceeding with the workflow. Prerequisites: - - ACM components including acm-runtime, required participants (http and kubernetes in this case) and Dmaap/kafka clients are deployed in docker or kubernetes environment. + - ACM components including acm-runtime, required participants (http and kubernetes in this case) and kafka clients are deployed in docker or kubernetes environment. - Kubernetes and Helm are installed. - Chartmuseum server is installed to host the acelement microservice helm chart. (`Procedure to install chartmuseum `_.) - The helm chart for ACM test microservice is available in the policy/clamp repository that can be cloned locally and uploaded to the chartmuseum using helm push.(`AC element helm chart `_.) diff --git a/docs/clamp/acm/api-protocol/acm-participant-protocol.rst b/docs/clamp/acm/api-protocol/acm-participant-protocol.rst index 6b69166f..2b6beaca 100644 --- a/docs/clamp/acm/api-protocol/acm-participant-protocol.rst +++ b/docs/clamp/acm/api-protocol/acm-participant-protocol.rst @@ -127,7 +127,7 @@ The CLAMP Automation Composition Participant Protocol uses the following message descriptions below give an overview of each message. For the precise definition of the messages, see the `CLAMP code at Github `_ -. All messages are carried on DMaaP. +. All messages are carried on Kafka. .. csv-table:: ACM Messages :file: ../files/ACM-Message-Table.csv diff --git a/docs/clamp/acm/design-impl/clamp-gui-acm.rst b/docs/clamp/acm/design-impl/clamp-gui-acm.rst index b0a2782f..600c721d 100644 --- a/docs/clamp/acm/design-impl/clamp-gui-acm.rst +++ b/docs/clamp/acm/design-impl/clamp-gui-acm.rst @@ -51,7 +51,7 @@ Class-based react components are used to render the different pages related to f 2.1.2 Automation Composition GUI ================================ -The current automation composition GUI is an extension of the previously created GUI for the Clamp project. The Clamp project used the CLAMP GUI to connect to various onap services, including policy api, policy pap, dcae, sdc and cds. Although the current automation composition project builds upon this GUI, it does not rely on these connected services. Instead, the Automation Composition GUI connects to the Automation Composition Runtime only. The Automation Composition Runtime then communicates with the database and all the Automation Composition participants (indirectly) over DMAAP. +The current automation composition GUI is an extension of the previously created GUI for the Clamp project. The Clamp project used the CLAMP GUI to connect to various onap services, including policy api, policy pap, dcae, sdc and cds. Although the current automation composition project builds upon this GUI, it does not rely on these connected services. Instead, the Automation Composition GUI connects to the Automation Composition Runtime only. The Automation Composition Runtime then communicates with the database and all the Automation Composition participants (indirectly) over Kafka. The CLAMP GUI was originally housed in the clamp repository but for the Istanbul release, it has been moved to the policy/gui repo. There are 3 different GUIs within this repository - clamp-gui (and Automation Composition gui) code is housed under the "gui-clamp" directory and the majority of development takes place within the "gui-clamp/ui-react" directory. @@ -106,15 +106,15 @@ This is where all of the endpoints for operations on Automation Compositions are The rest endpoints are split over two main classes; CommissioningController.java and InstantiationController.java. There are also some rest endpoints defined in the MonitoringQueryController. These classes have minimal business logic defined in them and delegate these operations to other classes within the controlloop.runtime package. The Automation Composition Runtime write all data received on its' endpoints regarding commissioning and instantiation to its; database, where it can be easily accessed later by the UI. -The Runtime also communicates with the participants over DMAAP. Commissioning a automation composition definition writes it to the database but also triggers priming of the definitions over DMAAP. The participants then receive those definitions and hold them in memory. Similarly, upon decommissioning, a message is sent over DMAAP to the participants to trigger de-priming. +The Runtime also communicates with the participants over Kafka. Commissioning a automation composition definition writes it to the database but also triggers priming of the definitions over Kafka. The participants then receive those definitions and hold them in memory. Similarly, upon decommissioning, a message is sent over Kafka to the participants to trigger de-priming. -Using DMAAP, the Runtime can send; updates to the automation composition definitions, change the state of automation compositions, receive information about participants, receive state information about automation compositions and effectively supervise the automation compositions. This data is then made available via Rest APIs that can be queried by the frontend. This is how the GUI can perform monitoring operations. +Using Kafka, the Runtime can send; updates to the automation composition definitions, change the state of automation compositions, receive information about participants, receive state information about automation compositions and effectively supervise the automation compositions. This data is then made available via Rest APIs that can be queried by the frontend. This is how the GUI can perform monitoring operations. More detail on the design of the Runtime Automation Composition can be found in :ref:`clamp-runtime-acm`. -2.4 DMAAP +2.4 Kafka --------- -DMAAP is component that provides data movement services that transports and processes data from any source to any target. It provides the capability to: +Kafka is component that provides data movement services that transports and processes data from any source to any target. It provides the capability to: - Support the transfer of messages between ONAP components, as well as to other components - Support the transfer of data between ONAP components as well as to other components. - Data Filtering capabilities @@ -131,10 +131,10 @@ The purpose of the Automation Composition participants is to communicate with di .. image:: ../images/gui/ParticipantsDirectory.png -The participants communicate with the Runtime over DMAAP. Tosca service template specifications, Automation Composition updates and state changes are shared with the participants via messages from runtime Automation Composition through the topic "POLICY-CLRUNTIME-PARTICIPANT". +The participants communicate with the Runtime over Kafka. Tosca service template specifications, Automation Composition updates and state changes are shared with the participants via messages from runtime Automation Composition through the topic "POLICY-CLRUNTIME-PARTICIPANT". 3. GUI Sample Flows ################### -The primary flows from the GUI to the backend, through DMAAP and the participants are shown in the diagram below. This diagram just serves as an illustration of the scenarios that the user will experience in the GUI. You can see factually complete dialogues in :ref:`system-level-label`. +The primary flows from the GUI to the backend, through Kafka and the participants are shown in the diagram below. This diagram just serves as an illustration of the scenarios that the user will experience in the GUI. You can see factually complete dialogues in :ref:`system-level-label`. .. image:: ../images/gui/GUI-Flow.png diff --git a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst old mode 100755 new mode 100644 index 5b88edba..c21cc171 --- a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst +++ b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst @@ -19,7 +19,7 @@ Terminology - Spring Scheduling: into SupervisionAspect class, the @Scheduled annotation invokes "schedule()" method every "runtime.participantParameters.heartBeatMs" milliseconds with a fixed delay - MessageIntercept: "@MessageIntercept" annotation is used into SupervisionHandler class to intercept "handleParticipantMessage" method calls using spring aspect oriented programming - GUI: swagger-ui, Postman or policy-gui -- Message Broker: supported message Broker are DMaap and Strimzi-Kafka +- Message Broker: It supports the message Broker Kafka Design of Rest Api ****************** diff --git a/docs/clamp/acm/design-impl/participants/a1pms-participant.rst b/docs/clamp/acm/design-impl/participants/a1pms-participant.rst index 23e70b9b..5afbf912 100644 --- a/docs/clamp/acm/design-impl/participants/a1pms-participant.rst +++ b/docs/clamp/acm/design-impl/participants/a1pms-participant.rst @@ -7,7 +7,7 @@ A1PMS Participant The A1PMS participant receives A1 policy service information from the CLAMP runtime and creates the A1 policy service in A1PMS. The participant acts as a wrapper around the A1PMS and creates the policy service. -Supported message Broker are DMaap and Strimzi-Kafka. +It supports the message Broker Kafka. .. image:: ../../images/participants/a1pms-participant.png diff --git a/docs/clamp/acm/design-impl/participants/http-participant.rst b/docs/clamp/acm/design-impl/participants/http-participant.rst index 3125e173..03605377 100644 --- a/docs/clamp/acm/design-impl/participants/http-participant.rst +++ b/docs/clamp/acm/design-impl/participants/http-participant.rst @@ -13,7 +13,7 @@ the microservice that runs a REST server. Once the microservice is up, the HTTP participant can be used to configure the microservice over its REST interface.Of course, the HTTP participant works towards any REST service, it is not restricted to REST services started by participants. -Supported message Broker are DMaap and Strimzi-Kafka. +It supports the message Broker Kafka. .. image:: ../../images/participants/http-participant.png diff --git a/docs/clamp/acm/design-impl/participants/k8s-participant.rst b/docs/clamp/acm/design-impl/participants/k8s-participant.rst index dae5df5d..82935bda 100644 --- a/docs/clamp/acm/design-impl/participants/k8s-participant.rst +++ b/docs/clamp/acm/design-impl/participants/k8s-participant.rst @@ -10,7 +10,7 @@ k8s cluster on the specified namespace. It can fetch the helm chart from remote that are configured on the helm client. The participant acts as a wrapper around the helm client and creates the required resources in the k8s cluster. -Supported message Broker are DMaap and Strimzi-Kafka. +It supports the message Broker Kafka. The kubernetes participant also exposes REST endpoints for onboarding, installing and uninstalling of helm charts from the local chart database which facilitates the user to also use this component as a standalone application for helm operations. diff --git a/docs/clamp/acm/design-impl/participants/kserve-participant.rst b/docs/clamp/acm/design-impl/participants/kserve-participant.rst index 618b7ebd..24314a3d 100644 --- a/docs/clamp/acm/design-impl/participants/kserve-participant.rst +++ b/docs/clamp/acm/design-impl/participants/kserve-participant.rst @@ -7,7 +7,7 @@ Kserve Participant The Kserve participant receives inference service information from CLAMP runtime and creates the inference services in the Kubernetes cluster. The participant acts as a wrapper around Kserve and creates the inference service. -Supported message Broker are DMaap and Strimzi-Kafka. +It supports the message Broker Kafka. .. image:: ../../images/participants/kserve-participant.png diff --git a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst old mode 100755 new mode 100644 index 891f5771..0fbaf897 --- a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst +++ b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst @@ -16,7 +16,7 @@ Terminology - Message to a participant: a message only for a participant (participantId properly filled) - MessageSender: a class that takes care of sending messages from participant-intermediary - GUI: graphical user interface, Postman or a Front-End Application -- Message Broker: supported message Broker are DMaap and Strimzi-Kafka +- Message Broker: It supports the message Broker Kafka Inbound messages to participants -------------------------------- diff --git a/docs/clamp/acm/design-impl/participants/participants.rst b/docs/clamp/acm/design-impl/participants/participants.rst index 4dab3434..6b12b7c4 100644 --- a/docs/clamp/acm/design-impl/participants/participants.rst +++ b/docs/clamp/acm/design-impl/participants/participants.rst @@ -7,7 +7,7 @@ Automation Composition Participants A Participant is a component that acts as a bridge between the CLAMP Automation Composition Management runtime and components such as the Policy Framework, DCAE, or a Kubernetes cluster that are taking part in automation composition management. It listens -to DMaaP to receive messages from the CLAMP runtime and performs operations towards components that +to Kafka to receive messages from the CLAMP runtime and performs operations towards components that are taking part in acms. A participant has an Automation Composition Management Element for each automation composition in which it is taking part. diff --git a/docs/clamp/acm/draw.io/acm-overview.drawio b/docs/clamp/acm/draw.io/acm-overview.drawio index d842e06f..489a086a 100644 --- a/docs/clamp/acm/draw.io/acm-overview.drawio +++ b/docs/clamp/acm/draw.io/acm-overview.drawio @@ -1 +1,418 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/clamp/acm/draw.io/acm-participant-a1pms-kserve.drawio b/docs/clamp/acm/draw.io/acm-participant-a1pms.drawio old mode 100755 new mode 100644 similarity index 95% rename from docs/clamp/acm/draw.io/acm-participant-a1pms-kserve.drawio rename to docs/clamp/acm/draw.io/acm-participant-a1pms.drawio index 848cf77e..2cada148 --- a/docs/clamp/acm/draw.io/acm-participant-a1pms-kserve.drawio +++ b/docs/clamp/acm/draw.io/acm-participant-a1pms.drawio @@ -1,26 +1,26 @@ - + - + - + - + - + - + - + @@ -40,20 +40,20 @@ - + - + - + - + - + @@ -152,7 +152,7 @@ - + diff --git a/docs/clamp/acm/draw.io/acm-participant-http.drawio b/docs/clamp/acm/draw.io/acm-participant-http.drawio new file mode 100644 index 00000000..04ca2605 --- /dev/null +++ b/docs/clamp/acm/draw.io/acm-participant-http.drawio @@ -0,0 +1,311 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/clamp/acm/draw.io/acm-participant-k8s.drawio b/docs/clamp/acm/draw.io/acm-participant-k8s.drawio new file mode 100644 index 00000000..dd2e05a2 --- /dev/null +++ b/docs/clamp/acm/draw.io/acm-participant-k8s.drawio @@ -0,0 +1,344 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/clamp/acm/draw.io/acm-participant-kserve.drawio b/docs/clamp/acm/draw.io/acm-participant-kserve.drawio new file mode 100644 index 00000000..d6cdaa85 --- /dev/null +++ b/docs/clamp/acm/draw.io/acm-participant-kserve.drawio @@ -0,0 +1,335 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/clamp/acm/draw.io/acm-participants.drawio b/docs/clamp/acm/draw.io/acm-participants.drawio new file mode 100644 index 00000000..d79d92fe --- /dev/null +++ b/docs/clamp/acm/draw.io/acm-participants.drawio @@ -0,0 +1,462 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/clamp/acm/draw.io/api-gateway-sandbox.drawio b/docs/clamp/acm/draw.io/api-gateway-sandbox.drawio index 78052944..21204385 100644 --- a/docs/clamp/acm/draw.io/api-gateway-sandbox.drawio +++ b/docs/clamp/acm/draw.io/api-gateway-sandbox.drawio @@ -1 +1 @@ - \ No newline at end of file + \ No newline at end of file diff --git a/docs/clamp/acm/draw.io/overview.drawio b/docs/clamp/acm/draw.io/overview.drawio new file mode 100644 index 00000000..290c457d --- /dev/null +++ b/docs/clamp/acm/draw.io/overview.drawio @@ -0,0 +1,529 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/clamp/acm/images/01-acm-overview.png b/docs/clamp/acm/images/01-acm-overview.png index 70f4d435..b32d8520 100644 Binary files a/docs/clamp/acm/images/01-acm-overview.png and b/docs/clamp/acm/images/01-acm-overview.png differ diff --git a/docs/clamp/acm/images/04-overview.png b/docs/clamp/acm/images/04-overview.png index 20f21812..893434f1 100644 Binary files a/docs/clamp/acm/images/04-overview.png and b/docs/clamp/acm/images/04-overview.png differ diff --git a/docs/clamp/acm/images/06-api-gateway-sandbox.png b/docs/clamp/acm/images/06-api-gateway-sandbox.png index 8ebceca7..0c8991db 100644 Binary files a/docs/clamp/acm/images/06-api-gateway-sandbox.png and b/docs/clamp/acm/images/06-api-gateway-sandbox.png differ diff --git a/docs/clamp/acm/images/participants/a1pms-participant.png b/docs/clamp/acm/images/participants/a1pms-participant.png old mode 100755 new mode 100644 index 769cedfe..76cae4c0 Binary files a/docs/clamp/acm/images/participants/a1pms-participant.png and b/docs/clamp/acm/images/participants/a1pms-participant.png differ diff --git a/docs/clamp/acm/images/participants/http-participant.png b/docs/clamp/acm/images/participants/http-participant.png index 0788b942..1e67881a 100644 Binary files a/docs/clamp/acm/images/participants/http-participant.png and b/docs/clamp/acm/images/participants/http-participant.png differ diff --git a/docs/clamp/acm/images/participants/k8s-participant.png b/docs/clamp/acm/images/participants/k8s-participant.png index 55945bc3..4879e318 100644 Binary files a/docs/clamp/acm/images/participants/k8s-participant.png and b/docs/clamp/acm/images/participants/k8s-participant.png differ diff --git a/docs/clamp/acm/images/participants/kserve-participant.png b/docs/clamp/acm/images/participants/kserve-participant.png old mode 100755 new mode 100644 index cc1f6b45..bed09870 Binary files a/docs/clamp/acm/images/participants/kserve-participant.png and b/docs/clamp/acm/images/participants/kserve-participant.png differ diff --git a/docs/clamp/acm/images/participants/participants.png b/docs/clamp/acm/images/participants/participants.png index 2c49c100..d4882456 100644 Binary files a/docs/clamp/acm/images/participants/participants.png and b/docs/clamp/acm/images/participants/participants.png differ