forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path_errands.html.md.erb
31 lines (17 loc) · 2.47 KB
/
_errands.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Errands are scripts that Ops Manager runs to automate tasks. By default, Ops Manager runs the post-install errands listed below when you deploy Elastic Runtime. However, you can prevent a specific post-install errand from running by deselecting its checkbox on the **Errands** page.
<p class='note'><strong>Note</strong>: Several errands deploy apps that provide services for your deployment, such as Autoscaling and Notifications. Once one of these apps is running, deselecting the checkbox for the corresponding errand on a subsequent deployment does not stop the app.</p>
<%= image_tag('errands.png') %>
* **Push Apps Manager** deploys the Apps Manager, a dashboard for managing apps, services, orgs, users, and spaces. Until you deploy Apps Manager, you must perform these functions through the cf CLI. After Apps Manager has been deployed, we recommend deselecting the checkbox for this errand on subsequent Elastic Runtime deployments. For more information about the Apps Manager, see [Getting Started with the Apps Manager](../console/dev-console.html).
* **Run Smoke Tests** verifies that your deployment can do the following:
* Push, scale, and delete apps
* Create and delete orgs and spaces
* **Push App Usage Service** deploys the Usage Service, a dashboard that provides resource usage data and analytics for your apps.
* **Notifications** deploys an API for sending email notifications to your PCF platform users.
<p id='notifications' class='note'><strong>Note</strong>:
The Notifications app requires that you <a href='#smtp'>configure SMTP</a> with a username and password, even if <code>SMTP Authentication Mechanism</code> is set to none.
</p>
* **Notifications with UI** deploys a dashboard for users to manage notification subscriptions.
* **Deploy CF Autoscaling App** enables your deployment to automatically scale the number of instances of an app in response to changes in its usage load. To enable Autoscaling for an app, you must also bind the Autoscaling service to it. For more information, see the [Bind a Service Instance](../devguide/services/managing-services.html#bind) section of the _Managing Service Instances with the CLI_ topic.
<p class='note'><strong>Note</strong>: The Autoscaling app requires the Notifications app to send scaling action alerts by email.
</p>
* **Register Autoscaling Service Broker** makes the Autoscaling service available to your applications. Without this errand, you cannot bind the Autoscaling app to your apps.