Who can do this (User role)

Data Publisher

Description

I want to import a pipeline created using other ODN instance so that I can use it within my own ODN instance. 

Preconditions

  • zip file representing a result of pipeline export containing DPU templates and configurations of DPU instances and optionally also scheduling rule(s) exists on local file system

How to do it:

  • selects and clicks 'Unified Views' from 'Tools' combo box on main page of internal catalog
    • 'Home' page of ODN/UV is displayed
  • clicks 'Pipelines' in main menu
    • list of all existing pipelines in the system is displayed
    • 'Import pipeline' button is available
  • clicks 'Import pipeline' button
    • 'Pipeline import' dialog is displayed
      • 'Upload file' button is available
    • clicks 'Upload file' button
      • upload dialog for selection of file to be uploaded from local file system is displayed
    • selects exported zip file containing DPU templates and configurations of DPU instances and optionally also scheduling rule(s) from local file system
      • upload dialog is closed
      • name of the zip file is displayed in dedicated field
      • system checks the content of the file after selection
        • if the name of the pipeline imported already exists in the system an error message is displayed 'Pipeline with such name already exists in the system' 
            • 'Import' button is disabled
        • if the DPU instances reference DPUs with older or the same version and there are no missing referenced DPUs
            • list of all DPU templates referenced by the DPU instances of imported pipeline is displayed 
            • empty list of missing or newer DPUs is displayed
            • 'Import' button is available
          • clicks 'Import' button
            • no new DPUs are installed 
            • no existing DPUs are overwritten
            • system creates the pipeline and uses the imported configurations of DPU instances to configure the pipeline, scheduling rule(s) are assigned if the zip file contains any 
            • 'Pipeline import' dialog is closed with message 'Import of the pipeline was successful. No new DPUs were installed and/or updated.'
            • imported pipeline works exactly the same way as it works on the system it was exported from (as long as the system where the pipeline is imported has the same access to external network resources)
        • if the DPU instances reference either DPUs with older, newer or the same version of DPU(s) and there could be also one or more missing referenced DPU(s)
            • list of all DPU templates referenced by the DPU instances of imported pipeline is displayed 
            • list of missing or newer DPUs is displayed
            • 'Import' button is available
          • clicks 'Import' button
            • dialog is opened with warning message: 'There is one or more missing or outdated DPUs, click 'Install/Update' if you agree to install the missing DPU(s) and update the outdated DPU(s) on your system. Click 'Cancel' to abandon pipeline import.'
            • 'Install/Update' button is available
            • 'Cancel' button is available
            • if clicks 'Cancel' button 
              • no installation is performed
              • no import is performed and 'Pipeline import' dialog is closed
            • if clicks 'Install/Update' button
              • import of 3rd level DPU templates is started after all 2nd level DPU templates are resolved 
              • 2nd level DPU templates referenced by DPU instances with newer version are installed replacing the older versions
              • 2nd level DPU templates referenced by DPU instances that do not exist yet are installed as 2nd level DPU templates
              • no 2nd level DPU template referenced by DPU instance(s) with version older than the version of DPU template in current system is installed
              • all existing (not imported) 3rd level DPU templates remain as child DPU templates of replaced parent 2nd level DPU templates
              • all non existing 3rd level DPU templates referenced by DPU instances are installed and created as child DPU templates for corresponding parent 2nd level DPU templates
              • existing 3rd level DPU template referenced by DPU instances are replaced only if the imported 3rd level DPU template has corresponding parent of newer version
              • system creates the pipeline and uses the imported configurations of DPU instances to configure the pipeline, scheduling rule(s) are assigned if the zip file contains any 
              • 'Pipeline import' dialog is closed with message 'Import of the pipeline was successful. All missing and/or outdated DPUs were installed/updated.'
              • imported pipeline works exactly the same way as it works on the system it was exported from (as long as the system where the pipeline is imported has the same access to external network resources)
              • all existing pipelines previously using the older version of DPU(s) work exactly the same way with the newer version of DPU(s)

Notes

83v2