nVentory 0.6 (Default branch)


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

nVentory is a Ruby on Rails application to manage inventory in multiple data centers. It can manage server functionality assignment, customer/server assignment, racking, and more. It can track which servers are doing what, and where they are in your data centers. It allows you to visualize server locations and rack space with GUI tools. License: MIT/X Consortium License Changes:
The server was upgraded from Rails 2.0.2 to 2.1.1. Support was added for queries on arbitrary associations. This allows you to query nodes based on their datacenter. nVentory now maintains "virtual" assignments for nodes based on the node group hierarchy. This makes working with the node group hierarchy easier. The server now only returns data from the main model by default. This allows you to request all of the nodes in the database once you scale past 1000 nodes or so. A variety of other miscellaneous bugs were fixed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
REST::Application::Routes(3pm)				User Contributed Perl Documentation			    REST::Application::Routes(3pm)

NAME
REST::Application::Routes - An implementation of Ruby on Rails type routes. SYNOPSIS
package MyApp; use base 'REST::Application::Routes'; my $obj = REST::Application::Routes->new(); $obj->loadResource( '/data/workspaces/:ws/pages/:page', => &do_thing, # ... other routes here ... ); sub do_thing { my %vars = @_; print $vars{ws} . " " . $vars{page} . " "; } # Now, in some other place. Maybe a CGI file or an Apache handler, do: use MyApp; MyApp->new->run("/data/workspaces/cows/pages/good"); # prints "cows good" DESCRIPTION
Ruby on Rails has this concept of routes. Routes are URI path info templates which are tied to specific code (i.e. Controllers and Actions in Rails). That is routes consist of key value pairs, called the route map, where the key is the path info template and the value is a code reference. A template is of the form: "/foo/:variable/bar" where variables are always prefaced with a colon. When a given path is passed to "run()" the code reference which the template maps to will be passed a hash where the keys are the variable names (sans colon) and the values are what was specified in place of the variables. The route map is ordered, so the most specific matching template is used and so you should order your templates from least generic to most generic. See REST::Application for details. The only difference between this module and that one is that this one uses URI templates as keys in the "resourceHooks" rather than regexes. METHODS
These are methods which REST::Application::Routes has but its superclass does not. getTemplateVars() Returns a hash whose keys are the ":symbols" from the URI template and whose values are what where matched to be there. It is assumed that this method is called either from within or after "loadResource()" is called. Otherwise you're likely to get an empty hash back. getLastMatchTemplate() This is an alias for "getLastMatchPattern()", since this class is about templates rather than regexes. AUTHORS
Matthew O'Connor <matthew@canonical.org> LICENSE
This program is free software. It is subject to the same license as Perl itself. SEE ALSO
REST::Application, <http://manuals.rubyonrails.com/read/chapter/65> perl v5.10.0 2007-08-09 REST::Application::Routes(3pm)