Search Engine: Elastic

Article ID: 130901, created on Jun 1, 2017, last review on Jun 29, 2017

  • Applies to:
  • Operations Automation 7.1

Dependencies and Pre-Requisites

  • Odin Automation Premium 7.1 or later
  • Updates https://kb.odin.com/en/130968 and https://kb.odin.com/en/130969 must be installed before Azure upgrade to prevent incorrect invoices
  • If the operating system of the old Azure Endpoint Server is a non-English installation, verify the date and number settings as per the following article: #130872 Azure CSP 4.1 import fails with "invalid input syntax" during the upgrade process.

Fixed Issues

  • APSA-18228 Account name with Cyrillic symbols is replaced with "?????" in Azure Portal
  • APSA-18189 Azure operations failed: org.postgresql.util.PSQLException: FATAL: remaining connection slots are reserved for non-replication superuser connections
  • APSA-18239 Setting budget_cap_settings.enabled_daily_notification may be ignored on Tenant when customer has several billing periods passed
  • APSA-18285 Price list for different instances are shown with improper currency

Upgrade

Important: Upgrade is supported from versions 3.2.4/3.2.5 and 4.1 only. The upgrade instructions for these version branches are different.

Upgrade from 3.2.4/3.2.5 version:

Requirements

Terms

  • Source endpoint node – old endpoint node on Windows with Azure CSP Integration version 3.2.4/3.2.5.
  • Target endpoint node – new endpoint node on Linux with Azure CSP Integration version 4.2.
  • export.ps1 – export script. It is run on the source endpoint node and exports all the data from the source endpoint node. The exported data is packed in a ZIP file. The export script performs the following actions:

    • Validation checks.
    • Stops the website for application instance, and disables its auto-start.
    • Exports database into CSV files.
    • Gathers additional data used by import and needed for resource schema changes.
    • Makes ZIP archive with exported data.
  • import.py – import script. It imports all the exported data to the target endpoint node. It is run on management node. The import script performs the following actions:

    • Validation checks.
    • Extracts ZIP archive.
    • Imports data into new database.
    • Starts the APS application instance upgrade (through OA Operations task) and waits for completion.
    • Removes temporary database tables.

Upgrade Procedure

  1. Deploy the Azure application endpoint host following all steps in the section Azure CSP Integration 4.1 Provider's Guide >> Deploying and Configuring Azure CSP Integration > Deploying 'Azure' Application > Deploying Azure Application Endpoint.

    Downtime starts. Azure services downtime depends on hardware performance and is approximately 1-2 hours per 1000 subscriptions plus 10 minutes on manual operations.

  2. If the operating system of the old Azure Endpoint Server is a non-English installation, verify the date and number settings as per the following article: #130872 Azure CSP 4.1 import fails with "invalid input syntax" during the upgrade process.

  3. Export data.

    1. Copy the export script (export.ps1) to the source node. The script is located in the Azure 4.2 distribution package. (For example, you have copied it into c:).
    2. On the source node, run the script in the PowerShell console. The required parameters: name of the IIS website of the Azure Integration 3.2.4/3.2.5 endpoint node and path for the ZIP file with exported data.

      Important: Before running the script, once again check that there are no Azure-related tasks in Odin Automation.

      The example for the default instance:

      c:\export.ps1 -azureSiteName "Azure Cloud Solution Provider - Internal" -outputZipFile c:\azure-export.zip
      
  4. Import data.

    Note: The import script has the -h option to print the usage help.

    1. Copy the ZIP file with the exported data from the source endpoint node to the target endpoint node (remember the path you copied it to, for example, /root/azure-export.zip).
    2. On management node, unzip the distribution package to the software root directory with files replace. For example:

      unzip -d /usr/local/ -o odin-azure-distr-4.2.x.zip
      
    3. On management node, run the import script (import.py) from the software root directory (default is /usr/local). The required parameters: service node ID, where the target endpoint is installed (provider control panel > Infrastructure > Service Nodes), Azure APS instance ID (In PCP, go to Services > Applications > > Instances tab) and path on the target endpoint node, where the ZIP file is copied to.

      The example:

      python azure/deployment/import.py --host=<NODE_ID> --instance=<INSTANCE_ID> --data=<PATH>
      
  5. Post upgrade configuration. Azure CSP Integration 4.2 requires additional global configuration because of the new functionality and changes in API for managing Microsoft Azure.

    1. In provider control panel, go to Services > Applications > > Instances tab.
    2. Click on the name of the migrated instance and then go to Configuration tab and click Edit.
    3. Enter the required information (refer to the Azure CSP Integration 4.1 Provider's Guide >> Deploying and Configuring Azure CSP Integration > Deploying 'Azure' Application > Creating 'Azure' Application Instance).

    Downtime ends.

  6. In Billing panel, remove the 'aps_defaults_azure' parameter in all Azure service templates. (Go to Products > Service Plans > Service Templates tab > > Service Parameters tab).
  7. In Billing panel, set the SHOW_APPLICATION_SERVICE_PARAMETERS of the 'Buy Azure CSP' screen to 'true'. (Go to Products > Online Store > Screens tab).
  8. In Billing panel, synchronize the online store. (Go to Products > Online Store and click Synchronize Now).
  9. In provider control panel, reapply a brand used for the Online Store. (Go to System > Settings > Brands > [brand name], click Edit, and click Submit.)

Notes:

  1. Starting from Azure CSP Integration 4.1, several application instances may be served with the single endpoint website. The upgrade supports such configuration: you can import the data from multiple application instances of Azure CSP Integration 3.2.4/3.2.5. You do not need new nodes in this case, only do repeat steps for exporting, importing, and post configuration.

  2. Upgrade does not export/import Partner Admin Password. This is to avoid saving unencrypted sensitive data into ZIP file, and transferring it over unknown channels between source and target endpoint nodes. Provider must enter this password in the application instance configuration along with other additional sensitive settings.

  3. Keep the source node and ZIP file for a while, do not remove it. They keep original data and may be useful for upgrade troubleshooting. Remove them when no issues found for some time.

Upgrade from 4.1 version:

  1. Copy the package to the endpoint node and perform the following commands:

    #unzip -o -d /usr/local /root/odin-azure-distr-4.2.8.zip
    #cd /usr/local/azure
    #python deployment/setup.py upgrade
    
  2. Copy the package to the management node and perform the following commands:

    #unzip -o -d /usr/local /root/odin-azure-distr-4.2.8.zip
    #cd /usr/local/azure
    #python deployment/setup.py upgrade
    

    If the command fails with the error "The application is not installed.", take the "AzureCloudSolutionProvider-4.2-8.app.zip" package from the "/usr/local/azure" directory and import it manually into Odin Automation via "Services / Applications" section in PCP. Then proceed with the next step.

  3. Upgrade instance.

    Important: If there is more than one instance on the node, run the instance upgrade sequentially, that is one by one.

Help Resources

Azure Cloud Solution Provider Integration guides are available here: http://download.automation.odin.com/poa/azurecsp/4.1/.

All Azure Cloud Solution Provider Integration Release Notes

Supported APS Application Packages Versions in Odin Automation

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF