production: Deploy deposit instance in elastic infra

changed milestone to %Dynamic infrastructure [Roadmap - Tooling and infrastructure]

changed the description

[x] Prepare azure storage account & azure blobstorage

$ terraform plan -target=azurerm_storage_account.deposit-storage -target=azurerm_storage_container.deposit-tarballs -out azure-deposit-resource-creation.production.txt
azurerm_resource_group.euwest-deposit: Refreshing state... [id=/subscriptions/49b7f681-8efc-4689-8524-870fc0c1db09/resourceGroups/euwest-deposit]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # azurerm_storage_account.deposit-storage will be created
  + resource "azurerm_storage_account" "deposit-storage" {
      + access_tier                       = "Cool"
      + account_kind                      = "BlobStorage"
      + account_replication_type          = "LRS"
      + account_tier                      = "Standard"
      + allow_nested_items_to_be_public   = true
      + cross_tenant_replication_enabled  = true
      + enable_https_traffic_only         = true
      + id                                = (known after apply)
      + infrastructure_encryption_enabled = false
      + is_hns_enabled                    = false
      + large_file_share_enabled          = (known after apply)
      + location                          = "westeurope"
      + min_tls_version                   = "TLS1_2"
      + name                              = "swhdepositstorage"
      + nfsv3_enabled                     = false
      + primary_access_key                = (sensitive value)
      + primary_blob_connection_string    = (sensitive value)
      + primary_blob_endpoint             = (known after apply)
      + primary_blob_host                 = (known after apply)
      + primary_connection_string         = (sensitive value)
      + primary_dfs_endpoint              = (known after apply)
      + primary_dfs_host                  = (known after apply)
      + primary_file_endpoint             = (known after apply)
      + primary_file_host                 = (known after apply)
      + primary_location                  = (known after apply)
      + primary_queue_endpoint            = (known after apply)
      + primary_queue_host                = (known after apply)
      + primary_table_endpoint            = (known after apply)
      + primary_table_host                = (known after apply)
      + primary_web_endpoint              = (known after apply)
      + primary_web_host                  = (known after apply)
      + queue_encryption_key_type         = "Service"
      + resource_group_name               = "euwest-deposit"
      + secondary_access_key              = (sensitive value)
      + secondary_blob_connection_string  = (sensitive value)
      + secondary_blob_endpoint           = (known after apply)
      + secondary_blob_host               = (known after apply)
      + secondary_connection_string       = (sensitive value)
      + secondary_dfs_endpoint            = (known after apply)
      + secondary_dfs_host                = (known after apply)
      + secondary_file_endpoint           = (known after apply)
      + secondary_file_host               = (known after apply)
      + secondary_location                = (known after apply)
      + secondary_queue_endpoint          = (known after apply)
      + secondary_queue_host              = (known after apply)
      + secondary_table_endpoint          = (known after apply)
      + secondary_table_host              = (known after apply)
      + secondary_web_endpoint            = (known after apply)
      + secondary_web_host                = (known after apply)
      + shared_access_key_enabled         = true
      + table_encryption_key_type         = "Service"
      + tags                              = {
          + "environment" = "SWH Deposit"
        }
    }

  # azurerm_storage_container.deposit-tarballs will be created
  + resource "azurerm_storage_container" "deposit-tarballs" {
      + container_access_type   = "blob"
      + has_immutability_policy = (known after apply)
      + has_legal_hold          = (known after apply)
      + id                      = (known after apply)
      + metadata                = (known after apply)
      + name                    = "deposit-tarballs"
      + resource_manager_id     = (known after apply)
      + storage_account_name    = "swhdepositstorage"
    }

Plan: 2 to add, 0 to change, 0 to destroy.

$ terraform apply azure-deposit-resource-creation.production.txt
azurerm_storage_account.deposit-storage: Creating...
azurerm_storage_account.deposit-storage: Still creating... [10s elapsed]
azurerm_storage_account.deposit-storage: Still creating... [20s elapsed]
azurerm_storage_account.deposit-storage: Creation complete after 22s [id=/subscriptions/49b7f681-8efc-4689-8524-870fc0c1db09/resourceGroups/euwest-deposit/providers/Microsoft.Storage/storageAccounts/swhdepositstorage]
azurerm_storage_container.deposit-tarballs: Creating...
azurerm_storage_container.deposit-tarballs: Creation complete after 0s [id=https://swhdepositstorage.blob.core.windows.net/deposit-tarballs]
╷
│ Warning: Applied changes may be incomplete
│
│ The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the output values may not
│ be fully updated. Run the following command to verify that no other changes are pending:
│     terraform plan
│
│ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or
│ when Terraform specifically suggests to use it as part of an error message.
╵

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Outputs:

marked the checklist item Prepare azure storage account & azure blobstorage as completed

mentioned in commit swh/infra/ci-cd/swh-charts@3aee1b8d

mentioned in merge request swh/infra/ci-cd/swh-charts!274 (merged)

changed the description

mentioned in commit swh/infra/ci-cd/swh-charts@16251b02

There is a bug when using python3.7, all paths have been stripped from client_x (for x a number) to nt_x... Of course, i can't seem to find the button to rename that... And anyway, i need to fix that behavior to allow the run to be incremental... Bref, i'll double check this tomorrow.

Fixed.

Migration started back.

mentioned in commit swh/devel/snippets@2d635557

mentioned in commit swh/devel/snippets@0f7a2c1b

production: Deploy deposit instance in elastic infra

Designs

Child items ...

Activity