Re: creating a job?

The create job command takes two parameters: a job specification saying which job from the config you want to start, and the config file. The job specification is a 4-tuple of cluster, role, environment, and jobname. In the vagrant setup: - Our vagrant configuration sets up a cluster named "examp

Re: Review Request 16130: First steps towards aurora client v2

N src/test/python/twitter/aurora/client/cli/test_kill.py PRE-CREATION src/test/python/twitter/aurora/client/cli/util.py PRE-CREATION src/test/python/twitter/aurora/client/commands/test_kill.py 3649969c77f992688a7ddbe592eda8d4edb94036 Diff: https://reviews.apache.org/r/16130/diff/ Testing --- Thanks, Mark Chu-Carroll

Re: Review Request 16130: First steps towards aurora client v2

t; D'oh. Didn't notice that was still there. It was an easy-to-search for placeholder for something. - Mark Chu-Carroll On Dec. 9, 2013, 8:26 p.m., Mark Chu-Carroll wrote: > > --- > This is an automatica

Re: Review Request 16130: First steps towards aurora client v2

erated e-mail. To reply, visit: https://reviews.apache.org/r/16130/#review30113 --- On Dec. 10, 2013, 5:14 p.m., Mark Chu-Carroll wrote: > > --- > This is an automatically gener

Re: Review Request 16130: First steps towards aurora client v2

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16130/#review30259 --- ping? - Mark Chu-Carroll On Dec. 10, 2013, 5:14 p.m., Mark Chu

Re: Review Request 16200: Use binaries for vagrant up.

I'm not one of the reviewers, but I'll still chime in and say BRILLIANT! This is terrific! On Wed, Dec 11, 2013 at 11:13 PM, Kevin Sweeney wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apac

Re: Review Request 16130: First steps towards aurora client v2

> On Dec. 12, 2013, 10:08 a.m., Mark Chu-Carroll wrote: > > ping? Hello? Is anybody out there? - Mark --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16130/#re

Re: Review Request 16130: First steps towards aurora client v2

tps://reviews.apache.org/r/16130/#comment58246> Sorry, not sure what you want here? Just get rid of the trailing spaces, or is there another formatting problem? - Mark Chu-Carroll On Dec. 10, 2013, 5:14 p.m., Mark Chu-Carroll

Re: Review Request 16130: First steps towards aurora client v2

CREATION src/test/python/twitter/aurora/client/cli/test_kill.py PRE-CREATION src/test/python/twitter/aurora/client/cli/util.py PRE-CREATION src/test/python/twitter/aurora/client/commands/test_kill.py 3649969c77f992688a7ddbe592eda8d4edb94036 Diff: https://reviews.apache.org/r/16130/diff/

Re: Review Request 16130: First steps towards aurora client v2

130/ > > Ship it! > > Ship It! > > > - Brian Wickman > > On December 16th, 2013, 4:45 p.m. UTC, Mark Chu-Carroll wrote: > Review request for Aurora, Jonathan Boulle and Brian Wickman. > By Mark Chu-Carroll. > > *Updated Dec. 16, 2013, 4:45 p.m.* > *Reposi

Review Request 16306: "job status" command, with wildcard support.

ent/cli/util.py 46883ecd696b0f6b691831b65bb5e71367cd652a Diff: https://reviews.apache.org/r/16306/diff/ Testing --- Thanks, Mark Chu-Carroll

Review Request 16325: Client v2: add support for options shared between verbs.

/python/twitter/aurora/client/cli/jobs.py 58a723fbc5591565fd51311e0dcfa9567282dbb3 src/main/python/twitter/aurora/client/cli/options.py PRE-CREATION Diff: https://reviews.apache.org/r/16325/diff/ Testing --- Thanks, Mark Chu-Carroll

Review Request 16326: Fix thermos glitch in aurora-12.

39ab1f24a615a8d0cafb571cd463fd8b5ba24f70 Diff: https://reviews.apache.org/r/16326/diff/ Testing --- Ran all unit tests. Thanks, Mark Chu-Carroll

Re: Review Request 16326: Fix thermos glitch in aurora-12.

> https://reviews.apache.org/r/16326/ > > Ship it! > > Ship It! > > > - Brian Wickman > > On December 17th, 2013, 6:15 p.m. UTC, Mark Chu-Carroll wrote: > Review request for Aurora and Brian Wickman. > By Mark Chu-Carroll. > > *Updated Dec. 17, 2013, 6:15 p.m.* >

Re: Review Request 16325: Client v2: add support for options shared between verbs.

ust a wrapper to save the parameters for add_argument in a reusable box. - Mark Chu-Carroll On Dec. 17, 2013, 11:46 a.m., Mark Chu-Carroll wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https:

Re: Review Request 16325: Client v2: add support for options shared between verbs.

--- Thanks, Mark Chu-Carroll

Re: Review Request 16306: "job status" command, with wildcard support.

a! - Mark --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16306/#review30575 --- On Dec. 16, 2013, 5:19 p.m., Mark Chu-Carroll wrote: &g

Re: Review Request 16306: "job status" command, with wildcard support.

rg/r/16306/diff/ Testing --- Thanks, Mark Chu-Carroll

Review Request 16423: client v2: added implementations of job diff, job inspect.

/test_status.py PRE-CREATION src/test/python/twitter/aurora/client/cli/util.py 46883ecd696b0f6b691831b65bb5e71367cd652a Diff: https://reviews.apache.org/r/16423/diff/ Testing --- Added new unit tests for "diff"; inspect doesn't do any API calls that aren't already tested.

Re: Review Request 16306: "job status" command, with wildcard support.

someone please just take a look? - Mark Chu-Carroll On Dec. 18, 2013, 4:27 p.m., Mark Chu-Carroll wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache

Review Request 16673: Bump version number to 0.5.0

--- Bump version number to 0.5.0 Diffs - .auroraversion 10145c26773e530ecf6165907130933fb9e4 Diff: https://reviews.apache.org/r/16673/diff/ Testing --- Thanks, Mark Chu-Carroll

Re: Review Request 16444: Client side changes for the client quota check.

/updater.py <https://reviews.apache.org/r/16444/#comment59760> nitpick, but doesn't the style guide say that local functions should be declared at the top of their enclosing method? - Mark Chu-Carroll On Jan. 3, 2014, 9:01 p.m., Maxim Khutor

Re: Build failed in Jenkins: Aurora #54

Looking into in; not sure what's going on - I ran the tests locally before pushing.. On Fri, Jan 17, 2014 at 11:59 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [mchucarroll] Get rid of ambiguities about ex

Possible Vagrant configuration change

Folks: I've been working on getting together an and-to-end test for open-source Aurora. In order to get it working with a realistic scenario including multiple task instances, I've modified the vagrant configuration to launch to mesos slaves, each of which believes that it has 4cpus to allocate. I

Re: Possible Vagrant configuration change

Sorry - the review is in https://reviews.apache.org/r/17457/. -mark On Mon, Feb 3, 2014 at 2:23 PM, Bill Farner wrote: > Can you link to the review? I can pull down the patch and try it out. > > -=Bill > > > On Sat, Feb 1, 2014 at 6:06 PM, Mark Chu-Carroll &

Vagrant provider statistics

I've been experimenting with using the VMWare provider for Vagrant, and I've gathered some stats on relative performance. General comments: - VMware consistently performs *slightly* better, but provisioning is slower. - VMware appears to be more resilient in the face of configuration

Re: Pants documentation

Hmm. Wonder if any of the stuff I wrote before coming to twitter finally made it in?! Gotta take a look when I have some time. On Tue, Feb 25, 2014 at 9:01 PM, Dan Norris wrote: > Thanks for sharing Kevin! > > It looks like it has a lot more info than what used to be included in the > twitter.

Client Hooks proposal

Since I'm still stuck waiting on reviews, I figured I'd move on to one of the next things on my agenda - Aurora-270, hooks for client commands. Here's what Id like to implement - please beat me up with any criticisms you have. We've got hooks in the client that surround API calls. These are pretty

Re: Client Hooks proposal

a file with defaults, we can add hooks there, which will allow per-user/per-project hooks. -Mark On Tue, Mar 25, 2014 at 3:52 PM, Mark Chu-Carroll wrote: > Since I'm still stuck waiting on reviews, I figured I'd move on to one of > the next things on my agenda - Aurora-270,

Client Command Hooks Proposal, v2

A while ago, I sent around a proposal for how to do hooks in the v2 command line for Aurora. Since then, I've been talking to a variety of people about what they'd like to be able to do with hooks, and I've revised the proposal. Please respond with any comments, criticisms, praise, or brickbats.

Re: Client Command Hooks Proposal, v2

ks for command-line operations. -Mark On Thu, Apr 3, 2014 at 6:19 PM, Kevin Sweeney wrote: > On Thu, Apr 3, 2014 at 2:24 PM, Mark Chu-Carroll >wrote: > > > A while ago, I sent around a proposal for how to do hooks in the v2 > command > > line for Aurora. Since then, I&#

Client Configuration Plugin Extension Proposal

I'm contemplating making a change to the current configuration plugins. I'd like to get a couple of other eyes to glance over it - I'm unsure whether this is sound, or just a reaction to an immediate problem that I encountered working on logging. The way that configuration plugins work right now i

Re: Client Configuration Plugin Extension Proposal

unds reasonable- do you foresee there being any additions > here? I'm not sure there'd be any more call-points, so it seems like a good > way to move forward by adding flexibility. > > On Apr 18, 2014, at 2:15 PM, Mark Chu-Carroll > wrote: > > > I'm cont

Python versions

Folks: For one of the client changes I'm working on, there's a python version compatibility issue. For Python 2.7 and 3.x, there's an "exec" function which I use for loading hooks. In python 2.6, exec is a statement, an the function form doesn't work. This is something that can be worked around,

Re: Python versions

> > for the min python version, its in review right now and if we are going > > to > > > look at setting a default min version this would be a good time to do > it > > > > > > -Jake > > > > > > > > > > > > > > >

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating) RC0

Grabbing the RC, downloading it, running vagrant up, and then trying to just run the end to end test fails, because the aurora client isn't found in the vagrant image: + vagrant ssh devcluster -c 'aurora killall devcluster/vagrant/test/flask_example' bash: line 2: aurora: command not found On Mo

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating) RC0

Attached in the previous email. On Tue, May 6, 2014 at 1:22 PM, Kevin Sweeney wrote: > That's not good. Mark, do you have vagrant up output you can share? > > > On Tue, May 6, 2014 at 8:41 AM, Mark Chu-Carroll >wrote: > > > Grabbing the RC, downloading it, runnin

Proposal for cron changes

In the design doc that's under review at: https://reviews.apache.org/r/18979/, there's a section talking about cron. When we were doing the clientv2 design, we discussed the idea of separating cron functionality on the command line. In the current client, to create a job that runs on a schedule, y

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating) RC0

Henry: yes, if it doesn't work, I'm definitely -1. -Mark On Tue, May 13, 2014 at 7:32 PM, Henry Saputra wrote: > Hi Mark, > > Does this mean you are -1 of the release candidate? > > - Henry > > On Tue, May 6, 2014 at 12:10 PM, Mark Chu-Carroll > wrote:

Adding shorthands, defaults, and initialization files to the aurora client

Folks: Now that clientv2 is approaching stability, I'd like to start making some usability changes. These are completely backwards compatible, but they're intended to make the most common ways of using the aurora client more convenient for users, without making any use-cases more difficult. A pro

Re: Adding shorthands, defaults, and initialization files to the aurora client

7;s very easy to forget what > init file defaults to. At the very least, I would not suggest supporting > kill/killall command defaults. > > > > On Mon, May 19, 2014 at 8:44 AM, Mark Chu-Carroll >wrote: > > > Folks: > > > > Now that clientv2 is approach

Re: Adding shorthands, defaults, and initialization files to the aurora client

I think that bash completion is orthogonal; completions only work if the user sets them up, and runs the correct shell. Built-in shorthands work regardless of how the user invokes the command. Whether they're running bash, zsh, tcsh, or esh in emacs, built-in shorthands are always available. I de

Re: Adding shorthands, defaults, and initialization files to the aurora client

For config file locations, I think having a command-line parameter is an excellent idea, but I'd still like to have a default setting. I think of it a lot like make: when I used to run make, most of the time, I'd just run "make" and expect it to use a reasonable default. When I didn't want the defa

Re: Handling of aurora update when job/task cannot be scheduled

On Tue, May 20, 2014 at 12:03 PM, Anindya Sinha wrote: > > > > > > Currently, aurora create is asynchronous whereas aurora update is > > > synchronous which is leading to an inconsistent behavior of how > instances > > > are scheduled in create vs update. > > > > I don't necessarily see the immedia

Updated proposal: Aurora Shorthands

The bulk of the feedback from the first round of comments on this could be summed up, roughly "get rid of the stupid command shortcuts you dope, they're a menace!". Message received: they're gone. But I still think that the configurable defaults are valuable. Based on some feedback, I've revised t

Re: Updated proposal: Aurora Shorthands

orthands, i'm pretty > confident people will still have a script to roll up the "build/test", and > "check that the service works" steps. If that holds true, it seems that > the goal of reducing scripting is not met. > > > > -=Bill > > > On Thu, May 22,

Re: Proposal: API changes to getTasksStatus

Interestingly, when we first expanded getTasksStatus, I didn't like the idea, because I thought it would have exactly this problem! It's a *lot* of information to get in a single burst. Have you checked what effect it'll have on the command-line client? In general, the command-line has the context

Re: Proposal: API changes to getTasksStatus

lso going to > be blocked for several seconds while executing getTasksStatus for large > jobs. Making the response more lightweight could be a big win there, but I > would need a better understanding of how the client is using those > responses first. > > > On Tue, May 27, 2014 at

Re: Updated proposal: Aurora Shorthands

d we just concede defeat to. If > I'm typing my commands manually and relying on aliases I'd make a bet that > I'm probably not going to be remembering what I alias'd different parts of > my jobpath to and again, what the order of the jobpath bits are. > > > Thanks

Re: Updated proposal: Aurora Shorthands

test-west = wickman/west/test/service > > test-east = wickman/east/test/service > > prod-west = wickman/west/test/service > > prod-east = wickman/east/test/service > > > > Maybe we could ask users to define pystachio structs with all their > options, then have a pr

One more try at defaults and aliases

I'm nothing if not persistent! After feedback from my second try at proposing a way of doing defaults and aliases, I've got a third draft. Feedback please! # Defaults and Shorthands in the Aurora Client ## Motivation Most of the time, users are doing the same thing, over and over again. The

Re: Does Aurora have a HTTP API?

At the moment, we do not have any kind of API for end-users. It's something that we'd probably like to have in the future, but for now, getting the command-line tools working correctly is more important to us. Any API that we implemented now would be changing so rapidly that it wouldn't be useful

Re: Does Aurora have a HTTP API?

ersus calling a > client which would require parsing of the output from the client. > > Lili > > > - Original Message - > From: "Mark Chu-Carroll" > To: dev@aurora.incubator.apache.org > Sent: Wednesday, June 18, 2014 6:19:53 PM > Subject: Re:

Re: One more try at defaults and aliases

isn’t as > > > well-tested/understood as shell scripts. > > > > > > It seems like we’re set on putting time into this, so if we are, then > > > ignore me and move onward :). IF we were going to go with an approach, > > this > > > seems reasonable

Re: One more try at defaults and aliases

t directory > > FWIW i don't see any particular reason why it needs to be in the root of a > repo/project dir. > > -=Bill > > > On Thu, Jun 19, 2014 at 1:31 PM, Mark Chu-Carroll > wrote: > > > I actually don't agree with standardizing the config fi

Re: One more try at defaults and aliases

-Mark On Thu, Jun 19, 2014 at 4:40 PM, Bill Farner wrote: > On Thu, Jun 19, 2014 at 1:36 PM, Mark Chu-Carroll > wrote: > > > Maybe I'm misunderstanding you? > > > > Where else should you look for a default configuration file, where it can > > automati

Re: One more try at defaults and aliases

Sorry, meant gradle. Back when I worked at Google, I wrote part of blaze, so it's easy to slip and say that when I'm talking about build tools. -Mark On Thu, Jun 19, 2014 at 4:45 PM, Kevin Sweeney wrote: > What's blaze ;-p? > > > On Thu, Jun 19, 2014 at 1:44 PM

Branches

Quick question for the gang: What's the right way to handle experimental branches? I've got a batch of code that I'm not ready to send for review, but I'm getting on a plane tomorrow, and I don't want my laptop to have the only copy of the code. Is it kosher to push my branch to the main git repos

Re: Build failed in Jenkins: Aurora #432

All tests pasts locally, so I'm not sure why they failed in the CB, but I'm going to revert while I debug. -Mark On Tue, Jul 15, 2014 at 11:31 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [mchucarroll]

Re: Build failed in Jenkins: Aurora #435

Ok, reverting again. On Wed, Jul 16, 2014 at 1:03 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [mchucarroll] Improve aurora "job diff" command. > > -- > [...truncat

Python versions (redux)

A couple of months ago, we had a discussion about which python versions to support. (See http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E to refresh your memory.) At the time, we punted on it, bec

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating) RC1

Downloaded, created the vagrant cluster, ran end-to-end tests. Looks good! +1! On Thu, Jul 17, 2014 at 4:53 PM, Bill Farner wrote: > +1 > > -=Bill > > > On Thu, Jul 17, 2014 at 4:09 PM, Bill Farner wrote: > > > The branch used to create the release with is 0.5.0-rc1: > >> > >> > https://git-

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating) RC2

Unfortunately, I'm not having much luck with this one. Vagrant provisioning is failing. Looking at the log, the culprit appears to be: /usr/local/bin/aurorabuild: line 51: ./gradlew: No such file or directory So the scheduler isn't getting built. -Mark On Thu, Jul 24, 2014 at 1:17 PM,

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating) RC2

x27;t contain the gradle wrapper since that > > uses > > > a thin binary jar - you'll need to bootstrap it manually by running > > gradle > > > wrapper in the root of the project in order for things that depend on > > > ./gradlew to work. This is documented

Re: [DISCUSS] Build security

+1 On Wed, Jul 30, 2014 at 12:10 PM, Kevin Sweeney wrote: > Hi all, > > Recently in the news there has been a lot of controversy regarding Maven > Central's lack of HTTPS support (without a donation for an access key which > isn't redistributable, see [1], [2], [3] for context). While Sonatype

Re: Build failed in Jenkins: Aurora #533

Working on fixing it. It's a time-zone issue: Jenkins build is using GMT, my laptop is using EST, which creates a different timestamp in the output. Dammit. On Thu, Sep 4, 2014 at 3:07 PM, Bill Farner wrote: > This was the previous commit. Filed > https://issues.apache.org/jira/browse/AURORA-

Re: Build failed in Jenkins: Aurora #535

Heads up: This is no longer the issue with my test. On Thu, Sep 4, 2014 at 4:19 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [mchucarroll] Fix build failure caused by timezone issue in tests. > >

Error handling in the aurora client

As we promote clientv2 and deprecate v1, we've come across some issues involving error handling in the v2 client. When there's an unexpected error in clientv1, most of the time, it crashes and dumps its stack. Dumping stack is a lousy user experience, but it proves the stack dump, which users can

Re: Error handling in the aurora client

ally > reasonable to throw a stack trace to someone whose .aurora file raised an > exception (since they are writing python they should get the tools needed > to debug python). > > On Thu, Oct 2, 2014 at 12:27 PM, Mark Chu-Carroll > wrote: > > > As we promote clientv2 and

Re: Error handling in the aurora client

hooks, I think it's best to err on the > > side > > > of > > > > overly verbose logging by default rather than have to ask client > users > > to > > > > rerun their command with an extra option just to get a stack trace. > > > > > > > > > >

[jira] [Commented] (AURORA-12) thermos.py trying to len() a generator

[ https://issues.apache.org/jira/browse/AURORA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850735#comment-13850735 ] Mark Chu-Carroll commented on AURORA-12: Proposed fix in h

[jira] [Assigned] (AURORA-12) thermos.py trying to len() a generator

[ https://issues.apache.org/jira/browse/AURORA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll reassigned AURORA-12: -- Assignee: Mark Chu-Carroll (was: brian wickman) > thermos.py trying to len(

[jira] [Created] (AURORA-42) Modify client side code to distinguish between api objects

Mark Chu-Carroll created AURORA-42: -- Summary: Modify client side code to distinguish between api objects Key: AURORA-42 URL: https://issues.apache.org/jira/browse/AURORA-42 Project: Aurora

[jira] [Commented] (AURORA-42) Modify client side code to distinguish between api objects

[ https://issues.apache.org/jira/browse/AURORA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873914#comment-13873914 ] Mark Chu-Carroll commented on AURORA-42: Review: https://reviews.apache.o

[jira] [Created] (AURORA-54) Create remaining clientv2 job verbs

Mark Chu-Carroll created AURORA-54: -- Summary: Create remaining clientv2 job verbs Key: AURORA-54 URL: https://issues.apache.org/jira/browse/AURORA-54 Project: Aurora Issue Type: Task

[jira] [Commented] (AURORA-53) Add update command for clientv2

[ https://issues.apache.org/jira/browse/AURORA-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874940#comment-13874940 ] Mark Chu-Carroll commented on AURORA-53: https://reviews.apache.org/r/17051/

[jira] [Created] (AURORA-53) Add update command for clientv2

Mark Chu-Carroll created AURORA-53: -- Summary: Add update command for clientv2 Key: AURORA-53 URL: https://issues.apache.org/jira/browse/AURORA-53 Project: Aurora Issue Type: Task

[jira] [Commented] (AURORA-54) Create remaining clientv2 job verbs

[ https://issues.apache.org/jira/browse/AURORA-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877821#comment-13877821 ] Mark Chu-Carroll commented on AURORA-54: Review of "restart&

[jira] [Created] (AURORA-76) Implement client v2 to v1 bridge

Mark Chu-Carroll created AURORA-76: -- Summary: Implement client v2 to v1 bridge Key: AURORA-76 URL: https://issues.apache.org/jira/browse/AURORA-76 Project: Aurora Issue Type: Task

[jira] [Assigned] (AURORA-76) Implement client v2 to v1 bridge

[ https://issues.apache.org/jira/browse/AURORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll reassigned AURORA-76: -- Assignee: Mark Chu-Carroll > Implement client v2 to v1 bri

[jira] [Updated] (AURORA-76) Implement bridging framework for clientv2 command line.

[ https://issues.apache.org/jira/browse/AURORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-76: --- Summary: Implement bridging framework for clientv2 command line. (was: Implement client v2

[jira] [Updated] (AURORA-76) Implement bridging for clientv2 command line framework.

[ https://issues.apache.org/jira/browse/AURORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-76: --- Summary: Implement bridging for clientv2 command line framework. (was: Implement bridging

[jira] [Updated] (AURORA-76) Implement bridging for clientv2 command line framework.

[ https://issues.apache.org/jira/browse/AURORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-76: --- Description: To eventually start supporting deployment of clientv2, and to help users

[jira] [Created] (AURORA-79) Move deployment into clientv2

Mark Chu-Carroll created AURORA-79: -- Summary: Move deployment into clientv2 Key: AURORA-79 URL: https://issues.apache.org/jira/browse/AURORA-79 Project: Aurora Issue Type: Task

[jira] [Created] (AURORA-81) Make clientv2 deployable.

Mark Chu-Carroll created AURORA-81: -- Summary: Make clientv2 deployable. Key: AURORA-81 URL: https://issues.apache.org/jira/browse/AURORA-81 Project: Aurora Issue Type: Task

[jira] [Updated] (AURORA-81) Make clientv2 deployable.

[ https://issues.apache.org/jira/browse/AURORA-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-81: --- Description: Before clientv2 can be deployed and used, we need to provide an implementation

[jira] [Created] (AURORA-80) Add end-to-end test of client v2, client v1, and bridged client.

Mark Chu-Carroll created AURORA-80: -- Summary: Add end-to-end test of client v2, client v1, and bridged client. Key: AURORA-80 URL: https://issues.apache.org/jira/browse/AURORA-80 Project: Aurora

[jira] [Commented] (AURORA-76) Implement bridging for clientv2 command line framework.

[ https://issues.apache.org/jira/browse/AURORA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880495#comment-13880495 ] Mark Chu-Carroll commented on AURORA-76: Review: https://reviews.apache.o

[jira] [Assigned] (AURORA-81) Make clientv2 deployable.

[ https://issues.apache.org/jira/browse/AURORA-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll reassigned AURORA-81: -- Assignee: Mark Chu-Carroll > Make clientv2 deploya

[jira] [Created] (AURORA-107) Add "user" noun to client

Mark Chu-Carroll created AURORA-107: --- Summary: Add "user" noun to client Key: AURORA-107 URL: https://issues.apache.org/jira/browse/AURORA-107 Project: Aurora Issue

[jira] [Updated] (AURORA-107) Add "user" noun to client

[ https://issues.apache.org/jira/browse/AURORA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-107: Priority: Major (was: Minor) > Add "user" n

[jira] [Updated] (AURORA-107) Add "user" noun to client

[ https://issues.apache.org/jira/browse/AURORA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-107: Description: Add a "role" noun to clientv2, with "get_quota" a

[jira] [Created] (AURORA-123) Building/provisioning vagrant VMs fails on OSX Mavericks.=

Mark Chu-Carroll created AURORA-123: --- Summary: Building/provisioning vagrant VMs fails on OSX Mavericks.= Key: AURORA-123 URL: https://issues.apache.org/jira/browse/AURORA-123 Project: Aurora

[jira] [Updated] (AURORA-123) Building/provisioning vagrant VMs fails on OSX Mavericks.=

[ https://issues.apache.org/jira/browse/AURORA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-123: Attachment: vagrant-trans.txt Transcript of the error initializing vagrant VMs

[jira] [Created] (AURORA-124) Implement a "task" noun for client v2

Mark Chu-Carroll created AURORA-124: --- Summary: Implement a "task" noun for client v2 Key: AURORA-124 URL: https://issues.apache.org/jira/browse/AURORA-124 Project: Aurora Issue

[jira] [Commented] (AURORA-124) Implement a "task" noun for client v2

[ https://issues.apache.org/jira/browse/AURORA-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883104#comment-13883104 ] Mark Chu-Carroll commented on AURORA-124: - Yes, exactly. > Implement

[jira] [Commented] (AURORA-123) Building/provisioning vagrant VMs fails on OSX Mavericks.=

[ https://issues.apache.org/jira/browse/AURORA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883280#comment-13883280 ] Mark Chu-Carroll commented on AURORA-123: - By default, the open file limi

[jira] [Resolved] (AURORA-123) Building/provisioning vagrant VMs fails on OSX Mavericks.=

[ https://issues.apache.org/jira/browse/AURORA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll resolved AURORA-123. - Resolution: Fixed > Building/provisioning vagrant VMs fails on OSX Maveri

[jira] [Created] (AURORA-125) "aurora ssh" and "aurora run" fail with a pystachio-related error.

Mark Chu-Carroll created AURORA-125: --- Summary: "aurora ssh" and "aurora run" fail with a pystachio-related error. Key: AURORA-125 URL: https://issues.apache.org/jira/browse/AURORA-125

[jira] [Updated] (AURORA-125) Fix clusters.json generated for vagrant."aurora ssh" and "aurora run" fail with a pystachio-related error.

[ https://issues.apache.org/jira/browse/AURORA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Chu-Carroll updated AURORA-125: Summary: Fix clusters.json generated for vagrant."aurora ssh" and "aurora r

  1   2   >