New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Binding reqs with caps #1

Open

jsoldani opened this issue Jan 16, 2019 · 0 comments

Member

jsoldani commented Jan 16, 2019

The prototype is currently assuming that the given TOSCA YAML files are such that each requirement of each node template indicates

the name of the node template satisfying such requirement (through the field node of the requirement assignment), and
the name of the capability satisfying such requirement (through the field capability of the requirement assignment).

E.g.,

requirements:
    - endpoint:
        node: backend_api
        capability: endp
    - endpoint
        node: utils_api
        capability: endp

(with backend_api and utils_api both offering a capability named endp)

This is needed to permit deriving the binding between reqs & caps, needed to analyse the management of an app with management protocols

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment