Re: Review Request 67077: Remove resource properties from ResourceAggregate

2018-05-29 Thread Jing Chen
/build.sh Thanks, Jing Chen

Re: Review Request 67077: Remove resource properties from ResourceAggregate

2018-05-25 Thread Jing Chen
s an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67077/#review203818 --- On May 11, 2018, 3:18 a.m., Jing Chen wrote: > > --- > This is an au

Re: Review Request 67077: Remove resource properties from ResourceAggregate

2018-05-22 Thread Jing Chen
iew203607 --- On May 11, 2018, 3:18 a.m., Jing Chen wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/

Re: Review Request 67077: Remove resource properties from ResourceAggregate

2018-05-10 Thread Jing Chen
://reviews.apache.org/r/67077/diff/2/ Changes: https://reviews.apache.org/r/67077/diff/1-2/ Testing --- ./pants test src/test/python/apache/aurora/config ./pants test src/test/python/apache/aurora/client/cli:cli ./build-support/jenkins/build.sh Thanks, Jing Chen

Review Request 67077: Remove resource properties from ResourceAggregate

2018-05-10 Thread Jing Chen
/aurora/client/cli:cli ./build-support/jenkins/build.sh Thanks, Jing Chen

Review Request 66980: aurora update info command should print out update metadata

2018-05-06 Thread Jing Chen
04 Current status: ROLLED_FORWARD Update events: Status: ROLLING_FORWARD at 2018-05-07T00:52:16 Status: ROLLED_FORWARD at 2018-05-07T00:53:04 Instance events: Instance 0 at 2018-05-07T00:52:16: INSTANCE_UPDATING Instance 0 at 2018-05-07T00:53:04: INSTANCE_UPDATED Metadata: org.apache.aurora.client.update_id: 57bf7161-23eb-4e8a-9d7f-099910a8d9ae ``` Thanks, Jing Chen

Re: Review Request 64341: Add metadata field to Job object in DSL

2017-12-17 Thread Jing Chen
data(key='stat', value='NY')] ) ] ``` Metadata information can be found in **job configuration** of UI as: ``` METADATA state: CA stat: NY ``` Thanks, Jing Chen

Re: Review Request 64341: Add metadata field to Job object in DSL

2017-12-11 Thread Jing Chen
name='metadata_test', task=hello_task, metadata=[Metadata(key='state', value='CA'), Metadata(key='stat', value='NY')] ) ] ``` Metadata information can be found in **job configuration** of UI as: ``` METADATA state: CA stat: NY ``` Thanks, Jing Chen

Re: Review Request 64341: Add metadata field to Job object in DSL

2017-12-10 Thread Jing Chen
even though they have same content - Jing --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/64341/#review192889 ---

Review Request 64341: Add metadata field to Job object in DSL

2017-12-05 Thread Jing Chen
llo_task, metadata={'tag':'metadata test', 'version': 1} ) ] ``` Metadata information can be found in job configuration of UI as: ``` METADATA version: 1 tag: metadata test ``` Thanks, Jing Chen

Review Request 64284: Expose thrift workload stats on pruneTasks() invocations

2017-12-03 Thread Jing Chen
Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 260530 260530 0 4074k 0 --:--:-- --:--:-- --:--:-- 4240k thrift_workload_pruneTasks 0 Thanks, Jing Chen

Re: Review Request 61249: Cron timezone should be configurable per job

2017-09-12 Thread Jing Chen
ot;cron_process", cmdline="echo 'cron job no tz runs'; date")], resources=Resources(cpu=1, ram=1*MB, disk=8*MB) ) ) ] ``` The _next cron run_ is scheduled at `08/04 10:00:00 LOCAL, 08/04 17:00:00 UTC` Thanks, Jing Chen

Re: Review Request 61249: Cron timezone should be configurable per job

2017-09-07 Thread Jing Chen
is will be null for all crons scheduled before this patch landed, and > > below it will default to "GMT", possibly conflicting with the scheduler > > default. > > > > So you can either do a null check here and call predictNextRun when > > it's null,

Re: Review Request 61249: Cron timezone should be configurable per job

2017-08-02 Thread Jing Chen
apache.org/r/61249/#review182031 --- On July 31, 2017, 10:29 a.m., Jing Chen wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https:

Review Request 61249: Cron timezone should be configurable per job

2017-07-31 Thread Jing Chen
e")], resources=Resources(cpu=1, ram=1*MB, disk=8*MB) ) ) ] ``` The _next cron run_ is scheduled at `08/04 10:00:00 LOCAL, 08/04 17:00:00 UTC` Thanks, Jing Chen

Re: Review Request 54624: Expose stats on ZooKeeper connection state

2016-12-20 Thread Jing Chen
zk_connection_state_RECONNECTED_counter 0 zk_connection_state_SUSPENDED 0 zk_connection_state_SUSPENDED_counter 0 ``` * zk_connection_state_STATE shows 1 if STATE is current connection state, otherwise 0. * zk_connection_state_STATE_counter represents occurence times of the STATE since scheduler state Thanks, Jing Chen

Re: Review Request 54624: Expose stats on ZooKeeper connection state

2016-12-11 Thread Jing Chen
or not - Jing --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/54624/#review158773 --- On Dec. 12, 2016, 1:32 a.m.,

Re: Review Request 54624: Expose stats on ZooKeeper connection state

2016-12-11 Thread Jing Chen
zk_connection_state_suspended 0 zk_connection_state_unknown 0 ``` Thanks, Jing Chen

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-11-11 Thread Jing Chen
;: {"gpu": 0, "disk": 8388608, "ram": 1048576, "cpu": 1.0}, "constraints": [ ]}, "production": false, "role": "www-data", "tier": "preemptible", "lifecycle": {"http": {"graceful_shutdown_endpoint": "/quitquitquit", "port": "health", "shutdown_endpoint": "/abortabortabort"}}, "priority": 0} ``` vagrant@aurora:~$ aurora job inspect devcluster/www-data/devel/cron_hello_jing /tmp/test.json --read-json ``` Job level information name: 'cron_hello_jing' role: 'www-data' cluster:'devcluster' instances: '1' cron: schedule: '*/10 * * * *' policy: 'CANCEL_NEW' service:False production: False Task level information name: 'cron_hello_jing' Process 'hello_jing': cmdline: echo 'cron hello jing' ``` Thanks, Jing Chen

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-11-11 Thread Jing Chen
;: {"gpu": 0, "disk": 8388608, "ram": 1048576, "cpu": 1.0}, "constraints": [ ]}, "production": false, "role": "www-data", "tier": "preemptible", "lifecycle": {"http": {"graceful_shutdown_endpoint": "/quitquitquit", "port": "health", "shutdown_endpoint": "/abortabortabort"}}, "priority": 0} ``` vagrant@aurora:~$ aurora job inspect devcluster/www-data/devel/cron_hello_jing /tmp/test.json --read-json ``` Job level information name: 'cron_hello_jing' role: 'www-data' cluster:'devcluster' instances: '1' cron: schedule: '*/10 * * * *' policy: 'CANCEL_NEW' service:False production: False Task level information name: 'cron_hello_jing' Process 'hello_jing': cmdline: echo 'cron hello jing' ``` Thanks, Jing Chen

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-11-07 Thread Jing Chen
This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/53114/#review154902 --- On Oct. 25, 2016, 2:14 a.m., Jing Chen wrote: > > -

Re: Review Request 52665: Populate curator latches with scheduler information

2016-10-29 Thread Jing Chen
t":"aurora.local","port":8081}},"status":"ALIVE"} (CONNECTED) /> get aurora/scheduler/_c_fe00a931-df92-4041-97db-9ef27a56e264-latch-000172 aurora.local Thanks, Jing Chen

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-10-24 Thread Jing Chen
luster/www-data/devel/cron_hello_jing /vagrant/cron_hello_world.aurora --write-json returns: ``` { "job": { "name": "cron_hello_jing", "role": "www-data", "cluster": "devcluster", "instances": "1", "cron": { "schedule": "*/10 * * * *", "policy": "CANCEL_NEW" }, "service": false, "production": false }, "task": { "name": "cron_hello_jing", "processes": [ { "name": "hello_jing", "daemon": false, "ephemeral": false, "final": false, "cmdline": [ "echo 'cron hello jing'" ] } ] } } ``` Thanks, Jing Chen

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-10-24 Thread Jing Chen
a job inspect devcluster/www-data/devel/cron_hello_jing /vagrant/cron_hello_world.aurora --write-json returns: ``` { "job": { "name": "cron_hello_jing", "role": "www-data", "contact": "", "cluster": "devcluster", "instances": "1", "cron": { "schedule": "*/10 * * * *", "policy": "CANCEL_NEW" }, "service": false, "production": false }, "task": { "name": "cron_hello_jing", "processes": [ { "name": "hello_jing", "daemon": false, "ephemeral": false, "final": false, "cmdline": [ "echo 'cron hello jing'" ] } ] } } ``` Thanks, Jing Chen

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-10-24 Thread Jing Chen
your patch (i.e. run `aurora job inspect` on master and this > > branch and diff the output)? > > Jing Chen wrote: > the only difference for non-json rendering is contraint. I use 2 spaces > to indent the containts content. For example, > > beofre: >

Re: Review Request 53114: aurora job inspect should have a --write-json option

2016-10-24 Thread Jing Chen
il. To reply, visit: https://reviews.apache.org/r/53114/#review153696 --- On Oct. 23, 2016, 12:37 a.m., Jing Chen wrote: > > --- > This is an automatically generated e-mail.

Review Request 53114: aurora job inspect should have a --write-json option

2016-10-22 Thread Jing Chen
n_hello_jing /vagrant/cron_hello_world.aurora --write-json returns: ``` { "job": { "name": "cron_hello_jing", "role": "www-data", "contact": "", "cluster": "devcluster", "instances": "1", "cron": { "schedule": "*/10 * * * *", "policy": "CANCEL_NEW" }, "service": false, "production": false }, "task": { "name": "cron_hello_jing", "processes": [ { "name": "hello_jing", "daemon": false, "ephemeral": false, "final": false, "cmdline": [ "echo 'cron hello jing'" ] } ] } } ``` Thanks, Jing Chen

Review Request 52665: Populate curator latches with scheduler information

2016-10-09 Thread Jing Chen
Endpoint":{"host":"aurora.local","port":8081},"additionalEndpoints":{"http":{"host":"aurora.local","port":8081}},"status":"ALIVE"} (CONNECTED) /> get /aurora/scheduler/_c_5c25d2a0-7070-4fde-a50d-78364e763e9c-latch-50 127.0.0.1 Thanks, Jing Chen

Re: Review Request 52508: Order job update events and instance events by ID rather than timestamp

2016-10-04 Thread Jing Chen
/JobUpdateDetailsMapper.xml d91c650a46f28b2bd832ce0615bc29e0a87721bc Diff: https://reviews.apache.org/r/52508/diff/ Testing --- Thanks, Jing Chen

Review Request 52508: Order job update events and instance events by ID rather than timestamp

2016-10-04 Thread Jing Chen
update events and instance events by ID rather than timestamp Diffs - src/main/resources/org/apache/aurora/scheduler/storage/db/JobUpdateDetailsMapper.xml d91c650a46f28b2bd832ce0615bc29e0a87721bc Diff: https://reviews.apache.org/r/52508/diff/ Testing --- Thanks, Jing Chen

Review Request 52506: Order job update events and instance events by ID rather than timestamp

2016-10-04 Thread Jing Chen
https://issues.apache.org/jira/browse/AURORA-655 Repository: aurora Description --- Order job update events and instance events by ID rather than timestamp Diffs - Diff: https://reviews.apache.org/r/52506/diff/ Testing --- Thanks, Jing Chen

Re: Review Request 52300: Running task ssh without an instance should pick a random instance

2016-09-30 Thread JING CHEN
/ Testing --- verified in vagrant Thanks, JING CHEN

Re: Review Request 52300: Running task ssh without an instance should pick a random instance

2016-09-30 Thread JING CHEN
/python/apache/aurora/client/cli/test_task.py d2233b67b37f8b34fae62372aa5d95e0a2e827b5 Diff: https://reviews.apache.org/r/52300/diff/ Testing --- verified in vagrant Thanks, JING CHEN

Re: Review Request 52300: Running task ssh without an instance should pick a random instance

2016-09-28 Thread JING CHEN
d2233b67b37f8b34fae62372aa5d95e0a2e827b5 Diff: https://reviews.apache.org/r/52300/diff/ Testing --- verified in vagrant Thanks, JING CHEN

Re: Review Request 52300: Running task ssh without an instance should pick a random instance

2016-09-27 Thread JING CHEN
e addtional suggestion. Thasnks. - JING --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52300/#review150540 --- On Sept. 27, 2016, 10:44 a

Review Request 52300: Running task ssh without an instance should pick a random instance

2016-09-27 Thread JING CHEN
/apache/aurora/client/cli/task.py a8a4edcfda8d879fcc4401bb8f5223de3ee5376d src/test/python/apache/aurora/client/cli/test_options.py f2aae5741611909d5a1700cb4da70dec313e00da Diff: https://reviews.apache.org/r/52300/diff/ Testing --- verified in vagrant Thanks, JING CHEN