ariatosca-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARIA-42) Implement full blown mechanism for serializing an operation context
Date Wed, 08 Feb 2017 15:24:42 GMT


ASF GitHub Bot commented on ARIA-42:

Github user mxmrlv commented on a diff in the pull request:
    --- Diff: tests/orchestrator/workflows/executor/ ---
    @@ -106,9 +112,9 @@ def mock_plugin(plugin_manager, tmpdir):
         return plugin_manager.install(source=plugin_path)
    -class MockContext(object):
    +class MockContext(operation.BaseOperationContext):
    -    def __init__(self, *args, **kwargs):
    +    def __init__(self, *args, **kwargs):                                            
               # pylint: disable=super-init-not-called
    --- End diff --

> Implement full blown mechanism for serializing an operation context
> -------------------------------------------------------------------
>                 Key: ARIA-42
>                 URL:
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Dan Kilman
>            Assignee: Maxim Orlov
> The current mechanism at aria/orchestration/workflows/context/ is very
> It serializes/deserializes the context.model and context.resource with hard coded knowledge
of the actual implementation involved and even how they were initialized. Specifically:
> The model storage initialized is always expected to be sqlachemy based with no additional
engine configuration (i.e. only the engine url is used to re-construct the sqlalchemy engine),
similar logic applies to the instantiated sqlalchemy session.
> The resource storage initialized is always the file based resource storage.

This message was sent by Atlassian JIRA

View raw message