Modified items

All recently modified items, latest first.

Products.RPMDistro-livecd-4.8.1-1.lbn13.noarch: Create live-CD/DVD's using RPMDistro

Products.RPMDistro-instance-4.8.1-1.lbn13.noarch: Deploy within Zope on port 8080

Products.RPMDistro-fam-4.8.1-1.lbn13.noarch: rpmbuilderd is a daemon that monitors the rpmdbtree for any changes and notifys RPMBuilder so that it's always synced with what's on the filesystem. This is very useful if you're using command-line tools or remotely syncing RPMBuilder installations.

Products.RPMDistro-4.8.1-1.lbn13.noarch: HTTP RedHat/SuSE Studio-style Package Manager distribution builder server. Full-featured SRPM package building tool which also creates custom installers and integrates with yum-based builder/packager build and deploy suites.

Products.BastionSubscriber-4.2.2-1.lbn13.noarch: Advanced subscription-based user management, billing and pricing.

Products.BastionMail-quota-4.0.4-2.lbn13.noarch: MailQuota allocations

Products.BastionMail-mail-4.0.4-2.lbn13.noarch: BastionBox/BastionContact skins

Products.BastionMail-list-4.0.4-2.lbn13.noarch: BastionList skins

Products.BastionMail-devel-4.0.4-2.lbn13.noarch: Products.BastionMail development suite

Products.BastionMail-4.0.4-2.lbn13.noarch: A range of web tools that control Courier Mail applications. This package also contains the import AuthCourier patch for SpamAssassin which is necessary for virtual mail account integration with SpamAssassin.

Products.BastionHosting-4.0.3-2.lbn13.noarch: Web Control Panel for Apache, Bind to allow you to configure and manage these services. In addition, these are integrated within our BastionHosting suite to automagically interact when clients add products requiring these features.

Products.BastionGraph-4.0.7-2.lbn13.noarch: matplotlib/networkx wrappers for Zope/Plone

Products.BastionBase-ldap-4.4.0-5.lbn13.noarch: Role management into LDAP/PAS

Products.BastionBase-4.4.0-5.lbn13.noarch: Wrappers to isolate ourselves from Zope source code changes with which we disagree. A set of utility functions to manage Zope installations Useful base classes (Archetypes wrappers) and tools for Plone (timezone tool)

MySQL_python-1.2.3-5.lbn13.x86_64: MySQLdb is an interface to the popular MySQL database server for Python. The design goals are: * Compliance with Python database API version 2.0 [PEP-0249] * Thread-safety * Thread-friendliness (threads will not block each other) MySQL-3.23 through 5.0 and Python-2.3 through 2.7 are currently supported. Python-3.0 will be supported in a future release.

MySQL_python-1.2.3-5.lbn13.armv6hl: MySQLdb is an interface to the popular MySQL database server for Python. The design goals are: * Compliance with Python database API version 2.0 [PEP-0249] * Thread-safety * Thread-friendliness (threads will not block each other) MySQL-3.23 through 5.0 and Python-2.3 through 2.7 are currently supported. Python-3.0 will be supported in a future release.

Plone: BastionLinux/Plone manual page

Chef: BastionLinux/Chef on Amazon Marketplace

Zope and Plone: BastionLinux/Plone on Amazon Marketplace

ZenPacks.lbn.ZopeMonitor-4.2.5_4.0.4-1.lbn13.noarch: ZopeMonitor ------------- ZopeMonitor provides a method for pulling performance metrics from a Zope Application Server (http://www.zope.org/) directly into Zenoss. It is necessary to first install the munin.zope eggs from pypi.python.org or our own repo at http://linux.last-bastion.net/LBN/up2date/monitor, and to have wget installed on this server. The monitor works by utilising ZenCommand to run wget on the local system - you do not need to make zope ports available through your firewall. The munin plugins do require a user with 'View Management Screens' access at the root however. This is configured using the zZopeURI zProperty of the device. This parameter uses Extended HTTP Authentication to specify user credentials, host and port. Note that the host is the hostname on the remote instance and should probably remain 'localhost' unless you've explicitly bound your Zope to a NIC. Note that the munin plugins expect to be installed on a Unix-like operating system with a /proc filesystem. The following metrics will be collected and graphed for the Zope Server. * Threads (only if you set up munin.zope on target - see code) o Free threads o Total threads * Cache o Total objects o Total objects in memory o Targe number * ZODB Activity o Total connections o Total load count o Total store count * Memory Utilisation o VmHWM - peak resident set size ("high water mark") o VmExe - size of text segments o VmStk - size of stack segments o VmPeak - peak virtual memory size o VmData - size of data segments o VmLck - locked memory size o VmPTE - page table entries size o VmLib - shared library code size o VmRSS - resident set size Once your Zope Server has the munin plugins installed, you can add Zope monitoring to the device within Zenoss by simply binding the ZopeMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the ZopeMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Zope Server metrics from this device.

« Previous 20 items Next 20 items » 1 ... 2240 2241 2242 2243 2244 2245 2246 ... 2359


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items