arrowhead-core

This repository includes a docker-compose.yaml file used to start two arrowhead clouds, together with an activemq server, to facilitate intercloud communication.

This repository is based on arrowhead-core, with quite a few modifications as here we are only interested in the creation of the clouds in docker. There is no longer any automatic certification generation when starting up the core systems, however, the certificate generation scripts are still available. Please refer to the repo from which this repo was forked for documentation of certificate generation.

This was developed from the instructions and resources from the Eclipse Arrowhead Framework core-java-spring.

The core systems which are initiated in each cloud: authorization, event handler, gatekeeper, gateway, orchestrator, and service registry. Currently, there is no transport layer security for the connection through the broker.

Prerequisites

The system was developed on the following setup:

• Ubuntu 22.04.5 LTS
• Docker 27.0

The docker compose will probably work on other systems however it has not been tested.

Setup

Clone the repository and create a .env file, by creating it manually or running the following command in the root location of the repository:

touch .env

In the .env file the following arguments can or must be added.

• PASSWORD, this is REQUIRED. This will be the password used for all the certificates. If u want to generate certificates this will set the password for all certificates generated.

Secondly, for development purposes, we set the same DNS names on the host as they are inside the docker containers as consumers/producers are usually developed locally before being deployed inside docker containers. These names need to be the same as the name as the docker containers as that is how docker does communication between containers. This is achieved by editing (on Unix-based systems) /etc/hosts and adding:

127.0.0.1 c1-gatekeeper
127.0.0.1 c1-eventhandler
127.0.0.1 c2-authorization
127.0.0.1 c1-authorization
127.0.0.1 c2-gatekeeper
127.0.0.1 c1-serviceregistry
127.0.0.1 c2-serviceregistry
127.0.0.1 c1-orchestrator
127.0.0.1 c2-gateway
127.0.0.1 c2-orchestrator
127.0.0.1 c2-eventhandler
127.0.0.1 c1-gateway
127.0.0.1 broker-activemq
127.0.0.1 c2-database
127.0.0.1 c1-database
127.0.0.1 172.17.0.1

If not on a Unix-based system, you need to figure out how to do it.

Furthermore, on linux systems in order to access the host from inside a docker container there is a static ip that can be used 172.17.0.1. On other systems you might have to change something in order to be able to access the underlying host from inside a docker container (required for letting the gateway in the consumer cloud being able to return the created tunnel).

You need to generate certificates for every single system in the clouds, but not for the activemq server. This can be done any way you would like. These certs need to be placed correctly in each individual directory in order to cp it correctly into the docker containers on startup. These paths are defined inside the docker-compose.yaml file. For example:

volumes:
   - ./c1/serviceregistry/application.properties:/opt/arrowhead/application.properties
   - ./c1/serviceregistry/certificates:/opt/arrowhead/certificates

i.e. for the cloud1 service registry the certificates have to be in the path of ./c1/serviceregistry/certificates.

If you want to change anything that has to do with any of the core systems please refer to the application.properties files for the corresponding systems.

If you want to set the debug levels for the core systems or change the run script for the individual containers this can be achieved by locating config/CORE_SYSTEM_NAME/run.sh or config/CORE_SYSTEM_NAME/log4j2.xml, where you can change the lines:

<Property name="JDBC_LEVEL">INFO</Property>
<Property name="CONSOLE_FILE_LEVEL">INFO</Property>

to:

<Property name="JDBC_LEVEL">DEBUG</Property>
<Property name="CONSOLE_FILE_LEVEL">DEBUG</Property>

This will change the log level from INFO to DEBUG.

Run

To start the containers, cd to the root folder and run:

docker compose up

After all the containers are running, you need to set up the rules for the intercloud communication. See This and below for this.

Generate certificates for custom systems

There are certificates uploaded in the two folders c1 and c2, however, if you want to start more core systems, or just wants to generate the certs yourself, please refer to the file scripts/certificate-generation-scripts/generate_all_certs.sh. There is also an arrowhead certificate generator but I have not tested it

Testing

Once everything is running and you are ready to test if you can provide a service that can then be consumed you can use: this. I tested it with demo-car and demo-exchange-rate-intercloud.

Remember to set up the intra-cloud rules for demo-car and the inter-cloud authorization rules for demo-exchange-rate-intercloud.