commit | 8e5e08ebfe6d848beb4e6037d3ab67e49321ae42 | [log] [tgz] |
---|---|---|
author | Bill Farner <wfarner@apache.org> | Thu Jan 04 08:02:55 2018 -0800 |
committer | Bill Farner <wfarner@apache.org> | Thu Jan 04 08:02:55 2018 -0800 |
tree | f6e7aeb027bcccc05538c99055978c9fdd74ae9f | |
parent | f1d9caf36dea2dbab6ccc44b9ba08a5572d7bbc8 [diff] |
Add a test to detect incompatible storage changes This is intended as a safeguard against future compatibility regressions like [AURORA-1959](https://issues.apache.org/jira/browse/AURORA-1959). I approached this with a few goals: - golden files should be text-based and human-readable. This allows for non-opaque code reviews, and simpler remedy when it's necessary to update the goldens (i.e. copy-pasteable) - guidance for schema evolution should be included directly in test failures - separate detection of 'what the scheduler _can_ read' and 'what the scheduler writes' - reasonably-complete schema coverage with minimal manual labor. These tests auto-generate structs to mitigate maintenance burden of test code as schemas evolve. This is not a replacement for vigilance with data compatibility, but it should at least 1. mitigate unintentional breakages in compatibility, especially for new contributors 2. draw code reviewer attention to compatibility changes in a patch (signaled by changes to golden files) Reviewed at https://reviews.apache.org/r/64519/
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.