radon-h2020/radon-delivery-toolchain issues and pull requests

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

Issue - State: closed - Opened by chinmaya-dehury over 4 years ago - 7 comments
Labels: Data Pipelines

#49 - R-T5.4-10 Support Google BigQuery data warehouse as a data source when deploying data pipelines.

Issue - State: open - Opened by pjakovits over 4 years ago - 4 comments
Labels: Data Pipelines, WP5

#48 - R-T5.16 - CI/CD templates

Issue - State: open - Opened by naesheim over 4 years ago - 2 comments
Labels: CI/CD, WP5

#47 - Refactor documentation files and prepare to publish

Pull Request - State: closed - Opened by anzoman over 4 years ago

#46 - FR-T5.2-16: Listing versions of a template with template library CLI

Issue - State: closed - Opened by neza-vehovar over 4 years ago - 3 comments
Labels: Template Library

#45 - FR-T5.2-15: Publishing and retrieving entities with template library CLI

Issue - State: closed - Opened by neza-vehovar over 4 years ago - 2 comments
Labels: Template Library

#44 - FR-T5.1-13: Orchestrator could support using ssh private keys

Issue - State: closed - Opened by anzoman over 4 years ago - 6 comments
Labels: Orchestrator

#43 - FR-T5.2-14: Generating a basic entity with template library CLI

Issue - State: closed - Opened by neza-vehovar over 4 years ago - 8 comments
Labels: Template Library

#42 - FR-T5.2-13: Template library publishing service should be RADON IAM compliant

Issue - State: closed - Opened by neza-vehovar over 4 years ago - 8 comments
Labels: Template Library

#41 - FR-T5.1-12: Orchestrator should consider each deployment separately

Issue - State: closed - Opened by anzoman over 4 years ago - 5 comments
Labels: Orchestrator

#40 - FR-T5.1-11: xOpera should be able to parse get_artifact TOSCA function

Issue - State: closed - Opened by anzoman over 4 years ago - 6 comments
Labels: Orchestrator

#39 - FR-T5.1-10: TOSCA orchestrator could provide a packaging command to prepare CSAR files

Issue - State: closed - Opened by anzoman over 4 years ago - 7 comments
Labels: Orchestrator

#38 - FR-T5.3-6: xOpera should support all available TOSCA policy type keywords

Issue - State: closed - Opened by anzoman over 4 years ago - 9 comments
Labels: Orchestrator, COULD

#37 - FR-T5.2-12: Template library publishing service filtering of entities

Issue - State: closed - Opened by neza-vehovar over 4 years ago - 10 comments
Labels: SHOULD, Template Library

#36 - FR-T5.3-5: SaaS orchestrator should be IAM compliant and should include proper level of security

Issue - State: closed - Opened by anzoman over 4 years ago - 4 comments
Labels: Orchestrator

#35 - FR-T5.1-9: xOpera orchestrator should be available as a service/RADON SaaS component

Issue - State: closed - Opened by anzoman over 4 years ago - 3 comments
Labels: Orchestrator

#34 - FR-T5.1-8: xOpera orchestrator should provide the support for compressed CSARs

Issue - State: closed - Opened by anzoman over 4 years ago - 5 comments
Labels: Orchestrator

#33 - monitoring tool microsite v1

Pull Request - State: closed - Opened by giopnd over 4 years ago

#32 - Praqma cicd

Pull Request - State: closed - Opened by naesheim over 4 years ago

#31 - Prepare the initial documentation template files

Pull Request - State: closed - Opened by anzoman over 4 years ago - 1 comment

#30 - Allow to link aws layers (by arn) when deploying aws lambda functions

Issue - State: closed - Opened by giopnd over 4 years ago - 2 comments

#29 - 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

Issue - State: closed - Opened by cankarm almost 5 years ago - 4 comments
Labels: Orchestrator, WP5, COULD

#28 - 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.

Issue - State: closed - Opened by cankarm almost 5 years ago - 1 comment
Labels: MUST, WP5

#27 - R-T5.3-4: The tool should be able to support configuring automatic scaling of Docker services based on TOSCA auto scaling policies.

Issue - State: open - Opened by cankarm almost 5 years ago - 2 comments
Labels: Orchestrator, WP5, SHOULD

#26 - R-T5.3-3: The tool must be able to support configuring AWS EC2 auto scaling service based on the TOSCA auto scaling policy.

Issue - State: open - Opened by cankarm almost 5 years ago - 2 comments
Labels: Orchestrator, SHOULD, Template Library

#25 - 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.

Issue - State: open - Opened by cankarm almost 5 years ago - 2 comments
Labels: Orchestrator, SHOULD

#24 - 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.

Issue - State: closed - Opened by cankarm almost 5 years ago - 3 comments
Labels: MUST, WP5

#23 - 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.

Issue - State: closed - Opened by cankarm almost 5 years ago - 5 comments
Labels: Data Pipelines, MUST, Orchestrator, WP5

#22 - 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.

Issue - State: closed - Opened by cankarm almost 5 years ago - 3 comments
Labels: Data Pipelines, MUST, Orchestrator, WP5

#21 - 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

Issue - State: closed - Opened by cankarm almost 5 years ago - 6 comments
Labels: Data Pipelines, MUST, Orchestrator, WP5, SHOULD

#20 - 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

Issue - State: closed - Opened by cankarm almost 5 years ago - 4 comments
Labels: Data Pipelines, MUST, Orchestrator

#19 - 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

Issue - State: closed - Opened by cankarm almost 5 years ago - 3 comments
Labels: Data Pipelines, Orchestrator, SHOULD

#18 - 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.

Issue - State: closed - Opened by cankarm almost 5 years ago - 3 comments
Labels: Data Pipelines, Orchestrator, WP5, SHOULD

#17 - R-T5.4-3: The data pipeline module of the Orchestrator should support event based scheduled data pipelines

Issue - State: closed - Opened by cankarm almost 5 years ago - 5 comments
Labels: Data Pipelines, Orchestrator, WP5

#16 - R-T5.4-1: The data pipeline module of the Orchestrator must be able to orchestrate data pipelines

Issue - State: closed - Opened by cankarm almost 5 years ago - 5 comments
Labels: Data Pipelines

#15 - R-T5.2-11: Support deployment to microservices architecture

Issue - State: closed - Opened by cankarm almost 5 years ago - 3 comments
Labels: MUST, WP5, Template Library

#14 - R-T5.2-10: Support deployment to regular VMs

Issue - State: closed - Opened by cankarm almost 5 years ago - 2 comments
Labels: MUST, Orchestrator, WP5

#13 - R-T5.2-9: Support of FaaS deployment to Azure cloud platform

Issue - State: closed - Opened by cankarm almost 5 years ago - 2 comments
Labels: MUST, WP5, Template Library

#12 - R-T5.2-8: Support of FaaS_deployment to Google cloud platform

Issue - State: closed - Opened by cankarm almost 5 years ago - 2 comments
Labels: Orchestrator, WP5, Template Library

#11 - R-T5.1-7: Support of FaaS deployment to AWS cloud platform

Issue - State: closed - Opened by cankarm almost 5 years ago - 3 comments
Labels: MUST, Orchestrator, Template Library

#10 - R-T5.1-6: Support of FaaS deployment to OpenFaas

Issue - State: closed - Opened by cankarm almost 5 years ago - 4 comments
Labels: MUST, Orchestrator, Template Library

#9 - 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.

Issue - State: closed - Opened by cankarm almost 5 years ago - 10 comments
Labels: Orchestrator, SHOULD

#8 - R-T5.1-4: At the end of deployment the deployment of services needs to be verified and its dependencies

Issue - State: closed - Opened by cankarm almost 5 years ago - 7 comments
Labels: CTT, MUST, Orchestrator, CI/CD

#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

Issue - State: closed - Opened by cankarm almost 5 years ago - 8 comments
Labels: Monitoring, MUST, Orchestrator, WP5

GitHub / radon-h2020/radon-delivery-toolchain issues and pull requests