Upgraded Mesos to 0.27.2
Added a new optional Apache Curator backend for performing scheduler leader election. You can enable this with the new -zk_use_curator scheduler argument.
Adding --nosetuid-health-checks flag to control whether the executor runs health checks as the job‘s role’s user.
New scheduler command line argument -offer_filter_duration to control the time after which we expect Mesos to re-offer unused resources. A short duration improves scheduling performance in smaller clusters, but might lead to resource starvation for other frameworks if you run multiple ones in your cluster. Uses the Mesos default of 5s.
New scheduler command line option -framework_name to change the name used for registering the Aurora framework with Mesos. The current default value is ‘TwitterScheduler’.
Added experimental support for launching tasks using filesystem images and the Mesos unified containerizer. See that linked documentation for details on configuring Mesos to use the unified containerizer. Note that earlier versions of Mesos do not fully support the unified containerizer. Mesos 0.28.x or later is recommended for anyone adopting task images via the Mesos containerizer.
Upgraded to pystachio 0.8.1 to pick up support for the new Choice type.
The container property of a Job is now a Choice of either a Container holder, or a direct reference to either a Docker or Mesos container.
New scheduler command line argument -ip to control what ip address to bind the schedulers http server to.
Added experimental support for Mesos GPU resource. This feature will be available in Mesos 1.0 and is disabled by default. Use -allow_gpu_resource flag to enable it.
IMPORTANT: once this feature is enabled, creating jobs with GPU resource will make scheduler snapshot backwards incompatible. Scheduler will be unable to read snapshot if rolled back to previous version. If rollback is absolutely necessary, perform the following steps:
-allow_gpu_resource to false-history_prune_threshold=1mins and -history_max_per_job_threshold=0/h2console endpoint or reduce job update pruning thresholds, e.g.: -job_update_history_pruning_threshold=1mins and -job_update_history_per_job_threshold=0aurora_admin scheduler_snapshot <cluster>Experimental support for a webhook feature which POSTs all task state changes to a user defined endpoint.
Added support for specifying the default tier name in tier configuration file (tiers.json). The default property is required and is initialized with the preemptible tier (preemptible tier tasks can be preempted but their resources cannot be revoked).
--restart-threshold option in the aurora job restart command to match the job updater behavior. This option has no effect now and will be removed in the future release.-framework_name default argument ‘TwitterScheduler’. In a future release this will change to ‘aurora’. Please be aware that depending on your usage of Mesos, this will be a backward incompatible change. For details, see MESOS-703.-thermos_observer_root command line arg has been removed from the scheduler. This was a relic from the time when executor checkpoints were written globally, rather than into a task's sandbox.container property of a Job to a Container holder is deprecated in favor of setting it directly to the appropriate (i.e. Docker or Mesos) container type.numCpus, ramMb and diskMb fields in TaskConfig and ResourceAggregate thrift structs. Use set<Resource> resources to specify task resources or quota values./slaves is deprecated. Please use /agents instead.production field in TaskConfig thrift struct. Use tier field to specify task scheduling and resource handling behavior.resources_*_ram_gb and resources_*_disk_gb metrics have been renamed to resources_*_ram_mb and resources_*_disk_mb respectively. Note the unit change: GB -> MB.aurora job add client command to scale out an existing job.--announcer-hostname to thermos executor to override hostname in service registry endpoint. See here for details.-thermos_home_in_sandbox to the scheduler for optionally changing HOME to the sandbox during thermos executor/runner execution. This is useful in cases where the root filesystem inside of the container is read-only, as it moves PEX extraction into the sandbox. See here for more detail.-require_docker_use_executor that indicates whether the scheduler should accept tasks that use the Docker containerizer without an executor (experimental).--populate_discovery_info. If set to true, Aurora will start to populate DiscoveryInfo field on TaskInfo of Mesos. This could be used for alternative service discovery solution like Mesos-DNS.Identity.roleTaskConfig.environmentTaskConfig.jobNameTaskQuery.ownerAddInstancesConfig parameter to addInstances RPC.-announcer-enable, which was a no-op in 0.12.0.acquireLockreleaseLockgetLocksLock parameters to RPCscreateJobscheduleCronJobdescheduleCronJobrestartShardskillTasksaddInstancesreplaceCronTemplate-mesos_role to Aurora scheduler at start time. This enables resource reservation for Aurora when running in a shared Mesos cluster.org.apache.aurora.metadata. to prevent clashes with other, external label sources.-default_docker_parameters to allow a cluster operator to specify a universal set of parameters that should be used for every container that does not have parameters explicitly configured at the job level.--preserve_env to thermos.--read-json, aurora can now load multiple jobs from one json file, similar to the usual pystachio structure: {"jobs": [job1, job2, ...]}. The older single-job json format is also still supported.aurora config list command now supports --read-json-shiro_after_auth_filter. Optionally specify a class implementing javax.servlet.Filter that will be included in the Filter chain following the Shiro auth filters.addInstances thrift RPC does now increase job instance count (scale out) based on the task template pointed by instance key.AddInstancesConfig argument in addInstances thrift RPC.TaskQuery argument in killTasks thrift RPC to disallow killing tasks across multiple roles. The new safer approach is using JobKey with instances instead.HealthCheckConfig client-side configuration fields: endpoint, expected_response, expected_response_code. These are now set exclusively in like-named fields of HttpHealthChecker.aurora job restart --restart-threshold=[seconds].--announcer-enable. Enabling the announcer previously required both flags --announcer-enable and --announcer-ensemble, but now only --announcer-ensemble must be set. --announcer-enable is a no-op flag now and will be removed in future version.-enable_cors_support. Enabling CORS is now implicit by setting the argument -enable_cors_for.-deduplicate_snapshots and -deflate_snapshots. These features are good to always enable.-enable_job_updates and -enable_job_creation-extra_modules-logtostderr, -alsologtostderr, -vlog, -vmodule, and use_glog_formatter. Removed in favor of the new logback configuration.HealthCheckConfig schema has been restructured to more cleanly allow configuring varied health checkers.--custom_executor_config which will override all other the command line arguments and default values pertaining to the executor.HealthCheckConfig are now deprecated: endpoint, expected_response, expected_response_code in favor of setting them as part of an HttpHealthChecker.apache.thermos package has been removed.apache.gen.aurora package has been renamed to apache.aurora.thrift.apache.gen.thermos package has been renamed to apache.thermos.thrift.apache.thermos.runner package has been introduced, providing the thermos_runner binary.apache.aurora.kerberos package has been introduced, containing the Kerberos-supporting versions of aurora and aurora_admin (kaurora and kaurora_admin).src/main have been removed, see here for details.--root option from the observer.ConfigGroup.instanceIds field has been deprecated. Use ConfigGroup.instances instead.SessionValidator and CapabilityValidator interfaces have been removed. All SessionKey-typed arguments are now nullable and ignored by the scheduler Thrift API.-enable_legacy_constraints has been removed, and the scheduler no longer automatically injects host and rack constraints for production services. (AURORA-1074)...nonprod_ms to ...ms_nonprod (AURORA-1350).--mesos-root This must point to the same path as --work_dir on the mesos slave.src/main/python/apache/aurora/tools:thermossrc/main/python/apache/aurora/tools:thermos_observer