Cosmetic changes.
diff --git a/content/en_index.php b/content/en_index.php
index 47da9d2..fd6a679 100644
--- a/content/en_index.php
+++ b/content/en_index.php
@@ -98,1289 +98,11 @@
</td>
<td class="content">
If you don’t have <code>mvn</code> installed, please <a
- href="https://maven.apache.org/install.html">read these instructions</a>.
+ href="https://maven.apache.org/install.html" target="_blank">read these instructions</a>.
</td>
</tr>
</table>
- <!--
- <h2 id="getting-started"><a class="anchor" href="#getting-started"></a>3. Getting Started</h2>
- <p>When Jemo starts, it iterates over supported CSP’s and attempts to find credentials for a user to run with.
- We call this the <code>jemo user</code>. These credentials can be found either as JVM properties or on the
- filesystem.
- When credentials are found for a CSP, Jemo validates them and if valid it checks if
- the user has the necessary permissions to run the server. If the permission validation succeeds,
- Jemo carries on with initialisation, otherwise it attempts to find credentials for the next supported CSP.
- If no user with valid credentials and permissions is found for any CSP, Jemo asks you to drive the setup process
- by printing the following log:</p>
-
- <pre>
- GSM is not setup yet. Please click on the following link to provide configuration: <a
- href="https://localhost:443/jemo/setup/" class="bare"
- target="_blank">https://localhost:443/jemo/setup/</a>
- </pre>
-
- <p>Browse to this link and select the CSP you want to use.
- Jemo, offers you 3 options:</p>
-
- <div class="olist arabic">
- <ol class="arabic">
- <li>
- <p>Login with the jemo user credentials (useful when the jemo user has been created before).</p>
- </li>
- <li>
- <p>Ask Jemo to install the required CSP resources including the jemo user.</p>
- </li>
- <li>
- <p>Download the terraform templates to run them locally (useful when you want to modify the
- templates).</p>
- </li>
- </ol>
- </div>
-
-
- <h3 id="aws"><a class="anchor" href="#aws"></a>3.1. AWS</h3>
- <h4 id="login-with-the-jemo-user-credentials"><a class="anchor"
- href="#login-with-the-jemo-user-credentials"></a>3.1.1. Login
- with the jemo user credentials</h4>
-
- <p>You will be asked to enter <code>aws_access_key_id</code> and <code>aws_access_key_id</code> and select
- the AWS region,
- the jemo user is created in. The dropdown menu displays all the available AWS regions as for now.
- If the region you are looking for is missing, please type its code in the provided text input.</p>
-
- <pre class="content">Every time you provide credentials, Jemo validates them and if valid,
- it writes them on your filesystem on <code>~/.aws/credentials</code> file by overwritting existing content.
- Keep a copy of this file, if there are credentials you want to preserve.
- </pre>
-
- <p>If the credentials are valid, then Jemo checks if the following permissions are given to the <code>jemo
- user</code>:</p>
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">
- // DynamoDB actions
- "dynamodb:BatchWriteItem",
- "dynamodb:CreateTable",
- "dynamodb:DeleteTable",
- "dynamodb:ListTables",
- "dynamodb:DescribeTable",
- "dynamodb:Scan",
- "dynamodb:Query",
- "dynamodb:GetItem",
-
- // S3 actions
- "s3:AbortMultipartUpload",
- "s3:CreateBucket",
- "s3:DeleteObject",
- "s3:GetObject",
- "s3:ListBucketMultipartUploads",
- "s3:ListBucket",
- "s3:PutObject",
-
- // SQS actions
- "sqs:CreateQueue",
- "sqs:DeleteMessage",
- "sqs:DeleteQueue",
- "sqs:GetQueueUrl",
- "sqs:ListQueues",
- "sqs:SendMessage",
- "sqs:SetQueueAttributes",
-
- // AmazonSQSAsync
- "sqs:ReceiveMessage",
-
- // AWSLogsAsync
- "logs:CreateLogGroup",
- "logs:CreateLogStream",
- "logs:DescribeLogStreams",
- "logs:PutLogEvents",
-
- // EC2
- "ec2:DescribeTags",
- "ec2:DescribeVpcs",
-
- // IAM
- "iam:GetUser",
- "iam:SimulatePrincipalPolicy",
- "iam:GetRole",
- "iam:ListPolicies"</code>
- </pre>
-
- <p>In case of missing permissions, Jemo displays the missing permissions.
- You have to add them, e.g. by browsing to the AWS console and then come back and try again to login.
-
- A genuine case for this error is when you have created the <code>jemo user</code> or the <code>jemo
- policy</code>
- yourself.
- Otherwise, the <code>jemo user</code> created by Jemo will always pass this validation.
- If you created the user with Jemo and get this error,
- it means you provided the credentials of an existing AWS user different than the <code>jemo user</code>.
- Please review the credentials you entered and retry to login.
- </p>
-
- <p>If the permissions are valid you will be forwarded to the next setup stage
- which is to select <code>Jemo parameter sets</code>.</p>
-
- <h4 id="jemo-installation"><a class="anchor" href="#jemo-installation"></a>3.1.2. Jemo Installation</h4>
- <p>You will be asked to provide credentials for a user with administrator credentials,
- we call this the <code>terraform user</code>.
- Jemo creates terraform templates to create the user and other resources.
- The terraform user is then used to run these terraform templates.</p>
-
- <pre class="content">
- If you don’t have credentials for the terraform user, you can create
- a user with "Programmatic access" and attach the "AdministratorAccess" policy.
- </pre>
-
- <p>Jemo generates terraform templates on your filesystem under the directory where
- Jemo runs, under the <code>aws/install/</code> directory. Then it runs terraform:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init -no-color -var-file=aws/install/terraform.tfvars aws/install
- > terraform plan -no-color -var-file=aws/install/terraform.tfvars aws/install
- > terraform apply -no-color -auto-approve -var-file=aws/install/terraform.tfvars aws/install</code>
- </pre>
-
- <pre class="content">
- If the <code>terraform</code> command is not found on your path, Jemo notifies you
- with <a href="https://learn.hashicorp.com/terraform/getting-started/install.html"
- target="_blank" rel="noopener">Terraform Installation Instructions</a>.
- </pre>
-
- <p>Besides the <code>jemo user</code>, a user group <code>jemo-group</code> and a policy
- <code>jemo-policy</code> are created.
- The <code>jemo-group</code> contains <code>jemo user</code> and is assigned to <code>jemo-policy</code>
- which declares all the permissions
- needed by Jemo to run.</p>
-
- <p>The UI notifies you with all the terraform created resources and printed outputs.
- The Jemo user credentials (<code>jemo_user_access_key_id</code> and
- <code>jemo_user_secret_access_key</code>)
- are displayed on the <code>outputs</code> section. Copy these two values on your notes for future
- reference.</p>
-
- <p>Behind the scenes, Jemo logs in with the <code>jemo user</code> and forwards you
- to the next setup stage which is to select <code>Jemo parameter sets</code>.</p>
-
- <h4 id="download-the-terraform-templates"><a class="anchor" href="#download-the-terraform-templates"></a>3.1.3.
- Download the Terraform Templates</h4>
- <p>Uppon clicking on the <code>DOWNLOAD</code> button, the <code>install.zip</code> fill
- will be
- downloaded. Run:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> unzip install.zip
- > cd install</code></pre>
-
- <p>You are required to provide values for the terraform user credentials.
- Create a file name with <code>terraform.tfvars</code> and set:
- </p>
- <pre>
- terraform_user_access_key="..."
- terraform_user_secret_key="..."
- region="..."</code>
- </pre>
-
- <p>Then run terraform with:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init
- > terraform plan
- > terraform apply</code></pre>
-
- <p>Enter <code>yes</code> when terraform asks you if you agree to create the proposed resources.
- After a while terraform will finish and print this:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">Apply complete! Resources: 6 added, 0 changed, 0 destroyed.
-
- Outputs:
-
- jemo_user_access_key_id = ********************
- jemo_user_secret_access_key = ****************************************</code></pre>
-
- <p>Besides the <code>jemo user</code>, a user group <code>jemo-group</code> and a policy
- <code>jemo-policy</code> are created.
- The <code>jemo-group</code> contains <code>jemo user</code> and is assigned to <code>jemo-policy</code>
- which declares all the permissions
- needed by Jemo to run.</p>
- <p>Then you can use the newly created <code>jemo user</code> credentials to login.
- Click the <code>LOGIN</code> button.</p>
-
-
- <h3 id="azure"><a class="anchor" href="#azure"></a>3.2. Azure</h3>
- <h4 id="login-with-the-jemo-user-credentials-2"><a class="anchor"
- href="#login-with-the-jemo-user-credentials-2"></a>3.2.1. Login
- with the jemo user credentials</h4>
- <p>You will be asked to enter <code>tenant_id</code>, <code>client_id</code>, <code>client_secret</code> and select
- the Azure region,
- the jemo user is created in. Notice that region code dropdown menu includes only those
- <a href="https://docs.microsoft.com/en-us/azure/aks/container-service-quotas" target="_blank">Azure regions that
- support the Azure Kubernetes Service (AKS)</a>
- as for now. If the region you are looking for is missing, please type its code in the provided text input,
- but make sure it supports AKS.</p>
-
- <pre>
- Every time you provide credentials, Jemo validates them and if valid,
- it writes them on your filesystem on <code>~/.azure/credentials</code> file.
- Keep a copy of this file, if there are credentials you want to preserve.
- </pre>
-
- <p>If the credentials are valid, then Jemo checks if the following permissions are given to the <code>jemo
- user</code>:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">
- "Microsoft.Resources/subscriptions/read",
- "Microsoft.Storage/storageAccounts/listKeys/action",
- "Microsoft.EventHub/namespaces/eventhubs/write",
- "Microsoft.EventHub/namespaces/AuthorizationRules/listKeys/action",
- "Microsoft.DocumentDB/databaseAccounts/listKeys/action",
- "Microsoft.DocumentDB/databaseAccounts/read",
- "Microsoft.OperationalInsights/workspaces/read",
- "Microsoft.Operationalinsights/workspaces/sharedkeys/read",
- "Microsoft.Authorization/roleAssignments/read",
- "Microsoft.Authorization/roleDefinitions/read",
- "Microsoft.Network/virtualNetworks/read",
- "Microsoft.ManagedIdentity/userAssignedIdentities/read",
- "Microsoft.KeyVault/vaults/read",
- "Microsoft.KeyVault/vaults/secrets/read",
- "Microsoft.KeyVault/vaults/secrets/write"</code></pre>
-
- <p>In case of missing permissions, Jemo displays the missing permissions.
- You have to add them, e.g. by browsing to the Azure console and then come back and try again to login.
-
- A genuine case for this error is when you have created the <code>jemo user</code> yourself.
- Otherwise, the <code>jemo user</code> created by Jemo will always pass this validation.
- If you created the user with Jemo and get this error,
- it means you provided the credentials of an existing Azure user different than the <code>jemo user</code>.
- Please review the credentials you entered and retry to login.
- </p>
-
- <p>If the permissions are valid you will be forwarded to the next setup stage
- which is to select <code>Jemo parameter sets</code>.</p>
-
- <h4 id="jemo-installation-2"><a class="anchor" href="#jemo-installation-2"></a>3.2.2. Jemo Installation</h4>
- <p>You will be asked to provide credentials for a user with administrator credentials,
- we call this the <code>terraform user</code>.
- Jemo creates terraform templates to create the user and other resources.
- The terraform user is then used to run these terraform templates.</p>
-
- <p>If you don’t have credentials for the terraform user, you can create
- a user with permissions to both <code>Read and write all applications</code> and
- <code>Sign in and read user profile</code> within the Windows Azure Active Directory API.
- Please install the <a href="https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest"
- target="_blank">Azure
- cli</a> and run:</p>
-
- <pre class="highlightjs highlight">> az ad sp create-for-rbac -n "terraform-user" --role Owner
- > az ad app permission add --id http://terraform-user --api 00000002-0000-0000-c000-000000000000
- --api-permissions 1cda74f2-2616-4834-b122-5cb1b07f8a59=Role
- 311a71cc-e848-46a1-bdf8-97ff7156d8e6=Scope
- </pre>
- Then, open the console and navigate to:
- <pre>
- <code>Azure Active Directory</code> → <code>App registrations (Preview)</code> →
- <code>terraform-user</code> → <code>API permissions</code> →
- <code>Grant admin consent for Default Directory</code> → <code>Yes</code></pre>
-
- <p>If the <code>Grant admin consent for Default Directory</code> button is disabled
- please ask your Azure administrator to do this for you.</p>
-
- <p>Jemo generates terraform templates on your filesystem under the directory where
- Jemo runs, under the <code>azure/install</code> directory. Then it runs terraform:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init -no-color -var-file=azure/install/terraform.tfvars azure/install
- > terraform plan -no-color -var-file=azure/install/terraform.tfvars azure/install
- > terraform apply -no-color -auto-approve -var-file=azure/install/terraform.tfvars azure/install</code></pre>
-
- <pre>
- If the <code>terraform</code> command is not found on your path, Jemo notifies you
- with <a href="https://learn.hashicorp.com/terraform/getting-started/install.html" target="_blank">Terraform Installation Instructions</a>.</pre>
-
- <p>Besides the <code>jemo user</code> (in the form of a service principal), many other resources are created.</p>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Created resources</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 75%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>role</code></p></td>
- <td class="tableblock halign-left valign-top">Declares permissions for all the needed actions and is
- assigned to the <code>jemo user</code></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>resource group</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure resource group that includes
- all the resources</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>storage account</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure storage account to be used by
- Jemo</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>cosoms DB account</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure Cosoms DB account to be used
- by Jemo</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eventhub namespace</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure Eventhub namespace to be used
- by Jemo</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>log analytics workspace</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure log workspace where Jemo
- redirects its logs</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>key vault</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure key vault to securely store
- the secrets needed by Jemo at runtime</p></td>
- </tr>
- </tbody>
- </table>
-
- <br/>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Key vault secrets</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 75%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>clientId</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user client_id</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>clientSecret</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user client_secret</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>tenantId</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user tenant_id</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>encryptionKey</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">A random string of 16 characters used by
- Jemo to encrypt modules</p></td>
- </tr>
- </tbody>
- </table>
-
- <p>The UI notifies you with all the terraform created resources and printed outputs.
- The Jemo user credentials (<code>jemo_user_client_id</code> and <code>terraform_user_client_secret</code>)
- are displayed on the <code>outputs</code> section. Copy these two values on your notes for future reference.
- </p>
-
- <p>Behind the scenes, Jemo logs in with the <code>jemo user</code> and forwards you
- to the next setup stage which is to select <code>Jemo parameter sets</code>.</p>
-
- <h4 id="download-the-terraform-templates-2"><a class="anchor" href="#download-the-terraform-templates-2"></a>3.2.3.
- Download the Terraform Templates</h4>
-
- <p>Uppon clicking on the <code>DOWNLOAD</code> button, the <code>install.zip</code> file
- will be
- downloaded. Run:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> unzip install.zip
- > cd install</code></pre>
-
- <p>You are required to provide values for the terraform user credentials. Create a file named with <code>terraform.tfvars</code>
- and set:</p>
- <pre class="highlightjs highlight">
- terraform_user_client_id="..."
- terraform_user_client_secret="..."
- tenant_id="..."
- subscription_id="..."
- region="..."
- log-workspace-location="..."</pre>
-
- <p>Then run terraform with:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init
- > terraform plan
- > terraform apply</code></pre>
-
- <pre class="content">
- To install <code>terraform</code> please read the <a
- href="https://learn.hashicorp.com/terraform/getting-started/install.html" target="_blank"
- rel="noopener">Terraform Installation Instructions</a>.</pre>
-
- <p>Enter <code>yes</code> when terraform asks you if you agree to create the proposed resources.
- After a while terraform will finish and print this:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">Apply complete! Resources: 19 added, 0 changed, 0 destroyed.
-
- Outputs:
-
- eclipse.jemo.azure.db = jemocdba-9wxaszuresvxl9ar0
- eclipse.jemo.azure.eventhub = jemoehn-9wxaszuresvxl9ar0
- eclipse.jemo.azure.keyvault = jemokv-9wxaszuresvxl9ar0
- eclipse.jemo.azure.log-workspace = jemo-log-workspace-9wxaszuresvxl9ar0
- eclipse.jemo.azure.resourcegroup = jemorg
- eclipse.jemo.azure.storage = jemosa9wxaszuresvxl9ar0
- jemo_user_client_id = ************************************
- jemo_user_client_secret = ********************************</code></pre>
-
- <p>Besides the <code>jemo user</code> (in the form of a service principal), many other resources are
- created.
- </p>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Created resources</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 75%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>role</p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Declares permissions for all the
- needed
- actions and is assigned to the <code>jemo user</code></p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>resource group</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure resource group that
- includes
- all the resources</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>storage account</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure storage account to be used
- by
- Jemo</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>cosoms DB account</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure Cosoms DB account to be
- used
- by Jemo</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eventhub namespace</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure Eventhub namespace to be
- used
- by Jemo</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>log analytics workspace</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure log workspace where Jemo
- redirects its logs</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>key vault</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Azure key vault to securely
- store
- the secrets needed by Jemo at runtime</p></td>
- </tr>
- </tbody>
- </table>
-
- <br/>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Key vault secrets</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 75%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>clientId</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user client_id</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>clientSecret</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user client_secret</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>tenantId</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user tenant_id</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>encryptionKey</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">A random string of 16 characters
- used by
- Jemo to encrypt modules</p></td>
- </tr>
- </tbody>
- </table>
-
- <p>You may notice that many of the created resources have names with the same randomly created suffix,
- e.g. the Azure Cosmos db account name is <code>jemocdba-9wxaszuresvxl9ar0</code>.
- Many azure resources need to have a globally unique name, because they are accessible via a url, e.g.
- <a href="https://jemocdba-9wxaszuresvxl9ar0.documents.azure.com" target="_blank">https://jemocdba-9wxaszuresvxl9ar0.documents.azure.com</a>.
- Jemo uses a randomly generated suffix to avoid
- collisions between people who use Jemo concurrently.</p>
-
- <p>Jemo asks you to provide the names of the created resources, as it is unaware of them.
- Just copy paste the values from the terraform outputs and click on the <code>SUBMIT</code> button.</p>
- <p>Then you can use the newly created <code>jemo user</code> credentials to login.
- Click the <code>LOGIN</code> button.</p>
-
-
- <h2 id="jemo-parameters"><a class="anchor" href="#jemo-parameters"></a>4. Jemo Parameters</h2>
- <p>Jemo functionality depends on global parameters that are the same for all CSP runtime implementations.
- A group of values for these parameters is called a <code>parameter set</code>.
- You can create multiple parameter sets and select to run Jemo instances
- with different parameter sets concurrently.</p>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Jemo parameters</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 75%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.location</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The location name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.location.type</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">One of [<code>CLOUD</code>, <code>ON-PROMISE</code>]
- </p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.whitelist</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">A list of module ids to allow</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.blacklist</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">A list of module ids to prevent</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.queue.polltime</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The queue poll interval</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.log.local</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Switch between local and cloud
- logging</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.log.output</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">If local logging is enabled, this
- parameter controls the log output (e.g. STDOUT or a local file)</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.log.level</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The log level</p></td>
- </tr>
- </tbody>
- </table>
-
- <p>Once a parameter set is created, the following actions take place:</p>
-
- <div class="olist arabic">
- <ol class="arabic">
- <li>
- <p>the local running Jemo instance updates the parameter values (it starts with default values)</p>
- </li>
- <li>
- <p>the parameter set is stored on the cloud on the blob storage of the selected CSP</p>
- </li>
- <li>
- <p>the name if the parameter set is stored on your local file system, on
- it is stored on the file system and on the cloud on the <code>~/jemo.properties</code> file.</p>
- </li>
- </ol>
- </div>
-
- <p>The first ensures that you get on running Jemo in developer mode with the selected parameter values.
- The second persists the parameter set so that any Jemo (local or cloud) instance
- can pick an existing parameter set to run with.
- The third, enables you when running in development mode to stop jvm and then restart with no disruption,
- Jemo will pick the parameter set name stored on the <code>~/jemo.properties</code> file and search on the
- CSP blob storage service to retrieve it.</p>
- <p>Notice that you can browse back and create multiple parameter sets if you wish.</p>
-
-
- <h2 id="production-environment-configuration"><a class="anchor" href="#production-environment-configuration"></a>5.
- Production Environment Configuration</h2>
-
- <p>After one or more parameter sets are created, Jemo offers you the ability to configure a production environment.
- With this, we mean the creation of a Kubernetes cluster and worker nodes running Jemo pods.</p>
-
- <h3 id="aws-2"><a class="anchor" href="#aws-2"></a>5.1. AWS</h3>
-
- <p>Jemo uses the <a href="https://aws.amazon.com/eks/" target="_blank">AWS EKS service</a> to
- create a cluster.
- Based on parameters provided by the user, Jemo generates terraform templates that drive the generation of
- AWS resources. The parameters are organized in 3 major groups.</p>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Cluster master parameters</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 25%;">
- <col style="width: 50%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Default Value</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>cluster-name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-cluster</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The cluster name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>cluster-role-name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-cluster-role</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The cluster role name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>cluster-security-group-name</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-cluster-security-group</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The cluster security group name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock">
- <code>cluster-security-group-name-tag</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-cluster</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The cluster security group name tag</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>workstation-external-cidr</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Your current IP</p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Comma separated list of local
- workstation IPs allowed to access the cluster</p></td>
- </tr>
- </tbody>
- </table>
-
- <br/>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Cluster nodes parameters</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 25%;">
- <col style="width: 50%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Default Value</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>worker-node-role-name</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-node-role</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The worker nodes role name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock">
- <code>worker-node-instance-profile-name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-node-instance-profile</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The worker nodes instance profile
- name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock">
- <code>worker-node-security-group-name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-node-security-group</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The worker nodes security group name</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>launch-conf-instance-type</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>m4.large</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The AWS launch configuration instance
- type</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>launch-conf-name-prefix</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The AWS launch configuration name
- prefix</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>autoscaling-group-name</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The AWS autoscaling group name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock">
- <code>autoscaling-group-desired-capacity</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>2</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The AWS autoscaling group capacity</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>autoscaling-group-max-size</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>2</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The AWS autoscaling group max size</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>autoscaling-group-min-size</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>1</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The AWS autoscaling group min size</p>
- </td>
- </tr>
- </tbody>
- </table>
-
- <p>Jemo, displays a dropdown menu with all the existing user managed policies.
- If there is one with the name <code>jemo-policy</code>, it is pre selected.
- If you have selected a different name for the policy during the installation phase,
- please find the name you selected.
- Notice that uppon the selection of a policy in the dropdown menu jemo validates
- the permissions declared by the policy to check if they cover the persmissions
- needed to run Jemo. If not the user is notified by a pop-up dialog to either add the
- missing permissions or select another policy.</p>
-
- <p>By default, Jemo creates a new network to run the cluster
- and the related paremeters are shown in <a href="#aws_network_params">Network parameters</a>.
- Alternatively, one can select to run the cluster on an existing network.
- To do so click on the <code>OR SELECT EXISTING NETWORK</code> button,
- the network parameters dissapear and a dropdown menu with all the exisitng network names
- is displayed. Click on <code>OR SELECT NEW NETWORK</code> to return to the previous state.</p>
-
- <table id="aws_network_params" class="tableblock frame-all grid-all stretch">
- <caption class="title">Network parameters</caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 25%;">
- <col style="width: 50%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Default Value</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>vpc-name-tag</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-vpc</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The cluster VPC name tag</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>subnet-name-tag</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-subnet</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The subnet name tag</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>internet-gateway-name-tag</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-internet-gateway</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The internet gateway name tag</p></td>
- </tr>
- </tbody>
- </table>
- <div class="paragraph">
- <p>Finally, you can optionally select how many containers you want to run with each parameter set.
- For instance, if there are 2 parameter sets and 5 Jemo containers
- (<code>autoscaling-group-desired-capacity</code>),
- we may select to run 3 containers with the first parameter set, 1 container with the
- second parameter set and 1 with no parameter set (will run with default values).</p>
- </div>
-
-
- <h4 id="create-the-cluster"><a class="anchor" href="#create-the-cluster"></a>5.1.1. Create the Cluster</h4>
- <p>Jemo generates the terraform templates to create the cluster under the <code>azure/cluster</code> directory.
- Then, it runs the terraform command with the terraform user.
- Jemo asks you to enter its credentials and if they are valid, it runs:</p>
-
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> terraform init -no-color -var-file=aws/cluster/terraform.tfvars aws/cluster
- > terraform plan -no-color -var-file=aws/cluster/terraform.tfvars aws/cluster
- > terraform apply -no-color -auto-approve -var-file=aws/cluster/terraform.tfvars aws/cluster</code></pre>
-
- <p>After the cluster and worker nodes are created, Jemo has to deploy the Jemo pods to
- worker nodes. On the background Jemo uses the Kubernetes java client to deploy the pods
- (as a stetefulset) and the ingress loadbalancer service that routes requests to the running
- Jemo containers.:</p>
-
- <p>The whole process can take up to 15 minutes. The Jemo UI monitors the progress.</p>
-
- <p>In the end, the UI notifies with the terraform crested resources and outputs,
- as well as with the URL where you can access Jemo.
- This is the external URL of the ingress load balancer.</p>
-
- <p>At this point, you can close your browser, the setup is complete.</p>
-
-
- <h4 id="download-the-terraform-templates-3"><a class="anchor" href="#download-the-terraform-templates-3"></a>5.1.2.
- Download the Terraform templates</h4>
- <p>Uppon clicking on the <code>DOWNLOAD</code> button, the <code>cluster.zip</code> fill will be
- downloaded. Run:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> unzip cluster.zip
- > cd cluster</code></pre>
-
- <p>Open the <code>terraform.tfvars</code> to review existing parameter values and
- append it with values for the terraform user credentials.</p>
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">terraform_user_access_key="..."
- terraform_user_secret_key="..."</code></pre>
-
- <p>Then run terraform with:</p>
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init
- > terraform plan
- > terraform apply</code></pre>
-
- <p>Enter <code>yes</code> when terraform asks you if you agree to create the proposed resources.
- After a while terraform will finish and print this:</p>
-
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">Apply complete! Resources: 26 added, 0 changed, 0 destroyed.
-
- Outputs:
-
- aws_eks_cluster_endpoint = ...
- aws_eks_worker_node_role_arn = ...
- config_map_aws_auth = ...
- kubeconfig = ...</code></pre>
-
- <p>At this point, the cluster and worker nodes are created.
- Jemo has to deploy the Jemo pods to worker nodes.
- In order to access the cluster the
- <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html" target="_blank">AWS CLI</a>
- and <a href="https://docs.aws.amazon.com/eks/latest/userguide/install-aws-iam-authenticator.html"
- target="_blank">aws-iam-authenticator</a>
- tool should be installed and accessible on your path.</p>
-
- <pre>
- Since the cluster was created with the terraform user,
- kubectl needs to use the terraform user credentials.
- Make sure the <code>~/.aws/credentials</code> file has the terraform user credentials.
- </pre>
-
- <p>Run the following commands:</p>
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> aws eks update-kubeconfig --name jemo-cluster
- > terraform output config_map_aws_auth > config-map.yaml
- > kubectl apply -f config-map.yaml
- > kubectl create -f kubernetes/jemo-statefulset.yaml
- > kubectl rollout status statefulset jemo
- > kubectl create -f kubernetes/jemo-svc.yaml</code></pre>
-
- <p>Then run the following command to find the URL where you can access Jemo:</p>
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> kubectl get svc jemo -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}'</code></pre>
- <p>This is the external URL of the ingress load balancer that route requests to the running
- Jemo containers. You may need to wait 1-2 minutes until you can access this URL.</p>
- <p>At this point, you can close your browser, the setup is complete.</p>
-
- <h5 id="delete-the-cluster"><a class="anchor" href="#delete-the-cluster"></a>5.1.2.1. Delete the cluster</h5>
- <p>To delete the cluster, run:</p>
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> kubectl delete statefulset jemo
- > kubectl delete svc jemo
- > kubectl delete -n kube-system configmap aws-auth
- > terraform destroy</code></pre>
- <p>And enter <code>yes</code> when terraform asks you if you agree to destroy the displayed resources.</p>
-
-
- <h3 id="azure-2"><a class="anchor" href="#azure-2"></a>5.2. Azure</h3>
- <p>Jemo uses the <a href="https://azure.microsoft.com/en-gb/services/kubernetes-service/" target="_blank">Azure AKS
- service</a> to create a cluster.
- Based on parameters provided by the user, Jemo generates terraform templates that drive the generation of Azure
- resources. The parameters are organized in 3 major groups.</p>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Cluster master parameters</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 25%;">
- <col style="width: 50%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Default Value</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>resource_group_name</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemorg</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The resource group name the cluster
- resources will be created in.
- Notice that Azure creates worker nodes in a separate namespace created automatically</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo_user_client_id</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user client id you logged in
- with</p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Jemo user client id</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo_user_client_secret</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The jemo user client secret you logged
- in with</p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Jemo user client secret</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>key_vault_name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The name of the key vault you created in
- the installation phase</p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The Jemo key vault name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-cluster</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The name of the AKS cluster to
- create</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_dns_prefix</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Optional DNS prefix to use with hosted
- Kubernetes API server FQDN</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_service_cidr</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>10.0.0.0/16</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">A CIDR notation IP range from which to
- assign service cluster IPs</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>vm_user_name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The user name for the VM</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>public_ssh_key_path</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>~/.ssh/id_rsa.pub</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The public key path for SSH</p></td>
- </tr>
- </tbody>
- </table>
-
- <br/>
-
- <table class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Cluster nodes parameters</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 25%;">
- <col style="width: 50%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Default Value</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_agent_os_disk_size</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>30</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Disk size (in GB) to provision for each
- of the agent pool nodes</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_agent_count</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>2</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The number of agent nodes for the
- cluster. Coincides with the number of Jemo containers.</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_agent_vm_size</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>Standard_D1_v2</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The size of the Virtual Machine</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_dns_service_ip</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>10.0.0.10</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Containers DNS server IP address</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_docker_bridge_cidr</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>172.17.0.1/16</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">A CIDR notation IP for Docker bridge</p>
- </td>
- </tr>
- </tbody>
- </table>
-
- <p>By default, Jemo creates a new network to run the cluster
- and the related paremeters are shown in <a href="#azure_network_params">Network parameters</a>.
- Alternatively, one can select to run the cluster on an existing network.
- To do so click on the <code>OR SELECT EXISTING NETWORK</code> button,
- the network parameters dissapear and a dropdown menu with all the exisitng network names
- is displayed. Click on <code>OR SELECT NEW NETWORK</code> to return to the previous state.</p>
-
- <table id="azure_network_params" class="tableblock frame-all grid-all stretch">
- <caption class="title"><strong>Network parameters</strong></caption>
- <colgroup>
- <col style="width: 25%;">
- <col style="width: 25%;">
- <col style="width: 50%;">
- </colgroup>
- <thead>
- <tr>
- <th class="tableblock halign-left valign-top">Name</th>
- <th class="tableblock halign-left valign-top">Default Value</th>
- <th class="tableblock halign-left valign-top">Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>virtual_network_name</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-virtual-network</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Virtual network name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock">
- <code>virtual_network_address_prefix</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>15.0.0.0/8</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Containers DNS server IP address</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_subnet_name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-subnet</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">AKS Subnet Name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>aks_subnet_address_prefix</code>
- </p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>15.0.0.0/16</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Containers DNS server IP address</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>app_gateway_subnet_name</code></p>
- </td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>appgwsubnet</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">The App Gateway Subnet Name</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock">
- <code>app_gateway_subnet_address_prefix</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>15.1.0.0/16</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Containers DNS server IP address</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>app_gateway_name</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>jemo-app-gateway</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Name of the Application Gateway</p></td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>app_gateway_sku</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>Standard_v2</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Name of the Application Gateway SKU</p>
- </td>
- </tr>
- <tr>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>app_gateway_tier</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock"><code>Standard_v2</code></p></td>
- <td class="tableblock halign-left valign-top"><p class="tableblock">Tier of the Application Gateway SKU</p>
- </td>
- </tr>
- </tbody>
- </table>
-
- <p>Finally, you can optionally select how many containers you want to run with each parameter set.
- For instance if there are 2 parameter sets and 5 Jemo containers (<code>aks_agent_count</code>),
- we may select to run 3 containers with the first parameter set, 1 container with the
- second parameter set and 1 with no parameter set (will run with default values).</p>
-
-
- <h4 id="create-the-cluster-2"><a class="anchor" href="#create-the-cluster-2"></a>5.2.1. Create the Cluster</h4>
- <p>Jemo generates the terraform templates to create the cluster and runs the terraform
- command with the terraform user. Jemo asks you to enter its credentials and if
- they are valid, it runs:</p>
-
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> terraform init -no-color -var-file=azure/cluster/terraform.tfvars azure/cluster
- > terraform plan -no-color -var-file=azure/cluster/terraform.tfvars azure/cluster
- > terraform apply -no-color -auto-approve -var-file=azure/cluster/terraform.tfvars azure/cluster</code></pre>
- <p>After the cluster and worker nodes are created, Jemo has to deploy the Jemo pods to
- worker nodes. In addition, it deploys some other pods that are needed to pass the
- keyvault secrets created in the installation phase to the Jemo pods.
- On the background Jemo runs:</p>
-
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> echo "$(terraform output kube_config)" > ~/.kube/config
- > kubectl create -f https://raw.githubusercontent.com/Azure/kubernetes-keyvault-flexvol/master/deployment/kv-flexvol-installer.yaml
- > kubectl create secret generic kvcreds --from-literal clientid='JEMO_USER_CLIENT_ID' --from-literal clientsecret='JEMO_USER_CLIENT_SECRET' --type=azure/kv
- > kubectl create -f kubernetes/jemo-statefulset.yaml
- > kubectl create -f kubernetes/jemo-svc.yaml
- > kubectl rollout status statefulset jemo</code></pre>
-
- <pre>
- If the <code>kubectl</code> command is not found on your path, Jemo notifies you
- with <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl"
- target="_blank">Kubectl Installation Instructions</a>.</pre>
- <p>The whole process can take up to 15 minutes. The Jemo UI monitors the progress.</p>
- <p>In the end, the UI notifies with the terraform crested resources and outputs,
- as well as with the URL where you can access Jemo.
- This is the external URL of the ingress load balancer that route requests to the running
- Jemo containers.</p>
- <p>At this point, you can close your browser, the setup is complete.</p>
-
-
- <h4 id="download-the-terraform-templates-4"><a class="anchor" href="#download-the-terraform-templates-4"></a>5.2.2.
- Download the Terraform templates</h4>
- <p>Uppon clicking on the <code>DOWNLOAD</code> button, the <code>cluster.zip</code> fill will be
- downloaded. Run:</p>
-
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> unzip cluster.zip
- > cd cluster</code></pre>
- <p>Open the <code>terraform.tfvars</code> to review existing parameter values and
- append it with values for the terraform user credentials.</p>
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">terraform_user_client_id="..."
- terraform_user_client_secret="..."</code></pre>
- <p>Then run terraform with:</p>
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init
- > terraform plan
- > terraform apply</code></pre>
- <p>Enter <code>yes</code> when terraform asks you if you agree to create the proposed resources.
- After a while terraform will finish and print this:</p>
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">Apply complete! Resources: 11 added, 0 changed, 0 destroyed.
-
- Outputs:
-
- client_certificate = ...
- client_key = ...
- cluster_ca_certificate = ...
- cluster_password = ...
- cluster_username = ...
- host = ...
- jemo-identity-client_id = ...
- jemo-identity-id = ...
- jemo-identity-principal_id = ...
- kube_config = ...</code></pre>
-
- <p>At this point, the cluster and worker nodes are created.
- Jemo has to deploy the Jemo pods to worker nodes.
- In addition, it deploys some other pods that are needed to pass the
- keyvault secrets created in the installation phase to the Jemo pods.</p>
-
- <p>Run the following commands:</p>
-
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> echo "$(terraform output kube_config)" > ~/.kube/config
- > kubectl create -f https://raw.githubusercontent.com/Azure/kubernetes-keyvault-flexvol/master/deployment/kv-flexvol-installer.yaml
- > kubectl create secret generic kvcreds --from-literal clientid='JEMO_USER_CLIENT_ID' --from-literal clientsecret='JEMO_USER_CLIENT_SECRET' --type=azure/kv
- > kubectl create -f kubernetes/jemo-statefulset.yaml
- > kubectl create -f kubernetes/jemo-svc.yaml
- > kubectl rollout status statefulset jemo</code></pre>
-
- <p>The last command waits until the number of Jemo pods you selected is ready.
- When it is finished, run the following command to find the URL where you can access Jemo:</p>
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> kubectl get svc jemo -o=jsonpath='{.status.loadBalancer.ingress[0].ip}'</code></pre>
-
- <p>This is the external URL of the ingress load balancer that route requests to the running
- Jemo containers.</p>
- <p>At this point, you can close your browser, the setup is complete.</p>
-
-
- <h5 id="delete-the-cluster-2"><a class="anchor" href="#delete-the-cluster-2"></a>5.2.2.1. Delete the cluster</h5>
- <p>To delete the cluster, run:</p>
- <pre class="highlightjs highlight"><code class="language-bash hljs" data-lang="bash">> kubectl delete statefulset jemo
- > kubectl delete svc jemo
- > terraform destroy</code></pre>
- <p>And enter <code>yes</code> when terraform asks you if you agree to destroy the displayed resources.</p>
-
-
- <h2 id="deleting-csp-resources"><a class="anchor" href="#deleting-csp-resources"></a>6. Deleting CSP resources</h2>
- <p>Jemo offers you the option to delete CSP resources that have been created with terraform at
- a previous step. All you have to do is to select the CSP and scroll down to the <code>Delete Existing
- Resources</code>
- section. You have the options to:</p>
-
- <div class="olist arabic">
- <ol class="arabic">
- <li>
- <p>Delete only the cluster resources (including kubernetes resources not managed by terraform),
- but keep the installation resources.</p>
- </li>
- <li>
- <p>Delete only the installation resources. This assumes the cluster resources are deleted or never
- created,
- otherwise the attempt to delete the installation resources fails.</p>
- </li>
- <li>
- <p>Delete all the existing resources.</p>
- </li>
- </ol>
- </div>
-
- <p>The UI monitors the deletion process and you are notified when it is finished.
- In case of an error, please read the error cause.
- This could be that some resources can not be deleted because they are still in use,
- e.g. when you have selected to delete the installation resources while the cluster resources
- are still in place. Rarely, the <code>terraform destroy</code> command that is called to delete resources
- fails due a timeout of an underlying call to the CSP REST services.
- In this case, click on the <code>RETRY</code> button.
- This will rerun the <code>terraform destroy</code> command and carry on deleting the remaining resources.
- </p>
- -->
-
</div>
-<!-- ./end #midcolumn -->
diff --git a/content/en_setup_aws.php b/content/en_setup_aws.php
index 1b22dc4..16d6237 100644
--- a/content/en_setup_aws.php
+++ b/content/en_setup_aws.php
@@ -114,7 +114,7 @@
"iam:ListPolicies"</code>
</pre>
- <p>In case of missing permissions, Jemo displays the missing permissions.
+ <p>In case of missing permissions, Jemo displays them.
You have to add them, e.g. by browsing to the AWS console and then come back and try again to login.
A genuine case for this error is when you have created the <code>jemo user</code> or the <code>jemo
diff --git a/content/en_setup_azure.php b/content/en_setup_azure.php
index 3f185df..3157224 100644
--- a/content/en_setup_azure.php
+++ b/content/en_setup_azure.php
@@ -90,7 +90,7 @@
"Microsoft.KeyVault/vaults/secrets/read",
"Microsoft.KeyVault/vaults/secrets/write"</code></pre>
- <p>In case of missing permissions, Jemo displays the missing permissions.
+ <p>In case of missing permissions, Jemo displays them.
You have to add them, e.g. by browsing to the Azure console and then come back and try again to login.
A genuine case for this error is when you have created the <code>jemo user</code> yourself.
diff --git a/content/en_setup_gcp.php b/content/en_setup_gcp.php
index e9b0156..372a4fd 100644
--- a/content/en_setup_gcp.php
+++ b/content/en_setup_gcp.php
@@ -25,10 +25,9 @@
by printing the following log:</p>
<pre>
- GSM is not setup yet. Please click on the following link to provide configuration: <a
- href="https://localhost:443/jemo/setup/" class="bare"
- target="_blank">https://localhost:443/jemo/setup/</a>
- </pre>
+GSM is not setup yet. Please click on the following link to provide configuration: <a
+ href="https://localhost:443/jemo/setup/" class="bare"
+ target="_blank">https://localhost:443/jemo/setup/</a></pre>
<p>Browse to this link and select GCP.
Jemo, offers you 3 options:</p>
@@ -56,27 +55,27 @@
<p>You will be asked to enter <code>project_id</code> and <code>service_account_id</code> and select
the GCP region the jemo user is created in. The dropdown menu displays all the available GCP regions as for now.
If the region you are looking for is missing, please type its code in the provided text input.
- Jemo attempts to locate the json key file on <code>~/.gcp/[SERVICE_ACCOUNT_ID]@[PROJECT_ID]-cred.json</code>.
+ Jemo attempts to locate the <a href="https://cloud.google.com/iam/docs/creating-managing-service-account-keys"
+ target="_blank">json key file</a>
+ on <code>~/.gcp/[SERVICE_ACCOUNT_ID]@[PROJECT_ID]-cred.json</code>.
If the file is there it validates its content.
</p>
<p>If the credentials are valid, then Jemo checks if the following permissions are given to the <code>jemo
- user</code>:</p>
- <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">"roles/datastore.user"
-"roles/storage.admin"
-"roles/logging.admin"</code></pre>
+ user</code>:</p>
+ <pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc"> "roles/datastore.user"
+ "roles/storage.admin"
+ "roles/logging.admin"</code></pre>
<p>These are the permissions needed for Jemo to run.
- In addition to these custom roles an additional <code>jemo-role</code> is required. This contains the
- <code>"iam.serviceAccounts.get"</code> and <code>"resourcemanager.projects.getIamPolicy"</code> permissions
+ In addition to these custom roles an additional <code>jemoRole</code> is required. This contains the
+ <code>iam.serviceAccounts.get</code> and <code>resourcemanager.projects.getIamPolicy</code> permissions
and is used to validate the user credentials and validate if the user is attahced to the above roles.</p>
- <p>In case of missing permissions, Jemo displays the missing permissions.
+ <p>In case of missing permissions, Jemo displays them.
You have to add them, e.g. by browsing to the GCP console and then come back and try again to login.
- A genuine case for this error is when you have created the <code>jemo user</code> or the <code>jemo
- policy</code>
- yourself.
+ A genuine case for this error is when you have created the <code>jemo user</code> yourself.
Otherwise, the <code>jemo user</code> created by Jemo will always pass this validation.
If you created the user with Jemo and get this error,
it means you provided the credentials of an existing GCP user different than the <code>jemo user</code>.
@@ -84,63 +83,63 @@
</p>
<p>If the permissions are valid you will be forwarded to the next setup stage
- which is to select <code>Jemo parameter sets</code>.</p>
+ which is to select <a href="#jemo-parameters">Jemo parameter sets</a>.</p>
<h3 id="jemo-installation"><a class="anchor" href="#jemo-installation"></a>1.2. Jemo Installation</h3>
<p>Jemo setup requires a GCP service account with the "Owner" role to run terraform with,
we call this the <code>terraform user</code>.
- Jemo creates terraform templates to create the user and other resources.
- The terraform user is then used to run these terraform templates.</p>
+ Jemo creates terraform templates to create the <code>jemo user</code> and other resources.
+ The <code>terraform user</code> is used to run these terraform templates.</p>
<pre class="content">
-If you don’t have credentials for the terraform user, first install <a href="https://cloud.google.com/sdk/install" target="_blank">gcloud</a>
- and then follow these steps:
+If you don’t have credentials for the terraform user, first <a
+ href="https://cloud.google.com/sdk/install" target="_blank">install gcloud</a> and then follow these steps:
1. Create a service account with the "terraform-user" name:
- > gcloud iam service-accounts create terraform-user
+> gcloud iam service-accounts create terraform-user
2. Attach the "Owner" role to terraform-user (replace PROJECT_ID with your project id):
- > gcloud projects add-iam-policy-binding [PROJECT_ID] --member serviceAccount:terraform-user@[PROJECT_ID].iam.gserviceaccount.com --role roles/owner
+> gcloud projects add-iam-policy-binding [PROJECT_ID] --member serviceAccount:terraform-user@[PROJECT_ID].iam.gserviceaccount.com --role roles/owner
3. Create a json key file to be used by terraform to retrieve the credentials:
- > gcloud iam service-accounts keys create terraform-user@[PROJECT_ID]-cred.json --iam-account terraform-user@[PROJECT_ID].iam.gserviceaccount.com
+> gcloud iam service-accounts keys create terraform-user@[PROJECT_ID]-cred.json --iam-account terraform-user@[PROJECT_ID].iam.gserviceaccount.com
4. Create a directory "~/.gcp" and copy the json key file there:
- > mkdir ~/.gcp
- > cp terraform-user@[PROJECT_ID]-cred.json ~/.gcp/</pre>
+> mkdir ~/.gcp
+> cp terraform-user@[PROJECT_ID]-cred.json ~/.gcp/
+</pre>
<p>Jemo generates terraform templates on your filesystem under the directory where
- Jemo runs, under the <code>gcp/install/</code> directory. Then it runs terraform:</p>
+ Jemo runs, under the <code>gcp/install</code> directory. Then it runs terraform:</p>
<pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> terraform init -no-color -var-file=gcp/install/terraform.tfvars gcp/install
> terraform plan -no-color -var-file=gcp/install/terraform.tfvars gcp/install
-> terraform apply -no-color -auto-approve -var-file=gcp/install/terraform.tfvars gcp/install</code>
- </pre>
+> terraform apply -no-color -auto-approve -var-file=gcp/install/terraform.tfvars gcp/install</code></pre>
<pre class="content">
-If the <code>terraform</code> command is not found on your path, Jemo notifies you
-with <a href="https://learn.hashicorp.com/terraform/getting-started/install.html"
- target="_blank" rel="noopener">Terraform Installation Instructions</a>.</pre>
+If the <code>terraform</code> command is not found on your path, Jemo notifies you with <a
+ href="https://learn.hashicorp.com/terraform/getting-started/install.html"
+ target="_blank" rel="noopener">Terraform Installation Instructions</a>.</pre>
<p>Besides the <code>jemo user</code>, a
- <code>jemo-role</code> is created and attached to it. Also the custom roles <code>roles/datastore.user</code>,
+ <code>jemoRole</code> is created and attached to it. Also the custom roles <code>roles/datastore.user</code>,
<code>roles/storage.admin</code> and <code>roles/logging.admin</code> are attached to the <code>jemo user</code>.
Finally, terraform creates the json key file <code>jemo-user@[PROJECT_ID]-cred.json</code> and Jemo copies this
under the <code>~/.gcp</code> directory.
- Every time jemo starts, it attempts to locate this file and validate its content to figure out if the <code>jemo-user</code>
+ Every time jemo starts, it attempts to locate this file and validate its content to figure out if the <code>jemo
+ user</code>
is setup for GCP.
</p>
<p>The UI notifies you with all the terraform created resources and printed outputs.</p>
<p>Behind the scenes, Jemo logs in with the <code>jemo user</code> and forwards you
- to the next setup stage which is to select <code>Jemo parameter sets</code>.</p>
+ to the next setup stage which is to select <a href="#jemo-parameters">Jemo parameter sets</a>.</p>
<h3 id="download-the-terraform-templates"><a class="anchor" href="#download-the-terraform-templates"></a>1.3.
Download the Terraform Templates</h3>
- <p>Uppon clicking on the <code>DOWNLOAD</code> button, the <code>install.zip</code> fill
- will be
- downloaded. Run:</p>
+ <p>Uppon clicking on the <code>DOWNLOAD</code> button, the <code>install.zip</code> file
+ will be downloaded. Run:</p>
<pre class="highlightjs highlight"><code class="language-asciidoc hljs" data-lang="asciidoc">> unzip install.zip
> cd install</code></pre>
@@ -169,15 +168,16 @@
user_account_id = jemo-user</code></pre>
<p>Besides the <code>jemo user</code>, a
- <code>jemo-role</code> is created and attached to it. Also the custom roles <code>roles/datastore.user</code>,
+ <code>jemoRole</code> is created and attached to it. Also the custom roles <code>roles/datastore.user</code>,
<code>roles/storage.admin</code> and <code>roles/logging.admin</code> are attached to the <code>jemo user</code>.
Finally, terraform creates the json key file <code>jemo-user@[PROJECT_ID]-cred.json</code> and you need to copy
this
under the <code>~/.gcp</code> directory, run:
+ under the <code>~/.gcp</code> directory, run:
<pre>
> cp jemo-user\@[PROJECT_ID]-cred.json ~/.gcp
</pre>
- Every time jemo starts, it attempts to locate this file and validate its content to figure out if the <code>jemo-user</code>
+ Every time jemo starts, it attempts to locate this file and validate its content to figure out if the <code>jemo user</code>
is setup for GCP.
</p>
@@ -211,9 +211,9 @@
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.location.type</code>
- </p></td>
+ </p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">One of [<code>CLOUD</code>, <code>ON-PROMISE</code>]
- </p></td>
+ </p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.whitelist</code></p>
@@ -227,20 +227,20 @@
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.queue.polltime</code>
- </p></td>
+ </p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">The queue poll interval</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.log.local</code></p>
</td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Switch between local and cloud
- logging</p></td>
+ logging</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.log.output</code></p>
</td>
<td class="tableblock halign-left valign-top"><p class="tableblock">If local logging is enabled, this
- parameter controls the log output (e.g. STDOUT or a local file)</p></td>
+ parameter controls the log output (e.g. STDOUT or a local file)</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock"><code>eclipse.jemo.log.level</code></p>
@@ -318,7 +318,7 @@
<p>The whole process can take up to 15 minutes. The Jemo UI monitors the progress.</p>
- <p>In the end, the UI notifies you with the terraform crested resources and outputs,
+ <p>In the end, the UI notifies you with the terraform created resources and outputs,
as well as with the URL where you can access Jemo.
This is the external URL of the ingress load balancer.</p>
