xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mina Naghshnejad <mina.naghshnejad@gmail.com>
To: xen-devel@lists.xenproject.org
Subject: Fwd: Last minute submission for OUTREACHY!
Date: Tue, 22 Mar 2016 14:59:41 -0700	[thread overview]
Message-ID: <CAPUWuQdT7dEv2w+KhyMOz+xkE8a0C=XhPdGyEkHVgSJScZoA-Q@mail.gmail.com> (raw)
In-Reply-To: <CAPUWuQf2U-VyH0Lzaxij-=Tox0ZRuNo9dXZdY+LixD96ea4qrg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2354 bytes --]

---------- Forwarded message ----------
From: Mina Naghshnejad <mina.naghshnejad@gmail.com>
Date: Tue, Mar 22, 2016 at 2:36 PM
Subject: Re: Last minute submission for OUTREACHY!
To: Brenton Leanhardt <bleanhar@redhat.com>



Great!
For "stages" class variable, "question", "action" types are already defined
elsewhere or should I define them? and also from what I understand Workflow
class only holds information about "question", "action",.. and is not
launching them,

-Mina


On Tue, Mar 22, 2016 at 12:18 PM, Brenton Leanhardt <bleanhar@redhat.com>
wrote:

> Hi Mina,
>
> There's still time to apply but you'll need to act fast.  Here's a task!
>
> Add a workflow module and Workflow class to the ftl_installer module
> that will eventually represent the Workflow format proposed here:
> https://github.com/ftl-toolbox/ftl_installer/pull/4
>
> The Workflow class should:
>
> 1) Take a string argument that represents the location of the workflow
> yaml file.
> 2) Store the contents of the workflow file as a native python datastructure
> 3) Have a method for returning a yaml representation of the internal
> workflow representation.
>
> Don't get too hung up on #2.  We realize it's not very well defined.
> The idea is that this module will represent the API of the workflow
> class and you might find that certain accessor methods are needed to
> make the class easier to work with.  As you get in to the details I'm
> sure you'll have questions and we can iron that out when the time
> comes.  I suspect we'll update the Workflow format based on questions
> you ask.
>
> --Brenton
>
>
> On Tue, Mar 22, 2016 at 1:49 PM, Mina Naghshnejad
> <mina.naghshnejad@gmail.com> wrote:
> > Hello!
> > I am applying for Outreachy and will have to submit my patch in the last
> > minute,
> > I am interested in
> >
> > Project 3: Learn Ansible internals and help us create FTL.
> >
> > I am a PhD student researching on Cloud infrastructure and want to do
> some
> > open source projects at this point to get more in depth insight of
> > real-world clouds.
> > I have experience working with Python and always curious about learning
> new
> > things,
> >
> > regards,
> > Mina
> >
> > _______________________________________________
> > dev mailing list
> > dev@lists.openshift.redhat.com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> >
>

[-- Attachment #1.2: Type: text/html, Size: 3806 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

           reply	other threads:[~2016-03-22 21:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAPUWuQf2U-VyH0Lzaxij-=Tox0ZRuNo9dXZdY+LixD96ea4qrg@mail.gmail.com>]

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='CAPUWuQdT7dEv2w+KhyMOz+xkE8a0C=XhPdGyEkHVgSJScZoA-Q@mail.gmail.com' \
    --to=mina.naghshnejad@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    --subject='Re: Fwd: Last minute submission for OUTREACHY'\!'' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).