rg/r/45177/
>> >
>> > Has anyone else comments, or identified a blocking issue? Otherwise, this
>> > beta-feature is close to merging, probably even before the RC planned for
>> > tomorrow.
>> > ________________
>> > From:
ng, probably even before the RC planned for
> > tomorrow.
> >
> > From: Zhitao Li
> > Sent: Friday, April 1, 2016 03:10
> > To: dev@aurora.apache.org
> > Subject: Re: Populate DiscoveryInfo in Mesos
> >
> > Benjamin,
> >
> > You are exactly right.
hitao Li
> Sent: Friday, April 1, 2016 03:10
> To: dev@aurora.apache.org
> Subject: Re: Populate DiscoveryInfo in Mesos
>
> Benjamin,
>
> You are exactly right. The problem is on Mesos DNS side because it has its
> own rules of shortening names and replacing dots to other chara
.
From: Zhitao Li
Sent: Friday, April 1, 2016 03:10
To: dev@aurora.apache.org
Subject: Re: Populate DiscoveryInfo in Mesos
Benjamin,
You are exactly right. The problem is on Mesos DNS side because it has its
own rules of shortening names and replacing dots to other characters.
IMO, relying one
cal, collision free DNS names such
> > as
> > > "http-exampled.test.vagrant.twitterscheduler.mesos".
> > >
> > > Bonus points if we get "twitterscheduler" replaced by the actual
> cluster
> > > name.
> > >
> > > __
l, collision free DNS names such
> as
> > "http-exampled.test.vagrant.twitterscheduler.mesos".
> >
> > Bonus points if we get "twitterscheduler" replaced by the actual cluster
> > name.
> >
> >
> > From: Zhitao
gt; > > > optional and configurable plugin on Aurora scheduler side to allow
> > > operator
> > > > to set additional fields before sending the message to Mesos. I like
> > such
> > > > idea because it would enable Aurora users to experiment faster. Do
oints if we get "twitterscheduler" replaced by the actual cluster name.
From: Zhitao Li
Sent: Thursday, March 31, 2016 01:08
To: dev@aurora.apache.org
Subject: Re: Populate DiscoveryInfo in Mesos
On Wed, Mar 30, 2016 at 3:58 PM, Joshua Cohen wro
t; > wrote:
> > >
> > >> I had a closer look at the Mesos documentation, and a design document
> > >> might be unnecessary. Most of the values are optional. We can
> therefore
> > >> leave them out until we have a proper usecase for them.
> >
; >> I had a closer look at the Mesos documentation, and a design document
> >> might be unnecessary. Most of the values are optional. We can therefore
> >> leave them out until we have a proper usecase for them.
> >>
> >> I left a couple of comments in the review request.
l. We can therefore
>> leave them out until we have a proper usecase for them.
>>
>> I left a couple of comments in the review request.
>> ________
>> From: Zhitao Li
>> Sent: Tuesday, March 22, 2016 21:15
>> To: dev@aurora.apache.org
>> Subject: Re: Populate Discover
ument
>>> might be unnecessary. Most of the values are optional. We can therefore
>>> leave them out until we have a proper usecase for them.
>>>
>>> I left a couple of comments in the review request.
>>>
>>
> From: Zhitao Li
> Sent: Tuesday, March 22, 2016 21:15
> To: dev@aurora.apache.org
> Subject: Re: Populate DiscoveryInfo in Mesos
>
> Hi Stephan,
>
> Sorry for the delay on follow up on this. I took a quick look at Aurora
> code, and it's actually quite easy
: Zhitao Li
Sent: Tuesday, March 22, 2016 21:15
To: dev@aurora.apache.org
Subject: Re: Populate DiscoveryInfo in Mesos
Hi Stephan,
Sorry for the delay on follow up on this. I took a quick look at Aurora
code, and it's actually quite easy to pipe this information to Mesos (see
Hi Stephan,
Sorry for the delay on follow up on this. I took a quick look at Aurora
code, and it's actually quite easy to pipe this information to Mesos (see
https://reviews.apache.org/r/45177/ for quick prototype).
I'll take a stab to see how I can get Mesos-DNS to work with this prototype.
IMO
That sounds like a good idea! Great.
If you go ahead with this, please be so kind and start by posting a short
design document here on mailinglist (similar to those here
https://github.com/apache/aurora/blob/master/docs/design-documents.md, but
probably shorter).
This will allow us to split t
16 matches
Mail list logo
