Creating a Workspace in Enterprise Mode

Restrictions

You can upgrade your workspace mode or create a workspace in enterprise mode only if you are assigned the DAYU Administrator or Tenant Administrator role.

Prerequisites

Before creating a workspace, ensure that:

• You have understood the differences between workspaces in simple mode and those in enterprise mode, such as the differences in the development process. For details, see Introduction to the Simple Mode and Enterprise Mode.
• You have configured workspace-level scheduling identities, including public agencies and public IAM accounts. For details, see Configuring a Public Agency and Configuring a Public IAM Account.
• You have prepared two sets of isolated data lake engines, one for the development environment and the other for the production environment.
  • Configure two sets of data lake services to isolate the development environment from the production environment.

    For clustered data sources, such as MRS, GaussDB(DWS), RDS, MySQL, Oracle, DIS, and ECS, you can create data connections in Management Center to distinguish data lake services in the development environment from those in the production environment. The data lake is automatically switched during development and production. Therefore, you need to prepare two sets of data lake services that have the same version, specifications, components, region, VPC, subnet, and other related configurations. For details, see Creating a DataArts Studio Data Connection.

    When creating a data connection, you can select different clusters for the development environment and production environment to isolate them.

    Figure 1 Selecting different clusters during data connection creation
    

  • Configure environment isolation for DLI.

    Configure environment isolation in enterprise mode, including DLI queue configuration and DB configuration.

    For serverless services (such as DLI), you can configure the mapping between data lake services in the production environment and those in the development environment through environment isolation in Management Center. The data lake is automatically switched during development and production. Therefore, you need to prepare two sets of queues and database resources in the serverless data lake service and distinguish them by name suffix. For details, see Configuring Environment Isolation for a DataArts Studio Workspace in Enterprise Mode.

  • Configure two databases in the same data lake service to isolate the development environment from the production environment.

    For GaussDB(DWS), MRS Hive, and MRS Spark, if you select the same cluster when creating a data connection (as shown in Figure 2), you must configure database mapping on the Configure Data Source Resource Mapping page shown in Figure 3 to isolate the development and production environments. For details, see DB configuration.

    Figure 2 Selecting the same cluster during data connection creation
    
    Figure 3 DB Configuration
    

• Prepare and synchronize data.
  • After creating data lake services, you must create databases, database schemas (required only for DWS), and data tables in the data lake services of the development and production environments based on the project plan (for example, the databases and tables required for data development).
    • For clustered data sources (such as MRS, DWS, RDS, MySQL, Oracle, DIS, and ECS), use two clusters, one for the development environment and the other for the production environment. The names of the databases, database schemas (required only for DWS), and data tables in the two environments must be the same.
    • For serverless services (such as DLI), you are advised to associate and distinguish the two queues and databases by name suffix (add suffix _dev to the names of the queues and databases in the development environment and add no suffix to those in the production environment). The names of data tables in the development environment must be the same as those in the production environment.
    • For DWS, MRS Hive, and MRS Spark data sources, if the same cluster is used for the development and production environments, use two databases to isolate the development and production environments (add suffix _dev to the database for the development environment and add no suffix to the database for the production environment). The names of database schemas (required only for DWS) and data tables in the development environment must be the same as those in the production environment.
  • After creating databases, database schemas (required only for DWS), and data tables, you must synchronize data of existing tables (if any) between the two data lake services.
    • Existing data in data lakes: Use data migration services such as CDM and DRS to synchronize data in batches between data lakes.
    • Data to be migrated from the data source: Use peering jobs of data migration services such as CDM and DRS to synchronize data between the data lake service of the production environment and that of the development environment.

Change Description

After the workspace mode is upgraded, a development environment isolated from the production environment is added.

Upgrading the Simple Mode to Enterprise Mode

With the DAYU Administrator or Tenant Administrator role, you can upgrade a workspace in simple mode to one in enterprise mode.

• Pre-upgrade operations

  Configure a workspace-level public agency or public IAM account in DataArts Factory to avoid an upgrade failure.

  For details about how to configure an agency, see Configuring a Scheduling Identity.

  Figure 4 Configuring a workspace-level agency
  

• Upgrade operations
  1. Log in to the DataArts Studio console.
  2. Locate a DataArts Studio instance and click Access. Then, click the Workspaces tab.
  3. Locate the workspace you want to upgrade and click Edit in Operation column.
  4. In the displayed Workspace Information dialog box, click Upgrade next to the Mode text box. In the displayed dialog box, click Upgrade.
     Figure 5 Upgrading to the enterprise mode
     

• Post-upgrade operations

  After the upgrade is complete, you (as the admin) need to modify data connections, configure environment isolation, and define roles such as the admin, developer, deployer, and operator in the workspace.

  1. Modify data connections. For details, see Creating a DataArts Studio Data Connection.
  2. Configure environment isolation. For details, see Configuring Environment Isolation for a DataArts Studio Workspace in Enterprise Mode.
  3. Define workspace roles for other users. For details, see Adding Workspace Members and Assigning Roles.

Creating a Workspace in Enterprise Mode

If you have not used the simple mode before and do not need to inherit business data, you can directly create a workspace in enterprise mode.

• Create a workspace.
  1. Log in to the DataArts Studio console using an account with the Administrator or Tenant Administrator permission.
  2. Locate an instance and click Access. Then click the Workspaces tab.
  3. Click Create. In the displayed Create dialog box, set parameters based on Table 1 and click OK.
     Figure 6 Creating a workspace
     

     Table 1 Parameters for creating a workspace

     Parameter	Description
     Name	Workspace name. It can contain a maximum of 32 characters, including only letters, digits, underscores (_), and hyphens (-). The workspace name must be unique in the current DataArts Studio instance.
     Description	Workspace description
     Mode	Mode of the workspace. Available options include Simple and Enterprise. Select Enterprise.
     Enterprise Project	Enterprise project associated with the default workspace of the DataArts Studio instance. An enterprise project facilitates management of cloud resources. For details, see Enterprise Management User Guide. This parameter is available only when an enterprise project has been created. If you want to connect the DataArts Studio instance to an instance of another cloud service, such as GaussDB(DWS), MRS, and RDS, ensure that the enterprise project of the DataArts Studio instance's workspace is the same as that of the target cloud service instance. You can buy only one DataArts Studio instance for an enterprise project. If you want to enable communication between DataArts Studio and another cloud service, ensure that the enterprise project of DataArts Studio is the same as that of the target cloud service.
     Job Log Path	OBS bucket for storing the job logs of DataArts Factory of DataArts Studio. To use the DataArts Factory module of DataArts Studio, workspace members must have the read and write permissions on the OBS bucket for storing job logs. Otherwise, the system cannot read or write job logs of DataArts Factory. Click Select. You can select an existing OBS bucket. The selected OBS bucket is globally configured in the current workspace. If you do not set this parameter, job logs of DataArts Factory are stored in the OBS bucket named dlf-log-{projectId} by default.
     Dirty Data Path	OBS bucket for storing dirty data generated during DLI SQL execution in DataArts Factory of DataArts Studio. To use DataArts Factory to develop and execute DLI SQL statements, workspace members must have the read and write permissions on the OBS bucket where DLI dirty data is stored. Otherwise, the system cannot read or write the dirty data generated during DLI SQL execution. Click Select. You can select a created OBS bucket. The selected OBS bucket is globally configured in the current workspace. If you do not set this parameter, dirty data generated during DLI SQL execution is stored in the OBS bucket named dlf-log-{projectId} by default.
     Tags	You can add resource tags to classify resources. NOTE: If your account belongs to an organization and the organization has configured DataArts Studio tag policies, you need to add tags based on these policies. If a tag does not comply with the tag policies, instance creation may fail. Contact your administrator to learn more about tag policies. If you have multiple workspaces, you can add tags to classify them by user, operator, or purpose. On the workspace list page, you can search for workspaces by tag. A tag consists of a key and a value. When adding a tag, you can select a predefined tag created in Tag Management Service (TMS) or enter a custom tag. Then click Add to the right of the text box to add the tag. NOTE: To select predefined tags, ensure that you have created predefined tags in TMS. You can click View predefined tags to enter the Predefined Tag page of TMS. Then, click Create Tag to create a predefined tag. For details, see Creating Predefined Tags in Tag Management Service User Guide. A maximum of 20 tags can be added to a workspace. Each tag key must be unique and can only match one tag value.

• Perform follow-up operations.

  After creating the workspace, you (as the admin) need to create data connections, configure environment isolation, and define roles such as the admin, developer, deployer, and operator in the workspace.

  1. Create data connections. For details, see Creating a DataArts Studio Data Connection.
  2. Configure environment isolation. For details, see Configuring Environment Isolation for a DataArts Studio Workspace in Enterprise Mode.
  3. Define workspace roles for other users. For details, see Adding Workspace Members and Assigning Roles.
  4. Configure a workspace-level public agency or public IAM account in DataArts Factory. For details about how to configure an agency, see Configuring a Scheduling Identity.
     Figure 7 Configuring a workspace-level agency