Can't automate the Cortex agent for Linux install due to the RPM issues

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Can't automate the Cortex agent for Linux install due to the RPM issues

L0 Member

We are having issues with rolling out Cortex using automation tools. Since the RPM doesn't take care of figuring out dependencies by itself, you need to manually go install those dependencies and then install the RPM. This makes installs messy and, since there are different distros and versions of Linux in the environment, this breaks the ability for us to automate this without creating our own installation scripts (for each distro and version) and maintaining them ourselves. 

Does anyone have any suggestions? We use salt. 

 

 

2 REPLIES 2

L4 Transporter

Hi @Megawatt,

 

There are package managers available for modern flavors of Linux. If you research one for your particular version, you should be able to use it to automate the dependency download and install. Is it possible for you to share the target version of Linux if this is still a concern for you? 

Visit our Cortex XDR Customer Corner on Live Community to access resources for your product journey, engage in discussions with community members and subject matter experts, and register for upcoming events!

*Cortex XDR Customer Corner: https://live.paloaltonetworks.com/t5/cortex-xdr-customer-corner/ct-p/Cortex_XDR_Customer_Corner

Join our Cortex XDR Office Hours to receive live guidance and training from our Customer Success Architects.

*Cortex XDR Office Hours [NAM]: https://paloaltonetworks.zoom.us/webinar/register/3316669859020/WN_yMpAB-aBTt6xk2h-gsra4w
*Cortex XDR Office Hours [EMEA/APAC]: https://paloaltonetworks.zoom.us/webinar/register/4116709604301/WN_CZuFE5CHQbG9LUEqugsIOw

L1 Bithead

Yeah, but a good Linux RPM citizens takes care of this in their RPM so that the customer doesn't need to go figure those out. And this is a complete pain if those prerequisites change. Not to mention that this means you need to create a separate script for each linux (ver and/or flavor) you run. Seems lazy to not just follow RPM build capabilities like a SPEC file. Implies to a paying customer that the software isn't that much of a focus for Palo Alto. 

  • 3821 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!