Skip to content

Commit e09d34d

Browse files
committed
Changes from #285392 comments by @denrea
1 parent 96d02ea commit e09d34d

37 files changed

+295
-137
lines changed

articles/modeling-simulation-workbench/concept-chamber.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 01/01/2023
1111
---
1212
# Chambers in the Azure Modeling and Simulation Workbench
1313

14-
In the Azure Modeling and Simulation Workbench, chambers are a security boundary for a group virtual machines (VM) (nodes) and share common users. A chamber provides a full-featured and secure environment for users to run engineering applications and workloads together in isolation. chamber VMs are all on the same subnet and have no internet access.
14+
In the Azure Modeling and Simulation Workbench, chambers are a security boundary for a group virtual machines (VM) (nodes) and share common users. A chamber provides a full-featured and secure environment for users to run engineering applications and workloads together in isolation. Chamber VMs are all on the same subnet and have no internet access.
1515

1616
## Key features
1717

articles/modeling-simulation-workbench/concept-data-pipeline.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,22 +18,22 @@ The data pipeline enables users to bring data into the [chamber](./concept-chamb
1818

1919
## Importing data overview
2020

21-
Users with access to the chamber can bring data into the chamber via AzCopy and an expiring SAS URI token they get from the chamber component. They then use AzCopy to move data into the data pipeline endpoint. The chamber recognizes the data pipeline request and moves the file into the chamber. For traceability purposes, when a file is moved into the chamber, the data pipeline automatically creates a file object in the chamber that represents the file data.
21+
Users with access to the chamber can bring data into the chamber via AzCopy and an expiring SAS URI token they get from the chamber component. They then use AzCopy to move data into the data pipeline endpoint. The chamber recognizes the data pipeline request and moves the file into the chamber. For traceability purposes, when a file is moved into the chamber, the data pipeline automatically creates a file object in the chamber that represents the file data.
2222

2323
## Exporting data overview
2424

2525
Users with access to the chamber can export data from the chamber via the data pipeline.
2626

27-
1. **Identify file to export.** The export process is triggered when a user places a file to export into a designated area within the chamber. A chamber Admin or chamber User copies the file to the data out folder within the pipeline. The data pipeline detects the copied file and creates a file object. The file creation activity is traceable in the logs and enables the next step of the data pipeline.
27+
1. **Identify file to export.** The export process is triggered when a user places a file to export into a designated area within the chamber. A chamber Admin or chamber User copies the file to the data out folder within the pipeline. The data pipeline detects the copied file and creates a file object. The file creation activity is traceable in the logs and enables the next step of the data pipeline.
2828

29-
1. **Request file to export.** A chamber Admin reviews files staged in the data pipeline and requests to export. The pipeline manager creates a file request object. The export request activity is traceable in the logs and enables the next step of the data pipeline.
29+
1. **Request file to export.** A Chamber Admin reviews files staged in the data pipeline and requests to export. The pipeline manager creates a file request object. The export request activity is traceable in the logs and enables the next step of the data pipeline.
3030

3131
1. **Approve/reject export request.** The Workbench Owner either approves or rejects the export file request. Only a Workbench Owner can approve or reject requests. The individual who approves or denies can't be the same person who initially requested the export.
3232

3333
1. **Download file.** If a file is approved for export, the user gets a download URI from the file request object and copies it out of the chamber using AzCopy. The URI has an expiration timestamp and must be downloaded before it expires. If the URI expires, you need to request a new download URI.
3434

35-
> [!NOTE]
36-
> Larger files take longer to be available to download after being approved and to download using AzCopy. Check the expiration on the download URI and request a new one if the window has expired.
35+
> [!NOTE]
36+
> Larger files take longer to be available to download after being approved and to download using AzCopy. Check the expiration on the download URI and request a new one if the window has expired.
3737
3838
## Next steps
3939

articles/modeling-simulation-workbench/concept-license-service.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,21 +12,19 @@ ms.date: 01/01/2023
1212

1313
# License service: Azure Modeling and Simulation Workbench
1414

15-
A license service automates the installation of a license manager to help customers accelerate their engineering design. A license service is integrated into Azure Modeling and Simulation Workbench.
15+
A license service automates the installation of a license manager to help customers accelerate their engineering design. A license service is integrated into Azure Modeling and Simulation Workbench.
1616

1717
## Overview
1818

1919
Engineering design tools are widely used across industries to enable design teams to run their flows efficiently. Many of these proprietary software programs require licenses. License management is integrated into our flows via the most commonly used license manager, FLEXlm.
2020

2121
Here's how the license service works:
2222

23-
- For each deployed chamber within the workbench, we set up a license server and expose the FLEXlm HostID's to procure licenses.
24-
- Users request tool licenses for the specific HostID.
25-
- Once the license file is received from the tool vendor, users import it to enable the license service.
23+
For each deployed chamber within the workbench, we set up a license server and expose the FLEXlm HostID's to procure licenses. Users then request tool licenses referencing the specific HostID. Once the license file is received from the tool vendor, users import it to the chamber license server to enable the license service.
2624

2725
## Additional information
2826

29-
For silicon EDA, our service automation deploys license servers for each of the four common software vendors (Synopsys, Cadence, Siemens, and Ansys) as part of resource creation to enable multi-vendor flows. The workbench also supports license service beyond these common EDA tool vendors with some manual configuration.
27+
For silicon Electronic Design Automation (EDA), our service automation deploys license servers for each of the four common software vendors (Synopsys, Cadence, Siemens, and Ansys) as part of resource creation to enable multi-vendor flows. The workbench also supports license service beyond these common EDA tool vendors with some manual configuration.
3028

3129
This flow is extendible and can also include other software vendors across industry verticals."
3230

articles/modeling-simulation-workbench/concept-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Storage: Azure Modeling and Simulation Workbench"
3-
description: Types of storage.
3+
description: Types of storage offered in Modeling and Simulation Workbench.
44
author: yousefi-msft
55
ms.author: yousefi
66
ms.service: modeling-simulation-workbench
@@ -31,7 +31,7 @@ The data pipeline file structure has two directories: `/mount/datapipeline/datai
3131

3232
### Chamber Storage
3333

34-
Chamber Storage is the high-performance, high-capacity storage solution for use within chambers. Based on Azure NetApp Files, it's available in two high-performance tiers, and dynamically scalable after creation. chamber Storage can be accessed at `/mount/chamberstorages` where a different directory exists for each created volume. Volumes are sizable in 4 TB increments up to the user's subscription quota.
34+
Chamber Storage is the high-performance, high-capacity storage solution for use within chambers. Based on Azure NetApp Files, it's available in two high-performance tiers, and dynamically scalable after creation. Chamber Storage can be accessed at `/mount/chamberstorages` where a different directory exists for each created volume. Volumes are sizable in 4 TB increments up to the user's subscription quota.
3535

3636
> [!TIP]
3737
> Users are encouraged to place all working directories and point all application runs at a chamber Storage volume for increased performance and data reliablity.

articles/modeling-simulation-workbench/concept-user-personas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The IT Admin is responsible for infrastructure deployment and user provisioning,
2020

2121
A Workbench Owner can create and delete chambers, and invite, remove, or change user roles. They can also define the connectivity methods that their users employ to connect into the workload. The Workbench Owner is also responsible for approving all data export requests and costs accrued by resource consumption during workbench usage.
2222

23-
## Project Manager (chamber Admin)
23+
## Project Manager (Chamber Admin)
2424

2525
The Project Manager, also known as the *Chamber Admin*, is responsible for installing and managing applications and licenses. They also own the installation and configuration of tools related to compute, network, and storage within the chamber. Chamber Admins set up and manage the chamber and have a higher elevated access within the workloads and the environment. They're responsible for procuring the licenses from the software vendors to enable design teams to run simulations on the deployed workloads.
2626

articles/modeling-simulation-workbench/concept-vm-offerings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "VM Offerings: Azure Modeling and Simulation Workbench"
3-
description: VM offerings available in the Azure Modeling and Simulation Workbench
3+
description: VM offerings available in the Azure Modeling and Simulation Workbench.
44
author: yousefi-msft
55
ms.author: yousefi
66
ms.service: modeling-simulation-workbench

articles/modeling-simulation-workbench/concept-workbench.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,19 +17,19 @@ This article presents an overview of the individual components, which make up th
1717

1818
## Workbench
1919

20-
A Workbench is the top-level container for the Azure Modeling and Simulation Workbench. It hosts conventional Azure resources in a closed environment. Workbenches house user and data isolation Chambers, virtual machines, and networking infrastructure. A Workbench has no managing controls and only a Workbench Owner can deploy.
20+
A Workbench is the top-level container for the Azure Modeling and Simulation Workbench. It hosts conventional Azure resources in a closed environment. Workbenches house user and data isolation chambers, virtual machines, and networking infrastructure. A Workbench has no managing controls and only a Workbench Owner can deploy.
2121

2222
## Chambers
2323

24-
[Chambers](./concept-chamber.md) are contained within a Workbench object and contain user data and workloads in an isolated environment. Users assigned to a chamber only have visibility to users and resources in that same Chamber. Compute resources are deployed into a Chamber as Workload VMs and several classes of storage are available.
24+
[Chambers](./concept-chamber.md) are contained within a Workbench object and contain user data and workloads in an isolated environment. Users assigned to a chamber only have visibility to users and resources in that same chamber. Compute resources are deployed into a chamber as Workload VMs and several classes of storage are available.
2525

2626
### Compute
2727

28-
chamber Workload VMs are the Workbench's compute resource and the encapsulating container for traditional VMs. Unlike traditional Infrastructure-as-a-Service offerings, Workload VMs are created with a sensible set of defaults, eliminating the expertise required to securely deploy a VM into a cloud environment. Workload VMs are isolated from the internet and VMs in other chambers, but have access to all VMs in the same chamber. User provisioning is automated at the chamber level. Chamber VMs offer a select set of the Azure virtual machine (VM) offerings that span diverse memory-to-core ratios and suit different workload requirements. VM offerings include general purpose, compute optimized memory optimized VMs.
28+
Chamber Workload VMs are the Workbench's compute resource and the encapsulating container for traditional VMs. Unlike traditional Infrastructure-as-a-Service offerings, Workload VMs are created with a sensible set of defaults, eliminating the expertise required to securely deploy a VM into a cloud environment. Workload VMs are isolated from the internet and VMs in other chambers, but have access to all VMs in the same chamber. User provisioning is automated at the chamber level. Chamber VMs offer a select set of the Azure virtual machine (VM) offerings that span diverse memory-to-core ratios and suit different workload requirements. VM offerings include general purpose, compute optimized memory optimized VMs.
2929

3030
## Storage
3131

32-
Storage components work together to provide high performance for engineering workflows. The storage service enables you to migrate and run enterprise file applications. Modeling and Simulation Workbench offers a range of storage configurations that offer high-performance, shared, or isolated access. Storage is preconfigured to be accessible to Chambers or between a select set of chambers.
32+
Storage components work together to provide high performance for engineering workflows. The storage service enables you to migrate and run enterprise file applications. Modeling and Simulation Workbench offers a range of storage configurations that offer high-performance, shared, or isolated access. Storage is preconfigured to be accessible to chambers or between a select set of chambers.
3333

3434
## Networking
3535

articles/modeling-simulation-workbench/disaster-recovery.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Disaster recovery for Modeling and Simulation Workbench
3-
description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench workbench component.
3+
description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench workbench .component.
44
author: meaghanlewis
55
ms.author: mosagie
66
ms.service: modeling-simulation-workbench
@@ -17,9 +17,10 @@ Planning for disaster recovery involves identifying expected recovery point obje
1717
A typical disaster recovery workflow starts with a failure of a critical service in your primary region. As the issue gets investigated, Azure publishes an expected time for the primary region to recover. If this timeframe is not acceptable for business continuity, and the problem does not impact your secondary region, you would start the process to fail over to the secondary region.
1818

1919
## Achieving business continuity for Azure Modeling and Simulation Workbench
20-
To be prepared for a data center outage, you can have a Modeling and Simulation workbench instance provisioned in a secondary region.
2120

22-
These Workbench resources can be configured to match the resources that exist in the primary Azure Modeling and Simulation workbench instance. Users in the workbench instance environment can be provisioned ahead of time, or when you switch to the secondary region. Chamber and connector resources can be put in a stopped state post deployment to invoke idle billing meters when not being used actively.
21+
To be prepared for a data center outage, you can have a Modeling and Simulation workbench instance provisioned in a secondary region.
22+
23+
These Workbench resources can be configured to match the resources that exist in the primary Azure Modeling and Simulation workbench instance. Users in the workbench instance environment can be provisioned ahead of time, or when you switch to the secondary region. Chamber and connector resources can be put in a stopped state post deployment to invoke idle billing meters when not being used actively.
2324

2425
Alternatively, if you don't want to have an Azure Modeling and Simulation Workbench instance provisioned in the secondary region until an outage impacts your primary region, follow the provided steps in the Quickstart, but stop before creating the Azure Modeling and Simulation Workbench instance in the secondary region. That step can be executed when you choose to create the workbench resources in the secondary region as a failover.
2526

@@ -47,22 +48,21 @@ List of supported regions can be found on the [Azure product availability roadma
4748

4849
Then, create a backup of your Azure Key Vault and keys used by Azure Modeling and Simulation in Key Vault including:
4950

50-
1. Application Client Id key
51-
2. Application Secret key
51+
1. Application Client Id key
52+
2. Application Secret key
5253

5354
## Configure the new instance
5455

5556
In the event of your primary region failure, and decision to work in a backup region, you would create a Modeling and Simulation Workbench instance in your backup region.
5657

57-
1. Register to the Azure Modeling and Simulation Workbench Resource Provider as described in [Create an Azure Modeling and Simulation Workbench](/azure/modeling-simulation-workbench/quickstart-create-portal#register-azure-modeling-and-simulation-workbench-resource-provider).
58+
1. Register to the Azure Modeling and Simulation Workbench Resource Provider as described in [Create an Azure Modeling and Simulation Workbench](/azure/modeling-simulation-workbench/quickstart-create-portal#register-azure-modeling-and-simulation-workbench-resource-provider).
5859

5960
1. Create an Azure Modeling and Simulation Workbench using this section of the Quickstart.
6061

6162
1. If desired, upload data into the new backup instance following Upload Files section of instructions.
6263

6364
You can now do your work in the new workbench instance created in the backup region.
6465

65-
6666
## Cleanup
6767

6868
Once your primary region is up and operating, and you no longer need your backup instance, you can delete it.

articles/modeling-simulation-workbench/how-to-guide-add-redirect-uris.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Add redirect URIs: Azure Modeling and Simulation Workbench"
3-
description: Add redirect URIs for Azure Modeling and Simulation Workbench
3+
description: Add redirect URIs for Azure Modeling and Simulation Workbench.
44
author: yousefi-msft
55
ms.author: yousefi
66
ms.service: modeling-simulation-workbench

0 commit comments

Comments
 (0)