18 Commits

Author SHA1 Message Date
Hieu LE
4469cacf39 Implement policy in code - event trigger (11)
This commit migrate all event trigger policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

This commit also remove policy.json file usage completely.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: Icd674fdc248e5b9c63f9e7d0f47c53288291ff07
2017-11-27 02:47:50 +00:00
Hieu LE
c73fb88c01 Implement policy in code - workflow (10)
This commit migrate all workflow policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: I8ab332abb5ebd4c67f8baf62c43ac3e9a10d7ee1
2017-11-27 02:47:42 +00:00
Hieu LE
0f6241b031 Implement policy in code - workbook (9)
This commit migrate all workbook policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: I267a528322cdf69f132503112bb7124ec882ce80
2017-11-27 02:47:35 +00:00
Hieu LE
643da24ff2 Implement policy in code - service and task (8)
This commit migrate all service and task policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: I20e9be2705a41931309b5da4f114715485d1797e
2017-11-27 02:47:29 +00:00
Hieu LE
3c999d01b2 Implement policy in code - member (7)
This commit migrate all member policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: I166d0d62489fa8230a2ba34ef09f9366ac321633
2017-11-27 02:47:21 +00:00
Hieu LE
d2274af9a2 Implement policy in code - execution (6)
This commit migrate all execution policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>
Closes-Bug: #1723333
Change-Id: I3e1d9f5b61d9f2511190fb810726aeb22912ad7b
2017-11-27 02:47:11 +00:00
Hieu LE
518066b019 Implement policy in code - environment (5)
This commit migrate all environment policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: I97307ad7f4c01d9b78ddf1b4cda8e59e736a7831
2017-11-27 02:47:03 +00:00
Hieu LE
22ff1ad400 Implement policy in code - cron trigger (4)
This commit migrate all cron trigger policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: Ib877e4ac6ebfe4068e85705955923d162757689f
2017-11-27 02:46:56 +00:00
Hieu LE
e32fa68bcb Implement policy in code - action (3)
This commit migrate all action policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: I2ced708b492026c7561cdfc417c43cfa0e4bb503
2017-11-27 02:46:49 +00:00
Hieu LE
33407d6f44 Implement policy in code - action execution (2)
This commit migrate all action execution policies into code [1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com>

Change-Id: Ic4b597995ae2ab49e793871c14060f0b9662f468
2017-11-27 02:46:42 +00:00
Dai Dang Van
49ed570cfe Implement policy in code (1)
This commit prepare for implementing policies in code[1].

Like oslo.config, with oslo.policy, we can define all of
default rules in code base and only change some rules
via policy file. Another thing that we should use yaml
format instead of json format.

[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Co-authored-By: Hieu LE <hieulq@vn.fujitsu.com>
Change-Id: I2051b6c25333c95aa9ea6786964d4ab710ea93e8
2017-11-27 02:46:32 +00:00
Nikolay Mahotkin
7d8d4fba82 Allow to list all cron-triggers
Closes-Bug: #1707942

Change-Id: Ia69972493a070aac4d413e27b26b02f6c60b19de
2017-08-01 18:39:59 +03:00
Nikolay Mahotkin
e780ffb06d [Event-triggers] Allow public triggers
* Allowed creating via API
 * Added the corresponding processing
   in the event engine
 * Corresponding test

Closes-Bug: #1704111

Change-Id: I73a1d10fe684f1ec962e42e9700064d06cb0bcbe
2017-07-26 12:21:21 +03:00
Nikolay Mahotkin
c430a4620b Fix get event triggers
* Added get event triggers for all projects
   and the corresponding rule in policy.json
 * Fixed corresponding policy rule names for
   event triggers API

Change-Id: I74e65a1cee8d074cfd637e460465922b610237c5
2017-07-11 12:46:58 +03:00
Lingxian Kong
965db538aa Role based resource access control - get workflows
We already supported role based api access control, this series patches
will implement resource access control for mistral, so that
administrator could define the rules of resource accessibility, e.g.
admin user could get/delete/update the workflows of other tenants
according to the policy.

TODO:
- Implement update workflow by admin
- Implement delete workflow by admin
- Implement for other resources(workfbook/execution/task/action, etc.)

Partially implements: blueprint mistral-rbac

Change-Id: I8b00e8a260a74457ad037ee7322a7cba9ae34fab
2016-12-22 14:12:33 +13:00
Dawid Deja
b1937191ee Delete unnecessary comma
Change-Id: I7049ec25870a148a78d619eb39c90d032a287af4
Closes-bug: 1623414
2016-09-14 12:14:16 +02:00
Lingxian Kong
4e1e358c8b Add event trigger REST API
This patch adds the Mistral changes to support the new event trigger
REST API.

Change-Id: I8190ce81d46cc8296db29f41442354cdfe1a5bbd
Implements: blueprint event-notification-trigger
Co-Authored-By: Lingxian Kong <anlin.kong@gmail.com>
2016-09-13 22:39:36 +12:00
hardik
11e443efeb Added role base authentication support
Mistral api access can be restricted base on role
by modifying /etc/mistral/policy.json file.

Change-Id: I4c78ca4cc04d25f46aea55948bce339cfe460ff0
Implements: blueprint mistral-customize-authorization
2016-06-14 05:15:00 +00:00