Jiri Stransky 95e1b2b2c9 Don't print stack trace when resource not found ...

CLI still prints that we don't have logging set up (bug 1218261), but
for resource not found it prints a nice error message instead of a
stack trace. The root cause of the problem was that we don't have
finding of resources by name implemented yet.

Fixes bug 1215433

Change-Id: Iee1444f1ee324eaae499052cd2117475a5154ce3

2013-10-08 10:07:17 +02:00

..

common

Don't print stack trace when resource not found

2013-10-08 10:07:17 +02:00

openstack

Add importutils

2013-07-04 15:30:17 +02:00

tests

Add python bindings for Nodes

2013-10-03 10:05:02 -04:00

v1

Add python bindings for Nodes

2013-10-03 10:05:02 -04:00

__init__.py

Basic project structure

2013-07-01 11:01:17 +02:00

client.py

Merge "Adds tests for client module and refactors"

2013-08-26 12:45:18 +00:00

exc.py

Add exceptions from ceilometerclient

2013-07-08 10:26:52 +02:00

shell.py

Implement a rough CLI foundation

2013-08-22 11:10:38 +02:00