hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Guo <paul...@gmail.com>
Subject Re: Publishing HAWQ dev docker images
Date Thu, 29 Dec 2016 02:48:24 GMT
Richard, both hdfs and hawq could run in single node.
hdfs: one datanode and one name node.
hawq: one seg and one master.

2016-12-29 10:38 GMT+08:00 Richard Guo <guofenglinux@gmail.com>:

> Good suggestion to have the hawq cluster with specific version
> pre-installed and pre-configured in docker.
> I will have an investigate on how to implement that.
>
> Now by default hawq cluster is multiple nodes. If you use 'make run', the
> cluster would be one namenode with three datanodes.
> Maybe a better way is to have a parameter to specify it is single or
> multiple.
>
> Best Regards,
> Richard
>
> On Wed, Dec 28, 2016 at 9:07 PM, Ruilong Huo <rhuo@pivotal.io> wrote:
>
> > Great to have this initiative that apache hawq community can have a quick
> > access to hawq deployment and contribute with less effort!
> >
> > If the purpose is to let contributor and user to leverage that for hawq
> > development and usage with minimum cost, it would be better that user can
> > specify the version of hawq release or master branch by default. When the
> > docker is started, the corresponding hawq cluster with specific version
> is
> > up and running.
> >
> > BTW, is the hawq cluster planned to be single node or multiple node?
> >
> >
> > Best regards,
> > Ruilong Huo
> >
> > On Wed, Dec 28, 2016 at 6:24 PM, Hong <xunzhang@apache.org> wrote:
> >
> > > +1 with Lili. Delivering docker images together with HAWQ releases are
> > very
> > > helpful to reproduce the bug environment that users have. It's better
> to
> > > create an official repo for it. Meanwhile, make the base image as
> minimal
> > > as we can.
> > >
> > > Hong
> > >
> > > 2016-12-28 15:54 GMT+08:00 Lili Ma <lilima@apache.org>:
> > >
> > > > Thanks Richard for this work! It will be convenient for others to try
> > > HAWQ.
> > > >
> > > > I think it will be more fancy if we can also merge latest code change
> > to
> > > > auto-build the docker image.
> > > >
> > > > A simple way is that we can provide separate docker images for
> > different
> > > > versions of HAWQ, for instance, delivering docker image together with
> > > HAWQ
> > > > release.
> > > >
> > > > Thanks
> > > > Lili
> > > >
> > > >
> > > >
> > > > 2016-12-28 14:10 GMT+08:00 stanly sheng <stanly.sxiang@gmail.com>:
> > > >
> > > > > We could create a public github account for community as a start
of
> > > > > sharing these facilities tools and environments.
> > > > >
> > > > > We could put the dockerfiles to github. And create a docker hub
> > > account.
> > > > > Create an automatic build repo in docker hub and link it with the
> > > github
> > > > > repo in the github account. Then every commit for the github repo
> > will
> > > > > trigger  a latest docker image build on docker hub. Community will
> > get
> > > > the
> > > > > latest docker image.
> > > > >
> > > > > Best Regards,
> > > > > Xiang Sheng
> > > > >
> > > > > > On Dec 28, 2016, at 1:55 PM, Richard Guo <guofenglinux@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > HAWQ team is building HAWQ dev docker images. The purpose is
to
> > > provide
> > > > > an
> > > > > > out-of-box way for developers to setup build and test environment
> > for
> > > > > HAWQ.
> > > > > >
> > > > > > A demo could be found on github hawq-docker
> > > > > > <https://github.com/guofengrichard/hawq-docker> . Currently
only
> > > > CentOS
> > > > > 7
> > > > > > is supported. CentOS 6 will be supported soon. It is based on
> > > Zhanwei's
> > > > > > work.
> > > > > >
> > > > > > The idea is to predefine all the environment setup steps in
the
> > > > > dockerfile
> > > > > > and then build the image from dockerfile with tools provided
by
> > > docker.
> > > > > > After that, users can simply create containers with the docker
> > image
> > > > and
> > > > > > then do the HAWQ build and test jobs.
> > > > > > Also a Makefile is provided to simplify this process. Please
> refer
> > to
> > > > the
> > > > > > README in the github repository for more details.
> > > > > >
> > > > > > Regarding the place to host the docker images and dockerfiles,
> does
> > > > > anyone
> > > > > > have any idea? Comments and discussions are welcomed.
> > > > > >
> > > > > > Best Regards,
> > > > > > Richard
> > > > >
> > > > >
> > > >
> > >
> >
>

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