gorealis: A Go library for interacting with Apache Aurora

Hi all, As part of the effort to bring support for custom executors for Apache Aurora, we have developed a library for interacting with the scheduler using Go. The library is essentially a shim on the Thrift API that is needed to interact with Aurora. The project can be found at

Re: aurora "environment" flexibility

There is a patch already in flight for this: https://reviews.apache.org/r/62692/ -Renan On Mon, Oct 2, 2017 at 3:45 PM, Mohit Jaggi wrote: > Folks, > Why is the environment limited to a few strings? Is there a way I can > customize this? > > Mohit. > > > > Error loading

gorealis is now officially a PayPal Open Source Project

Hi all, Just wanted to drop a note about a recent update for gorealis[1]. For those who aren't familiar with it, gorealis is a library that aims to enable users to programmatically interact with the Aurora scheduler without dealing with thrift directly. A few days ago the project was moved from

Re: HTTP API examples

Hi Mohit, I think it would be useful if you could include a link to the documentation on the UI you're talking about. Looking at the source code, the UI uses Thrift via javascript to query the scheduler for the info it needs for each page. As far as I know, there is no way to query the scheduler

Re: [ANNOUNCE] 0.19.0 release

Hi Bill, It's been almost a month since the release. Any idea when the official deb and rpm packages will be released? -Renan On Sat, Nov 11, 2017 at 8:50 AM, Bill Farner wrote: > Hello folks, > > Aurora 0.19.0 has been released! Please see the blog post for more >

[DISCUSS] State of the Community

Hello all, I wanted to bring up a few points for discussion with the community. I'd really like to hear what the community's thoughts are on these issues and how can resolve them. 1. Lack of participation. This is due to many members moving on from the project and becoming dormant. More

Re: [DISCUSS] State of the Community

cipate more, at least with > testing new releases. > > We thank you though! > > Rick and the rest of Chartbeat Engineering > > > > On May 4, 2018, at 2:38 PM, Renan DelValle <re...@apache.org> wrote: > > > > Hello all, > > > > I wanted to bring up a

[NOTICE] Aurora is moving to Apache GitBox

All, The vote to move from the legacy ASF git hosting to the GitBox service has passed. When we finish our move we cannot guarantee that the the legacy ASF git repository will continue to be operational. Thus, I encourage users to evaluate dependencies and prepare to make changes accordingly. As

Re: shutdown vs kill API is Mesos

oc > across the tests!) but Mesos's Java wrapper doesn't seem to have that > call either. Perhaps, that is why David referred to the HTTP API. > > On Thu, Jan 11, 2018 at 1:14 PM, Renan DelValle <renanidelva...@gmail.com> > wrote: > >> https://github.com/apache/aurora/bl

Re: shutdown vs kill API is Mesos

witter was that with status >>> updates that were similar to our production volume, they started to get >>> dropped and tasks end up being LOST and unnecessarily killed. So it's a >>> definite blocker for us to adopt in its current state. We have someone who >>> has fixing

Re: shutdown vs kill API is Mesos

https://github.com/apache/aurora/blob/aae2b0dc73b7534c66982ed07b1f029150e245de/src/main/java/org/apache/aurora/scheduler/mesos/SchedulerDriverModule.java

Re: Staggered deployments

>> Thx >> >> On Jan 31, 2018, at 6:56 PM, David McLaughlin <dmclaugh...@apache.org> >> wrote: >> >> It's not currently possible with a single API call, you'd have to submit >> multiple calls to startJobUpdate, changing the JobUpdateSettings each tim

Staggered deployments

Hi all, We have a use case where we want to deploy X amount of instances in N amount of steps. The size of the batch could potentially change every step. For example, we might start a with deploying 1 instances, followed by batch size of 50, followed by a batch of 49 to deploy 100 instances. Is

[ANNOUNCEMENT] aurora and aurora-packaging repositories moved to gitbox

All, As of today we have transitioned our git repositories for aurora and aurora-packaging from git-wip to gitbox. The old address for the aurora git repository was: https://git-wip-us.apache.org/repos/asf/aurora.git The new address for the aurora git repository is:

Re: [ANNOUNCEMENT] aurora and aurora-packaging repositories moved to gitbox

/apache/aurora.git * aurora-packaging: https://github.com/apache/aurora-packaging.git Apologies for the noise. -Renan On Mon, Jul 30, 2018 at 10:30 AM Renan DelValle wrote: > All, > > As of today we have transitioned our git repositories for aurora and > aurora-packaging from git-w

Regarding our recent move to gitbox

All, I wanted to take a few minutes to explain what our recent change to gitbox means in practice. For our users: * The change is (hopefully) not very impactful. The only thing that changes is the location of the aurora and aurora-packing repositories. Update those as needed by your usage. * You

Slack IRC Gateway support ending

Hi all, Slack has announced that their gateway for IRC will no longer be available after May 15th, 2018. [1] mslackbot was last seen in our IRC channel on February 9th, 2018. [2] I would like to hear some feedback from the community as to how we should proceed. My personal experience has been

Sunsetting official binary package for Ubuntu 14.04 after Aurora 0.21.0

Hi all, We're almost exactly one year away from the end of life of Ubuntu 14.04.[1] Taking this into consideration, I wanted to see how the community felt about 0.21.0 being the last release to have official Ubuntu 14.04 packages. Please let use know what you think! Thanks, -Renan [1]

Unofficial Binaries for Aurora 0.21.0

All, Since we voted to eliminate official binary packages with our last official binary release being 0.20.0, I'm providing UNOFFICIAL binary packages for the community via my own personal bintray account for 0.21.0 These unofficial packages were created with

Volunteers needed

All, We are in dire need of folks who would be willing to commit time to review patches and submit patches to maintain the project. Small things like submitting a patch to upgrade our Mesos dependency (or any other dependency really) go a long way towards keeping the project up to date.

Re: Python 2 is being sunset on January, 2020

be guaranteed to work with Python3. -Renan On Mon, Sep 9, 2019 at 2:34 PM Renan DelValle wrote: > All, > > Python 2 is on it's way out and will no longer be receiving security > updates after Jan 1st, 2020. [1] Aurora currently has a few components > which are currently only compatibl

Python 2 is being sunset on January, 2020

All, Python 2 is on it's way out and will no longer be receiving security updates after Jan 1st, 2020. [1] Aurora currently has a few components which are currently only compatible with Python 2 including thermos. Running Aurora components that are only compatible with Python 2 may become an

Extending Aurora Pluggable Scheduling Proposal

Hello fellow Aurorans, I'd like to share a proposal doc that seeks to lay out a roadmap for bringing in new scheduling features to Aurora. David McLaughlin did a fantastic job of getting the ball rolling with the pluggable scheduling patches he contributed (1) and I'd like to expand upon that