In this blog, I’m going to explain what you consider adding the SaltStack Config resource in your Cloud Assembly designs.
If you integrated Salt Stack Config with vRealize Automation, you could apply the Salt Stack Config resource to install the minions on virtual machines in your deployments. After the minion is deployed, you can use Salt Stack Config's powerful configuration management, drift remediation, and state management capabilities to manage your resources.
Minions are agents that run the salt-minion service. The service subscribes to jobs published by a Salt master, which is a server that runs the salt-master service. When a specific job applies to a minion, the minion executes the job.
There are three types of minions in the Salt environment:
· Proxy minions that manage devices that cannot run the salt-minion service.
· Agentless minions that run Salt commands on a system without installing a Salt minion.
You can use the Salt Stack Config resource to deploy minions and apply state files when you deploy Linux and Windows machines. To add or update minions and state files on existing deployments, you can run the Attach Salt Stack Resource Day 2 action.
If you used the salt Configuration property to deploy minions and state files as a day 0 action, update your cloud templates to use the Salt Stack Config resource. The salt Configuration property is now deprecated.
The Apply Salt Configuration Day 2 action is still available for resources that use the salt Configuration property.
Before you start
1. Verify that you installed SaltStack Config and configured the integration. See Configure a SaltStack Config integration in vRealize Automation.
To familiarize yourself with how SaltStack Config works, including the key concepts of minions, see Understanding the SaltStack User Interface.
2. In SaltStack Config, verify that the FQDN name resolution from minion to master is working.
a. To verify the FQDN on the Salt master in SaltStack Config, select Minions > All Minons.
b. Filter the Minion ID column for the value saltmaster.
c. Click saltmaster to see the details.
d. Verify that the FQDN value is correct.
3. If you are deploying minions on a Linux machine, verify that the images in vSphere that you intend to deploy with a Salt minion have SSH capabilities enabled. SSH is used to remotely access the machine and deploy the minion.
4. If you are deploying minions on a Windows machine, see How do I deploy minions using the API (RaaS) in a Windows environment.
5. If you are deploying minions on a virtual machine that has VMware Tools installed and a Salt minion configured, verify that the VMware Tools Salt minion key appears under the Accepted tab in the Minion Keys workspace in SaltStack Config. See Enable Salt minion using VMware Tools for more information.
Note: If the VMware Tools Salt minion is an older version, deploying a minion against the virtual machine does not upgrade the Salt master to the latest version. You must upgrade your Salt master manually. See Upgrade the Master Plugin for more information.
6. Verify that you can assign IP addresses to the machines you deploy.
SaltStack Config requires the machines to have IP addresses. Use the IP addresses for the public IP CIDR range for the SDDC (software-defined data center) where your Salt master is located.
7. Verify that the cloud template that you are adding the minion to is deployable before you add the SaltStack Config resource properties.
8. Verify that you have the following service roles:
1. Cloud Assembly administrator
2. Cloud Assembly user
3. Service Broker administrator
These service roles are required to use the SaltStack Config resource.
Stay with me 😃 In my next blog, I will cover below topics.
1- Add the SaltStack Config resource to the cloud template
2- Troubleshoot minion deployments
3- Add the SSC minion to deployments in air-gapped environments
Post a Comment