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?\
+ All retries have been exhausted. APP-C is giving up on the connection and will \
reject the operation request.|\
.
.
AAI_GET_DATA_FAILED=APPC0108E|\
- APP-C is unable to retrieve VF/VFC {0} data for Transaction ID?{1}?as a \
+ 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.?
+ 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}|\
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 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 \
included in the message.
TERMINATING_SERVER=APPC0114I|\
- {0} IAAS Adapter?terminate server requested|\
+ {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|\
+ {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...|\
+ 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...|\
+ Stack {0} is being terminated...|\
No recovery required|\
The processing being performed by APPC requires that the indicated server be terminated.
message should be referred to support for assistance.
SNAPSHOTING_STACK=APPC0122I|\
- Stack {0} is being?snapshoted...|\
+ Stack {0} is being snapshoted...|\
No resolution is required|\
Stack snapshot.
RESTORING_STACK=APPC0124I|\
- Stack {0} is being?restored to snapshot {1}...|\
+ Stack {0} is being restored to snapshot {1}...|\
No resolution is required|\
Stack restore.
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_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_STOPPING=APPC0154W|\
+ Application {0} is stopping... |\
+ No recovery required|\
+ The APPC will no longer accept new LCM requests. Previously accepted LCM requests will be allowed to complete.
+
+OAM_OPERATION_STOPPED=APPC0155W|\
+ Application {0} is stopped|\
+ 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 starting...|\
+ 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 started|\
+ No recovery required|\
+ The APPC will now accept new LCM requests for processing.
+
+
Code Review / appc.git / blobdiff