Search results

R-xtable-1.7.1-4.lbn25.noarch

Coerce data to LaTeX and HTML tables.

meminfo-1.0.2-3.lbn25.noarch

meminfo was born out of a need to report large system memory usage in some meaningful way. ps and top have their uses, as do others, but they have two problems (in my opinion): 1) they don't show URES (unique resident size) 2) the information they provide is of limited value once you start having 1000+ processes on a multi-user system meminfo fills the gap (or aims to at least). Tested on 2.6 kernels and one 2.4 system (debian 3.1) --------------------------- meminfo is Copyright 2006 Aleksandr Koltsoff. meminfo is released under the GPLv2 in the hopes that it may be of use to other people (please see the accompanying COPYING file, or if the file is missing [bad!] you can find it at http://www.gnu.org/licenses/gpl.txt). --------------------------- generates three lists according to real memory usage: - first is sorted by URES per process - second one groups processes according to usernames and sorts that based on ures - third groups based on process names and again sorts based on total ures - fourth is optional and depends whether you have SMP-system or not tries to group memory and runtimes according to logical CPUs if you don't have SMP (enabled), you won't see the fourth report and the first report will be missing the C#-field (CPU that last executed a process). For explanation on URES, please see http://koltsoff.com/pub/ures/ For feedback and patches, please contact me via czr(at)iki(dot)fi while including 'meminfo' in the subject.

rubygem-hiera-3.4.2-1.lbn25.noarch

A pluggable data store for hierarcical data.

rubygem-hiera-aws-parameter-store-0.1.0-1.lbn25.noarch

Configuration hiera-aws-parameter-store configuration is quite simple. It uses default AWS connection and the following parameters: prefix : prefix used to find parameters in AWS Parameter Store. Mandatory. max_results : maximum number of results per AWS Parameter Store request. Default value is 50 (which is the maximum at 2017-01-21). Here is a sample hiera.yaml: --- :backends: - aws_parameter_store :aws_parameter_store: :prefix: puppet. :max_results: 50 :logger: console AWS credentials You need AWS credentials in order to access to AWS Parameter Store. The following policy shows you the required permissions: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ssm:DescribeParameters" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "ssm:GetParameters" ], "Resource": "arn:aws:ssm:{region}:{account}:parameter/{prefix}*" } ] } where: region: AWS region in which parameters are stored. account: your AWS account. prefix: prefix for those parameters you want to access from Hiera. E.g. if you want to organize your parameters starting with puppet., you have to use this as prefix. As an example, you can have parameters like: puppet.myapp.version. Conversions between AWS Parameter Store and Hiera types In AWS Parameter Store are present the following types: String: if the parameter name does not contains dots (.), the resulting hiera object is a String with parameter's value. If it contains dots, it's splitted and converted into a hash of objects with the last element as a string. String List: Converted into an array. Secure String: Not compatible yet. Examples: myappname=MyAppName (String) -> hiera('myappname') = "MyAppName" (String) myapp.name=MyAppName (String) myapp.version=1.3 (String) -> hiera_hash('myapp') = {"name"=>"MyAppName","version"=>"1.3"} (Hash) mylist=e1,e2,e3 (String List) -> hiera('mylist') = ["e1","e2","e3"] myapp.name=MyAppName (String) myapp.list=1,2,3 (String List) -> hiera_hash('myapp') = {"name"=>"MyAppName","list"=>["1",

rubygem-hiera-eyaml-2.1.0-1.lbn25.noarch

Hiera backend for decrypting encrypted yaml properties.

rubygem-hiera-eyaml-kms-0.1-1.lbn25.noarch

AWS KMS encryptor for use with hiera-eyaml.

rubygem-hiera-http-eyaml-0.9.0-1.lbn25.noarch

Fork of the Hiera HTTP backend with eYAML support.

rubygem-hiera-vault-0.2.2-1.lbn25.noarch

Hiera backend for looking up secrets stored in Vault.

zope-Record-3.4-1.lbn19.noarch

Special Record objects used in Zope2.

Products.AddRemoveWidget-1.5.0-3.lbn25.noarch

This is a replacement for KeywordWidget which permits you to add items from a vocabulary (and optionally new items) using a pair of selection boxes with "add" and "remove" buttons to transfer items between them. It overlaps in functionality with InAndOutWidget, but does not suffer from InAndOut's requirement for all items in the "target" list to be selection upon form submission. I believe InAndOut does not allow textual items to be added by the user, though it does support adding of referenced objects, which AddRemove does not. You are advised to test both to find out which one is more suitable for your needs. Please see the docstring in AddRemoveWidget.py for a list of options you may pass to the widget to configure it. You can also use the widget standalone, by defining a couple of variables (notably fieldName and vocabulary) and include the macro add_remove_box from widget_addremove.pt. See the comment in that file for details. Also included is a ComboBoxWidget - it can be seen as supporting the same use case, when only one item may be selected. It presents a selection box from which to select a value, and a text box to enter an "other" value if none of the items in the list are sufficient. Again, see the docstring in ComboBoxWidget.py, and the comment in widget_combobox.pt for details on how to use it within and outside Archetypes.