package google.genomics.v1alpha2

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service PipelinesV1Alpha2

pipelines.proto:33

A service for running genomics pipelines.

message ComputeEngine

pipelines.proto:111

Describes a Compute Engine resource that is being managed by a running [pipeline][google.genomics.v1alpha2.Pipeline].

Used in: RuntimeMetadata

message ControllerConfig.RepeatedString

pipelines.proto:328

Used in: ControllerConfig

message DockerExecutor

pipelines.proto:618

The Docker execuctor specification.

Used in: Pipeline

message LoggingOptions

pipelines.proto:391

The logging options for the pipeline run.

Used in: RunPipelineArgs

message Pipeline

pipelines.proto:139

The pipeline object. Represents a transformation from a set of input parameters to a set of output parameters. The transformation is defined as a docker image and command to run within that image. Each pipeline is run on a Google Compute Engine VM. A pipeline can be created with the `create` method and then later run with the `run` method, or a pipeline can be defined and run all at once with the `run` method.

Used as response type in: PipelinesV1Alpha2.CreatePipeline, PipelinesV1Alpha2.GetPipeline

Used as field type in: CreatePipelineRequest, ListPipelinesResponse, RunPipelineRequest

message PipelineParameter

pipelines.proto:583

Parameters facilitate setting and delivering data into the pipeline's execution environment. They are defined at create time, with optional defaults, and can be overridden at run time. If `localCopy` is unset, then the parameter specifies a string that is passed as-is into the pipeline, as the value of the environment variable with the given name. A default value can be optionally specified at create time. The default can be overridden at run time using the inputs map. If no default is given, a value must be supplied at runtime. If `localCopy` is defined, then the parameter specifies a data source or sink, both in Google Cloud Storage and on the Docker container where the pipeline computation is run. The [service account associated with the Pipeline][google.genomics.v1alpha2.RunPipelineArgs.service_account] (by default the project's Compute Engine service account) must have access to the Google Cloud Storage paths. At run time, the Google Cloud Storage paths can be overridden if a default was provided at create time, or must be set otherwise. The pipeline runner should add a key/value pair to either the inputs or outputs map. The indicated data copies will be carried out before/after pipeline execution, just as if the corresponding arguments were provided to `gsutil cp`. For example: Given the following `PipelineParameter`, specified in the `inputParameters` list: ``` {name: "input_file", localCopy: {path: "file.txt", disk: "pd1"}} ``` where `disk` is defined in the `PipelineResources` object as: ``` {name: "pd1", mountPoint: "/mnt/disk/"} ``` We create a disk named `pd1`, mount it on the host VM, and map `/mnt/pd1` to `/mnt/disk` in the docker container. At runtime, an entry for `input_file` would be required in the inputs map, such as: ``` inputs["input_file"] = "gs://my-bucket/bar.txt" ``` This would generate the following gsutil call: ``` gsutil cp gs://my-bucket/bar.txt /mnt/pd1/file.txt ``` The file `/mnt/pd1/file.txt` maps to `/mnt/disk/file.txt` in the Docker container. Acceptable paths are: <table> <thead> <tr><th>Google Cloud storage path</th><th>Local path</th></tr> </thead> <tbody> <tr><td>file</td><td>file</td></tr> <tr><td>glob</td><td>directory</td></tr> </tbody> </table> For outputs, the direction of the copy is reversed: ``` gsutil cp /mnt/disk/file.txt gs://my-bucket/bar.txt ``` Acceptable paths are: <table> <thead> <tr><th>Local path</th><th>Google Cloud Storage path</th></tr> </thead> <tbody> <tr><td>file</td><td>file</td></tr> <tr> <td>file</td> <td>directory - directory must already exist</td> </tr> <tr> <td>glob</td> <td>directory - directory will be created if it doesn't exist</td></tr> </tbody> </table> One restriction due to docker limitations, is that for outputs that are found on the boot disk, the local path cannot be a glob and must be a file.

Used in: Pipeline

message PipelineParameter.LocalCopy

pipelines.proto:585

LocalCopy defines how a remote file should be copied to and from the VM.

Used in: PipelineParameter

message PipelineResources

pipelines.proto:404

The system resources for the pipeline run.

Used in: Pipeline, RunPipelineArgs

message PipelineResources.Disk

pipelines.proto:406

A Google Compute Engine disk resource specification.

Used in: PipelineResources

enum PipelineResources.Disk.Type

pipelines.proto:408

The types of disks that may be attached to VMs.

Used in: Disk

message RunPipelineArgs

pipelines.proto:189

The pipeline run arguments.

Used in: RunPipelineRequest

message RuntimeMetadata

pipelines.proto:128

Runtime metadata that will be populated in the [runtimeMetadata][google.genomics.v1.OperationMetadata.runtime_metadata] field of the Operation associated with a RunPipeline execution.

message ServiceAccount

pipelines.proto:374

A Google Cloud Service Account.

Used in: RunPipelineArgs

message TimestampEvent

pipelines.proto:351

Stores the list of events and times they occured for major events in job execution.

Used in: SetOperationStatusRequest