openstack
/
blazar
Code Issues Proposed changes
blazar/blazar
History
Masahito Muroi 68d769bf71 Migrate climate namespace to blazar 
Although the Climate project was renamed to Blazar in 2014, the code has
still been using the climate namespace.

This patch moves all code to the blazar directory and allows users and
operators to use the 'blazar' command namespace. The 'climate' namespace
remains O release to allow users of Blazar time to move their own
code to the blazar namespace, but will be removed in P release
development cycle.

Change-Id: Icbe6fab1051aae4ac819982a1fa4f323cb0bf2d0
Partial-Bug: #1662734
 		2017-03-02 09:36:14 +00:00
..
api Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
cmd Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
db Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
manager Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
notification Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
plugins Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
tests Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
utils Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
__init__.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
config.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
context.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
exceptions.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
i18n.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
opts.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
policy.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
states.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00
version.py Migrate climate namespace to blazar 2017-03-02 09:36:14 +00:00