Magnolia Cloud Simulator
Use these instructions to smoke test your bundle before trying it properly in Magnolia Cloud. It ensures that basic contracts between our cloud platform and the deployed bundle are met.
|
When submitting HELPDESK tickets for support related to new cloud deployments, always attach the logs from the simulator to help narrow down issues. Also ensure that the Cloud Compatibility Checks have been executed successfully. We highly recommended including these checks as part of your Continuous Deployment pipelines. |
The current state is only compatible with Magnolia versions > 6.2.1. For older version use the tag compat/pre-6.2.1.
|
Prerequisites
-
You need Docker Engine’s latest stable release.
-
You need Docker Compose’s latest stable release that supports profiles.
-
You must have created your custom cloud bundle.
-
You must have verified/validated your custom cloud bundle.
-
You must have locally deployed your custom cloud WAR file.
-
You must have set up the PostgreSQL databases for your cloud bundle.
Don’t worry, the database setup is handled by the provided Dockerfile.
Instructions
-
Clone the magnolia cloud simulator repository.
git clone https://git.magnolia-cms.com/scm/od/magnolia-cloud-simulator.git -
From your custom cloud bundle project, copy your
.warfile into thedist/folder. -
Copy the following into your project
pom.xmlfile:<build> <pluginManagement> <!-- Copy artifact to dist folder for docker build. See docker/README.md --> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <configuration> <artifactItems> <artifactItem> <groupId>${project.groupId}</groupId> <artifactId>example-cloud-webapp</artifactId> <type>war</type> </artifactItem> </artifactItems> <outputDirectory>dist</outputDirectory> <stripVersion>true</stripVersion> </configuration> </plugin> </plugins> </pluginManagement> </build> -
Run the following to copy the artifact into the
docker/distfolder:mvn clean verify -U dependency:copyEnsure the war file is now in the docker/distfolder. Alternatively, you can copy the war file manually.
Build and run docker compose
Ensure that you have your LICENSE_ID and LICENSE_SECRET to hand in the .env file to use when running docker-compose up.
Alternatively, you can run the command below along with docker-compose up.
|
docker-compose upRun Cloud Compatibility Tests
A successful execution of these Cloud Compatibility Tests is required before uploading the bundle to the cloud.
After launching the instances in docker-compose, run the following commands to test reachability of
the .rest/status endpoint on the public and author instances.
# Build the simulator-check docker image
$ docker build checks -t simulator-check
# Print the help message, for e.g. tweaking the wait times
$ docker run -t simulator-check -h
# check the author instance
$ docker run -t simulator-check --delay 90 --retry 45 http://host.docker.internal:8080/.healthcheck/
$ docker run -t simulator-check --delay 90 --retry 45 http://host.docker.internal:8080/.rest/status
# check the public instance
$ docker run -t simulator-check --delay 90 --retry 45 http://host.docker.internal:8180/.healthcheck/
$ docker run -t simulator-check --delay 90 --retry 45 http://host.docker.internal:8180/.rest/statusOn Linux systems you need to enable the docker engine to communicate with the host:
$ docker run --add-host=host.docker.internal:host-gateway -t simulator-check [...]Refer to the Jenkinsfile for automating these steps as part of your CD job.