Configure an Ozone target

You can migrate data to an Ozone bucket by configuring one as a target filesystem.

note

Ozone does not support ACL or extended attributes. If you are migrating from HDFS to Ozone, ACLs will not be supported.

Follow these steps to create an Ozone target:

UI

Configure an Ozone target filesystem in the UI

1. From the Dashboard, select an instance under Instances.
2. In the Filesystems & Agents menu, select Filesystems.
3. Select Add target filesystem.
4. Enter the following details:
   • Filesystem Type - The type of filesystem target. Select Apache Ozone.
   • Display Name - Enter a name for your target filesystem.
   • Default Filesystem - The Ozone filesystem scheme. For example, ofs://omservice or o3fs://bucket1.vol1.omservice/.
   • User - Enter the name of the filesystem user you want to migrate data with, only if your target is not Kerberized.
5. Kerberos Configuration - The details of your Kerberos configuration. You can authenticate with Kerberos using multi-realm Kerberos, cross-realm trust or target-only Kerberos. See Configure Kerberos.
   • Kerberos Principal - Enter a principal that maps to a user with appropriate permissions for your Ozone target filesystem.
   • Kerberos Keytab Location - Enter the path to the Kerberos keytab file containing the Kerberos Principal. The keytab file must be accessible from the edge node where Data Migrator is installed.
6. Advanced Configuration
   • Configuration Property File Paths - Enter the directory or directories containing your target filesystem's configuration (such as the core-site.xml and ozone-site.xml) on your Data Migrator host's local filesystem.
     note

     Data Migrator reads core-site.xml and ozone-site.xml once, during filesystem creation, applying any configuration within paths added under Configuration Property File Paths. After creation, these paths are no longer visible in the UI. You can see all filesystem properties using the API.

     • Configuration Property Overrides (Optional) - Enter override properties or additional properties for your Ozone filesystem by adding key/value pairs.
7. Select Save. You can now use your Ozone target in data migrations.

CLI

Configure an Ozone target filesystem in the CLI

To create an Ozone target in the Data Migrator CLI, run the filesystem add ozone command:

Add an Ozone filesystem

filesystem add ozone  [--default-fs] string 
                      [--file-system-id] string
                      [--kerberos-keytab] string
                      [--kerberos-principal] string
                      [--properties] string
                      [--properties-files] list
                      [--user] string

For guidance about access, permissions, and security when adding Ozone as a target filesystem, see Securing Ozone.

Ozone mandatory parameters

• --default-fs A string that defines how Data Migrator accesses Ozone. In the UI, this is called Default Filesystem. You can enter it in the following ways:
  1. As the ofs:// scheme such as ofs://omservice or
  2. As the o3fs:// scheme, for example, o3fs://bucket1.vol1.omservice/. For more information, see OFS Hadoop compatible file system.
• --file-system-id The ID for the new filesystem resource. In the UI, this is called Display Name.
• --properties-files Reference a list of existing properties files that contain configuration properties in the format used by core-site.xml or ozone-site.xml.
  note

  Define the absolute paths to the core-site.xml and ozone-site.xml files. For example, --properties-files /etc/hadoop/conf/core-site.xml,/etc/hadoop/conf/ozone-site.xml.

Ozone optional parameters

• --kerberos-keytab The Kerberos keytab that contains the principal defined for the --kerberos-principal parameter. This must be accessible to the local system user running the Data Migrator service.
• --kerberos-principal The Kerberos principal to authenticate with and perform migrations as.
• --properties Enter properties to use in a comma-separated key/value list. In the UI, this is called Configuration Property Overrides.
• --user Data Migrator will use this Ozone user to perform operations against the filesystem. If Kerberos is disabled on the filesystem, this user must be the Ozone superuser.

Example

filesystem add ozone --file-system-id ozone-tgt
                     --default-fs ofs://omservice2
                     --properties-files /etc/targetConf/core-site.xml,/etc/targetConf/ozone-site.xml

Next steps

If you haven't already, configure a source filesystem from which to migrate data. Then, you can create a migration to migrate data to your new Ozone target.