You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Colin Williams <la...@gmail.com> on 2015/05/08 05:12:44 UTC
Problems With EC2 Script
I've been trying to set up a mesos cluster on AWS, and I've run into a
number of problems with the script:
- When the script reaches the rsync, the new instances are still
starting up, and so the ssh daemon is not yet available.
- Once I was able to get the cluster set up, the script wasn't able to
find it to perform additional operations like stopping.
- The default instance type is m1.large, which is now considered a
previous generation.
I'd like to spend some time working on these problems. Do these sound like
issues worth solving?
Thanks,
Colin
Re: Problems With EC2 Script
Posted by Cody Maloney <co...@mesosphere.io>.
On Fri, May 8, 2015 at 2:32 PM, Adam Bordelon <ad...@mesosphere.io> wrote:
> Colin, these /ec2 scripts haven't seen much love in a while, and we may
> want to move them out of the main repo.
> I'm not sure if it's worth keeping these up, but if you figure them out,
> feel free to submit a patch.
>
> The question of Mesos on AWS has come up before:
>
> http://search-hadoop.com/m/0Vlr64nJ0d1uPHf31/cloudformation-mesos&subj=Re+Fwd+Questions+about+Mesos
>
> http://search-hadoop.com/m/0Vlr6ttDWImnU5Q1/cloudformation-mesos&subj=Re+Error+when+creating+a+new+HA+cluster+on+EC2
>
> http://search-hadoop.com/m/0Vlr6lGr3215j7yK1/cloudformation-mesos&subj=Re+Simplest+approach+to+installing+Mesos
>
> We base our DCOS <https://mesosphere.com/product/> on AWS installs off
> https://github.com/mbabineau/cloudformation-mesos
I just want to note Mesosphere doesn't actually base DCOS on AWS on those
templates, although the person who wrote / maintains those templates helped
build the templates we now use to deploy DCOS on AWS.
If you're looking to get a mesos cluster up quickly / easily on AWS I'd
definitely recommend signing up for the Mesosphere DCOS Early Access / Beta
program.
>
>
> On Fri, May 8, 2015 at 10:44 AM, Colin Williams <la...@gmail.com> wrote:
>
> > Ouch, refereeing = referring. Sorry about the autocorrect fail.
> >
> > On Fri, May 8, 2015 at 8:54 AM, Colin Williams <la...@gmail.com>
> wrote:
> >
> > > I'm sorry, I'm refereeing to the script ec2/mesos-ec2.
> > >
> > > Colin
> > > On May 8, 2015 2:48 AM, "Erik Weathers" <ew...@groupon.com> wrote:
> > >
> > >> Can you please clarify what this "the script" thing is that you're
> > >> referring to? :-)
> > >>
> > >> - Erik
> > >>
> > >> On Thu, May 7, 2015 at 8:12 PM, Colin Williams <la...@gmail.com>
> > wrote:
> > >>
> > >> > I've been trying to set up a mesos cluster on AWS, and I've run
> into a
> > >> > number of problems with the script:
> > >> >
> > >> > - When the script reaches the rsync, the new instances are still
> > >> > starting up, and so the ssh daemon is not yet available.
> > >> > - Once I was able to get the cluster set up, the script wasn't
> able
> > >> to
> > >> > find it to perform additional operations like stopping.
> > >> > - The default instance type is m1.large, which is now considered
> a
> > >> > previous generation.
> > >> >
> > >> > I'd like to spend some time working on these problems. Do these
> sound
> > >> like
> > >> > issues worth solving?
> > >> >
> > >> > Thanks,
> > >> > Colin
> > >> >
> > >>
> > >
> >
>
Re: Apache Mesos Committer Checklist
Posted by Benjamin Mahler <bm...@twitter.com.INVALID>.
Thanks Bernd! Looks great.
On Fri, May 8, 2015 at 3:47 PM, Vinod Kone <vi...@apache.org> wrote:
> This looks great. Thanks for sharing!
>
> On Fri, May 8, 2015 at 3:17 PM, Bernd Mathiske <be...@mesosphere.io>
> wrote:
>
> > As mentioned at the community meeting at Twitter headquarters yesterday,
> a
> > few of us have compiled a list that Apache Mesos committer candidates can
> > use to gather material for their nomination. It is in no way binding.
> Just
> > a collection of categories of achievements and behaviors that can be
> > helpful to look at, including handy links to relevant JIRA tickets etc.
> > Some of us aspiring committers will play with this and start filling it
> out
> > to gauge by ourselves where we stand so far. I propose that eventually
> some
> > variant of this doc can be handed over to the PMC to facilitate
> evaluating
> > a nomination case.
> >
> > The doc at this link is open for viewing and commenting by everybody who
> > has the link:
> >
> >
> >
> https://docs.google.com/document/d/1orsIXW41W_W-v4fb3jU1QntND6m961qOLalFDsZ-sxg/edit?usp=sharing
> > <
> >
> https://docs.google.com/document/d/1orsIXW41W_W-v4fb3jU1QntND6m961qOLalFDsZ-sxg/edit?usp=sharing
> > >
> >
> > Bernd
> >
> >
>
Re: Apache Mesos Committer Checklist
Posted by Vinod Kone <vi...@apache.org>.
This looks great. Thanks for sharing!
On Fri, May 8, 2015 at 3:17 PM, Bernd Mathiske <be...@mesosphere.io> wrote:
> As mentioned at the community meeting at Twitter headquarters yesterday, a
> few of us have compiled a list that Apache Mesos committer candidates can
> use to gather material for their nomination. It is in no way binding. Just
> a collection of categories of achievements and behaviors that can be
> helpful to look at, including handy links to relevant JIRA tickets etc.
> Some of us aspiring committers will play with this and start filling it out
> to gauge by ourselves where we stand so far. I propose that eventually some
> variant of this doc can be handed over to the PMC to facilitate evaluating
> a nomination case.
>
> The doc at this link is open for viewing and commenting by everybody who
> has the link:
>
>
> https://docs.google.com/document/d/1orsIXW41W_W-v4fb3jU1QntND6m961qOLalFDsZ-sxg/edit?usp=sharing
> <
> https://docs.google.com/document/d/1orsIXW41W_W-v4fb3jU1QntND6m961qOLalFDsZ-sxg/edit?usp=sharing
> >
>
> Bernd
>
>
Apache Mesos Committer Checklist
Posted by Bernd Mathiske <be...@mesosphere.io>.
As mentioned at the community meeting at Twitter headquarters yesterday, a few of us have compiled a list that Apache Mesos committer candidates can use to gather material for their nomination. It is in no way binding. Just a collection of categories of achievements and behaviors that can be helpful to look at, including handy links to relevant JIRA tickets etc. Some of us aspiring committers will play with this and start filling it out to gauge by ourselves where we stand so far. I propose that eventually some variant of this doc can be handed over to the PMC to facilitate evaluating a nomination case.
The doc at this link is open for viewing and commenting by everybody who has the link:
https://docs.google.com/document/d/1orsIXW41W_W-v4fb3jU1QntND6m961qOLalFDsZ-sxg/edit?usp=sharing <https://docs.google.com/document/d/1orsIXW41W_W-v4fb3jU1QntND6m961qOLalFDsZ-sxg/edit?usp=sharing>
Bernd
Re: Problems With EC2 Script
Posted by Adam Bordelon <ad...@mesosphere.io>.
Colin, these /ec2 scripts haven't seen much love in a while, and we may
want to move them out of the main repo.
I'm not sure if it's worth keeping these up, but if you figure them out,
feel free to submit a patch.
The question of Mesos on AWS has come up before:
http://search-hadoop.com/m/0Vlr64nJ0d1uPHf31/cloudformation-mesos&subj=Re+Fwd+Questions+about+Mesos
http://search-hadoop.com/m/0Vlr6ttDWImnU5Q1/cloudformation-mesos&subj=Re+Error+when+creating+a+new+HA+cluster+on+EC2
http://search-hadoop.com/m/0Vlr6lGr3215j7yK1/cloudformation-mesos&subj=Re+Simplest+approach+to+installing+Mesos
We base our DCOS <https://mesosphere.com/product/> on AWS installs off
https://github.com/mbabineau/cloudformation-mesos
On Fri, May 8, 2015 at 10:44 AM, Colin Williams <la...@gmail.com> wrote:
> Ouch, refereeing = referring. Sorry about the autocorrect fail.
>
> On Fri, May 8, 2015 at 8:54 AM, Colin Williams <la...@gmail.com> wrote:
>
> > I'm sorry, I'm refereeing to the script ec2/mesos-ec2.
> >
> > Colin
> > On May 8, 2015 2:48 AM, "Erik Weathers" <ew...@groupon.com> wrote:
> >
> >> Can you please clarify what this "the script" thing is that you're
> >> referring to? :-)
> >>
> >> - Erik
> >>
> >> On Thu, May 7, 2015 at 8:12 PM, Colin Williams <la...@gmail.com>
> wrote:
> >>
> >> > I've been trying to set up a mesos cluster on AWS, and I've run into a
> >> > number of problems with the script:
> >> >
> >> > - When the script reaches the rsync, the new instances are still
> >> > starting up, and so the ssh daemon is not yet available.
> >> > - Once I was able to get the cluster set up, the script wasn't able
> >> to
> >> > find it to perform additional operations like stopping.
> >> > - The default instance type is m1.large, which is now considered a
> >> > previous generation.
> >> >
> >> > I'd like to spend some time working on these problems. Do these sound
> >> like
> >> > issues worth solving?
> >> >
> >> > Thanks,
> >> > Colin
> >> >
> >>
> >
>
Re: Problems With EC2 Script
Posted by Colin Williams <la...@gmail.com>.
Ouch, refereeing = referring. Sorry about the autocorrect fail.
On Fri, May 8, 2015 at 8:54 AM, Colin Williams <la...@gmail.com> wrote:
> I'm sorry, I'm refereeing to the script ec2/mesos-ec2.
>
> Colin
> On May 8, 2015 2:48 AM, "Erik Weathers" <ew...@groupon.com> wrote:
>
>> Can you please clarify what this "the script" thing is that you're
>> referring to? :-)
>>
>> - Erik
>>
>> On Thu, May 7, 2015 at 8:12 PM, Colin Williams <la...@gmail.com> wrote:
>>
>> > I've been trying to set up a mesos cluster on AWS, and I've run into a
>> > number of problems with the script:
>> >
>> > - When the script reaches the rsync, the new instances are still
>> > starting up, and so the ssh daemon is not yet available.
>> > - Once I was able to get the cluster set up, the script wasn't able
>> to
>> > find it to perform additional operations like stopping.
>> > - The default instance type is m1.large, which is now considered a
>> > previous generation.
>> >
>> > I'd like to spend some time working on these problems. Do these sound
>> like
>> > issues worth solving?
>> >
>> > Thanks,
>> > Colin
>> >
>>
>
Re: Problems With EC2 Script
Posted by Colin Williams <la...@gmail.com>.
I'm sorry, I'm refereeing to the script ec2/mesos-ec2.
Colin
On May 8, 2015 2:48 AM, "Erik Weathers" <ew...@groupon.com> wrote:
> Can you please clarify what this "the script" thing is that you're
> referring to? :-)
>
> - Erik
>
> On Thu, May 7, 2015 at 8:12 PM, Colin Williams <la...@gmail.com> wrote:
>
> > I've been trying to set up a mesos cluster on AWS, and I've run into a
> > number of problems with the script:
> >
> > - When the script reaches the rsync, the new instances are still
> > starting up, and so the ssh daemon is not yet available.
> > - Once I was able to get the cluster set up, the script wasn't able to
> > find it to perform additional operations like stopping.
> > - The default instance type is m1.large, which is now considered a
> > previous generation.
> >
> > I'd like to spend some time working on these problems. Do these sound
> like
> > issues worth solving?
> >
> > Thanks,
> > Colin
> >
>
Re: Problems With EC2 Script
Posted by Erik Weathers <ew...@groupon.com>.
Can you please clarify what this "the script" thing is that you're
referring to? :-)
- Erik
On Thu, May 7, 2015 at 8:12 PM, Colin Williams <la...@gmail.com> wrote:
> I've been trying to set up a mesos cluster on AWS, and I've run into a
> number of problems with the script:
>
> - When the script reaches the rsync, the new instances are still
> starting up, and so the ssh daemon is not yet available.
> - Once I was able to get the cluster set up, the script wasn't able to
> find it to perform additional operations like stopping.
> - The default instance type is m1.large, which is now considered a
> previous generation.
>
> I'd like to spend some time working on these problems. Do these sound like
> issues worth solving?
>
> Thanks,
> Colin
>