You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is my understanding that deploying from TOSCA YAML files should yield the same result as deploying from a csar.
I can deploy from a csar using turandot service deploy self-contained --file=dist/self-contained.csar
but the command string turandot service deploy self-contained --file=examples/self-contained/self-contained.yaml
results in the service continually toggling between the states of 'Instantiating' and 'Not instantiated'
while the command string turandot service deploy self-contained --directory=examples/self-contained
does not seem to start and service provision process.
Adding -vv did not result in any additional output which might indicate a problem
The text was updated successfully, but these errors were encountered:
More info: the assumption was that puccini-csar, which is currently written in bash, would be converted to Go, which would in turn provide us with an API to use here. It is not clear if this is going to happen anytime soon.
It is my understanding that deploying from TOSCA YAML files should yield the same result as deploying from a csar.
I can deploy from a csar using
turandot service deploy self-contained --file=dist/self-contained.csar
but the command string
turandot service deploy self-contained --file=examples/self-contained/self-contained.yaml
results in the service continually toggling between the states of 'Instantiating' and 'Not instantiated'
while the command string
turandot service deploy self-contained --directory=examples/self-contained
does not seem to start and service provision process.
Adding -vv did not result in any additional output which might indicate a problem
The text was updated successfully, but these errors were encountered: