It is not yet tracked in our end - we have yet to think about what mesos' presistent resources look like under Aurora. Given the timeframe we're shooting for with 0.7.0, it's unlikely MESOS-1554 will be committed and released by the time we cut 0.7.0.
-=Bill On Mon, Dec 1, 2014 at 2:21 PM, Joe Stein <joe.st...@stealth.ly> wrote: > It might be minor, already tracked or maybe nothing todo but support for > https://issues.apache.org/jira/browse/MESOS-1554 would be awesome :) ( > once > released ) without forcing dedicated service. > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop > ********************************************/ > On Dec 1, 2014 4:17 PM, "Bill Farner" <wfar...@apache.org> wrote: > > > Now that 0.6.0 is buttoned up, it's time to think about what we would > like > > to shoot for in 0.7.0 [1]! > > > > Framing the discussion - i'd like to suggest we keep 0.7.0 a 'minor' > > release to allow us to wrap it up by mid Q1. So while lofty goals are > more > > than welcome in JIRA, let's be somewhat resistant to them in the upcoming > > release. > > > > To summarize what's currently on the docket, we have: > > - removal of several minor deprecated behaviors [2] > > - begin phasing out the 'v1' client > > - promote server-side updates, phase out client-side job update behavior > > > > With that in mind, what else would you all (non-committers welcome) like > to > > see in 0.7.0? > > > > > > [1] https://issues.apache.org/jira/browse/AURORA-872 > > [2] https://issues.apache.org/jira/browse/AURORA-423 > > > > > > -=Bill > > >
