pipen-cli-gbatch 0.1.0__tar.gz → 0.1.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.


This version of pipen-cli-gbatch might be problematic. Click here for more details.

@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pipen-cli-gbatch
3
- Version: 0.1.0
3
+ Version: 0.1.2
4
4
  Summary: A pipen cli plugin to run command via Google Cloud Batch
5
5
  License: MIT
6
6
  Author: pwwang
@@ -79,7 +79,7 @@ from pipen.cli import CLIPlugin
79
79
  from pipen.scheduler import GbatchScheduler
80
80
  from pipen_poplog import LogsPopulator
81
81
 
82
- __version__ = "0.1.0"
82
+ __version__ = "0.1.2"
83
83
  __all__ = ("CliGbatchPlugin", "CliGbatchDaemon")
84
84
  MOUNTED_CWD = "/mnt/disks/.cwd"
85
85
 
@@ -200,6 +200,10 @@ class CliGbatchDaemon:
200
200
  target: The target mount path inside the container.
201
201
  """
202
202
  mount = self.config.get("mount", [])
203
+ if not isinstance(mount, (list, tuple, set)):
204
+ mount = [mount]
205
+ else:
206
+ mount = list(mount)
203
207
  # mount the workdir
204
208
  mount.append(f"{source}:{target}")
205
209
 
@@ -617,30 +621,45 @@ class XquteCliGbatchPlugin: # pragma: no cover
617
621
  scheduler: The scheduler instance.
618
622
  job: The job that started.
619
623
  """
620
- logger.info("Job is picked up by Google Batch, pulling stdout/stderr...")
624
+ logger.info("Job is picked up by Google Batch, pulling stdout/stderr ...")
621
625
  if not self.stdout_file:
622
626
  self.stdout_populator.logfile = scheduler.workdir.joinpath(
623
627
  "0", "job.stdout"
624
628
  )
625
629
  elif not self.stdout_file.exists():
626
- await asyncio.sleep(3) # wait a bit for the file to be created
630
+ logger.warning(f"Running logs file not found: {self.stdout_file}")
631
+ logger.warning(" Waiting for it to be created ...")
632
+ i = 0
633
+ while not self.stdout_file.exists():
634
+ await asyncio.sleep(3)
635
+ i += 1
636
+ if i >= 20:
637
+ break
638
+
627
639
  if not self.stdout_file.exists():
628
- logger.warning(f"Running logs not found: {self.stdout_file}")
629
640
  logger.warning(
630
- "Make sure pipen-log2file plugin is enabled for your pipeline."
641
+ " Still not found, falling back to pull logs from daemon ..."
642
+ )
643
+ logger.warning(
644
+ " Make sure pipen-log2file plugin is enabled for your pipeline."
631
645
  )
632
- logger.warning("Falling back to pull logs from daemon...")
633
646
  self.stdout_populator.logfile = scheduler.workdir.joinpath(
634
647
  "0", "job.stdout"
635
648
  )
636
649
  else:
650
+ logger.info(" Found the running logs, pulling ...")
637
651
  self.stdout_populator.logfile = (
638
652
  self.stdout_file.resolve()
639
653
  if self.stdout_file.is_symlink()
640
654
  else self.stdout_file
641
655
  )
642
656
  else:
643
- self.stdout_populator.logfile = self.stdout_file
657
+ self.stdout_populator.logfile = (
658
+ self.stdout_file.resolve()
659
+ if self.stdout_file.is_symlink()
660
+ else self.stdout_file
661
+ )
662
+
644
663
  self.stderr_populator.logfile = scheduler.workdir.joinpath("0", "job.stderr")
645
664
 
646
665
  @plugin.impl
@@ -1,6 +1,6 @@
1
1
  [tool.poetry]
2
2
  name = "pipen-cli-gbatch"
3
- version = "0.1.0"
3
+ version = "0.1.2"
4
4
  description = "A pipen cli plugin to run command via Google Cloud Batch"
5
5
  authors = ["pwwang <pwwang@pwwang.com>"]
6
6
  license = "MIT"
@@ -17,7 +17,7 @@ entry_points = \
17
17
 
18
18
  setup_kwargs = {
19
19
  'name': 'pipen-cli-gbatch',
20
- 'version': '0.1.0',
20
+ 'version': '0.1.2',
21
21
  'description': 'A pipen cli plugin to run command via Google Cloud Batch',
22
22
  'long_description': '# pipen-cli-gbatch\n\nA pipen CLI plugin to run commands via Google Cloud Batch.\n\nThe idea is to submit the command using xqute and use the gbatch scheduler to run it on Google Cloud Batch.\n\n## Installation\n\n```bash\npip install pipen-cli-gbatch\n```\n\n## Usage\n\n### Basic Command Execution\n\nTo run a command like:\n\n```bash\npython myscript.py --input input.txt --output output.txt\n```\n\nYou can run it with:\n\n```bash\npipen gbatch -- python myscript.py --input input.txt --output output.txt\n```\n\n### With Configuration File\n\nIn order to provide configurations like we do for a normal pipen pipeline, you can also provide a config file (the `[pipen-cli-gbatch]` section will be used):\n\n```bash\npipen gbatch @config.toml -- \\\n python myscript.py --input input.txt --output output.txt\n```\n\n### Detached Mode\n\nWe can also use the `--nowait` option to run the command in a detached mode:\n\n```bash\npipen gbatch --nowait -- \\\n python myscript.py --input input.txt --output output.txt\n```\n\nOr by default, it will wait for the command to complete:\n\n```bash\npipen gbatch -- \\\n python myscript.py --input input.txt --output output.txt\n```\n\nWhile waiting, the running logs will be pulled and shown in the terminal.\n\n### View Logs\n\nWhen running in detached mode, one can also pull the logs later by:\n\n```bash\npipen gbatch --view-logs -- \\\n python myscript.py --input input.txt --output output.txt\n\n# or just provide the workdir\npipen gbatch --view-logs --workdir gs://my-bucket/workdir\n```\n\n## Configuration\n\nBecause the daemon pipeline is running on Google Cloud Batch, a Google Storage Bucket path is required for the workdir. For example: `gs://my-bucket/workdir`\n\nA unique job ID will be generated per the name (`--name`) and workdir, so that if the same command is run again with the same name and workdir, it will not start a new job, but just attach to the existing job and pull the logs.\n\nIf `--name` is not provided in the command line, it will try to grab the name (`--name`) from the command line arguments after `--`, or else use "name" from the root section of the configuration file, with a "GbatchDaemon" suffix. If nothing can be found, a default name "PipenGbatchDaemon" will be used.\n\nThen a workdir `{workdir}/<daemon pipeline name>/` will be created to store the meta information.\n\nWith `--profile` provided, the scheduler options (`scheduler_opts`) defined in `~/.pipen.toml` and `./.pipen.toml` will be used as default.\n\n## All Options\n\n```bash\n> pipen gbatch --help\nUsage: pipen gbatch [-h] [--nowait | --view-logs {all,stdout,stderr}] [--workdir WORKDIR]\n [--error-strategy {retry,halt}] [--num-retries NUM_RETRIES] [--prescript PRESCRIPT]\n [--postscript POSTSCRIPT] [--jobname-prefix JOBNAME_PREFIX] [--recheck-interval RECHECK_INTERVAL]\n [--cwd CWD] [--project PROJECT] [--location LOCATION] [--mount MOUNT]\n [--service-account SERVICE_ACCOUNT] [--network NETWORK] [--subnetwork SUBNETWORK]\n [--no-external-ip-address] [--machine-type MACHINE_TYPE] [--provisioning-model {STANDARD,SPOT}]\n [--image-uri IMAGE_URI] [--entrypoint ENTRYPOINT] [--commands COMMANDS] [--runnables RUNNABLES]\n [--allocationPolicy ALLOCATIONPOLICY] [--taskGroups TASKGROUPS] [--labels LABELS] [--gcloud GCLOUD]\n [--name NAME] [--profile PROFILE] [--version]\n [--loglevel {DEBUG,INFO,WARNING,ERROR,CRITICAL,debug,info,warning,error,critical}]\n ...\n\nSimplify running commands via Google Cloud Batch.\n\nKey Options:\n The key options to run the command.\n\n --workdir WORKDIR The workdir (a Google Storage Bucket path is required) to store the meta information of the\n daemon pipeline.\n If not provided, the one from the command will be used.\n command The command passed after `--` to run, with all its arguments. Note that the command should be\n provided after `--`.\n\nScheduler Options:\n The options to configure the gbatch scheduler.\n\n --error-strategy {retry,halt}\n The strategy when there is error happened [default: halt]\n --num-retries NUM_RETRIES\n The number of retries when there is error happened. Only valid when --error-strategy is \'retry\'.\n [default: 0]\n --prescript PRESCRIPT\n The prescript to run before the main command.\n --postscript POSTSCRIPT\n The postscript to run after the main command.\n --jobname-prefix JOBNAME_PREFIX\n The prefix of the name prefix of the daemon job.\n If not provided, try to generate one from the command to run.\n If the command is also not provided, use \'pipen-gbatch-daemon\' as the prefix.\n --recheck-interval RECHECK_INTERVAL\n The interval to recheck the job status, each takes about 0.1 seconds. [default: 600]\n --cwd CWD The working directory to run the command. If not provided, the current directory is used. You\n can pass either a mounted path (inside the VM) or a Google Storage Bucket path (gs://...). If a\n Google Storage Bucket path is provided, the mounted path will be inferred from the mounted paths\n of the VM.\n --project PROJECT The Google Cloud project to run the job.\n --location LOCATION The location to run the job.\n --mount MOUNT The list of mounts to mount to the VM, each in the format of SOURCE:TARGET, where SOURCE must be\n either a Google Storage Bucket path (gs://...). [default: []]\n --service-account SERVICE_ACCOUNT\n The service account to run the job.\n --network NETWORK The network to run the job.\n --subnetwork SUBNETWORK\n The subnetwork to run the job.\n --no-external-ip-address\n Whether to disable external IP address for the VM.\n --machine-type MACHINE_TYPE\n The machine type of the VM.\n --provisioning-model {STANDARD,SPOT}\n The provisioning model of the VM.\n --image-uri IMAGE_URI\n The custom image URI of the VM.\n --entrypoint ENTRYPOINT\n The entry point of the container to run the command.\n --commands COMMANDS The list of commands to run in the container, each as a separate string. [default: []]\n --runnables RUNNABLES\n The JSON string of extra settings of runnables add to the job.json.\n Refer to https://cloud.google.com/batch/docs/reference/rest/v1/projects.locations.jobs#Runnable\n for details.\n You can have an extra key \'order\' for each runnable, where negative values mean to run before\n the main command,\n and positive values mean to run after the main command.\n --allocationPolicy ALLOCATIONPOLICY\n The JSON string of extra settings of allocationPolicy add to the job.json. Refer to\n https://cloud.google.com/batch/docs/reference/rest/v1/projects.locations.jobs#AllocationPolicy\n for details. [default: {}]\n --taskGroups TASKGROUPS\n The JSON string of extra settings of taskGroups add to the job.json. Refer to\n https://cloud.google.com/batch/docs/reference/rest/v1/projects.locations.jobs#TaskGroup for\n details. [default: []]\n --labels LABELS The JSON string of labels to add to the job. Refer to\n https://cloud.google.com/batch/docs/reference/rest/v1/projects.locations.jobs#Job.FIELDS.labels\n for details. [default: {}]\n --gcloud GCLOUD The path to the gcloud command. [default: gcloud]\n\nOptions:\n -h, --help show this help message and exit\n --nowait Run the command in a detached mode without waiting for its completion. [default: False]\n --view-logs {all,stdout,stderr}\n View the logs of a job.\n --name NAME The name of the daemon pipeline.\n If not provided, try to generate one from the command to run.\n If the command is also not provided, use \'PipenCliGbatchDaemon\' as the name.\n --profile PROFILE Use the `scheduler_opts` as the Scheduler Options of a given profile from pipen configuration\n files,\n including ~/.pipen.toml and ./pipen.toml.\n Note that if not provided, nothing will be loaded from the configuration files.\n --version Show the version of the pipen-cli-gbatch package. [default: False]\n --loglevel {DEBUG,INFO,WARNING,ERROR,CRITICAL,debug,info,warning,error,critical}\n Set the logging level for the daemon process. [default: INFO]\n\nExamples:\n \u200b\n # Run a command and wait for it to complete\n > pipen gbatch --workdir gs://my-bucket/workdir -- \\\n python myscript.py --input input.txt --output output.txt\n\n # Use named mounts\n > pipen gbatch --workdir gs://my-bucket/workdir --mount INFILE=gs://bucket/path/to/file \\\n --mount OUTDIR=gs://bucket/path/to/outdir -- \\\n cat $INFILE > $OUTDIR/output.txt\n \u200b\n # Run a command in a detached mode\n > pipen gbatch --nowait --project $PROJECT --location $LOCATION \\\n --workdir gs://my-bucket/workdir -- \\\n python myscript.py --input input.txt --output output.txt\n \u200b\n # If you have a profile defined in ~/.pipen.toml or ./.pipen.toml\n > pipen gbatch --profile myprofile -- \\\n python myscript.py --input input.txt --output output.txt\n \u200b\n # View the logs of a previously run command\n > pipen gbatch --view-logs all --name my-daemon-name \\\n --workdir gs://my-bucket/workdir\n```\n\n## API\n\nThe API can also be used to run commands programmatically:\n\n```python\nimport asyncio\nfrom pipen_cli_gbatch import CliGbatchDaemon\n\npipe = CliGbatchDaemon(config_for_daemon, command)\nasyncio.run(pipe.run())\n```\n\nNote that the daemon pipeline will always be running without caching, so that the command will always be executed when the pipeline is run.\n',
23
23
  'author': 'pwwang',