pulling latest master #3

Release docs for 0.14.1

New Release: Singularity-0.14.1

Tailer

add slave and task usage tracking inside singularity ZK

Prevent flapping slave from rejoining cluster

Add a task credit system

Allow new tabs from global search page

Slave Usage Monitoring UI

Pass the user who clicks the "Run Now" button as the value of the environment variable `JOB_USER` in the task environment. Can provide more granular, task-level permissions or auditability.

Two small changes: * Change the name of the environment variable to something more descriptive (`JOB_USER` -> `STARTED_BY_USER`) * Don't set the environment variable at all if the user can't be found.

Add links between tailer versions

fix task direct link to logs

Fix tailer when reloading file

add jita access for updating readWriteAccessGroup

Add in a note about running singularity on docker for mac

Add a small amount of padding at the bottom of the logging container. Now if you scroll all the way to the bottom of log tailer, there should be a small space between the last log line and the bottom of the screen, so that the scrollbar (on MacOS) won't overlap the last line of the text.

Previously there was a configurable timeout applied to the http request involved in grabbing the logs dor tailing, but not one associated with grabbing the sandbox environment for a task. This applies the same timeout the grbbing the sandbox for a task.

Drop the default timeout on HTTP requests to the sandbox from 5 seconds to 2 seconds.

Bump to java 8

More disabled actions for pollers

Pass job user as environment variable to task

Lock logging

better perf zk logging

Add spacing line at the bottom of logs

Reduce timeout on requests to task sandboxes

Put a limit on number of slaves to decommission at once

…caching

Better zk cleanup for removed requests

allow expensive endpoints to be disabled for non-admins

From the docs: > Deploy ids *over* this size will cause deploy requests to fail with 400 > Request ids *over* this size will cause new requests to fail with 400 Example: If `maxDeployIdSize` is set to 50 and `deployId.length()` is 50 an error is still thrown: ``` Deploy id must be less than 50 characters, it is 50 (foobarbizbanghelloworldwhywontmyidworkthisreallyfu) ```

Fix Task Search navigation and refresh

Extend the leader and web caching

correctly redirect when no instances are found

Singularity is configured to automatically kill tasks which are nonresponsive for a certain amount of time after startup (`killAfterTasksDoNotRunDefaultSeconds`, set in the config file). If a task is configured such that it won't start accepting healthchecks for longer than that interval, Singularity will just kill it off, without ever sending health checks. This makes it so that that task configuration will be rejected ahead of time by Singularity.

There were two fields on the new deploy form that were labeled "HC startup delay." This renames one of them to "HC startup timeout." They bot functioned correctly and pointed to the the correct fields in the deploy JSON; the label on one of them was just mixed up.

Previously the copy button on the JSON modal would not copy the text of the modal into the clipboard. This was because by default Bootstrap Modals demand focus, and clipboard js works by creating a hidden text field and copying the text out of that. The fix is allowing the modal to yield focus to the hidden text field. There was an additional performance problem that went into the problem. In particular, attaching the clipboard to a class attaches the clipboard to every modal on the page, even when the modal isn't open. Tis was fixed by starting the clipboard only when the modal is open and destroying it after the modal is closed, to prevent attaching many handlers that accumulate on the page.

Scale message

Mark as not bouncing if paused before bounce completes

Fix proxy to leader calls

Use web cache for request groups

use a zk cache for deploy data

Immediately decline offers from decommissioned slaves

leader cache for task history updates

If a task is currently stopped and never reached the RUNNING state, don't show the "Logs" section, or include a link to "tail_of_finished_service.log".

Was previously giving perhaps too much information to the user (ie, that the upper limit was coming from how long we would wait to kill a task that didn't appear to be starting). Not it just reflects the maximum amount of time that you are allowed to put down.

Slight style improvement; prefer using `_.bindAll` over many calls to `bind`.

Instead of showing a red label with "Task lost" when a task failed to start (eg, due to it attempting to accept an invalid offer), show a blue (info) label with the label "Task aborted."

Don't redirect until done fetching active tasks

MD5 is case insensitive

switch not loaded to loading

If the directory is linked directory is empty - either there never was anything there or whatever was there has now been cleaned up - don't show a link to the latest log on the task detail page.

Delay pollers when under heavy load

Was previously checking the `length` property to determine if a given array had contents. This didn't work because in cases where the directory had been cleaned up, the query to get that field would respond with an error code, which resulted in `files` being `null` or `undefined`, rather than the empty array.

In some cases the whole object can be null, not just a field of it. This checks that the object is present before accessing its fields, which should hopefully prevent more exceptions from being thrown due to state oddities.

React requires that a component evaluate to either null, a dom element, or a react component when it renders. The `TaskLatestLog` component was rendering as `false`, rather than `null`, in cases when files were not loaded - in particular, when following links directly into a directory rather than the task page itself.

Warn when removing a request with lb configs

Ability to provide HttpConfig for SingularityClient

Allow copying from the JSON button dialog

When the page was loaded the first time, the call to get the files to the directory wasn't being called with the directory splat. It was therefore always fetching the files from the top-level directory. When linked to the top level directory, this wasn't notable, but links into the subdirectory of the file browser would seem as if the directory was empty until going back to the root directory.

Add getTaskByRunIdForRequest to client

Modify the default command for grep that's specified

Update README.md

…elay Forbid health checks longer than kill time

allow artifact list

add leader cache

Don't show logs panel if task never running

Add ability to prefix all email subjects

Include deploy marker and oldest deploy step in state

More flexible match on filename from logrotate

Write files in subdirectories to splat path

don't include cleaning tasks in instance count

Be sure to close Graphite properly

Spread to all slaves

0.15.0 release notes

New Release: Singularity-0.15.0

sync branches with master

Typo

Fix deleting request failure due to task cleanup failure

Some of the documentation still referred to old dependencies, in particular Java 7 and Dropwizard 0.x. Either removed or bumped these to refer to current versions.

Bump version numbers in documentation

Fix maxDeployIdSize and maxRequestIdSize validation

Commits on Mar 22, 2017

move from hard coding to util function

matush-v committed Mar 22, 2017

Configuration menu

View commit details

Copy full SHA for a2d64e7

Browse repository at this point

Copy the full SHA

a2d64e7 View commit details

Browse the repository at this point in the history

Commits on Apr 27, 2017

Be sure to close Graphite properly

ssalinas committed Apr 27, 2017

Configuration menu

View commit details

Copy full SHA for 3ea075b

Browse repository at this point

Copy the full SHA

3ea075b View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

pulling latest master #3

pulling latest master #3

Commits on Mar 17, 2017

Commits on Mar 20, 2017

Commits on Mar 21, 2017

Commits on Mar 22, 2017

Commits on Mar 23, 2017

Commits on Mar 24, 2017

Commits on Mar 27, 2017

Commits on Mar 28, 2017

Commits on Mar 29, 2017

Commits on Mar 30, 2017

Commits on Mar 31, 2017

Commits on Apr 4, 2017

Commits on Apr 5, 2017

Commits on Apr 6, 2017

Commits on Apr 7, 2017

Commits on Apr 10, 2017

Commits on Apr 11, 2017

Commits on Apr 12, 2017

Commits on Apr 13, 2017

Commits on Apr 14, 2017

Commits on Apr 18, 2017

Commits on Apr 19, 2017

Commits on Apr 20, 2017

Commits on Apr 21, 2017

Commits on Apr 26, 2017

Commits on Apr 27, 2017

Commits on Apr 28, 2017

Commits on May 1, 2017

Commits on May 5, 2017

Commits on May 8, 2017