Table of Contents

Search

  1. Preface
  2. Advanced clusters
  3. Setting up AWS
  4. Setting up Google Cloud
  5. Setting up Microsoft Azure
  6. Setting up a self-service cluster
  7. Setting up a local cluster
  8. Advanced configurations
  9. Troubleshooting
  10. Appendix A: Command reference

Advanced Clusters

Advanced Clusters

Download and install a Secure Agent

Download and install a Secure Agent

A local cluster requires a Secure Agent. Download and install a Secure Agent on a local Linux machine.

Step 1: Verify software and hardware requirements

Verify that you are running a supported version of Linux. For the list of supported Linux operating systems for the Secure Agent, see the Product Availability Matrix (PAM) for Informatica Intelligent Cloud Services in the Knowledge Base.
Verify that your machine meets the minimum hardware requirements to set up a local cluster:
  • 8 vCPU, 32 GB memory
  • 100 GB disk space for the root volume
  • 20 GB disk space on the root volume for
    /var
  • 30 GB disk space on the root volume for
    /tmp
To keep the cluster from hanging when it starts, allocate at least 30 GB of disk space each for
/var
and
/tmp
.

Step 2: Verify NOPASSWD sudo privileges

To run the local cluster on the Secure Agent, the user who starts the Secure Agent requires NOPASSWD sudo privileges on the Secure Agent machine. If it's not possible to grant the NOPASSWD privilege, perform one the following workaround:
Use the pmsuid file
  1. Copy
    pmsuid
    from:
    <Secure Agent home>/apps/At_Scale_Server/<latest version>/bin/Linux.64/
    to:
    <Secure Agent home>/apps/At_Scale_Server/ext/
  2. Change the owner and group of
    pmsuid
    to root and set the
    setgid
    bit for the file.
  3. Set
    ccs.localcluster.deployment.mode=SUID
    in the runtime properties section for the local cluster.
  4. Use Monitor to stop the local cluster and run a job to start the cluster again.
Update the sudoers file
Edit the
/etc/sudoers
file, and add the following line:
<user ID> ALL=(ALL) NOPASSWD: /usr/bin/kubeadm, /usr/bin/tee, /usr/bin/yum, /usr/sbin/modprobe, /usr/sbin/sysctl, /usr/bin/systemctl, /usr/sbin/swapoff, /usr/bin/chown, /usr/bin/cp, /usr/bin/rm
Where <user ID> is a non-root user who doesn't have sudo privileges on the Secure Agent machine.

Step 3: Download and install the Secure Agent

Download and install a Secure Agent on a local Linux machine. For detailed information about installing a Secure Agent, see "Secure Agent installation on Linux" in
Runtime Environments
.

0 COMMENTS

We’d like to hear from you!
Alessio Giordani - October 25, 2024

Hello documentation team,

regarding the space available in the /tmp directory, it is possible specify a custom property to change the default when needed.

Specifying the following custom variable in the local cluster runtime configuration, is possible redirect the temporary objects in a different filesystem

k8s.pod.shared.host.path =

Please consider that folder name must match this regex '[a-z0-9]([-a-z0-9]*[a-z0-9])?' to be valid, so for example it can have all lowercase and NO "_" (i.e. /data/advclustertmp will work).

Best regards,

Alessio

 

 

Informatica Documentation Team - October 26, 2024

Thanks for reaching out, Alessio!

We'll address this in an upcoming KB article.


Alessio Giordani - October 28, 2024

Thanks. If possible, please link the KB article in this page so the users know that there are additional information available for the local cluster setup.

Regards,


Alessio

Informatica Documentation Team - October 28, 2024

Thanks, Alessio! We will do that.