Product
Introducing License Enforcement in Socket
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
An Event-Task Pilot for EWMS
The EWMS Pilot is a non-user-facing wrapper for task container instances in the Event Workflow Management System (EWMS), running on an HTCondor Execution Point (EP). The pilot:
The following outlines what users need to know to operate within EWMS.
The Pilot is designed to be invisible to users. However, some key details are necessary for running a task container:
A task container is created for each inbound event, it is defined by its image, arguments, and environment variables. See the WMS docs for information on setting these within EWMS.
An input event is provided to the task container as a file. The task container creates an output event by writing to a predetermined location.
The pilot provides the filepaths to the input and output files in two ways:
{{INFILE}}
and {{OUTFILE}}
, in the container's arguments at runtime.EWMS_TASK_INFILE
and EWMS_TASK_OUTFILE
.The files' extensions are configured by the pilot's environment variables, EWMS_PILOT_INFILE_EXT
and EWMS_PILOT_OUTFILE_EXT
: by default, these are .in
and .out
, respectively.
No other event or message handling is required by the task container.
An init container is an optional, user-supplied image used to set up the environment, wait for conditions, or perform other preparatory actions before running task containers. It is configured using the EWMS_PILOT_INIT_IMAGE
, EWMS_PILOT_INIT_ARGS
, and EWMS_PILOT_INIT_ENV_JSON
environment variables.
Task containers (and init containers) can interact with external files in two ways:
To transfer files between task containers, a shared directory is available to all task containers and the init container.
The pilot provides the filepath to the "data hub" in two ways:
{{DATA_HUB}}
, in the container's arguments at runtime.EWMS_TASK_DATA_HUB_DIR
.Note:
Externally-mounted directories are supported in EWMS. See the WMS documentation for more details.
Does not exist within the Pilot. Compare to WMS.
The message queue is abstracted from the task container and can be ignored. Compare to WMS.
An event is an object transferred via event I/O. Compare to WMS.
In the context of the Pilot, the task is the runtime instance of the task image (a task container) applied to an inbound event, possibly producing outbound events. Compare to WMS.
The task container is an instance of a task image and is nearly synonymous with task.
Does not exist within the Pilot. Compare to WMS.
Does not exist within the Pilot. Compare to WMS.
FAQs
EWMS's Pilot: A Job Pilot for Processing EWMS Events/Tasks
We found that ewms-pilot demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
Product
We're launching a new set of license analysis and compliance features for analyzing, managing, and complying with licenses across a range of supported languages and ecosystems.
Product
We're excited to introduce Socket Optimize, a powerful CLI command to secure open source dependencies with tested, optimized package overrides.