nVentory 0.5 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News nVentory 0.5 (Default branch)
# 1  
Old 08-26-2008
nVentory 0.5 (Default branch)

nVentory is a Ruby on Rails application to manageinventory in multiple data centers. It can manageserver functionality assignment, customer/serverassignment, racking, and more. It can track whichservers are doing what, and where they are in yourdata centers. It allows you to visualize serverlocations and rack space with GUI tools.License: MIT/X Consortium LicenseChanges:
Ruby and Perl command-line clients were added.Both can gather a bunch of data about a node andregister it with the database. An advanced searchcapability for nodes was implemented, allowingsearching on any aspect of a node (for example,show all nodes with an Intel CPU running CentOS4). The data model was simplified a bit, replacingvarious specific types of grouping with a generic,hierarchical "node group" model.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
NSTRPUSH(5)							File Formats Manual						       NSTRPUSH(5)

NAME
NSTRPUSH - maximum number of STREAMS modules in a single stream VALUES
Failsafe Default Allowed values Recommended values DESCRIPTION
This tunable defines the maximum number of STREAMS modules that can be pushed onto a stream. This provides some protection against run- away processes that might automatically select modules to push onto a stream. It is not intended as a defense against malicious use of STREAMS modules by system users. Most systems do not require more than about three or four modules in a stream. However, there may be some unusual cases where more modules are needed. The default value for this tunable allows as many as 16 modules in a stream, which should be sufficient for even the most demanding installations and applications. Who Is Expected to Change This Tunable? Any customer. Restrictions on Changing Changes to this tunable take effect at next reboot. When Should the Value of This Tunable Be Raised? When the customer needs to push more STREAMS modules in a single stream. What Are the Side Effects of Raising the Value of This Tunable? Might allow run-away applications to unduly consume system resources. When Should the Value of This Tunable Be Lowered? There is no need to lower the tunable value from the default value. What Are the Side Effects of Lowering the Value of This Tunable? Too low of a value might cause network commands to fail. What Other Tunable Should Be Changed at the Same Time as This One? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. Tunable Kernel Parameters NSTRPUSH(5)