Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 837F210DB8 for ; Tue, 24 Mar 2015 07:19:01 +0000 (UTC) Received: (qmail 18935 invoked by uid 500); 24 Mar 2015 07:19:01 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 18884 invoked by uid 500); 24 Mar 2015 07:19:01 -0000 Mailing-List: contact dev-help@tajo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.apache.org Delivered-To: mailing list dev@tajo.apache.org Received: (qmail 18873 invoked by uid 99); 24 Mar 2015 07:19:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2015 07:19:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.214.174] (HELO mail-ob0-f174.google.com) (209.85.214.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2015 07:18:36 +0000 Received: by obbgg8 with SMTP id gg8so140929099obb.1 for ; Tue, 24 Mar 2015 00:15:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=LTFKWQPFODOZtuU2oyxtVcozZ+fWpZJP+LVhfhzJ2zw=; b=NLc+oxHefsFCBv3F4mCMY4DJy+OjEbchHu3vDuZYn+LNATXqnKPduVCt/CsR3UmLhH hboY45eE3RqPViWvgFKdA3tfLrlxhu1MnIiLXoh1any3V3W1QKh+A5ibFaqn/LmFoOeh VLp1+2NnSupUwZRifl85R7fF66ZkwEpXETG6/KXtmRClpDqPUluZ/5knm4nc1I+/t8FR KULRyUs2YSiI2dEH67dkJomfexMj9nK7swxn5KTQ8Xv5B9YEi+0sCDhkp42+a72Sv5gQ AafunHPCjSgAOJfVyfUOsEkOuYlRuT6AO3BMrKmmncslRwda+y9TjYTPwthXz4Tz3I0O dK1w== X-Gm-Message-State: ALoCoQmmJjrTNDjh7fuSc4+cdhQ0QHBUw2deFOZ8VYab107M+REAOW1C1mvqRMzEkACLlySboVTv MIME-Version: 1.0 X-Received: by 10.60.155.135 with SMTP id vw7mr2274689oeb.62.1427181356929; Tue, 24 Mar 2015 00:15:56 -0700 (PDT) Sender: jhjung@gruter.com Received: by 10.202.60.66 with HTTP; Tue, 24 Mar 2015 00:15:56 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Mar 2015 16:15:56 +0900 X-Google-Sender-Auth: 22rwP7zQuX4fBTb97EoBDk31i48 Message-ID: Subject: Re: Proposal draft for supporting official Tajo docker images. From: Jaehwa Jung To: "dev@tajo.apache.org" Content-Type: multipart/alternative; boundary=047d7bd76720cf68420512038d36 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd76720cf68420512038d36 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Dongjoon Thanks for your understanding. I also think the official docker image will be useful to preliminary users and it will be helpful to promote Tajo. So, I agree for supporting the official image. And I would suggest that the official image just contain hadoop and Tajo excepting third party. Cheers Jaehwa 2015-03-24 14:44 GMT+09:00 Dongjoon Hyun : > Thank you. Now I understand your point clearly. > > By the way, I think we need it for two reasons. > > First, It's for basic users who will not make a docker image. > Making docker images is easy, but Using pre-built images is really easy. > (That's my points) > Even on Windows, users can run Tajo cluster. > > Second, it's for other advanced users. > Making docker image process started from importing another docker images. > In my case, I started from OS images. > If Tajo community provides official Tajo images, many users will start fr= om > our Tajo docker images instead of OS. > It dramatically reduce their time and effort. > > How do you think about the above two reasons? > > Warmly, > Dongjoon. > > > On Tue, Mar 24, 2015 at 2:30 PM, Jaehwa Jung wrote: > > > I think there has been a misunderstanding. > > > > It was intended that we don=E2=80=99t need to maintain the docker image= within > our > > source tree. > > > > And I think we don=E2=80=99t need to announce docker support officially= . > > Because anybody can provide their own docker image autonomously and it > will > > make a wide range of Tajo ecosystem. > > > > 2015-03-24 9:47 GMT+09:00 Dongjoon Hyun : > > > > > No problem! > > > > > > Then, could you make an official Tajo git repository 'contrib', then?= I > > > will make a pull request there. > > > > > > Thank you for your comment. > > > > > > Warmly, > > > Dongjoon. > > > > > > On Tuesday, March 24, 2015, Jaehwa Jung wrote: > > > > > > > Hello Dongjoon > > > > > > > > Thanks for your contribution and it looks good. > > > > > > > > But I suggest to maintain it within another repository like > > > emrboot-strap. > > > > Hadoop and Hadoop ecosystem, such as, Hive don't maintain their > docker > > > > image within their source tree. It would be good to maintain within > > > docker > > > > repository or others. > > > > > > > > Best Regards > > > > Jaehwa > > > > 2015. 3. 23. =EC=98=A4=ED=9B=84 10:07=EC=97=90 "Dongjoon Hyun" > > >=EB=8B=98=EC=9D=B4 > > > > =EC=9E=91=EC=84=B1: > > > > > > > > > That looks a clear and best policy. I totally agree with you. > > > > > You mean '/contrib/dockerfiles', right? I will update my pull > > request. > > > > > For the maintainer issue, I insist to use the current one. :-) > > > > > > > > > > By the way, we need to setup Dockerhub for automated Docker image > > > > building > > > > > and registration. > > > > > Unfortunately, I found that userid 'tajo' in Dockerhub had used b= y > > > > another > > > > > user already. > > > > > It seems that we cannot use ' > https://registry.hub.docker.com/u/tajo/ > > '. > > > > > > > > > > Instead, I think we are able to try to get a really Official > > Repository > > > > for > > > > > Tajo. > > > > > Other open source software communities, e.g. > > > > Ubuntu/CentOS/Postgres/MySQL, > > > > > have theirs. > > > > > It will be 'https://registry.hub.docker.com/_/tajo/'. (Note: '_' > > > > instead > > > > > of 'u') > > > > > > > > > > In this case, I think you are the right person to contact Dockerh= ub > > > > > officially. > > > > > Could you contact Dockerhub, please? > > > > > > > > > > Warmly, > > > > > Dongjoon. > > > > > > > > > > > > > > > On Mon, Mar 23, 2015 at 8:26 PM, Hyunsik Choi > > > > wrote: > > > > > > > > > > > Excellent work! > > > > > > > > > > > > In my opinion, you are the best maintainer because you've made > it. > > > > > > Honestly, I don't have any knowledge about docker. I would > > appreciate > > > > > > it if you continue to maintain it now. I think other guys will > also > > > > > > contribute it later. > > > > > > > > > > > > The docker image is necessary, but this is not directly related > to > > > > > > Tajo core. So, I'd like to suggest to make it as a contribute > > > package. > > > > > > For example, Hadoop maintains or maintained some packages like > > Hadoop > > > > > > streaming and EMR script as contribute packages. If we do, we > > should > > > > > > make '/contrib' directory, and we will maintain the docker imag= es > > in > > > > > > the contrib directory. > > > > > > > > > > > > How do you think about that? > > > > > > > > > > > > Best regards, > > > > > > Hyunsik > > > > > > > > > > > > > > > > > > On Sat, Mar 21, 2015 at 11:01 PM, Dongjoon Hyun < > > dongjoon@apache.org > > > > > > > > > > > wrote: > > > > > > > Hi, all. > > > > > > > > > > > > > > I made a proposal for supporting official Tajo docker images. > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/TAJO-1423 > > > > > > > (It's a WISH issue.) > > > > > > > > > > > > > > Briefly, Docker images provide OS + SW + parameters together > for > > > > > various > > > > > > > purpose, e.g. easy deploying or testing. > > > > > > > > > > > > > > This issue is just for receiving your comments and advices. > > > > > > > > > > > > > > To Hyunsik, > > > > > > > I included your name in this script without your permission. > > Really > > > > > sorry > > > > > > > for that. > > > > > > > It's just because I was not sure which email is preferred by > Tajo > > > > > > > community. So I think you are the best person. (It's my > > intention.) > > > > > > > > > > > > > > Could you be a maintainer for docker images, if this issue is > > > > accepted? > > > > > > > > > > > > > > Warmly, > > > > > > > Dongjoon. > > > > > > > > > > > > > > > > > > > > > --047d7bd76720cf68420512038d36--