[appc.git] / appc-common / src / main / resources / org / onap / appc / i18n / MessageResources.properties

###
# ============LICENSE_START=======================================================
# ONAP : APPC
# ================================================================================
# Copyright (C) 2017-2018 AT&T Intellectual Property. All rights reserved.
# ================================================================================
# Copyright (C) 2017 Amdocs
# =============================================================================
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# 
#      http://www.apache.org/licenses/LICENSE-2.0
# 
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# 
# ============LICENSE_END=========================================================
###

# This property file contains all message definitions used by APPC
#
# Message resources are identified by a key, which is defined in the Msg enumeration.  This key is
# assigned a value which consists of 4 parts separated by a pipe (|) symbol.  These parts are:
#
# 1. The message identifier
# 2. The Message text to be formatted and issued to the user
# 3. The suggested resolution text, how to fix the problem.
# 4. The description text, what is the problem so the user can understand
#
CONFIGURATION_STARTED=APPC0001I|\
  ECOMP Application Controller (APP-C) initialization started at {0}|\
  No resolution is required, this is an informational message|\
  The APP-C component configuration has been started because the component is being \
    initialized or loaded for the first time, or a new instance of the component is \
    being created.  This message indicates that the component is starting.

CONFIGURATION_CLEARED=APPC0002I|\
  All prior configuration has been cleared|\
  No resolution is required, this is an informational message|\
  The APP-C component is being started or restarted and any prior configuration \
    (if present), is cleared.  This is normal.

LOADING_CONFIGURATION_OVERRIDES=APPC0003I|\
  Loading configuration properties from file "{0}"|\
  No resolution is required, this is an informational message|\
  This message indicates that the configuration of the APP-C component was located \
    and is being loaded from the specified file.

LOADING_DEFAULTS=APPC0004I|\
  Configuration defaults loaded from resource file "{0}"|\
  No resolution is required, this is an informational message|\
  This is a normal indication that the default configuration settings were loaded \
    from the resource file.  The APP-C components load a default configuration first \
    so that all configuration values have valid default settings.  Any user configuation \
    that may be specified then overrides these defaults.

NO_DEFAULTS_FOUND=APPC0005E|\
  No default property resource "{0}" was found!|\
  This is an internal error.  Contact support.|\
  This is an internal error that indicates that the default resource property file \
    could not be located.  This is likely a packaging error and is indicative of \
    a construction problem.  Refer this to development or level 3 support for assistance.

PROPERTY_VALUE=APPC0006I|\
  Property "{0}" ="{1}"|\
  No resolution is required, this is an informational message|\
  This message is issued to show the value of configuration properties and is used to \
    debug start up of the component.

NO_OVERRIDE_PROPERTY_FILE_LOADED=APPC0007E|\
  No configuration file named [{0}] was found on the configuration search path [{1}]. \
    If a configuration file should have been loaded, check the file name and search \
    path specified.  APPC will proceed using the default values and command-line \
    overrides (if any).|\
  If a configuration file was expected, verify the file name and that it exists on \
    the search path for the configuration properties.  The search path defaults to \
    <em>&#36;{user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> and can be overridden \
    by specification of the property <em>org.onap.appc.bootstrap.path</em>.  The \
    property file name defaults to <em>appc.properties</em> and can also be \
    overridden by the <em>org.onap.appc.bootstrap.file</em> property.|\
  This message indicates that the bootstrap path was searched for the bootstrap \
    property file (a file that can be supplied to configure APPC) and that no file \
    with the specified name was found on any of the path elements of the path.

SEARCHING_CONFIGURATION_OVERRIDES=APPC0008I|\
  Searching path "{0}" for configuration settings "{1}"|\
  No resolution is required|\
  This message indicates that the specified path is being examined for a configuration \
    file of the indicated name.  The configuration file defaults to <em>appc.properties</em> \
    but can be overridden by specification of the <em>org.onap.appc.bootstrap.file</em> \
    property (using a command-line override, for example).  This message is intended to \
    assist in the debugging and analysis of configuration issues where the indicated \
    file may not be processed or found.  The path that is searched is a comma-delimited \
    list of directories and defaults to <em>&#36;{user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> \
    but can also be overridden by specification of the <em>org.onap.appc.bootstrap.path</em> \
    property.

LOADING_APPLICATION_OVERRIDES=APPC0009I|\
  Loading application-specific override properties|\
  No resolution required|\
  This message indicates that the APPC component was invoked as an embedded component \
    and that the caller has supplied an override property object.

NO_APPLICATION_OVERRIDES=APPC0010I|\
  No application-specific override properties were provided!|\
  No resolution required|\
  This message indicates that the APPC component was invoked as an embedded component \
    and that the caller has supplied an override property object, but that object was \
    empty.

MERGING_SYSTEM_PROPERTIES=APPC0011I|\
  Merging system properties into configuration|\
  No resolution is required|\
  This message indicates that the java virtual machine system properties are being \
    examined and merged into the APP-C component configuration.  This allows for command \
    line specification of any APP-C configuration property as a standard java define \
    JVM option (ex: -Dproperty=value).

SETTING_SPECIAL_PROPERTY=APPC0012I|\
  Setting property "{0}={1}" in system properties|\
  No resolution required.|\
  This message indicates that the specified property loaded from defaults, property \
    file overrides, application overrides, or command-line overrides is being placed \
    in the system (java virtual machine) properties object.  Some libraries that may \
    be integrated with APP-C (for example, DME2 or AFT libraries) may only look for \
    their properties in the system properties object.  This allows those components \
    to be configured from the APP-C configuration.

LOADING_RESOURCE_BUNDLE=APPC0013I|\
  Loading resource bundle "{0}"|\
  No resolution required|\
  This message indicates that the specified resource bundle is being loaded.

LOGGING_ALREADY_INITIALIZED=APPC0014W|\
  Logging has already been initialized, check the container logging definitions to ensure \
    they represent your desired logging configuration.|\
  If logging is configured incorrectly, move the definitions to the container or component \
    that first initialized logging.  If they are ok, no resolution is required.|\
  This message indicates that the logging environment already exists and has been configured.

SEARCHING_LOG_CONFIGURATION=APPC0015I|\
  Searching path "{0}" for log configuration file "{1}"|\
  No resolution is required|\
  This message indicates that the APP-C component configuration file specified a logging \
    configuration file and/or search path and the path is being searched.  This is used to \
    assist in debugging the configuration process.

LOADING_DEFAULT_LOG_CONFIGURATION=APPC0016I|\
  Loading default logging configuration from system resource file "{0}"|\
  No resolution is required|\
  A default logging configuration for the component is loaded from system resources to \
    ensure that a valid logging environment exists.  This is a normal message, and will \
    be followed by APPC0019I if a user-specified logging configuration overrides the \
    defaults.

NO_LOG_CONFIGURATION=APPC0017E|\
  No log configuration could be found or defaulted!|\
  A valid logging configuration cannot be found, and no default configuration resource \
    was loaded.  This is likely a packaging issue and should be referred to development \
    or level 3 support for assistance.|\
  This is an internal error.

UNSUPPORTED_LOGGING_FRAMEWORK=APPC0018E|\
  An unsupported logging framework is bound to SLF4J.  Only Logback or Log4J are supported.|\
  This is a compatibility error with logging frameworks used in the application environment \
    and should be referred to development or level 3 support for assistance.|\
  This is an internal error.

LOADING_LOG_CONFIGURATION=APPC0019I|\
  Loading logging configuration from file "{0}"|\
  No resolution is required|\
  The specified logging configuration is being loaded.

UNKNOWN_PROVIDER=APPC0020E|\
  Provider {0} cannot be found or cannot be resolved to one of the known providers, [{1}].|\
  Specify the name of a valid provider. The IAAS adapter contains a set of providers \
    that are defined.  Each of these providers is assigned a logical name.  The call \
    to the IAAS adapter must specify the name of the provider that is desired.  This \
    could be the result of an incorrect call, or the IAAS adapter configuration is \
    wrong.|\
  The APP-C IAAS adapter is being called to request a service on a specific provider, but \
    the name of the provider cannot be found in the list of defined providers.  This may \
    be an error in the directed graph that contains the call to the IAAS adapter, or it \
    may be an error in the request, or the configuration of the IAAS adapter may need \
    to be updated.

SERVER_STATE_CHANGE_TIMEOUT=APPC0021E|\
  Server name "{0}" with id "{1}" in tenant "{2}" and region "{3}" did not change state \
    within the alloted time. Current state is "{4}" and the desired state(s) are "{5}"|\
  This is likely a provider issue.  If the provider is OpenStack, check the virtual \
    machine on the horizon dashboard.  If the machine is in an invalid state, you may \
    need to contact Openstack support.  The exact mechanisms for recovery of a machine \
    in an invalid state are varied and will be different from provider to provider.|\
  This message indicates that the IAAS adapter has performed some requested action \
    on the specified server (virtual machine) but the server did not enter a valid \
    state (running, stopped, etc) within the timeout period.  The last state (current state) \
    is shown, as well as the state that was expected.  The servers name, UUID, containing \
    tenant, and region are shown so that the correct provider can be examined.

SERVER_DELETED=APPC0022E|\
  Server name "{0}" with id "{1}" in tenant "{2}" has a state of deleted and cannot be {3}.|\
  The specified server has been deleted on the provider.  This is likely an incorrect \
    request.  Make sure that you are specifying the correct server ID/name, provider, \
    and region.  If the self-link URL is used, make sure that the correct server resource \
    is specified.  If the machine was correct, recreate or rebuild the machine to make \
    it usable.  Correct the request.|\
  This message indicates that the server specified was found to have been deleted in the \
    target provider and that the requested action cannot be performed.  This may be caused \
    by several things:\
    <ol>\
      <li>The UUID of the server is wrong and specifies a machine that no longer exists</li>\
      <li>The machine was deleted by a different process or request</li>\
      <li>The wrong provider was requested</li>\
      <li>The request was out-of-order</li>\
    </ol>

UNKNOWN_SERVER_STATE=APPC0023E|\
  Server name "{0}" with id "{1}" in tenant "{2}" has an unknown state of "{3}".|\
  Check the machine to determine the state of the machine.  Correct that state to a valid \
    state if possible.  This may also be caused by an internal error in the PAL (Provider \
    Abstraction Layer) used by the IAAS if a new state definition has been added to the \
    provider (such as a new version or the installation of an unknown or unsupported \
    extension).  If the machine's state is valid, refer this error to development or \
    level 3 support for assistance.|\
  This message indicates that a request was made to the IAAS adapter to take some action \
    on the specified virtual machine, but the machine was found to be in a state that \
    prevents that action from being performed.

COMPONENT_INITIALIZING=APPC0024I|\
  {0} component {1} is being initialized...|\
  No resolution needed|\
  The IAAS adapter is being initialized

COMPONENT_INITIALIZED=APPC0025I|\
  {0} component {1} has completed initialization|\
  No resolution needed|\
  The IAAS adapter has been initialized

COMPONENT_TERMINATING=APPC0026I|\
  {0} component {1} is terminating...|\
  No resolution needed|\
  The IAAS adapter is being terminated

COMPONENT_TERMINATED=APPC0027I|\
  {0} component {1} has terminated|\
  No resolution needed|\
  The IAAS adapter has been terminated

IAAS_ADAPTER_UNSUPPORTED_OPERATION=APPC0028E|\
  Operation {0} is not supported or implemented at this time.|\
  Change the request to a supported operation|\
  The IAAS adapter has been requested to perform some operation that it cannot \
    perform at this time.

IAAS_ADAPTER_RPC_CALLED=APPC0029I|\
  Operation [{0}] called.  Input document:\n{1}|\
  No resolution required|\
  The IAAS adapter operation indicated was called with the requested input \
    parameters.

NO_SERVICE_FOUND=APPC0030E|\
  Unable to locate the [{0}] service in the OSGi container|\
  Ensure that the feature containing that service is installed and running|\
  This indicates that the required feature could not be located

CONTEXT_PARAMETERS_DISPLAY=APPC0031I|\
  Dump of context parameters for module [{0}], RPC [{1}], and version [{2}]|\
  No resolution required|\
  The specified RPC is being called and the context properties are being \
    displayed.  This is a debugging message and preceeds the display of \
    each context property.

RESPONSE_PARAMETERS_DISPLAY=APPC0032I|\
  Response properties from execution of module [{0}], RPC [{1}], and version [{2}] are:|\
  No resolution required|\
  The service logic directed graph has been executed and returned the response properties. \
  This message preceeds the dump of the response properties.  It is used for debugging \
  of service logic and execution problems.

NULL_OR_INVALID_ARGUMENT=APPC0033E|\
  Service {0}:{1} was provided a null (empty) or invalid argument, [{2}] = [{3}]|\
  This is likely an internal error, refer to support for assistance|\
  The indicated service was called, but the specified parameter or argument was either \
    null or empty, or it was invalid.  If it has a value, the value is shown.  If the \
    value is null, the value is shown as 'null'.

PROCESSING_REQUEST=APPC0034I|\
  Service {0}:{1} is processing service [{2}] with request id [{3}]|\
  No resolution required|\
  The indicated application and RPC is processing the specified service request.

INVALID_SERVICE_REQUEST=APPC0035E|\
  Service {0}:{1} received request for service [{2}] but that service is invalid or unknown.|\
  Correct the service request, likely a directed graph issue|\
  The RPC was invoked to process a service request, but the service is not valid.

REGISTERING_SERVICE=APPC0036I|\
  {0} registering service {1} using class {2}|\
  No resolution required|\
  The indicated application service is registering itself with the OSGi container using the \
    indicated java class name.

UNREGISTERING_SERVICE=APPC0037I|\
  {0} unregistering service {1}|\
  No resolution required|\
  The application service is being unregistered from the OSGi container services list.

LOADING_PROVIDER_DEFINITIONS=APPC0038I|\
  {0} IAAS Adapter initializing provider {1} as {2}|\
  No resolution is required|\
  The IAAS adapter is loading the definition of the specified provider from its \
    configuration file.

RESTARTING_SERVER=APPC0039I|\
  {0} IAAS Adapter restart of server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the restart of a server.  The \
    properties that govern the request are echoed immediately following this message.

REBUILDING_SERVER=APPC0040I|\
  {0} IAAS Adapter rebuild of server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the rebuilding of a server.  The \
    properties that govern the request are echoed immediately following this message.

INVALID_SELF_LINK_URL=APPC0041E|\
  {0} IAAS Adapter cannot perform requested service, VM url [{1}] is invalid|\
  Correct the call to the adapter with a valid self-link URL|\
  The IAAS adapter has been called to perform some operation on a virtual machine \
    but the vm_id of the virtual machine is not valid.

SERVER_FOUND=APPC0042I|\
  Located server {0} on tenant [{1}] and in state [{2}]|\
  No resolution required|\
  This message indicates that a service request was made to perform some action on the server \
    and the indicated server was located on the specified tenant.\


STACK_FOUND=APPC0042I|\
  Located stack {0} on tenant [{1}] and in state [{2}]|\
  No resolution required|\
  This message indicates that a service request was made to perform some action on the server \
    and the indicated server was located on the specified tenant.



SERVER_NOT_FOUND=APPC0043E|\
  No server found in provider with self-link URL [{0}]|\
  Correct the server URL|\
  The requested server, identified by its self link URL, could not be found in the provider

SERVER_OPERATION_EXCEPTION=APPC0044E|\
  Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
  Contact support for assistance|\
  An exception was caught while trying to perform the indicated operation on the server. The \
    exception may yield more information about the cause of the error.  This may be because \
    of access security, or the server is in an invalid state, or any number of reasons.  This \
    message should be referred to support for assistance.


STACK_NOT_FOUND=APPC0043E|\
  No stack found in provider with self-link URL [{0}]|\
  Correct the server URL|\
  The requested stack, identified by its self link URL, could not be found in the provider

STACK_OPERATION_EXCEPTION=APPC0044E|\
  Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
  Contact support for assistance|\
  An exception was caught while trying to perform the indicated operation on the stack. The \
    exception may yield more information about the cause of the error.  This may be because \
    of access security, or the stack is in an invalid state, or any number of reasons.  This \
    message should be referred to support for assistance.

MISSING_REQUIRED_PROPERTIES=APPC0045E|\
  One or more properties for [{0}] are missing, null, or empty.  They are:|\
  A request to execute the adapter indicated was made from a directed graph, but the properties \
    of the request that are required by the adapter are missing or do not have a value.  Correct \
    the directed graph to supply the missing properties.|\
  The specified properties for the indicated adapter operation are invalid or missing.

SERVER_ERROR_STATE=APPC0046E|\
  The server [{0}] (id={1}) in tenant {2} is in error state, {3} is not allowed|\
  Destroy and recreate the instance|\
  A request to restart or rebuild a server in an error state was received, but those operations \
    are not allowed on a server in this state.  OpenStack only allows a deletion of a server \
    that is in the error state.

IMAGE_NOT_FOUND=APPC0047E|\
  The image {0} could not be located for {1}.|\
  The image indicated could not be found.  If the operation being requested is a rebuild of \
    a server, then there is no action that can be taken other than to destroy the server and \
    rebuild it using an image that exists.|\
  This is likely caused by an image being deleted after it was used to build a server.  If the \
    request is for a server rebuild, then the image used to create the server was later deleted \
    and no longer exists.  The server cannot be rebuilt, because the image doesnt exist. \
    The server must be deleted and reconstructed using a valid, existing image.

STATE_CHANGE_TIMEOUT=APPC0048E|\
  Time out waiting for {0} with name {1} (and id {2}) to reach one of {3} states, current state is {4}|\
  Recover the resource in whatever means is appropriate|\
  The resource indicated (by name and id) was expected to change it's state (status) to one of the \
    indicated expected states within a specified timeout but the resource did not complete the \
    state change.  It's current state is also shown. This can be caused by any number of factors \
    but is normally a problem or conflict within the IaaS provider (OpenStack).

STATE_CHANGE_EXCEPTION=APPC0049E|\
  Exception {0} waiting for {1} with name {2} (and id {3}) to reach one of {4} states, current state is {5}\n\
    cause={6}|\
  Recover the resource in whatever means is appropriate|\
  The resource indicated (by name and id) was expected to change it's state (status) to one of the \
    indicated expected states within a specified timeout but the resource did not complete the \
    state change.  It's current state is also shown. This can be caused by any number of factors \
    but is normally a problem or conflict within the IaaS provider (OpenStack).

STOP_SERVER=APPC0050I|\
  Server {0} is being stopped...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be stopped.

START_SERVER=APPC0051I|\
  Server {0} is being started...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be started.

RESUME_SERVER=APPC0052I|\
  Server {0} is being resumed...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be resumed from a suspended state.

UNPAUSE_SERVER=APPC0053I|\
  Server {0} is being unpaused...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be unpaused from a paused state.

CONNECTION_FAILED_RETRY=APPC0054E|\
  Connection to provider {0} at identity {1} using tenant name {2} (id {3}) failed, reason={4}, \
    retrying in {5} seconds, attempt {6} of {7}.|\
  The connection to the provider could not be obtained for the indicated reason.  The application \
    controller will retry the attempt to connect to the provider a maximum number of times.  The \
    message contains the amount of time the system will wait to retry the connection, and the \
    current attempt and the maximum number of attempts.|\
  Correct the cause of the connection failure as indicated by the reason.

CONNECTION_FAILED=APPC0055E|\
 Connection to provider {0} at service {1} failed after all retry attempts.|\
 The connection to the named provider at the indicated service URL cannot be opened.  All \
   retries have been exhausted.  The application controller is giving up on the connection and will \
   fail the request.|\
 Correct the cause of the connection failure as indicated by the reason(s) in previous APPC0054E \
   messages.

STOPPING_SERVER=APPC0056I|\
  {0} IAAS Adapter stop server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the server to be stopped.  The \
    properties that govern the request are echoed immediately following this message.

REBUILD_SERVER_FAILED=APPC0057E|\
  Server {0} (id {1}) failed to rebuild, reason {2}|\
  The server rebuild failed for the indicated reason. Correct the cause of the failure and \
    rerun, if applicable.|\
  The adapter has attempted to rebuild the indicated server but the rebuild request has \
    been failed by the provider for some reason.  The reason returned by the provider is \
    included in the message.

PARAMETER_IS_MISSING=APPC0058E|\
  Application {0} graph {1} response did not set the {2} parameter. This parameter is \
    required for synchronization with the controller. Absence of this parameter is assumed \
    to be a failure. Please correct the DG.|\
  The indicated directed graph was called from the application controller but when the \
    graph returned the indicated property was not defined in the return parameters.  The \
    controller requires that property to be defined and set to a value that is used to \
    inform the controller of the outcome of operations in the graph.  Failure to set \
    the required parameter is assumed to be a failure regardless if the graph actually \
    succeeded or not.|\
  Correct the DG to set the specified parameter to a value that is expected and understood \
    by the controller.

PARAMETER_NOT_NUMERIC=APPC0059E|\
  Application {0} graph {1} did not set parameter {2} to a valid numeric value ({3}). \
    Please correct the DG.|\
  The indicated directed graph was called by the application controller and the graph \
    did set the specified property, however the property is not a valid numeric \
    value.  The parameter is used to convey a numeric quantity and the controller \
    cannot convert the value specified to a number. |\
  Correct the DG.

DG_FAILED_RESPONSE=APPC0060E|\
  Application {0} graph {1} completed with failure: error code = {2}, message = {3}|\
  The directed graph indicated was called by the application controller and when \
    the graph returned, an error code was set indicating that the graph failed. This \
    is a message that echoes the results of the graph, and shows the returned error \
    code and message.|\
  Correct the cause of the error.

EXCEPTION_CALLING_DG=APPC0061E|\
  Application {0} received exception {1} attempting to call graph {2}, exception \
    message = {3}|\
  The application controller attempted to call the service logic interpreter (SLI) \
    to execute the indicated graph, but an exception was caught.  The class of the \
    exception is shown, as is the message associated with the exception.  An \
    abbreviated stack trace is also displayed to provide information as to the \
    state of the thread at the time of the exception.|\
  Correct the cause of the exception and rerun.

GRAPH_NOT_FOUND=APPC0062E|\
  Application {0} was unable to locate graph {1}|\
  The application controller attempted to call the service logic interpreter (SLI) \
    to execute the specified graph but the graph does not exist in the SLI database.|\
  Correct the database and install the correct graph.

DEBUG_GRAPH_RESPONSE_HEADER=APPC0063D|\
  Application {0} graph {1} responded with {2} properties|\
  This is a debugging message that is output immediately after the call to the \
    directed graph and before any processing is performed to determine the success \
    or failure of that call.  The heading is output prior to dumping all the parameters \
    that were returned by the graph.|\
  No recovery action is required.

DEBUG_GRAPH_RESPONSE_DETAIL=APPC0064D|\
  {0}:{1} - {2} = {3}|\
  This is a debugging message that is output immediately after the call to the \
    directed graph and before any processing is performed to determine the success \
    or failure of that call.  This message is repeated for each parameter that \
    exists in the return context from the graph.|\
  No recovery action is required.

INVALID_REQUIRED_PROPERTY=APPC0065E|\
  Application {0} request "{1}" was supplied a property "{2}" with the value "{3}" \
    that does not meet the required form(s):|\
  This message indicates that the specified requested operation was passed the \
    specific property named and the property value did not meet the expected \
    format requirements.  For example, if the property is expected to be a \
    numeric quantity and it contains alphabetic characters, or if it is expected \
    to be a URL and it is not valid.  The message also contains a list of one \
    or more regular expressions that were used to validate the input, and which \
    supply the syntax required for the property.|\
  Correct the property and retry.

ATTACHINGVOLUME_SERVER=APPC0068I|\
  {0} IAAS Adapter attaching of volume to server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the attaching of volume to server.  The \
    properties that govern the request are echoed immediately following this message.

DETTACHINGVOLUME_SERVER=APPC0069I|\
  {0} IAAS Adapter detaching of volume from server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the detaching of volume from server.  The \
   properties that govern the request are echoed immediately following this message.

MIGRATING_SERVER=APPC066I|\
  {0} IAAS Adapter migrate of server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the migration of a server.  The \
    properties that govern the request are echoed immediately following this message.

EVACUATING_SERVER=APPC0067I|\
  {0} IAAS Adapter evacuate of server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the evacuation of a server.  The \
    properties that govern the request are echoed immediately following this message.

MIGRATE_SERVER_FAILED=APPC0068E|\
  Server {0} (id {1}) failed to migrate during {2} phase, reason {3}|\
  The server migration failed for the indicated reason. Correct the cause of the failure and \
    rerun, if applicable.|\
  The adapter has attempted to migrate the indicated server but the migration request has \
    been failed by the provider for some reason.  The reason returned by the provider is \
    included in the message.

EVACUATE_SERVER_FAILED=APPC0069E|\
  Server {0} (id {1}) failed to evacuate, reason {2}|\
  The server evacuation failed for the indicated reason. Correct the cause of the failure and \
    rerun, if applicable.|\
  The adapter has attempted to evacuate the indicated server but the evacuation request has \
    been failed by the provider for some reason.  The reason returned by the provider is \
    included in the message.

APPC_TOO_BUSY=APPC0080E|\
  APP-C instance is too busy|\
  The APP-C instance handles too many requests and cannot accept new ones as its internal \
  execution queue is full. The problem can appear when the APP-C instance gets more requests \
  than it can handle simultaneously.|\
  Check the server KPIs for possible performance issues (e.g. insufficient memory, \
  high network latency, slow responsiveness of southbound systems and so on) which can affect \
  the system throughput.

VF_SERVER_BUSY=APPC0081E|\
  Concurrent access to server "{0}"|\
  APP-C currently executes a command on the specified server and cannot accept yet another request \
  for the same one.|\
  Try to resubmit the request at later time.

VF_ILLEGAL_COMMAND=APPC0082E|\
  Server "{0}" does not support command "{1}" in the current state "{2}"|\
  APP-C cannot perform the requested command on the server in the current state as no state transition \
  is defined for that.|\
  Contact support for assistance.

VF_UNDEFINED_STATE=APPC0083E|\
  Server "{0}" cannot handle command "{1}" because of its doubtful state|\
  The resource has undefined working state as result of abnormal termination of a previous command.|\
  Recover the resource in whatever means is appropriate.

APPC_NO_RESOURCE_FOUND=APPC0084E|\
  No resource found with ID "{0}" in A&AI system.|\
  APP-C is unable to resolve the VF details given the instance ID.|\
  Check whether the resource has been deleted (terminated) before.

APPC_EXPIRED_REQUEST=APPC0085E|\
  The request "{0}" for server "{1}" has exceeded its TTL limit of "{2}" seconds|\
  The received expired event won't be handled by APP-C instance. Normally the problem might be \
  related to asynchronous requests arriving to APP-C instance via DMaaP channel.|\
  Try to submit a new request if still relevant.

APPC_WORKFLOW_NOT_FOUND=APPC0086E|\
  Workflow for vnfType = "{0}" and  command = "{1}" not found.|\
  Unable to retrive Workflow related to mention VNF type and command.|\
  Check provided VNF and Command details are correct.

APPC_INVALID_INPUT=APPC0087E|\
  Null vnfId and command provided|\
  Request contains Null vnfId and command|\
  Provided non-null VNF and Command details.

APPC_AUDIT_MSG=APPC0090A|\
  Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" \
  was started at "{4}" and ended at "{5}" with status code "{6}"|\
  Audit detailed msg|\
  Audit detailed msg.

AAI_CONNECTION_FAILED=APPC0106E|\
  APP-C is unable to communicate with A&AI|\
  Connection to A&AI at service {0} failed after all retry attempts.|\
  The connection to the A&AI at the indicated service URL cannot be opened. \
  All retries have been exhausted. APP-C is giving up on the connection and will \
  reject the operation request.|\
  .

AAI_UPDATE_FAILED=APPC0107E|\
  APP-C is unable to update COMPONENT_ID {0} to {1} for reason {2}|\
  The update at the end of the operation wasn't performed as a result of \
  A&AI communication failure or its internal error.|\
  .

AAI_GET_DATA_FAILED=APPC0108E|\
  APP-C is unable to retrieve VF/VFC {0} data for Transaction ID {1} as a \
  result of A&AI communication failure or its internal error.|\
  Operation request will be rejected by APP-C|\
  .

AAI_CONNECTION_FAILED_RETRY=APPC0105W|\
  A&AI at identity {0} using VNF_ID {1} failed, reason={2}, retrying in {3} seconds, attempt {4} of {5}.|\
  The connection to the A&AI could not be obtained for the indicated reason. APP-C will retry to connect \
  to the A&AI. The message contains the retry delay, the current attempt and the maximum number of attempts.|\
  Correct the cause of the connection failure as indicated by the reason.

AAI_DELETE_FAILED=APPC0114E|\
  APP-C is unable to delete COMPONENT_ID {0} for reason {1}|\
  The deletion at the end of the operation wasn't performed as a result of \
  A&AI communication failure or its internal error.|\
  .

AAI_QUERY_FAILED=APPC0115E|\
  Error Querying AAI with vnfID = {0}|\
  Querying AAI for the given vnf id returns failure to APPC|\
  .

VNF_CONFIGURED=APPC0118I|\
  VNF {0} is configured|\
  No resolution is required, this is an informational message|\
  The VNF configuration has been completed.

VNF_CONFIGURATION_STARTED=APPC0116I|\
  VNF {0} is being configured|\
  No resolution is required, this is an informational message|\
  The VNF configuration has been started

VNF_CONFIGURATION_FAILED=APPC0119E|\
  VNF {0} configuration failed for reason {1}|\
  The configuration operation wasn't performed as a result of VNF communication failure or its internal error.|\
  .

VNF_TEST_STARTED=APPC0120I|\
  VNF {0} is being tested|\
  No resolution is required, this is an informational message|\
  The VNF test has been started

VNF_TESTED=APPC0121I|\
  VNF {0} was tested|\
  No resolution is required, this is an informational message|\
  The VNF test has been completed

VNF_TEST_FAILED=APPC0122E|\
  VNF {0} test failed for reason {1}|\
  The test operation wasn't performed as a result of VNF communication failure or its internal error.|\
  .

VNF_NOT_FOUND=APPC0123E|\
  VNF not found with vnf_id {0}|\
  The VNF wasn't found for the given vnf-id.|\
  .

VNF_HEALTHCECK_FAILED=APPC0124E|\
  VNF {0} Healthcheck operation failed, reason {1}|\
  The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
  .

VM_HEALTHCECK_FAILED=APPC0125E|\
  VM {0} Healthcheck operation failed, reason {1}|\
  The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
  .

STOP_SERVER_FAILED=APPC0112E|\
  Server {0} (id {1}) failed to stop during {2} phase, reason {3}|\
  The server stop failed for the indicated reason. Correct the cause of the failure and \
  rerun, if applicable.|\
  The adapter has attempted to stop the indicated server but the stop request has \
  been failed by the provider for some reason. The reason returned by the provider is \
  included in the message.

TERMINATE_SERVER_FAILED=APPC0113E|\
  Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
  The server termination failed for the indicated reason. Correct the cause of the failure and \
  rerun, if applicable.|\
  The adapter has attempted to terminate the indicated server but the migration request has \
  been failed by the provider for some reason. The reason returned by the provider is \
  included in the message.

TERMINATE_STACK_FAILED=APPC0113E|\
  Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
  The server termination failed for the indicated reason. Correct the cause of the failure and \
  rerun, if applicable.|\
  The adapter has attempted to terminate the indicated server but the migration request has \
  been failed by the provider for some reason. The reason returned by the provider is \
  included in the message.

TERMINATING_SERVER=APPC0114I|\
  {0} IAAS Adapter terminate server requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
  properties that govern the request are echoed immediately following this message.


TERMINATING_STACK=APPC0115I|\
  {0} IAAS Adapter terminate stack requested|\
  No resolution required|\
  A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
  properties that govern the request are echoed immediately following this message.

TERMINATE_SERVER=APPC0116I|\
  Server {0} is being terminated...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be terminated.

TERMINATE_STACK=APPC0117I|\
  Stack {0} is being terminated...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be terminated.

MIGRATE_COMPLETE=APPC0118I|\
  Migrate {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
  No resolution is required, this is an informational message|\
  APP-C Migrate Operation has completed.

RESTART_COMPLETE=APPC0119I|\
  Restart {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
  No resolution is required, this is an informational message|\
  APP-C Restart Operation has completed.

REBUILD_COMPLETE=APPC0120I|\
  Rebuild {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
  No resolution is required, this is an informational message|\
  APP-C Rebuild Operation has completed.

CLOSE_CONTEXT_FAILED=APPC0121E|\
  Exception {0} was caught attempting to close provider context for {1}.|\
  Contact support for assistance|\
  An exception was caught while trying to close the provider context. The \
    exception may yield more information about the cause of the error.  This may be because \
    of access security, or the server is in an invalid state, or any number of reasons.  This \
    message should be referred to support for assistance.

SNAPSHOTING_STACK=APPC0122I|\
  Stack {0} is being snapshoted...|\
  No resolution is required|\
  Stack snapshot.

STACK_SNAPSHOTED==APPC0123I|\
  Stack {0} snapshoted, snapshot ID = [{1}].|\
  No resolution is required|\
  Stack snapshoted successfully.


RESTORING_STACK=APPC0124I|\
  Stack {0} is being restored to snapshot {1}...|\
  No resolution is required|\
  Stack restore.

STACK_RESTORED=APPC0125I|\
  Stack {0} is restored to snapshot {1}.|\
  No resolution is required|\
  Stack restored successfully.

MISSING_PARAMETER_IN_REQUEST=APPC0126E|\
  Parameter {0} is missing in svc request of {1}.|\
  Check DG node definition to pass missing parameter's value.|\
  Node definition in DG missing indicated parameter value or value is incorrect, \
  check the graph definition.

CANNOT_ESTABLISH_CONNECTION=APPC0127E|\
  Cannot establish connection to server {0} port {1} with user {2}.|\
  Check server IP, port and user credentials.|\
  Wrong data sent in request's payload.


APPC_METRIC_MSG=APPC0128I|\
  Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" on "{4}" with action "{5}" \
  ended in {6} ms with result "{7}"|\
  No resolution is required, this is an informational message|\
  This message indicates that the APPC logged some operation to metric

 SNAPSHOTING_SERVER=APPC0129I|\
{0} IAAS Adapter create snapshot of server requested|\
No resolution is required, this is an informational message|\
This message indicates that a IAAS Adapter create snapshot of server was requested.

INPUT_PAYLOAD_PARSING_FAILED = APPC0130E|\
   Failed to parsing the input payload: {0}|\
   Please provide correct input string for parsing.|\
  .

APPC_EXCEPTION = APPC0132E|\
  Error occurred for VNF type : {0}, reason {1}|\
  Runtime exception thrown by APPC.|\
  .

SSH_DATA_EXCEPTION = APPC0133E|\
  SSH Data Exception occurred, reason {0}|\
  SSH Data exception occurred.|\
  .

JSON_PROCESSING_EXCEPTION = APPC0134E|\
  Json processing exception occurred, reason {0}|\
  Json processing Exception|\
  .

SUCCESS_EVENT_MESSAGE = APPC0136I|\
  Operation {0} succeed for {1}|\
  Success message.|\
  .
DEPENDENCY_MODEL_NOT_FOUND = APPC0137E|\
  Dependency model not found for VNF type {0}, reason {1}|\
  Please provide dependency model|\
  .

INVALID_DEPENDENCY_MODEL = APPC0138E|\
  Invalid Dependency model for VNF Type {0}, reason {1}|\
  Invalid dependency model found |\
  .


FAILURE_RETRIEVE_VNFC_DG = APPC0139E|\
  Failed to retrieve DG for VNFC Type: {0}|\
  Failed to retrieve VNFC DG |\
  .


SERVER_NETWORK_ERROR=APPC0140E|\
  Server {0} either has a port {1} that is NOT online, or the status of the network to which the port is connected to is not ACTIVE|\
  Please ensure they are UP and running before requested operation|\
  It is critical that the VM Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
  the requested operation on it.
  .

REBUILD_SERVER=APPC0140I|\
  Server {0} is being rebuilt...|\
  No recovery required|\
  The processing being performed by APPC requires that the indicated server be rebuilt.

HYPERVISOR_DOWN_ERROR=APPC0141E|\
  Hypervisor {0} for the Server {1} is either NOT ENABLED, or its status is DOWN or UNKNOWN|\
  Please ensure the Hypervisor is UP and running before proceeding with the requested operation|\
  It is critical that the Hypervisor that manages the Virtual Machine for the Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
  the requested operation on it.
  .

HYPERVISOR_STATUS_UKNOWN=APPC0158E|\
  Unable to determine the status of the Hypervisor for the Server {0} |\
  Please ensure the userid has privileges enabled to query for the Hypervisor status. |\
  If you wish to proceed with the requested operation, either obtain the privileges from the Cloud provider, or skip the Hypervisor check and retry the request.
  .

HYPERVISOR_NETWORK_ERROR=APPC0142E|\
  Hypervisor {0} for the Server {1} is NOT Reachable by APPC for initiating the requested operation|\
  Please ensure the Hypervisor is connected to the network before proceeding with the requested operation|\
  It is critical that the Hypervisor that manages the Virtual Machine for the Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
  the requested operation on it.

EVACUATE_SERVER_REBUILD_FAILED=APPC0143E|\
  Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
  The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
    run a rebuild, if applicable.|\
  The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
    been failed by the provider for some reason.  The reason returned by the provider is \
    included in the message.

RESTART_APPLICATION=APPC0144I|\
  Application on server {0} is being restarted...|\
  No recovery required|\
  The processing being performed by APPC requires that the application on the indicated server be restarted.

START_APPLICATION=APPC0145I|\
  Application on server {0} is being started...|\
  No recovery required|\
  The processing being performed by APPC requires that the application on the indicated server be started.

APPLICATION_RESTART_FAILED=APPC0146E|\
  Restart application operation failed on server : {0}, reason {1}|\
  Restart application operation failure.|\
  Correct the cause of the failure as indicated by the reason. 

APPLICATION_START_FAILED=APPC0147E|\
  Start application operation failed on server : {0}, reason {1}|\
  Start application operation failure.|\
  Correct the cause of the failure as indicated by the reason. 

LOOKING_SERVER_UP=APPC0148I|\
{0} IAAS Adapter looking up for the server requested|\
No resolution is required, this is an informational message|\
This message indicates that a IAAS Adapter lookup of server was requested.

EVACUATE_SERVER_REBUILD_FAILED=APPC0149E|\
  Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
  The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
    run a rebuild, if applicable.|\
  The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
    been failed by the provider for some reason.  The reason returned by the provider is \
    included in the message.

APPLICATION_STOP_FAILED=APPC0150E|\
  Stop application operation failed on server : {0}, reason {1}|\
  Stop application operation failure.|\
  Correct the cause of the failure as indicated by the reason.

STOP_APPLICATION=APPC0151I|\
  Application on server {0} is being stopped...|\
  No recovery required|\
  The processing being performed by APPC requires that the application on the indicated server be stopped.

LCM_OPERATIONS_DISABLED=APPC0152E|\
  APPC LCM operations have been administratively disabled|\
  No recovery required|\
  This is a indication that the APPC LCM operations are disabled.

OAM_OPERATION_EXCEPTION=APPC0153E|\
  Application {0} received exception {1} while attempting to execute oam operation {2}, exception message = {3}|\
  The application controller attempted to perform an OAM operation \
    but an exception was caught.  The class of the \
    exception is shown, as is the message associated with the exception.  An \
    abbreviated stack trace is also displayed to provide information as to the \
    state of the thread at the time of the exception.|\
  Correct the cause of the exception and rerun.

OAM_OPERATION_ENTERING_MAINTENANCE_MODE=APPC0154W|\
  Application {0} is {1}|\
  No recovery required|\
  The APPC will no longer accept new LCM requests. Previously accepted LCM requests will be allowed to complete.

OAM_OPERATION_MAINTENANCE_MODE=APPC0155W|\
  Application {0} is in {1}|\
  No recovery required|\
  The APPC is not accepting new LCM requests and all previously accepted LCM requests have completed.

OAM_OPERATION_STARTING=APPC0156I|\
  Application {0} is {1}|\
  No recovery required|\
  The APPC has initiated its startup procedure. Its internal components are coming online.  Once completed it will start accepting LCM requests.

OAM_OPERATION_STARTED=APPC0157I|\
  Application {0} is {1}|\
  No recovery required|\
  The APPC will now accept new LCM requests for processing.

INVALID_STATE_TRANSITION=APPC0158E|\
  A {1} API is not allowed when {0} in the {2} state|\
  No recovery required|\
  The Operation requested cannot be performed as per the current state of APPC.

OAM_OPERATION_STOPPING=APPC0159W|\
  Application {0} is {1}|\
  No recovery required|\
  The APPC has initiated its stop procedure. Its internal LCM bundles are stopping.

OAM_OPERATION_STOPPED=APPC0160W|\
  Application {0} is {1}|\
  No recovery required|\
  The APPC LCM bundles have now stopped.

REQUEST_HANDLER_UNAVAILABLE=APPC0161E|\
  Application {0} was unable to find the Request Handler service |\
  The application controller attempted to get a handle on Request Handler service \
    but was unable to locate it in  the OSGi Service Registry.|\
  Verify if the Request Handler bundle is running.

OAM_OPERATION_RESTARTING=APPC0162W|\
  Application {0} is {1}|\
  No recovery required|\
  The APPC has initiated its restart procedure. Its internal LCM bundles are stopping and will then start again.

OAM_OPERATION_RESTARTED=APPC0163W|\
  Application {0} is {1} for restart|\
  No recovery required|\
  The APPC LCM bundles have been restared (stopped and then started).

OAM_OPERATION_INVALID_INPUT=APPC0162E|\
  {0}|\
  No recovery required|\
  Fix the input parameter and retry.

IAAS_UNSUPPORTED_IDENTITY_SERVICE=APPC0163E|\
  Unsupported identity service version, unable to retrieve ServiceCatalog for identity service {0}|\
  Verify the identity url provided is correct. Currently supported version of the OpenStack identity servicer\
    are v2 and v3. If a support for a new version in required contact development.|\
  This message indicates that a request was made to connect to an unsupported version of \
    identity service.

SFTP_TRANSFER_FAILED=APPC0164E|\
  Sftp data transfer failed on connection to host {0} with user {1} for {2} operation, reason : {3}|\
  Correct the cause of the failure as indicated by the reason and retry.|\
  This message indicates that a failure occured during data transfer over sftp connection.\
    The reason returned by the target instance is included in the message.

SSH_CONNECTION_TIMEOUT=APPC0165E|\
  Ssh session with host {0} has timed out during command {1} execution|\
  Check connection to host and validate executed command.|\
  The APPC tried to execute ssh command on specified host, and the execution took longer time than expected.

SSH_SESSION_CONFIG_ERROR=APPC0166E|\
  Could not configure existing ssh session, reason: {0}|\
  Correct the cause of the failure as indicated by the reason.|\
  This message indicates that additional configuration for already opened ssh session has failed.\
    The reason returned by the session provider is included in the message.