test

Sun N1 Service Provisioning System 5.2 System Administration Guide

Configuring Logs for Deployments

When you run a plan, you deploy components to remote agents within the provisioning system. You have the ability to view which components are being created or deleted by setting your log configuration file to log when an event occurs. If components are unaffected by a deployment, you can be notified that the system has optimized the deployment by only deploying resources that need to be updated or removed. When you set the configuration file to notify you about how your deployment has been optimized, the log displays the files that were not overwritten.

Each message type has two versions: info and debug. The info message typically describes what happened to each file, while the debug message describes what happened to each file and why it happened.

ProcedureHow to Configure Your Remote Agent Logs

Steps

  1. In the N1SPS-RemoteAgent-home/agent/config/logger_config.xml file, add the appropriate code.

    Note –

    These logger changes must be added to the logger_config.xml file after the appender section and before the root section.

    The level value can equal error, warn , info or debug. The debug option provides a more verbose output.

    • Log when a differential deployment creates a component


      <logger name="com.sun.n1.sps.resource.deploy.filechanges.actual.creates">
                <level value="info"/>
                <appender-ref ref="STDOUT"/>
</logger>

    • Log when a differential deployment deletes a component


       <logger name="com.sun.n1.sps.resource.deploy.filechanges.actual.deletes">
                <level value="info"/>
                <appender-ref ref="STDOUT"/>
</logger>

    • Log differential deployment optimizations


      <logger
name="com.sun.n1.sps.resource.deploy.filechanges.actual.optimizations">
                <level value="debug"/>
                <appender-ref ref="STDOUT"/>
/logger>

  2. Run a plan using the differential deployment feature.

  3. View the messages in the N1SPS-RemoteAgent-home/agent/bin/cr_agent.out file.

    The following example shows that the file /tmp/test/file3 existed on the remote agent and was updated with a newer version. First the file was deleted, then the new version was created.


    com.sun.n1.sps.resource.deploy.filechanges.actual.deletes
(DeployLogger.java:83) - file /tmp/test/file3 is being deleted. (020613)
2006-02-02 15:16:33,950 INFO  [ROX:ThrPool:1:NetPool-Worker-3]
com.sun.n1.sps.resource.deploy.filechanges.actual.creates
(DeployLogger.java:83) - file /tmp/test/file3 is being created. (020605)

ProcedureHow To Configure The Master Server Log

To check the status of the master server , edit the logger_config.xml file.

Step

    Edit the root entry in N1SPS-MasterServer-home/server/config/logger_config.xml file by editing the code as shown below. Additional information will be generated and output in the master server log file cr_server.out. This can viewed at N1SPS-MasterServer-home/server/bin/cr_server.out. The MS log file cr_server.out can be viewed through the browser interface by clicking on the View Log button.


    <root>
					<priority value="debug" />
					<appender-ref ref="STDOUT" />
</root>