pivotal-cf / docs-scheduler Goto Github PK

From this URL https://docs.pivotal.io/scheduler/1-5/using.html - the "Scheduler API Documentation" link is dead here. And this URL https://docs.pivotal.io/scheduler/1-5/ - the "Scheduler HTTP API" link is dead here.
Would like to know how to use the Scheduler HTTP API but not finding anything helpful with dead links everywhere.

Using the scheduler for the first time and followed the docs here: http://docs.pivotal.io/pcf-scheduler/using.html#list-jobs

cf jobs does not seem to be a registered command. When I looked on cf help in the cli and searched for "jobs" "tasks" or "schedule" no commands came up. I tired cf create-job as well but got the same result.

The docs says that the latest release is v1.2.3
https://docs.pivotal.io/pcf-scheduler/1-2/index.html#snapshot

On pivotal network, we have v1.2.5
https://network.pivotal.io/products/p-scheduler/#/releases/221276

Could you please update the documentation page?
Thank you

It's not a requirement that scheduled jobs be idempotent, but it's a really really really good idea. The product all but assumes that the resolution of a failed job is just to run the job again later. There are few if any tools for pausing or ad hoc execution of scheduled jobs for that reason. Some customers are using scheduler with non-idempotent tasks and finding it challenging. Perhaps we can warn off those use cases earlier, or at least make them aware they are not using it in the best possible way.

There are 2 fields for the tile - Name and Plan Name. Both should be documented. For example, does Name refer to the tile name, the bosh deployment name, or the service name as reported by "cf marketplace"?

Docs says "Day of week starts at 0 for Sunday".
However when I tried to run a job earlier today (Wednesday) I needed to use 4 instead of 3:
25 16 ? * 4
So, it seems that the docs are wrong regarding the starting of the week, or that some information is missing.

Also, I believe the example "Every week at 6pm on Friday:" should be
cf schedule-call my-call "0 18 ? * 6"

It would be really nice to have a table with the corresponding weekdays and their numbers/abbreviations.
Also, the scheduling use UTC dates, however I found difficult to find this info on the docs.

Supposedly can set memory and disk limit as of 1.3 CLI. Should update docs accordingly.

Hello, We're working on releasing a 1.5 version of p-scheduler. We need a 1.5 branch of scheduler to create docs for this release.

Thanks,

ben fuller

(link to story, not sure how helpful it will be though https://www.pivotaltracker.com/story/show/175841098)

On https://docs.pivotal.io/pcf-scheduler/1-2/using-jobs.html#list-jobs, it indicates the syntax is

cf delete-job-schedule SCHEDULE-GUID

However, when running the plugin, the following usage message is returned:

Incorrect Usage: the required arguments are JOB_NAME and SCHEDULE_GUID

NAME:
delete-job-schedule - deletes a schedule for a job

USAGE:
delete-job-schedule JOB_NAME SCHEDULE_GUID [--force]

OPTIONS:
--force, -f Force deletion without confirmation

Documentation should reflect all parameters... i.e.:

cf delete-job-schedule JOB-NAME SCHEDULE-GUID

Documentation states that Sundays are '0' in cron expressions, but testing "M H ? * 5" runs on Thursdays at HH:MM.

Currently the scheduler 1.6 API docs are not published : currently a 404.

Pivotal uses GITBOT to synchronize Github issues and pull requests with Pivotal Tracker.
Please add your new repo to the GITBOT config-production.yml in the Gitbot configuration repo.
If you don't have access you can send an ask ticket to the CF admins. We prefer teams to submit their changes via a pull request.

Steps:

• Fork this repo: cfgitbot-config
• Add your project to config-production.yml file
• Submit a PR

If there are any questions, please reach out to [email protected].

Describe the bug

A user mentioned that the Product Snapshot on https://docs.pivotal.io/scheduler/1-6/index.html is not current.

Reproduction steps

Go to https://docs.pivotal.io/scheduler/1-6/index.html

Expected behavior

up-to-date snapshot

Additional context

No response

The document for PCF Scheduler mentions only PAS 2.3 as the last supported version. However, the tile description on Pivnet shows that PAS 2.4 and 2.5 are also supported. So, either this document or PivNet description need to be changed.

Hi,
If I have scaled out an an app to have say 8 running instances would a scheduled job/call execute 8 times?
Thanks
John

doc shows example call $ cf delete-call-schedule 2b69e0c2-9664-46bb-4817-54afcedbb65d

this would result in:

Incorrect Usage: the required arguments are `CALL_NAME` and `SCHEDULE_GUID`

NAME:
   delete-call-schedule - deletes a schedule for a call

USAGE:
   delete-call-schedule CALL_NAME SCHEDULE_GUID [--force]

OPTIONS:
   --force, -f   Force deletion without confirmation

The docs say to use the cf logs command to view job logs:

You can view logs for jobs by running `cf logs JOB-NAME --recent`. See the following example:

<pre class="terminal">
$ cf logs my-job --recent<br>
Connected, dumping recent logs for app my-app in org my-org / space my-space as user<span>@</span>example.com...
[...]
2017-04-19T23:04:13.79-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT Creating container
2017-04-19T23:04:14.01-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT Successfully created container
2017-04-19T23:04:14.22-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT bin
2017-04-19T23:04:14.22-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT db
2017-04-19T23:04:14.23-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT Exit status 0
2017-04-19T23:04:14.24-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT Destroying container
2017-04-19T23:04:14.55-0600 [APP/TASK/cc6fab7f-32a9-4404-4574-b0c430a96cd9 -|- 0d30f4f0-11a4-4d6a-7e77-5e1cdc1aa5ec/0]OUT Successfully destroyed container
[...]
</pre>

However, that didn't work when I tried it. cf logs appears to expect an app name, not a job name:

$ cf run-job test-job
Enqueuing job test-job for app <app> in org <org> / space <space> as <user>...
OK

$ cf logs test-job --recent
Retrieving logs for app test-job in org <org> / space <space> as <user>...

Application 'test-job' not found.
FAILED

How this PCF Job scheduler handles Job during daylight Saving . For Example - I am running a job Every Sunday at 5PM EST . Will the job start at 4PM EST during Daylight Savings, or it will be starting at 5 PM only?

on the page http://docs.pivotal.io/pcf-scheduler/1-1/using-api.html there is a link to https://docs.pivotal.io/pcf-scheduler/api . that target does not work. looking at the url schema, i guessed to look at https://docs.pivotal.io/pcf-scheduler/1-1/api/ which seems to be the correct thing.