quattor / ncm-query

Node Configuration Manager CLI for Querying Profile

ncm-query

Front end for querying the NCM profile configuration

Basic usages:

ncm-query --component <component>
ncm-query /some/path
ncm-query --list

ncm-query's Issues

ncm-query may only be run as root even if the profile is readable by the user

Removing the restriction causes an exception when trying to open a file:

Uncaught exception!!! Calling stack is:
  LC::Exception::throw_error called at /opt/edg/lib/perl/EDG/WP4/CCM/Configuration.pm line 141
  EDG::WP4::CCM::Configuration::_create_pid_file called at /opt/edg/lib/perl/EDG/WP4/CCM/Configuration.pm line 105
  EDG::WP4::CCM::Configuration::new called at /opt/edg/lib/perl/EDG/WP4/CCM/CacheManager.pm line 221
  EDG::WP4::CCM::CacheManager::_getConfig called at /opt/edg/lib/perl/EDG/WP4/CCM/CacheManager.pm line 165
  EDG::WP4::CCM::CacheManager::getUnlockedConfiguration called at bin/ncm-query line 231
  query::setCCMConfig called at bin/ncm-query line 409
*** _touch_file(/var/lib/ccm/profile.33/ccm-active-profile.33-13892): open (/var/lib/ccm/profile.33/ccm-active-profile.33-13892): Permission denied
Uncaught exception!!! Calling stack is:
  LC::Exception::throw_error called at bin/ncm-query line 233
  query::setCCMConfig called at bin/ncm-query line 409
*** cannot get configuration via CCM

useprofile command line option does not work as documented

See quattor/CCM#38 - ncm-query uses Cachemanager::getUnlockedConfiguration() but @stdweird says that an UnlockedConfiguration always gives the latest CID. Therefore if CID is not undef then it must use a LockedConfiguration?

ncm-query to support different output formats

Sometimes it is necessary for programs to run ncm-query directly to lookup information in the current host profile. Unfortunately, the output of ncm-query is not so easy for a computer to parse.

The contents of a host profile are easy to get hold of from within an NCM component, but problematic when running a tool that is not an NCM component.

I suggest there are multiple ways of tackling this, and we might provide all of them:

• ncm-query --format native that outputs the profile, or portions of the profile, in whatever the native format is (XML or JSON, depending on what is being used).
• ncm-query --format json that outputs the profile, or portions thereof, in JSON.
• ncm-query --format xml for XML format.
• ncm-query --format yaml for YAML format.
• Perl API that allows a non-NCM component to get hold of a configuration hash similar to that passed through to the Configure subroutine in an NCM component (this isn't an ncm-query issue, but I thought I'd put it here to keep things all together for discussion at first).