| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Both of these are currently being reworked
and it doesn't make much sense to keep them
around in the code tree at this point.
Change-Id: I2fa257ae91d117effccbe6298d29e002a64e08b3
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is first in series of changes that provides separation of flows into
engines and pattens. Patterns define structure, while engine define how
the task should be run according to said structure.
This change adds the basic patterns and a very simple engine that
is able to run flow defined with patterns by converting it to recursive
structure of so-called 'actions'.
For simplicity and ease of review certain major features like
resumption, saving and passing on task results and notifications are
left out for farther changes.
Partially implements blueprint patterns-and-engines
Co-authored-by: Anastasia Karpinska <akarpinska at griddynamics.com>
Change-Id: I68515d8a5b30d5d047bf9beb67cc3e2111175190
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Adjust how import reforming is done to use a function
to reform the import line (after modification).
2. Clean the old copy of taskflow (if it exists) before
placing a new copy in its place, this is very useful
to avoid stale files.
3. Move some constants to be offical global constants.
4. Show exactly what modules are being used from the
containing projects openstack.common.
5. Fix how the distributed flow was breaking imports due
to the location/usage of logbook in that module no
longer being functionally correct.
6. Add a header to each file copied/created that tells
people not to modify them directly.
Change-Id: I6387722e092b93418bd63b722a95a8efcaef788d
|
| |
|
|
|
|
|
| |
- Fix new hacking violations!
- Add more comments!
Change-Id: Ida0c1b6c98a8f45a15985b33529a1f479e595db5
|
| |
|
|
|
|
| |
Hacking rules: H302, H303, H304, H401, H404
Change-Id: I38e62696724a99c5ebe74d95d477999bd91a2c9a
|
| |
|
|
|
|
| |
This was mostly unused modules or local variables.
Change-Id: I39f9598ba8b64101a10f80bae448d27272abeddd
|
| |
|
|
|
|
|
|
| |
The test pip ordering was resulting in the pep8 rules not really
running so this fixes that up and the resulting errors so we can
get a clean run.
Change-Id: Icc27be05cd513c4f04135c7e768007dbf9d07b10
|
| |
|
|
| |
Change-Id: I5ff975bb5ded48a84341efa4ebfdae4bf430ab60
|
| |
|
|
|
|
| |
Use a new rollback accumulator to collect which tasks need to be rolled back
and use that in the ordered workflow code. Move the usage of provides/requires
as functions and just let them be attributes of the flow objects.
|
| | |
|
| |
|