radon-h2020 xopera-opera issues

radon-h2020 / xopera-opera

🔀This is a fork of xOpera, TOSCA compliant orchestrator

Apache License 2.0

0 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Update the fork with the upstream

#18 cankarm closed 3 years ago
0
Project name clash

#17 gcasale closed 3 years ago
3
Adding credentials on xopera SaaS

#16 gcasale closed 3 years ago
5
Validation sometimes doesn't help to locate the bug

#15 gcasale closed 3 years ago
2
Nodetype property definition - Opera 0.6.4

#14 AlexSpart closed 3 years ago
25
Opera 0.6.4 deployment issue

#13 AlexSpart closed 3 years ago
9
Updating the RADON fork of the orchestrator

#12 cankarm closed 3 years ago
0
Input passing into a newly defined relationship type

#11 sydkbc closed 3 years ago
13
Deploying with CSAR.

#10 chinmaya-dehury closed 4 years ago
3
Installing using README.md getting start

#9 gcasale closed 4 years ago
7
Exposure of (un)deployment "sub-steps" via CLI/API (Feature Request)

#8 duelle closed 3 years ago
3
Availability of the Opera parsing functionality for TOSCA files as a (Python) library

#7 duelle closed 3 years ago
10
Missing definition for `tosca.capabilities.EndPoint`

#6 miwurster closed 4 years ago
2
Specify the location of the `.opera` folder (feature)

#5 duelle closed 4 years ago
8
Access deployment IP-addresses via opera

#4 duelle closed 3 years ago
11
Ansible module dependency handling

#3 duelle closed 4 years ago
9
Storing/caching information between deploy and undeploy

#2 duelle closed 3 years ago
11
Files linked to the main TOSCA yaml are not accessible to the orchestrator.

#1 cankarm closed 4 years ago
3