Andrew Donald KENNEDY grkvlt

Effector Parameters

The idiomatic definition of effectors in Brooklyn requires setting up some naming conventions for various tings. One of these is the arguments to a method. In Java, compiled bytecode does not provide us with the symbol names for these arguments, so a method is uniquely determined by it's argument types and their order (and the return type) - that is, method(String a, Integer b) and method(String x, Integer z) are considered identical. This can be seen in many IDEs where Javadoc comments are not available on interfaces, and the method arguments are listed as arg0, arg1 and so on.

In a Brooklyn effector declaration, we usually annotate each parameter with the @EffectorParam annotation, which takes name, description and defaultValue properties. These are defined as Strings, due to the restrictions inherent in the Java type annotation specification, which can cause problems for the defaultValue property. The description is normally a 'Sentence case' fr

$ script.sh | (tee output.log | xargs -I X -L 10  echo -n . && echo)
..........
$ wc -l output.log
1005

Clocker Configuration

The following sections list the location configuration options to be used when testing Clocker releases. All of these must be combined, to give 2 x 6 x 3 or 36 separate configurations. The default setup is a remote Ubuntu server running Brooklyn, with Clocker deployed to Ubuntu 14.04 VMs in Softlayer London. Results are to be recorded in a spreadsheet and successful completion of all configurations is required for a release GO or NO-GO decision, with performance to be included as a success criterion one a baseline has been established.

Sign-off on a release must be by both Clocker Architect and Lead Engineer @grkvlt and Cloudsoft VP Engineering @aledsage.

Brooklyn Server Location

Local OSX 10.10 Laptop
Remote Ubuntu 14.04 VM

	id: riak-cluster-centos
	name: "Riak Cluster CentOS"
	location: clocker-calico-london

	services:
	- type: org.apache.brooklyn.entity.nosql.riak.RiakCluster
	initialSize: 2
	id: mycluster
	brooklyn.config:
	install.version: 2.1.1

	id: redis-store
	location: jclouds:softlayer:lon02

	services:
	- type: org.apache.brooklyn.entity.nosql.redis.RedisStore

	id: my-redis-cluster
	name: My Redis Cluster
	location: jclouds:softlayer:lon02

	services:
	- type: org.apache.brooklyn.entity.nosql.redis.RedisCluster
	id: redis-cluster

	# this Apache Brooklyn blueprint will deploy an example Java service cluster

	brooklyn.catalog:
	version: 1.1.0-PREVIEW.20150818

	items:
	- id: host
	item:
	type: brooklyn.entity.basic.VanillaSoftwareProcess
	name: Host

	# this catalog bom is an illustration supplying a few useful sample items
	# and templates to get started using Brooklyn

	brooklyn.catalog:
	version: 1.1.0-PREVIEW.20150818
	items:

	# load everything in the classpath with a @Catalog annotation
	- scanJavaAnnotations: true

	void main() {
	for (int i = 0; i < 5; i++) {
	print('hello ${i + 1}');
	}
	}