public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Feature - add support for Amazon EC2
Date: Thu, 22 May 2014 19:55:34 +0100	[thread overview]
Message-ID: <537E4826.4020305@gentoo.org> (raw)
In-Reply-To: <20140520160344.6958ba49.dolsen@gentoo.org>

On 05/21/2014 12:03 AM, Brian Dolbec wrote:
> On Wed, 21 May 2014 04:18:17 +0530
> Proneet Verma <proneet11@gmail.com> wrote:
> 
>>  Hi,
>>
>> I would like to add a feature to the catalyst project. I would like to
>> deliver the following:
>>
>> Catalyst <https://www.gentoo.org/proj/en/releng/catalyst/> module
>> which would be used to build AMI (amazon machine images) and upload
>> it directly to the AWS
>>
>>    - Catalyst currently produces Gentoo stages using spec files into
>> which I would add a feature to build AMIs in the same manner by using
>> the spec file.
>>    - In this manner, user can generate AMIs from latest stages and
>>    configure their system in whatever fashion they want without
>> bloating there system with pre-generated stages (which have
>> unnecessary packages).
>>    - 'rich0' (gentoo-dev Richard Freeman) has very nicely blogged
>> about how to bootstrap Gentoo on EC2
>> [here<http://rich0gentoo.wordpress.com/2012/09/24/gentoo-ec2-tutorial-bootstrapping/>
>>    ] which I would be following to write this module up inside of
>> catalyst for which I would be using Python.
>>    - User would be expected to provide their AWS related information
>> (like region, key pair).
>>
>> Currently, I'll be concentrating on AWS only but would be extending
>> this to Openstack, Virtualbox, DigitalOcean. I have a brief idea
>> about the catalyst module (3.0 branch) and have been following as
>> well as contributing (some minor bug fixes) it from past few months.
>> I'd be really happy to contribute to the gentoo community.
>>
>> Please give me your feedback.
>>
>> Regards,
>> Proneet Verma
>> (irc: proneet @ freenode)
> 
> Yes, by all means, go ahead.  When you have some code, ping me and/or
> others for some review.  Or just send the patches to the mail list.
> But for interim code to review just send a link we can look at it or
> fetch it from.
> 
Indeed that sounds a good idea to me.

-- 
Regards,
Markos Chandras


      parent reply	other threads:[~2014-05-22 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 22:48 [gentoo-catalyst] Feature - add support for Amazon EC2 Proneet Verma
2014-05-20 23:03 ` Brian Dolbec
2014-05-20 23:24   ` Proneet Verma
2014-05-22 18:55   ` Markos Chandras [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537E4826.4020305@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox