This commit adds the functionality of masakari-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.
Change-Id: I17c79af15eca5f6da7e32dbedbdc392c97114d42
Story: 2003657
Task: 26140
This change adds hooks for pulling in plugins for
Interoperable recovery method customization taksflow
by configuring the actions in terms of execution order,
extra parameters to execute commands in action.
Implements: blueprint recovery-method-customization
Change-Id: I8150935ce0a4e592bd0f87bb3c7b3e599cefa033
Adds below things for the implementation of framework for registering and
using default policy rules.
* Policy-in-code
The framework for registering and using default policy rules.
Rules should be defined and returned from a module in
masakari/policies/, and then added to the list in masakari/policies/__init__.py.
A new context.can() method has been added for policy enforcement of
registered rules. It has the same parameters as the enforce() method
currently being used.
* Add policy sample generation
The entry point and config file necessary for using the
oslo.policy sample generation script. It also adds a tox target to
simplify the usage of it.
* Add policy documentation and sample file
Documentation and sample file for default policy in code feature.
* Hacking check for policy registration
It ensures that policy registration happens in the centralized
masakari/policies/ directory.
* Hacking check for _ENFORCER.enforce()
Hacking check in order to ensure that only registered policies
are used for authorization checks _ENFORCER.authorize should be used rather
than _ENFORCER.enforce.
* Add entry_point for oslo policy scripts
There are two helper scripts in oslo.policy to help deployers understand
their policy configuration better. With the setup.cfg entry these can be
called directly from oslo.policy.
Changes done here are with the reference of [1] at NOVA side
which is contributed by Andrew Laski and Claudiu Belu
[1] https://review.openstack.org/#/q/topic:bp/policy-in-code+project:openstack/nova+status:merged
Change-Id: If885a66d92c31be440d27d6780635800a0b12e3e
As per community goal [1], this patch allows deploying
masakari-api with uwsgi.
NOTE:
This patch takes reference from the nova implementation of deploying
nova-api with uwsgi.
[1] https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
Change-Id: I469d4b6df49ad3489722feae0b795c20a6a3913b
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: Ieecf7342152cc813ec3585a3b1873ac0dc13d804
Added base NotificationDriver and TaskFlowDriver which will implement
NotificationDriver for procesing the notification workflows such as
host-failure, instance-failure and process-failure.
Change-Id: I2d12681bd26b5b1fb2535732d9f3c08ec2409d7a
Added masakari-engine service using oslo_service framework. Added
MasakariManager class which will handle RPC calls related to
notifications.
Change-Id: Ifd704cf452ceb4ece2867ca8fba3f94fbb94aa42
This patch will add following notification apis:
1] GET /v1/notifications
2] GET /v1/notifications/<notification_uuid>
3] POST /v1/notifications
Change-Id: Id2d2b8ba5c372b21a5b0df4f1e4db9054e55831f
Host controller will allow user to do CRUD operations on hosts.
Added authorize policy for host controller methods as these are
going to be called by admin only.
Change-Id: I9871d4163d13bddfa49e6ee5f532de641711c30e
This patch will allow masakari operators to hit following apis:
1] GET /v1/segments
2] GET /v1/segments/<segment_uuid>
3] POST /v1/segments
4] PUT /v1/segments/<segment_uuid>
5] DELETE /v1/segments/<segment_uuid>
Change-Id: I63b48bfa70db7bfacec1c8431fe48feb7aa4c7ef
Python 3.3 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it also.
Change-Id: I4fc9589b181a8dc2f5879573e39ca7fee6083452
Closes-Bug: #1526170
oslo_config provide a utility for generating sample config files,
which provide more detail about opts, like Minimum/Maximum value
and Allowed values.
After this patch, new config options of masakari code should register
with masakari/conf/opts.py.
Change-Id: I8f2f7e87268498ebee7ca164db1c98ef43c279b0
Added migration scripts for failover segment and host.
User will be able to sync the database with masakari-manage
command.
Change-Id: Ic37e681c6cb1ca6a341a77b738abb0a43a2910c4
Added wsgi framework support to create masakari-api
service using oslo_service framework. Similar to core
openstack projects, config items will be kept at centralized
location.
Refer README.rst to cofigure and run masakari-api service.
Change-Id: Idb0120b8cf3b10642c51b286d82cd0944cad5ca3