radon-h2020 radon-delivery-toolchain issues

radon-h2020 / radon-delivery-toolchain

Project listing all delivery toolchain requirements including: RADON orchestrator, Monitoring, Template Library, CI/CD.

Apache License 2.0

0 stars 4 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

R-T5.4-2 The data pipeline module of the Orchestrator must support cron based scheduled data pipelines.

#50 chinmaya-dehury closed 3 years ago
7
R-T5.4-10 Support Google BigQuery data warehouse as a data source when deploying data pipelines.

#49 pjakovits opened 4 years ago
4
R-T5.16 - CI/CD templates

#48 naesheim opened 4 years ago
2
Refactor documentation files and prepare to publish

#47 anzoman closed 4 years ago
0
FR-T5.2-16: Listing versions of a template with template library CLI

#46 neza-vehovar closed 3 years ago
3
FR-T5.2-15: Publishing and retrieving entities with template library CLI

#45 neza-vehovar closed 3 years ago
2
FR-T5.1-13: Orchestrator could support using ssh private keys

#44 anzoman closed 3 years ago
6
FR-T5.2-14: Generating a basic entity with template library CLI

#43 neza-vehovar closed 3 years ago
8
FR-T5.2-13: Template library publishing service should be RADON IAM compliant

#42 neza-vehovar closed 3 years ago
8
FR-T5.1-12: Orchestrator should consider each deployment separately

#41 anzoman closed 3 years ago
5
FR-T5.1-11: xOpera should be able to parse get_artifact TOSCA function

#40 anzoman closed 4 years ago
6
FR-T5.1-10: TOSCA orchestrator could provide a packaging command to prepare CSAR files

#39 anzoman closed 3 years ago
7
FR-T5.3-6: xOpera should support all available TOSCA policy type keywords

#38 anzoman closed 4 years ago
9
FR-T5.2-12: Template library publishing service filtering of entities

#37 neza-vehovar closed 3 years ago
10
FR-T5.3-5: SaaS orchestrator should be IAM compliant and should include proper level of security

#36 anzoman closed 3 years ago
4
FR-T5.1-9: xOpera orchestrator should be available as a service/RADON SaaS component

#35 anzoman closed 3 years ago
3
FR-T5.1-8: xOpera orchestrator should provide the support for compressed CSARs

#34 anzoman closed 4 years ago
5
monitoring tool microsite v1

#33 giopnd closed 4 years ago
0
Praqma cicd

#32 naesheim closed 4 years ago
0
Prepare the initial documentation template files

#31 anzoman closed 4 years ago
1
Allow to link aws layers (by arn) when deploying aws lambda functions

#30 giopnd closed 3 years ago
2
R-T5.5-1: The xOpera command line interface needs to have a dry run mode to verify changes without asking for input in execution

#29 cankarm closed 3 years ago
4
R-T5.1: The TOSCA blueprint must be able to enable Operations Engineers to define the usage of different FaaS/Serverless providers for different parts of their application.

#28 cankarm closed 3 years ago
1
R-T5.3-4: The tool should be able to support configuring automatic scaling of Docker services based on TOSCA auto scaling policies.

#27 cankarm opened 4 years ago
2
R-T5.3-3: The tool must be able to support configuring AWS EC2 auto scaling service based on the TOSCA auto scaling policy.

#26 cankarm opened 4 years ago
2
R-T5.3-2: The tool must be able to configure automatic scaling of the deployed components based on the auto scaling policies defined in the RADON models.

#25 cankarm opened 4 years ago
2
R-T5.3-1: The TOSCA blueprint needs to be able to support the definition of security and privacy policy of specific serverless/FaaS provider.

#24 cankarm closed 3 years ago
3
R-T5.4-9: The data pipeline module of the Orchestrator should support deploying data pipelines expressed using TOSCA models into a private OpenStack cloud.

#23 cankarm closed 4 years ago
5
R-T5.4-8: The data pipeline module of the Orchestrator should support deploying data pipelines expressed using TOSCA models into the AWS data pipeline service.

#22 cankarm closed 3 years ago
3
R-T5.4-7: The data pipeline module of the Orchestrator should support configuring encryption between data pipeline tasks when data needs to be moved between systems

#21 cankarm closed 3 years ago
6
R-T5.4-6: The data pipeline module must support data pipelines tasks that initiate data analytics tasks for processing data moving through the pipeline

#20 cankarm closed 3 years ago
4
R-T5.4-5: The data pipeline module of the Orchestrator should support deployment of data pipelines which automate movement of data between two or more clouds

#19 cankarm closed 3 years ago
3
R-T5.4-4: It would be useful for the data pipeline module of the Orchestrator to support logging and generating alerts on pipeline task failures.

#18 cankarm closed 3 years ago
3
R-T5.4-3: The data pipeline module of the Orchestrator should support event based scheduled data pipelines

#17 cankarm closed 3 years ago
5
R-T5.4-1: The data pipeline module of the Orchestrator must be able to orchestrate data pipelines

#16 cankarm closed 3 years ago
5
R-T5.2-11: Support deployment to microservices architecture

#15 cankarm closed 3 years ago
3
R-T5.2-10: Support deployment to regular VMs

#14 cankarm closed 3 years ago
2
R-T5.2-9: Support of FaaS deployment to Azure cloud platform

#13 cankarm closed 3 years ago
2
R-T5.2-8: Support of FaaS_deployment to Google cloud platform

#12 cankarm closed 3 years ago
2
R-T5.1-7: Support of FaaS deployment to AWS cloud platform

#11 cankarm closed 4 years ago
3
R-T5.1-6: Support of FaaS deployment to OpenFaas

#10 cankarm closed 4 years ago
4
R-T5.1-5: The orchestrator should be able to calculate the diff between the current state and the desired state expressed by a new model version and redeploy only the difference.

#9 cankarm closed 3 years ago
10
R-T5.1-4: At the end of deployment the deployment of services needs to be verified and its dependencies

#8 cankarm closed 3 years ago
7
R-T5.1-3: The runtime toolchain need to provide a status on each stage of deployment of the application on the underlying architecture

#7 cankarm closed 3 years ago
8
R-T5.1-2: A Software Developer describes the application architecture and dependencies at least in TOSCA YAML 1.2

#6 cankarm closed 3 years ago
3
R-T5.1-1: The orchestrator tasks must be executable through CLI

#5 cankarm closed 3 years ago
2
Monitoring example for lambda functions using code injection and pushGateway

#4 giopnd closed 4 years ago
0
**RADON GMT and Orchestrator integration**

#3 cankarm closed 3 years ago
2
Create common repo for delivery toolchain

#2 cankarm closed 3 years ago
0
Add a monitoring example to the GitHub.

#1 cankarm opened 4 years ago
1