Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70C32179C2 for ; Thu, 9 Apr 2015 13:35:03 +0000 (UTC) Received: (qmail 54750 invoked by uid 500); 9 Apr 2015 13:35:02 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 54697 invoked by uid 500); 9 Apr 2015 13:35:02 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 54685 invoked by uid 99); 9 Apr 2015 13:35:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 13:35:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ian@ianduffy.ie designates 209.85.220.173 as permitted sender) Received: from [209.85.220.173] (HELO mail-qk0-f173.google.com) (209.85.220.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 13:34:37 +0000 Received: by qkgx75 with SMTP id x75so124512866qkg.1 for ; Thu, 09 Apr 2015 06:33:50 -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:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=ZdvjUaXTJF2PN25UCYCpdowqaNTqHNMSyxYHbTT5mig=; b=fbt5Gm/oZv7jLkkR0EFOcWFCTAiY/Hae+yG8MWzkrRDnHyqEv0xYSkVhTDuZffRBui e9weGdGPXBTjFlMNoudf3jR7IEbu0pvRE2hVzdgV8+8RvZESpuSZykkYzHvFnUA1JSBD ZIpkXkPP9gSCjkBL03HBmx88fVuO1NeuCZqM3llBEwKwybeX83XlRuDzgQWASIXfgqLl H/UP4jdORXWH35Ol/LqgAdszgLdzf/lEQgQXUfWoGMxe4hU641Ro1JAcEsmhAPqwEhbm ebNqcoPaLJLfrrgTWmryzrDkDgPG75pcD7FRTfVAxmeFdbyxd57qkESw6jMCDCQ49lRL z2og== X-Gm-Message-State: ALoCoQmtPXM8FFGClgmY3WdZalKEb2TQKl0PAkAK/DuKOSpjMA1pFp4H/Q68LNFPHcaz8azDLCPR MIME-Version: 1.0 X-Received: by 10.55.52.129 with SMTP id b123mr59790202qka.94.1428586430531; Thu, 09 Apr 2015 06:33:50 -0700 (PDT) Received: by 10.96.168.104 with HTTP; Thu, 9 Apr 2015 06:33:50 -0700 (PDT) X-Originating-IP: [136.206.142.68] In-Reply-To: <6A45C266-0F6C-46B1-91F0-D9F4C076B2FC@gmail.com> References: <5524F74C.80504@shapeblue.com> <6A45C266-0F6C-46B1-91F0-D9F4C076B2FC@gmail.com> Date: Thu, 9 Apr 2015 14:33:50 +0100 Message-ID: Subject: Re: /tools, devcloud and extras From: Ian Duffy To: CloudStack Dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Awesome! Thanks for the feedback all. I've started to bring over the stuff on my own fork https://github.com/imduffy15/cloudstack/commit/08f1cef3d0e5fae85bb5312c7b7c= 1c82d3e4c7e1 Need to add in the apache licenses everywhere and I wish to test everything again (its been awhile). Expect a PR over the next week or so assuming I can find enough free time. On 9 April 2015 at 07:53, Sebastien Goasguen wrote: > >> On Apr 8, 2015, at 3:48 PM, Ian Duffy wrote: >> >>> If you need to host the readymade DevCloud4 disk images, I can help hos= t >> it on packages.shapeblue.com which can be also mirrored by Lucian. >> >> Thanks but I got this covered. All images are hosted on S3 and shared >> via vagrant-cloud which makes them very easy to import. The question >> refers to the "code" i.e. vagrant file and recipes. >> >>> I would say let's get rid of a lot of archaic /tools stuff, remove the >> /tools/devcloud and replace with devcloud4. Do it boldly! >> >> We sure this is a good idea? I'm cautious of many scripts and >> documents that may reference the deploydb command for devcloud or >> those marvin configuration files for example or run purposes. I don't >> really want to break things for people.... That said introducing mixed >> versions is messy. >> >> Preferably, I'd feel safer to go /tools/devcloud4. We can discuss >> cleaning up at a later point and move things about accordingly? (Yes I >> am totally just problem avoiding here) > > +1 for devcloud4 JDI > >> >> Should this only be applied to master or other branches too? >> > > I would put it everywhere up to 4.3 branch > >>> My Ansible based peppercorn is not really general purpose and assumes >> someone has already setup a Debian/Ubuntu VM/host with a running SSH ser= ver. >> >> OK Cool... I might play about with wrapping vagrant/vmware/parallels >> around this if I find some time (vmware unlikely due to licensing). >> >>> We can put a page on wiki or on website. Put links to books (like >> Sebastien's), blogs, articles etc. >> >> Sounds good to me. I don't know about you guys but I feel there may be >> a need for a rating/commenting system with such a listing. There are >> many duplicate efforts of work, for example of the top of my head I >> believe there are 4 different cookbooks >> >> On 8 April 2015 at 10:39, Rohit Yadav wrote: >>> Hi Ian, >>> >>> On Wednesday 08 April 2015 11:02 AM, Ian Duffy wrote: >>>> >>>> tl;dr I want to move devcloud4 into some community location, where >>>> should I put it? >>> >>> >>> If you need to host the readymade DevCloud4 disk images, I can help hos= t >>> it on packages.shapeblue.com which can be also mirrored by Lucian. >>> >>>> Hi all, >>>> >>>> As previously discussed on the list awhile back I'm wanting to move >>>> the devcloud4[1] stuff into more of a primary view and out of a public >>>> repository that is just hosted on my personal github account. I have >>>> questions around this.... >>>> >>>> 1) For those who have tried devcloud4 did it work, were you happy with >>>> the experience? Do you feel the dependencies on vagrant, chef, >>>> virtualbox, berkshelf, etc. introduce a whole new learning curve that >>>> is too complex? >>>> >>>> 2) Assuming 1) gets positive responses, what would the most >>>> appropriate way to bring in devcloud4? I was thinking of using /tools, >>>> however when I began to explore /tools I found myself in a place of >>>> mystery and wonder.... >>>> >>>> Originally I was thinking it may be acceptable to just replace >>>> /tools/devcloud, however I've come to the conclusion this is a bad >>>> idea given the great marvin configurations that are there and the pom >>>> for deploying the devcloud db. >>>> >>>> Then I began exploring..... >>>> >>>> /tools/devcloud - The original devcloud as documented on rohits >>>> blog.... http://bhaisaab.org/logs/devcloud/ (I think???) >>> >>> >>> I would say let's get rid of a lot of archaic /tools stuff, remove the >>> /tools/devcloud and replace with devcloud4. Do it boldly! >>> >>>> >>>> /tools/appliance/definitions/devcloud - Not a clue what this is? >>>> Appears to be some veewee definitions that build up a single box of >>>> mysql, nfs, management server and xen? Is this used by anyone? >>>> >>>> /tools/vagrant/devcloud - This was cool, it was recently added it is >>>> like the devcloud4 basic setup except it doesn't use chef for mysql >>>> and nfs configuration. Instead it uses a bash script, loved the >>>> simplicity of this. >>> >>> >>> We need a lot of cleanup in tools/vagrant and in /tools in general as >>> Sebastien commented. >>> >>>> /tools/devcloud-kvm - This appears just to be marvin configuration >>>> files and a sql file.... I think it might be neat if we were to update >>>> this with something like Rohit's peppercorn (assuming my understanding >>>> of them is correct they are attempting to achieve the same goal). I >>>> know there's another duplicate effort of a KVM development environment >>>> by Marcus: http://marcus.mlsorensen.com/cloudstack-extras/ >>> >>> >>> My Ansible based peppercorn is not really general purpose and assumes >>> someone has already setup a Debian/Ubuntu VM/host with a running SSH se= rver. >>> >>>> Slightly off topic but.... I think it would be a good idea if we began >>>> to maintain some sort of a "resources" list (more recommended >>>> resources over official resources) for Cloudstack. There's lots of >>>> really cool things out there (chef cookbook, ansible cookbook, >>>> cloudmonkey, marvin, prebuilt templates by openvm.eu, cloudstack perl >>>> client and probably many more....) that folks really wouldn't discover >>>> unless they went searching. >>> >>> >>> We can put a page on wiki or on website. Put links to books (like >>> Sebastien's), blogs, articles etc. >>> >>> Regards, >>> Rohit Yadav >>> Software Architect, ShapeBlue >>> M. +91 8826230892 | rohit.yadav@shapeblue.com >>> Blog: bhaisaab.org | Twitter: @_bhaisaab >>> PS. If you see any footer below, I did not add it :) >>> Find out more about ShapeBlue and our range of CloudStack related servi= ces >>> >>> IaaS Cloud Design & >>> Build >>> CSForge =E2=80=93 rapid IaaS deployment framework >>> CloudStack Consulting >>> CloudStack Software >>> Engineering >>> CloudStack Infrastructure >>> Support >>> CloudStack Bootcamp Training >>> Courses >>> >>> This email and any attachments to it may be confidential and are intend= ed >>> solely for the use of the individual to whom it is addressed. Any views= or >>> opinions expressed are solely those of the author and do not necessaril= y >>> represent those of Shape Blue Ltd or related companies. If you are not = the >>> intended recipient of this email, you must neither take any action base= d >>> upon its contents, nor copy or show it to anyone. Please contact the se= nder >>> if you believe you have received this email in error. Shape Blue Ltd is= a >>> company incorporated in England & Wales. ShapeBlue Services India LLP i= s a >>> company incorporated in India and is operated under license from Shape = Blue >>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Br= asil >>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd= is a >>> company registered by The Republic of South Africa and is traded under >>> license from Shape Blue Ltd. ShapeBlue is a registered trademark. >