commit | 47c689956f77ed635d26f7ec659689002bd047af | [log] [tgz] |
---|---|---|
author | Stephan Erb <serb@apache.org> | Sat Dec 09 14:02:46 2017 +0100 |
committer | Stephan Erb <serb@apache.org> | Sat Dec 09 14:02:46 2017 +0100 |
tree | 6de70a1c9dd5247b98b9e76cf0326b6f20977dd7 | |
parent | 4f0299b2ada81932feb5c06fd223c0fdbd303c18 [diff] |
Update Python deps incl requests and pex * Update requests to 2.18.4. The major visible change is that requests has un-vendored its dependencies in 2.16.0. Details: https://github.com/requests/requests/blob/master/HISTORY.rst * The usage of a newer urllib3 within requests adds support for ipAddress subject alternative name fields in TLS certificates. This is relevant in some Aurora scheduler deployments. * Pex update with various improvements and fixes. The most important feature appears to be first-class support for multi-interpreter and multi-platform pex construction. Details: https://github.com/pantsbuild/pex/blob/master/CHANGES.rst * Update to latest twitter commons. There are no Aurora related fixes in there, but updating does no harm. Details: https://github.com/twitter/commons/commits/master * Regular virtualenv update to the latest version. Details: https://virtualenv.pypa.io/en/latest/changes/ Reviewed at https://reviews.apache.org/r/64382/
Apache Aurora lets you use an Apache Mesos cluster as a private cloud. It supports running long-running services, cron jobs, and ad-hoc jobs. Aurora aims to make it extremely quick and easy to take a built application and run it on machines in a cluster, with an emphasis on reliability. It provides basic operations to manage services running in a cluster, such as rolling upgrades.
To very concisely describe Aurora, it is like a distributed monit or distributed supervisord that you can instruct to do things like run 100 of these, somewhere, forever.
Aurora is built for users and operators.
User-facing Features:
Under the hood, to help you rest easy:
Aurora can take over for most uses of software like monit and chef. Aurora can manage applications, while these tools are still useful to manage Aurora and Mesos themselves.
However, if you have very specific scheduling requirements, or are building a system that looks like a scheduler itself, you may want to explore developing your own framework.
Are you using Aurora too? Let us know, or submit a patch to join the list!
If you have questions that aren‘t answered in our documentation, you can reach out to one of our mailing lists. We’re also often available in IRC: #aurora on irc.freenode.net.
You can also file bugs/issues in our JIRA queue.
Except as otherwise noted this software is licensed under the Apache License, Version 2.0
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.