Difference between revisions of "Cartographer Agent Installation"

From Krupczak.org
Jump to: navigation, search
(Future Work)
Line 9: Line 9:
  
 
==Future Work==
 
==Future Work==
 +
 +
* Self installation and deployment
  
 
Self installation and distribution development are in the works.  What does that mean?  Essentially, Cartographer agents will deploy themselves throughout an enterprise as they discover dependencies.  Typically, a deployment is started by first installing Cartographer agents on a handful of Windows and UNIX machines and letting Cartographer agents take care of the rest.
 
Self installation and distribution development are in the works.  What does that mean?  Essentially, Cartographer agents will deploy themselves throughout an enterprise as they discover dependencies.  Typically, a deployment is started by first installing Cartographer agents on a handful of Windows and UNIX machines and letting Cartographer agents take care of the rest.
 +
 +
* Automatic testing and measuring of performance
 +
 +
Cartographer agents will use the dependencies they discover to automatically configure service testing.  When agents measure and detect sub-optimal performance, they will communicate amongst themselves to identify possible causes.  They will do so all without management intervention.
 +
 +
* Additional platform support
 +
 +
Ports to other platforms (e.g. MacOS and other proprietary platforms) are in the planning stages.
 +
 +
* Support for virtualization
 +
 +
Right now, agents run within the context of a machine/OS context w/o regard for virtualization.  Future versions will detect virtual machine dependencies.
  
 
==Supported Platforms and Platform Specific Notes==
 
==Supported Platforms and Platform Specific Notes==

Revision as of 20:00, 21 October 2008

Contents

Overview

There is a single Cartographer agent distribution that encompasses all supported platforms. That is, the single distribution contains binaries, libraries, plugins, and configuration files needed to run on all supported platforms. Files are built using a naming scheme that identifies the platform that they are compiled for.

Home Directory Location

  • UNIX /opt/cartographer
  • Win32/64 c:\program files\cartographer

Future Work

  • Self installation and deployment

Self installation and distribution development are in the works. What does that mean? Essentially, Cartographer agents will deploy themselves throughout an enterprise as they discover dependencies. Typically, a deployment is started by first installing Cartographer agents on a handful of Windows and UNIX machines and letting Cartographer agents take care of the rest.

  • Automatic testing and measuring of performance

Cartographer agents will use the dependencies they discover to automatically configure service testing. When agents measure and detect sub-optimal performance, they will communicate amongst themselves to identify possible causes. They will do so all without management intervention.

  • Additional platform support

Ports to other platforms (e.g. MacOS and other proprietary platforms) are in the planning stages.

  • Support for virtualization

Right now, agents run within the context of a machine/OS context w/o regard for virtualization. Future versions will detect virtual machine dependencies.

Supported Platforms and Platform Specific Notes

Cartographer agents run on the following platforms:

  • Solaris 9+ Sparc/64-bit (-solaris platform suffix)
  • Solaris 9+ on x86 (-solx86 platform suffix)
  • Linux systems containing 2.4+ kernels on x86 (-linux platform suffix)
  • Windows 2000/XP/2003/Vista (-win32 platform suffix)

Notes:

  • Support for 64-bit Windows (win64) is undergoing testing.
  • Testing on 64-bit Linux kernels is underway.
  • A port to MacOS is being contemplated but has not yet been finalized.
  • Ports to neither the iPhone/iPod nor Android have been planned at this time.
  • On Solaris, Cartographer agents are started with init scripts rather than the service management facility
  • The agent distribution contains its own builds of OpenSSL that conform to our platform-specific naming scheme. Doing so makes installation and deployment, as well as upgrading, simpler and more consistent. The current version of OpenSSL shipped with Cartographer is 0.9.8g 19 Oct 2007.
  • On UNIX, we use the native XML libraries; on Windows, we distribute a Windows version of libxml2.
  • On UNIX, we use the native POSIX threading libraries (pthreads); on Windows, we distribute a Windows version of pthreads.

See Also

Personal tools