locked
Pre - installation setup for Batch Tasks RRS feed

  • Question

  • How can we install pre-requisites before task triggers.

    In this case , I have task to get processed end of the task , we will process data to SQL Azure from compute node via BCP utility.

    Default compute node doesn't have the BCP utility(installer) installed, to do that what was the right context to get this installed during batch work flow / life cycle ? 

    Remember there is an another option use image , since it's a very small installer and prefer to go with pre-installation.

    Thanks in advance for your response ?

    Thursday, May 25, 2017 11:29 AM

All replies

  • Hi Venkat,

    You can install prereqs at the node level as specified with a Start Task or on the Job Level (thus tasks) with a Job Preparation Task. An alternative, if you can package up your dependency in a zip file, is to use Application Packages (currently only available for CloudServiceConfiguration pools) which can be installed at the node or task level.

    Cheers,

    Fred


    Thursday, May 25, 2017 2:32 PM
  • Thanks for your response Fred. I tried by changing command , part of command for .MSI file part of start task and it's working as expected. Would like to understand more about when we will go for Cloud Service configuration pools , any specific criteria ? 
    Monday, May 29, 2017 7:36 AM
  • Hi Venkat,

    You can get a brief overview regarding the two types at this article.

    Right now, each type of configuration offer different advantages over the other, although we are working to close the gap on each. If you are looking to execute on Windows and do not require a VM size that is exclusively only available on Virtual Machines (e.g., STANDARD_F series), then CloudServiceConfiguration pools may offer better speed in terms of resizing (allocation) along with larger limits for inter-node communication and application packages feature. However, you cannot deploy CloudServiceConfiguration pools using a User Subscription Batch Account.

    VirtualMachineConfiguration pools can deploy to any Batch supported VM size and has features such as non-Windows support, custom images, file output support, but no application packages.

    Both types of pools support bringing your own Virtual Network.

    The above descriptions are not meant to be comprehensive, but to offer some points of differentiation between the offerings. Again, we are trying to minimize the differences between the two types in the future wherever possible.

    Cheers,

    Fred

    Tuesday, May 30, 2017 2:36 PM