You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by he...@apache.org on 2022/07/22 10:50:30 UTC
[brooklyn-docs] branch master updated (b42a9298 -> 0c4c26bc)
This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
from b42a9298 update container effector/sensor docs
new 06ba4a7b explain kubectl slightly better
new 07ef35e3 Clarify object store configuration
new 0c4c26bc Merge remote-tracking branch 'juan/clarify-persistence-location'
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
guide/blueprints/effectors.md | 22 +++++++++++++++++-----
guide/ops/persistence/index.md | 4 ++--
2 files changed, 19 insertions(+), 7 deletions(-)
[brooklyn-docs] 03/03: Merge remote-tracking branch 'juan/clarify-persistence-location'
Posted by he...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit 0c4c26bc7a46fb15d354ff123eede85321f09841
Merge: 06ba4a7b 07ef35e3
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Fri Jul 22 11:50:09 2022 +0100
Merge remote-tracking branch 'juan/clarify-persistence-location'
guide/ops/persistence/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
[brooklyn-docs] 02/03: explain kubectl slightly better
Posted by he...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit 06ba4a7b6b987b5d0bb708fccc2ddea08681a588
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Fri Jul 22 11:49:21 2022 +0100
explain kubectl slightly better
---
guide/blueprints/effectors.md | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/guide/blueprints/effectors.md b/guide/blueprints/effectors.md
index 63ecb79c..cb46c368 100644
--- a/guide/blueprints/effectors.md
+++ b/guide/blueprints/effectors.md
@@ -54,7 +54,12 @@ See [`here`](https://brooklyn.apache.org/v/latest/misc/javadoc/org/apache/brookl
### ContainerEffector
-An `Effector` to invoke a command or (a list of commands) on a container node accessible via `kubectl`. This obviously means access to a Kubernetes cluster must be ensured and `kubectl` must be installed where Apache Brooklyn runs. This effector is defined in the blueprint to be added to the entity using Apache Brooklyn initializers.
+This defines an effector to invoke a command or (a list of commands) on a container node accessible via `kubectl`.
+This that the `kubectl` CLI is available on the host where Apache Brooklyn is running
+and configured to access the desired Kubernetes cluster and the associated images.
+Supported Kubernetes environments to run containers include EKS, GKE, AKS, and (locally) Minikube and Docker Desktop.
+
+This effector is defined in the blueprint to be added to the entity using Apache Brooklyn initializers.
It enables execution of a `command` in a specific container managed by a Kubernetes cluster. _Under the covers_ the commands and other configurations are used to generate a Kubernetes job that will execute in its own namespace. Regardless of the job execution result (success or failure) the namespace is deleted at the end, unless configured otherwise.
@@ -92,10 +97,17 @@ services:
hello: world-amp
image: perl
imagePullPolicy: IfNotPresent
- commands:
- - /bin/bash
- - -c
- - HELLO=$(ls -la) ; echo $HELLO; date ; echo $hello
+ bashScript: >
+ HELLO=$(ls -la)
+ echo $HELLO
+ date
+ echo $hello
+
+ brooklyn.initializers:
+ - type: org.apache.brooklyn.tasks.kubectl.ContainerEffector
+ brooklyn.config:
+ name: run-spark-job
+ image: my-spark-container
{% endhighlight %}
[brooklyn-docs] 01/03: Clarify object store configuration
Posted by he...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit 07ef35e3151897746ee9ed012f7619ac0f4bdd37
Author: Juan Cabrerizo <ju...@cabrerizo.es>
AuthorDate: Fri Jul 22 12:19:04 2022 +0200
Clarify object store configuration
---
guide/ops/persistence/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/guide/ops/persistence/index.md b/guide/ops/persistence/index.md
index a6423a9f..f283a469 100644
--- a/guide/ops/persistence/index.md
+++ b/guide/ops/persistence/index.md
@@ -29,7 +29,7 @@ directory of your Brooklyn instance. The following options are available:
* `REBIND` - will rebind to the existing state, or fail if no state available;
* `CLEAN` - will start up fresh (removing any existing state)
-`persistenceDir` - This is the directory to which Apache Brooklyn reads and writes its persistence data. The default location depends
+`persistenceDir` - This is the directory or object store container name to which Apache Brooklyn reads and writes its persistence data. The default location depends
on your installation method. Checkout [this page](/guide/ops/paths.md) for more information.
`persistenceLocation` - This is the location for an object store to read and write persisted state.
@@ -73,7 +73,7 @@ This gives access to any compatible Object Store product or cloud provider inclu
SoftLayer, Rackspace, HP and Microsoft Azure. For a complete list of supported
providers, see [jclouds](http://jclouds.apache.org/reference/providers/#blobstore).
-To configure the Object Store, add the credentials to `brooklyn.cfg` such as:
+To configure the Object Store, add the credentials to `brooklyn.cfg` by creating a new location such as:
{% highlight properties %}
brooklyn.location.named.aws-s3-eu-west-1=aws-s3:eu-west-1