Improvements for Orchestrator

Description

PRDE - Story default text according to the team DoR (Definition of Ready)

01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

  • Carol Apps with a huge number of tenants with the app installed:
    • We need to spread the number of tenant in groups to avoid overuse slots in a specific moment and not use them later.
    • The orchestrator should receive how many groups the orchestrator should group the tenants.
    • The cron expression will be used to run it for each group of tenants.
    • Example:
      • Number of groups: 4
      • Number of tenants: 700
      • Cron: sleep 10 minutes
      • Automatically, we can sort it by name.
      • Each group will have a total of 175 tenants.
      • It will wait for the cron expression to run the next group.
      • When it finishes the four groups, it will start over again.
      • Finishing the total number of tenants will take an average of 40 minutes.
  • Carol App with Installation group
    • When running the pipelines for the specified tenant:
      • Read all pipelines without connector group.
        • Run the pipeline as of today.
      • For pipelines with the connector group specified, we should run only when the connector group for the tenant matches the connector group defined on the pipeline.
        • Since today, we don't have the connector group on the manifest of pipelines, we can pass the name of the pipeline and the connector group as a parameter.
  • Instead of defining the cron on the orchestrator, get it from the pipeline's manifest.

04 - WHO CAN USE THIS FEATURE (USER ROLES): Carol Admin
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:

  • Carol Apps with a huge number of tenants with the app installed:
  • Supporting Carol App with Installation group
  • Instead of defining the cron on the orchestrator, get it from the pipeline's manifest.

Activity

Automation for Jira 12 February 2024, 18:44 Jira Internal Users

@Robson Thanael Poffo ,
@Gabriel DAmore Marciano , @Ingo Wagner , @Douglas Coimbra Lopes , @Moises Jose Soares Filho

This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-01-23, 2024-02-12, 2024-03-04, 2024-01-02

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Douglas Coimbra Lopes 12 February 2024, 12:58 Jira Internal Users

@Jonathan Willian Moraes @Chámam Diomede Caires We will wait for the product team’s tests before closing this card.

Automation for Jira 22 January 2024, 19:01 Jira Internal Users

@Robson Thanael Poffo ,
@Jonathan Willian Moraes , @Ingo Wagner , @Douglas Coimbra Lopes

This issue was planned to be delivered until 2024-02-12. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-01-23, 2024-02-12, 2024-01-02

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Ingo Wagner 12 January 2024, 13:10 Jira Internal Users

I am adding one story point because we are adding support to Connector Groups.

Automation for Jira 2 January 2024, 18:33 Jira Internal Users

@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Ingo Wagner , @Douglas Coimbra Lopes

This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-01-22, 2024-01-02

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Automation for Jira 14 December 2023, 13:12 Jira Internal Users

@Robson Thanael Poffo ,

@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-01-02. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-01-02

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.