iip-ecosphere / platform Goto Github PK

Uptake of artifacts folder and URI prefix

Simple flow, standalone execution, usable with CLI/UI. (see RTSA)
Initial with app-specific service. Extend towards Python platform service.

Problems with Spring Cloud Stream in this respect, already first workaround in place in generation.

AbstractIvmlTest, one test per class -> execute only required in dockerhub container creation

Seems to cause problems for Monika.
May be related to #28

common monitoring / Prometheus

-> ConcurrentModification in server processes, interference of TomCat

AAS repository, package

services.environment -> Starter -> mapService

Prepared with 5600e1d, waiting for @adewes

Ensure that only broker.sh/.bat is used/mentioned (Monika, platform handbook).
Remove VTL calls

Consider as alternative to SelfDeviceAasProvider

Implemented, failed with no disk space on Jenkins.

Demonstrator demand

• generic tracing
• via transport

Commit existing state of Management UI.
Just a reminder ;)

(Integrate) scripts for

• Dockerfile
• Python requirements
• installed dependences YML file
• container descriptor
• system dependencies to be installed -> bash, script creation and execution as part of Dockerfiles
• deployment of containers to registry
• setup information for container registry in configuration (authKey and registry as String [host:port], so far no tokens/certs)
• turn container constants into enum
• take up JAVA8 requirements if e.g., RTSA is installed -> must be in container and mentioned in installedDependencies.yml
• extend scripting for LXC integration
• deploy container descriptor to artifacts folder
• test container descriptor deployment to an absolute artifacts folder (may require EASy copy revision/fix)
• adjust ContainerManager (communicate with Luca Schulz for LXC) to take up Docker image name instead of filename/URL. Requires coordinates of container registry in DockerContainerManager in configuration, similar for LXC
• Adjust ecsRuntime.docker to pull container in addContainer if adequate
• Test in distributed test/evaluation environment #59 (@AhmadAlamoush)
• Document container creation in platform handbook section 6.5

already on the way :)

• only one POM
• build.sh
• README.md
• platform handbook (add to Section 6.3)

impl.impl/impl.model
-> README.md
-> platform handbook (Section 6.4)

Python not updated after change

Broker, also for testing, directly contain their user/pwd, also in the model -> Change to IdentityStore.

In progress, still fighting against KODEX_SETTING file

Generated, programmed, similar to ServiceSelector

Simple flow, standalone execution, usable with CLI/UI.

grpc, dynamic look for /opt/plcnext

Make it accessible to service implementations

Monika: Seems to cause problems

Already ongoing.

AAS identifiers are currently rather pragmatic and initial.

-> 4.4.6 Best Practice for Creating URI Identifiers in Details of AAS V3.0

now gen/broker and broker.sh instead of amqp.sh

• always/per default (performance?)
• on demand/flag in configuration
  -> not in service code (as it is now)

Redirect println to error stream in all python code and use direct writing to sysout in serviceenviroment.

from HM'22, e.g., QR code scanning with (optional) Python fallback
ProcessSupport (PythonSupport in HM'22) is already in services.environment

• IDTA 02003-1-2 Generic Frame for Technical Data for Industrial Equipment in Manufacturing migrated from BaSyx
• IDTA 02004-1-2 Handover Documentation
• IDTA 02011-1-0 Hierarchical Structures enabling Bills of Material
• IDTA 2023-01-24 Draft Submodel PCF
• IDTA 02008-1-1 Time Series Data
• IDTA 02002-1-0 Submodel for Contact Information
• IDTA 02007-1-0 software nameplate

Relevant/Candidates:

• 02006 digital nameplate for industrial equipment

Candidates:

• 02030 platform resources (device on/offboarding?)
• 02020 capability description
• 02019 asset plant management

Java/Spring resource loading currently in services.environment. Right place, spring fix in, currently not used in services.spring.

Monika: Runs in strange spring state

-> ephemeral ports for more stability in CI

• Concept see Docker integration
• Settings as usual
• IVML integration
• Tests

Just a reminder

• Actions + effects on data (affect future configuration model changes)
• How to change port (REST)
• AGPL statement for binary integration
• Statements for requirements R66, R66 a-c
• Nested data structures

Links, text fragments etc. welcome.

AAS, turn Micronmeter JSON structures into values
(migrate UI)

-> example folder
Simple flow, standalone execution, usable with CLI/UI. (see RTSA example)

Currently, arbitrary transitions are allowed

Delayed service mapping (for all services)

Currently, arbitrary transitions are allowed

... still strange