mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pankaj Saha <psa...@binghamton.edu>
Subject Re: creating a mesos cluster with many nodes without public ips
Date Thu, 14 Jul 2016 14:09:21 GMT
hi @pradeep, I have access to many cloud accounts. I was thinking if we can
set up a cluster with many nodes from many cloud networks and many
university networks.

On Thu, Jul 14, 2016 at 3:20 AM, Pradeep Chhetri <
pradeep.chhetri89@gmail.com> wrote:

> Just curious, why are you running master in cloud and slaves in lab, why
> don't you run your entire setup in the lab ? Running cluster like this is
> not recommended.
>
> On Jul 14, 2016 12:35 PM, "haosdent" <haosdent@gmail.com> wrote:
>
> > >Now the problem is I have many other machines in my lab, which does not
> > >have public ip addresses. How can I connect them to the Mesos master?
> >
> > Hi, @Pankaj Currently Mesos agent(slave) must have a public ip which
> could
> > access by Mesos master.
> >
> > On Thu, Jul 14, 2016 at 4:52 AM, Pankaj Saha <psaha4@binghamton.edu>
> > wrote:
> >
> > > Hello Devs,
> > > I have a running Mesos master node with a public IP on a KVM based
> > Virtual
> > > machine on the Cloud, to which I can connect other agents across the
> > > network. I have one machine in my lab which I have public ip and I can
> > > connect it to the Mesos master. I have used below commands to start
> > master
> > > and slaves into the cluster.
> > >
> > > sudo ./bin/mesos-master.sh --work_dir=/var/lib/mesos
> > > --advertise_ip=129.xxx.110.yy
> > >
> > > sudo ./bin/mesos-slave.sh --master=129.xxx.110.yy:5050
> > > --advertise_ip=129.xxx.111.zz
> > >
> > >
> > > Now the problem is I have many other machines in my lab, which does not
> > > have public ip addresses. How can I connect them to the Mesos master?
> > >
> > > if I run slaves without advertise public ip, then I can see the agent
> > > getting added to Mmesos master under the deactivated slaves. And we can
> > not
> > > submit jobs, jobs are getting failed. Mesos master reporting:
> "Transport
> > > endpoint is not connected". I suspect it's not actually connecting to
> the
> > > master.
> > >
> > >
> > > Thanks
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message