Github user grkvlt commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/213#discussion_r138938596
--- Diff: guide/blueprints/policies.md ---
@@ -100,6 +100,39 @@ The ConnectionFailureDetector is an HA policy for
monitoring an http connection,
### Optimization Policies
+#### PeriodicEffector Policy
+
+- org.apache.brooklyn.policy.action.PeriodicEffectorPolicy
+
+The `PeriodicEffectorPolicy` calls an effector with a set of arguments at
a specified time and date. The following example
+calls a `resize` effector to resize a cluster up to 10 members at 8am and
then down to 1 member at 6pm.
+
+ - type: org.apache.brooklyn.policy.action.PeriodicEffectorPolicy
+ brooklyn.config:
+ effector: resize
+ args:
+ desiredSize: 10
+ period: 1 day
+ time: 08:00:00
+ - type: org.apache.brooklyn.policy.action.PeriodicEffectorPolicy
+ brooklyn.config:
+ effector: resize
+ args:
+ desiredSize: 1
+ period: 1 day
+ time: 18:00:00
+
+#### ScheduledEffector Policy
+
+- org.apache.brooklyn.policy.action.ScheduledEffectorPolicy
+
+The `ScheduledEffectorPolicy` calls an effector after a specified interval
has expired. The interval can be triggered from a sensor, `SERVICE_UP` by
default.
--- End diff --
change to:
> The `ScheduledEffectorPolicy` calls an effector at a specific time,
waiting until the entity is ready using the same mechanism as the
`PeriodicEffectorPolicy`. There are two modes of operation, one based solely on
policy configuration where the effector will execute at the time set using the
`time` key or after the duration set using the `wait` key, or by monitoring
sensors. The policy monitors the `scheduler.invoke.now` sensor and will execute
the effector immediately when its value changes to `true`. When the
`scheduler.invoke.at` sensor changes, it will set a time in the future when the
effector should be executed.
---
