cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Duffy <...@ianduffy.ie>
Subject Re: /tools, devcloud and extras
Date Thu, 09 Apr 2015 13:33:50 GMT
Awesome! Thanks for the feedback all.

I've started to bring over the stuff on my own fork
https://github.com/imduffy15/cloudstack/commit/08f1cef3d0e5fae85bb5312c7b7c1c82d3e4c7e1

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 <runseb@gmail.com> wrote:
>
>> On Apr 8, 2015, at 3:48 PM, Ian Duffy <ian@ianduffy.ie> wrote:
>>
>>> If you need to host the readymade DevCloud4 disk images, I can help host
>> 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 server.
>>
>> 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 <rohit.yadav@shapeblue.com> 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 host
>>> 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 server.
>>>
>>>> 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 services
>>>
>>> IaaS Cloud Design &
>>> Build<http://shapeblue.com/iaas-cloud-design-and-build//>
>>> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
>>> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
>>> CloudStack Software
>>> Engineering<http://shapeblue.com/cloudstack-software-engineering/>
>>> CloudStack Infrastructure
>>> Support<http://shapeblue.com/cloudstack-infrastructure-support/>
>>> CloudStack Bootcamp Training
>>> Courses<http://shapeblue.com/cloudstack-training/>
>>>
>>> This email and any attachments to it may be confidential and are intended
>>> 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 necessarily
>>> 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 based
>>> upon its contents, nor copy or show it to anyone. Please contact the sender
>>> if you believe you have received this email in error. Shape Blue Ltd is a
>>> company incorporated in England & Wales. ShapeBlue Services India LLP is
a
>>> company incorporated in India and is operated under license from Shape Blue
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>>> 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.
>

Mime
View raw message