Create 24.2 docs, remove 24.2 features from 24.1 docs #282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
llewellyn-sl
requested review from
jason-seqera,
justinegeffen and
christopher-hakkaart
|
Preview looks good to me, thanks! This PR has been opened based on this branch: #283 but I think we'll have to pin it until Enterprise release. |
justinegeffen
approved these changes
Nov 6, 2024
christopher-hakkaart
requested changes
Nov 7, 2024
|
|
||
| Azure regions are specific geographic locations around the world where Microsoft has established data centers to host its cloud services. Each Azure region is a collection of data centers that provide users with high availability, fault tolerance, and low latency for cloud services. Each region offers a wide range of Azure services that can be chosen to optimize performance, ensure data residency compliance, and meet regulatory requirements. Azure regions also enable redundancy and disaster recovery options by allowing resources to be replicated across different regions, enhancing the resilience of applications and data. | ||
| Seqera Platform relies on an existing Azure Storage and Azure Batch account. You need at least 1 valid Azure Storage account and Azure Batch account within your subscription. |
There was a problem hiding this comment.
Suggested change
| Seqera Platform relies on an existing Azure Storage and Azure Batch account. You need at least 1 valid Azure Storage account and Azure Batch account within your subscription. | |
| Seqera Platform relies on an existing Azure Storage and Azure Batch account. You need at least one valid Azure Storage account and Azure Batch account within your subscription. |
|
|
||
| #### Resource groups | ||
| Azure uses 'accounts' for each service. For example, an [Azure Storage account][az-learn-storage] will house a collection of blob containers, file shares, queues, and tables. While you can have multiple Azure Storage and Azure Batch accounts in an Azure subscription, each compute environment on the platform can only use one of each (one storage and one Batch account). You can set up multiple compute environments on the platform with different credentials, storage accounts, and Batch accounts. |
There was a problem hiding this comment.
Suggested change
| Azure uses 'accounts' for each service. For example, an [Azure Storage account][az-learn-storage] will house a collection of blob containers, file shares, queues, and tables. While you can have multiple Azure Storage and Azure Batch accounts in an Azure subscription, each compute environment on the platform can only use one of each (one storage and one Batch account). You can set up multiple compute environments on the platform with different credentials, storage accounts, and Batch accounts. | |
| Azure uses 'accounts' for each service. For example, an [Azure Storage account][az-learn-storage] will house a collection of blob containers, file shares, queues, and tables. While you can have multiple Azure Storage and Azure Batch accounts in an Azure subscription, each compute environment on Platform can only use one of each (one storage and one Batch account). You can set up multiple compute environments on Platform with different credentials, storage accounts, and Batch accounts. |
Please check these for meaning
|
|
||
| 2. Enter a name for the storage account (e.g., _towerrgstorage_). | ||
| 3. Choose the preferred region (same as the Batch account). | ||
| 4. The platform supports any performance or redundancy settings — select the most appropriate settings for your use case. |
There was a problem hiding this comment.
Suggested change
| 4. The platform supports any performance or redundancy settings — select the most appropriate settings for your use case. | |
| 4. Platform supports any performance or redundancy settings — select the most appropriate settings for your use case. |
| - Enable public access from all networks. You can enable public access from selected virtual networks and IP addresses, but you will be unable to use Forge to create compute resources. Disabling public access is not supported. | ||
| 1. Select **Data protection**. | ||
| 8. Select **Data protection**. | ||
| - Configure appropriate settings. All settings are supported by the platform. |
There was a problem hiding this comment.
Suggested change
| - Configure appropriate settings. All settings are supported by the platform. | |
| - Configure appropriate settings. All settings are supported by Platform. |
| 5. Select **Advanced**. | ||
| 6. For _Pool allocation mode_, select Batch service. | ||
| 7. For _Authentication mode_, ensure _Shared Key_ is selected. | ||
| 8. Select **Networking**. Ensure networking access is sufficient for the platform and any additional required resources. |
There was a problem hiding this comment.
Suggested change
| 8. Select **Networking**. Ensure networking access is sufficient for the platform and any additional required resources. | |
| 8. Select **Networking**. Ensure networking access is sufficient for Platform and any additional required resources. |
| 12. Enter the default **VMs type**, depending on your quota limits set previously. The default is _Standard_D4_v3_. | ||
| 13. Enter the **VMs count**. If autoscaling is enabled (default), this is the maximum number of VMs you wish the pool to scale up to. If autoscaling is disabled, this is the fixed number of virtual machines in the pool. | ||
| 14. Enable **Autoscale** to scale up and down automatically, based on the number of pipeline tasks. The number of VMs will vary from **0** to **VMs count**. | ||
| 15. Enable **Dispose resources** for Seqera to automatically delete the Batch pool if the compute environment is deleted on the platform. |
There was a problem hiding this comment.
Suggested change
| 15. Enable **Dispose resources** for Seqera to automatically delete the Batch pool if the compute environment is deleted on the platform. | |
| 15. Enable **Dispose resources** for Seqera to automatically delete the Batch pool if the compute environment is deleted on Platform. |
| @@ -8,172 +8,116 @@ tags: [azure, batch, compute environment] | |||
| :::note | |||
| This guide assumes you already have an Azure account with a valid Azure Subscription. | |||
| For details, visit [Azure Free Account][az-create-account]. | |||
| Ensure you have sufficient permissions to create resource groups, an Azure Storage account, and an Azure Batch account. | |||
| Ensure you have sufficient permissions to create resource groups, an Azure Storage account, and a Batch account. | |||
There was a problem hiding this comment.
Suggested change
| Ensure you have sufficient permissions to create resource groups, an Azure Storage account, and a Batch account. | |
| Ensure you have sufficient permissions to create resource groups, an Azure Storage account, and an Azure Batch account. |
I would keep this as Azure Batch rather than Batch. It's the first use on this page, and IMO, it isn't as clear. Ignore if you disagree.
|
Closing in favor of #285 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.