source/locale/pot/events.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2016, Apache Software Foundation
# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-22 13:55+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../events.rst:18
msgid "Event Notification"
msgstr ""

#: ../../events.rst:20
msgid "An event is essentially a significant or meaningful change in the state of both virtual and 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 CloudStack an event could be a state change of virtual or physical resources, an action performed by an user (action events), or policy based events (alerts)."
msgstr ""

#: ../../events.rst:30
msgid "Event Logs"
msgstr ""

#: ../../events.rst:32
msgid "There are two types of events logged in the CloudStack Event Log. Standard events log the success or failure of an event and can be used to identify jobs or processes that have failed. There are also long running job events. Events for asynchronous jobs log when a job is scheduled, when it starts, and when it completes. Other long running synchronous jobs log when a job starts, and when it completes. Long running synchronous and asynchronous event logs can be used to gain more information on the status of a pending job or can be used to identify a job that is hanging or has not started. The following sections provide more information on these events.."
msgstr ""

#: ../../events.rst:45
msgid "Notification"
msgstr ""

#: ../../events.rst:47
msgid "Event notification framework provides a means for the Management Server components to publish and subscribe to CloudStack events. Event notification is achieved by implementing the concept of event bus abstraction in the Management Server."
msgstr ""

#: ../../events.rst:52
msgid "A new event for state change, resource state change, is introduced as part of Event notification framework. Every resource, such as user VM, volume, NIC, network, public IP, snapshot, and template, is associated with a state machine and generates events as part of the state change. That implies that a change in the state of a resource results in a state change event, and the event is published in the corresponding state machine on the event bus. All the CloudStack events (alerts, action events, usage events) and the additional category of resource state change events, are published on to the events bus."
msgstr ""

#: ../../events.rst:63
msgid "Implementations"
msgstr ""

#: ../../events.rst:64
msgid "An event bus is introduced in the Management Server that allows the CloudStack components and extension plug-ins to subscribe to the events by using the Advanced Message Queuing Protocol (AMQP) client. In CloudStack, a default implementation of event bus is provided as a plug-in that uses the RabbitMQ AMQP client. The AMQP client pushes the published events to a compatible AMQP server. Therefore all the CloudStack events are published to an exchange in the AMQP server."
msgstr ""

#: ../../events.rst:73
msgid "Additionally, both an in-memory implementation and an Apache Kafka implementation are also available."
msgstr ""

#: ../../events.rst:77
msgid "Use Cases"
msgstr ""

#: ../../events.rst:79
msgid "The following are some of the use cases:"
msgstr ""

#: ../../events.rst:81
msgid "Usage or Billing Engines: A third-party cloud usage solution can implement a plug-in that can connects to CloudStack to subscribe to CloudStack events and generate usage data. The usage data is consumed by their usage software."
msgstr ""

#: ../../events.rst:86
msgid "AMQP plug-in can place all the events on the a message queue, then a AMQP message broker can provide topic-based notification to the subscribers."
msgstr ""

#: ../../events.rst:90
msgid "Publish and Subscribe notification service can be implemented as a pluggable service in CloudStack that can provide rich set of APIs for event notification, such as topics-based subscription and notification. Additionally, the pluggable service can deal with multi-tenancy, authentication, and authorization issues."
msgstr ""

#: ../../events.rst:98
msgid "AMQP Configuration"
msgstr ""

#: ../../events.rst:100
#: ../../events.rst:209
msgid "As a CloudStack administrator, perform the following one-time configuration to enable event notification framework. At run time no changes can control the behaviour."
msgstr ""

#: ../../events.rst:104
#: ../../events.rst:219
msgid "Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/core``"
msgstr ""

#: ../../events.rst:106
#: ../../events.rst:221
msgid "Inside that folder, open ``spring-event-bus-context.xml``."
msgstr ""

#: ../../events.rst:108
msgid "Define a bean named ``eventNotificationBus`` as follows:"
msgstr ""

#: ../../events.rst:110
msgid "name : Specify a name for the bean."
msgstr ""

#: ../../events.rst:112
msgid "server : The name or the IP address of the RabbitMQ AMQP server."
msgstr ""

#: ../../events.rst:114
msgid "port : The port on which RabbitMQ server is running."
msgstr ""

#: ../../events.rst:116
msgid "username : The username associated with the account to access the RabbitMQ server."
msgstr ""

#: ../../events.rst:119
msgid "password : The password associated with the username of the account to access the RabbitMQ server."
msgstr ""

#: ../../events.rst:122
msgid "exchange : The exchange name on the RabbitMQ server where CloudStack events are published."
msgstr ""

#: ../../events.rst:125
msgid "A sample bean is given below:"
msgstr ""

#: ../../events.rst:148
msgid "The ``eventNotificationBus`` bean represents the ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class."
msgstr ""

#: ../../events.rst:151
msgid "If you want to use encrypted values for the username and password, you have to include a bean to pass those as variables from a credentials file."
msgstr ""

#: ../../events.rst:154
msgid "A sample is given below"
msgstr ""

#: ../../events.rst:194
msgid "Create a new file in the same folder called ``cred.properties`` and the specify the values for username and password as jascrypt encrypted strings"
msgstr ""

#: ../../events.rst:196
msgid "Sample, with ``guest`` as values for both fields:"
msgstr ""

#: ../../events.rst:204
#: ../../events.rst:241
msgid "Restart the Management Server."
msgstr ""

#: ../../events.rst:207
msgid "Kafka Configuration"
msgstr ""

#: ../../events.rst:213
msgid "Create an appropriate configuration file in ``/etc/cloudstack/management/kafka.producer.properties`` which contains valid kafka configuration properties as documented in http://kafka.apache.org/documentation.html#newproducerconfigs The properties may contain an additional ``topic`` property which if not provided will default to ``cloudstack``. While ``key.serializer`` and ``value.serializer`` are usually required for a producer to correctly start, they may be omitted and will default to ``org.apache.kafka.common.serialization.StringSerializer``."
msgstr ""

#: ../../events.rst:223
msgid "Define a bean named ``eventNotificationBus`` with a single ``name`` attribute, A sample bean is given below:"
msgstr ""

#: ../../events.rst:245
msgid "Standard Events"
msgstr ""

#: ../../events.rst:247
#: ../../events.rst:269
msgid "The events log records three types of standard events."
msgstr ""

#: ../../events.rst:249
#: ../../events.rst:271
msgid "INFO. This event is generated when an operation has been successfully performed."
msgstr ""

#: ../../events.rst:252
#: ../../events.rst:274
msgid "WARN. This event is generated in the following circumstances."
msgstr ""

#: ../../events.rst:254
#: ../../events.rst:276
msgid "When a network is disconnected while monitoring a template download."
msgstr ""

#: ../../events.rst:257
#: ../../events.rst:279
msgid "When a template download is abandoned."
msgstr ""

#: ../../events.rst:259
#: ../../events.rst:281
msgid "When an issue on the storage server causes the volumes to fail over to the mirror storage server."
msgstr ""

#: ../../events.rst:262
#: ../../events.rst:284
msgid "ERROR. This event is generated when an operation has not been successfully performed"
msgstr ""

#: ../../events.rst:267
msgid "Long Running Job Events"
msgstr ""

#: ../../events.rst:289
msgid "Event Log Queries"
msgstr ""

#: ../../events.rst:291
msgid "Database logs can be queried from the user interface. The list of events captured by the system includes:"
msgstr ""

#: ../../events.rst:294
msgid "Virtual machine creation, deletion, and on-going management operations"
msgstr ""

#: ../../events.rst:297
msgid "Virtual router creation, deletion, and on-going management operations"
msgstr ""

#: ../../events.rst:299
msgid "Template creation and deletion"
msgstr ""

#: ../../events.rst:301
msgid "Network/load balancer rules creation and deletion"
msgstr ""

#: ../../events.rst:303
msgid "Storage volume creation and deletion"
msgstr ""

#: ../../events.rst:305
msgid "User login and logout"
msgstr ""

#: ../../events.rst:309
msgid "Deleting and Archiving Events and Alerts"
msgstr ""

#: ../../events.rst:311
msgid "CloudStack provides you the ability to delete or archive the existing alerts and events that you no longer want to implement. You can regularly delete or archive any alerts or events that you cannot, or do not want to resolve from the database."
msgstr ""

#: ../../events.rst:316
msgid "You can delete or archive individual alerts or events either directly by using the Quickview 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. For example, you can select categories such as **USER.LOGOUT**, **VM.DESTROY**, **VM.AG.UPDATE**, **CONFIGURATION.VALUE.EDI**, and so on. You can also view the number of events or alerts archived or deleted."
msgstr ""

#: ../../events.rst:325
msgid "In order to support the delete or archive alerts, the following global parameters have been added:"
msgstr ""

#: ../../events.rst:328
msgid "**alert.purge.delay**: The alerts older than specified number of days are purged. Set the value to 0 to never purge alerts automatically."
msgstr ""

#: ../../events.rst:331
msgid "**alert.purge.interval**: The interval in seconds to wait before running the alert purge thread. The default is 86400 seconds (one day)."
msgstr ""

#: ../../events.rst:336
msgid "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."
msgstr ""

#: ../../events.rst:342
msgid "Permissions"
msgstr ""

#: ../../events.rst:344
msgid "Consider the following:"
msgstr ""

#: ../../events.rst:346
msgid "The root admin can delete or archive one or multiple alerts or events."
msgstr ""

#: ../../events.rst:349
msgid "The domain admin or end user can delete or archive one or multiple events."
msgstr ""

#: ../../events.rst:354
msgid "Procedure"
msgstr ""

#: ../../events.rst:356
msgid "Log in as administrator to the CloudStack UI."
msgstr ""

#: ../../events.rst:358
msgid "In the left navigation, click Events."
msgstr ""

#: ../../events.rst:360
msgid "Perform either of the following:"
msgstr ""

#: ../../events.rst:362
msgid "To archive events, click Archive Events, and specify event type and date."
msgstr ""

#: ../../events.rst:365
msgid "To archive events, click Delete Events, and specify event type and date."
msgstr ""

#: ../../events.rst:368
msgid "Click OK."
msgstr ""