RETIRED, further work has moved to Debian project infrastructure
Go to file
2017-06-28 12:44:55 +00:00
doc/source Turn on warning-is-error in sphinx build 2017-06-26 20:17:57 +08:00
tools push initial version 2015-06-04 14:59:34 +02:00
watcherclient Add CLI for Action Plan Cancel 2017-05-31 11:19:20 +00:00
.gitignore Update Watcher CLI documentation 2016-05-27 08:19:17 +00:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:38:13 +00:00
.testr.conf Tidy up 2016-05-24 15:45:12 +02:00
babel.cfg push initial version 2015-06-04 14:59:34 +02:00
CONTRIBUTING.rst push initial version 2015-06-04 14:59:34 +02:00
HACKING.rst Change stackforge to openstack 2015-10-23 16:14:56 +05:30
LICENSE Add license file 2016-07-04 18:04:10 +00:00
README.rst Optimize the link address 2017-04-10 16:15:11 +05:30
requirements.txt Updated from global requirements 2017-06-10 11:48:35 +00:00
setup.cfg Turn on warning-is-error in sphinx build 2017-06-26 20:17:57 +08:00
setup.py Updated from global requirements 2017-03-03 03:09:00 +00:00
test-requirements.txt Updated from global requirements 2017-06-27 12:23:00 +00:00
tox.ini Enable some off-by-default checks 2017-06-23 10:13:40 +08:00

Team and repository tags

image

python-watcherclient

Client for resource optimization service for OpenStack.

OpenStack Watcher provides a flexible and scalable resource optimization service for multi-tenant OpenStack-based clouds. Watcher provides a complete optimization loop-including everything from a metrics receiver, complex event processor and profiler, optimization processor and an action plan applier. This provides a robust framework to realize a wide range of cloud optimization goals, including the reduction of data center operating costs, increased system performance via intelligent virtual machine migration, increased energy efficiency-and more!

Installation

Install the prerequisite packages

On Ubuntu (tested on 14.04-64)

sudo apt-get install python-dev libssl-dev python-pip git-core libmysqlclient-dev libffi-dev

On Fedora-based distributions e.g., Fedora/RHEL/CentOS/Scientific Linux (tested on CentOS 6.5)

sudo yum install python-virtualenv openssl-devel python-pip git gcc libffi-devel mysql-devel postgresql-devel

On openSUSE-based distributions (SLES 12, openSUSE 13.1, Factory or Tumbleweed)

sudo zypper install gcc git libmysqlclient-devel libopenssl-devel postgresql-devel python-devel python-pip

Install the Watcher client

You can install the Watcher CLI with the following command:

sudo pip install python-watcherclient

You can also use the OpenStack client with Watcher (our watcher plugin for OpenStack client is included in the python-watcherclient package). To install it, you have just to run this command:

sudo pip install python-openstackclient

Configuration

Create a creds file containing your OpenStack credentials:

export OS_IDENTITY_API_VERSION=3
export OS_AUTH_URL=http://<your-keystone-server>:5000/v3
export OS_PROJECT_DOMAIN_ID=default
export OS_USER_DOMAIN_ID=default
export OS_USERNAME=admin
export OS_PASSWORD=<your-password>
export OS_PROJECT_NAME=<your-project-name>

Source these credentials into your current shell session:

# source creds

You should be able to launch the following command which gets the list of previously created Audit Templates:

# watcher audittemplate list

or:

# openstack optimize audittemplate list
+--------------------------------+------+----------------------+----------+
| UUID                           | Name | Goal                 | Strategy |
+--------------------------------+------+----------------------+----------+
+--------------------------------+------+----------------------+----------+

You can view the entire list of available Watcher commands and options using this command:

# watcher help

or:

# openstack help optimize

Troubleshootings

If any watcher command fails, you can obtain more details with the --debug option :

# watcher --debug audittemplate list

or:

# openstack --debug optimize audittemplate list

Install the openstack CLI :

# pip install python-openstackclient

Make sure that your Openstack credentials are correct. If so, you should be able to verify that the watcher user has been declared in your Openstack keystone :

# openstack user list

and that the watcher endpoints have been declared as well :

# openstack endpoint list