CLOUDSTACK-1567 ui and api changes

docs/en-US/added-API-commands-4.2.xml

@@ -39,5 +39,29 @@
       <para>The response parameters are: id, ipaddress, secondaryips, gateway, netmask, macaddr,
         broadcasturi, isolationuri, isdefault,</para>
     </listitem>
+    <listitem>
+      <para>deleteAlerts </para>
+      <para>Deletes the specified alerts. The request parameters are: ids (allowed to pass one or
+        more IDs separated by comma); type (string); olderthan (yyyy-mm-dd format).</para>
+      <para>The response parameters are: true, false </para>
+    </listitem>
+    <listitem>
+      <para>archiveAlerts</para>
+      <para>Archives the specified alerts. The request parameters are: ids (allowed to pass one or
+        more IDs separated by comma); type (string); olderthan (yyyy-mm-dd format).</para>
+      <para>The response parameters are: true, false </para>
+    </listitem>
+    <listitem>
+      <para>deleteEvents </para>
+      <para>Deletes the specified events. The request parameters are: ids (allowed to pass one or
+        more IDs separated by comma); type (string); olderthan (yyyy-mm-dd format).</para>
+      <para>The response parameters are: true, false</para>
+    </listitem>
+    <listitem>
+      <para>archiveEvents</para>
+      <para>Archives the specified events. The request parameters are: ids (allowed to pass one or
+        more IDs separated by comma); type (string); olderthan (yyyy-mm-dd format).</para>
+      <para>The response parameters are: true, false </para>
+    </listitem>
   </itemizedlist>
 </section>

docs/en-US/delete-event-alerts.xml

@@ -28,6 +28,18 @@
     or by using the Details page. If you want to delete multiple alerts or events at the same time,
     you can use the respective context menu. You can delete alerts or events by category for a time
     period.</para>
+  <para>In order to support the delete or archive alerts, the following global parameters have been
+    added:</para>
+  <itemizedlist>
+    <listitem>
+      <para><emphasis role="bold">alert.purge.delay</emphasis>: The alerts older than specified
+        number of days are purged. Set the value to 0 to never purge alerts automatically.</para>
+    </listitem>
+    <listitem>
+      <para><emphasis role="bold">alert.purge.interval</emphasis>: The interval in seconds to wait
+        before running the alert purge thread. The default is 86400 seconds (one day).</para>
+    </listitem>
+  </itemizedlist>
   <note>
     <para>Archived alerts or events cannot be viewed in the UI, or by using the API. They are
       maintained in the database for auditing or compliance purposes.</para>

docs/en-US/events.xml

@@ -25,7 +25,7 @@
     physical resources associated with a cloud environment. Events are used by monitoring systems,
     usage and billing systems, or any other event-driven workflow systems to discern a pattern and
     make the right business decision. In &PRODUCT; an event could be a state change of virtual or
-    psychical resources, an action performed by an user (action events), or policy based events
+    physical resources, an action performed by an user (action events), or policy based events
     (alerts).</para>
   <xi:include href="events-log.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
   <xi:include href="event-framework.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>