Creating a Workspace in Simple Mode
Scenario
During the digital transformation of enterprises, data teams usually need to define their work boundaries based on the organizational structure, business domains, or implementation environments. If you want to quickly set up a data development environment and do not require strict isolation between the development and production environments, you can create a workspace in simple mode.
The simple mode is traditional and easy to use. Scripts or jobs submitted can be directly executed in the scheduling system without being published.
Notes and Constraints
- There is no limit on the number of workspaces that can be created for a DataArts Studio instance.
- The storage of job logs and dirty data depends on the OBS service.
Prerequisites
You have obtained a DataArts Studio instance. For details, see Buying a DataArts Studio Instance.
Context
- The system creates a default workspace named default for the DataArts Studio instance you buy and assigns the admin role to you.
- In a DataArts Studio instance created by an account, if an IAM user of the account needs to create a workspace, the IAM user must be assigned the DAYU Administrator or Tenant Administrator permissions. By default, the account has all the permissions for a DataArts Studio instance created by a user of the account.
- Users with the DAYU User permissions can access a workspace only after they are added as members of the workspace.
Procedure
- Log in to the DataArts Studio console as the DAYU Administrator or Tenant Administrator account by referring to Accessing the DataArts Studio Instance Console.
- On the Workspaces page, click Create Workspace. In the displayed dialog box, set the parameters listed in Table 1. Figure 1 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. It can contain a maximum of 1,024 characters.
Mode
Select Simple.
- Simple: This is the traditional workspace mode of DataArts Studio and is easy to use.
- Enterprise: In this mode, you can isolate the development environment from the production environment in the DataArts Factory and Management Center modules of DataArts Studio. This prevents developers' operations from affecting services in the production environment. For details about the enterprise mode, see Enterprise Mode.
Enterprise Project
You can select an enterprise project only if you have created one. If you want to connect the DataArts Studio instance to an instance of another cloud service (such as DWS, MRS, and RDS), ensure that the enterprise project of the DataArts Studio 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 the instance and another cloud service, ensure that the enterprise project of the instance is the same as that of the target cloud service.
NOTE:If the enterprise project function is not enabled, only one DataArts Studio instance can be created for each IAM project. To create multiple instances, enable the enterprise project function and create an enterprise project.
Job Log Path
OBS path for storing job logs and running data in the workspace, including job logs in DataArts Factory, reports in DataArts Quality, and dump logs of DataArts DataService clusters. Workspace members who want to use DataArts Factory, DataArts Quality, or DataArts DataService functions must have the read and write permissions of the job log OBS bucket. Otherwise, the system cannot read or write job logs and running data.
- Click Select OBS Path and select an OBS bucket and object. The selected OBS bucket applies to the workspace. You can only select an OBS object bucket, but not a parallel file system.
- If you do not set this parameter, job logs in DataArts Factory and reports in DataArts Quality are stored in the dlf-log-{projectId}/{workspaceId} directory by default. Dump logs of DataArts DataService clusters are stored in the dlm-{projectId} bucket by default. {projectId} indicates the project ID, which can be obtained in the following way:
- Register with and log in to the management console.
- Hover the cursor on the username in the upper right corner and select My Credentials from the drop-down list.
- On the API Credentials page, obtain the account name, account ID, IAM username, and IAM user ID, and obtain the project and its ID from the project list.
NOTE:After a job in DataArts Factory is executed, the execution result log is stored in the OBS bucket path in {Job ID}.log format. The log shows the historical execution records. Deleting the historical records of SQL statements does not affect services.
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 OBS Path. You can select a created OBS bucket and an object. 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}/{workspaceId} 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.
- Click OK.
Related Operations
Related APIs
| API | Description |
|---|---|
| This API is used to create a workspace. | |
| This API is used to obtain the workspace list. | |
| This API is used to obtain information about a workspace. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot