I uploaded my initial codes just to give an idea how it will look like: https://github.com/mina1987/ftl_installer/commit/cd0c24723c41262b62e98b74c75113e1f7dd1211 , let me know of your comments,
Mina On Wed, Mar 23, 2016 at 7:33 AM, Jason DeTiberus <[email protected]> wrote: > > > On Tue, Mar 22, 2016 at 5:36 PM, Mina Naghshnejad < > [email protected]> wrote: > >> 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, >> > > They are not currently defined anywhere, feel free to define those in the > Workflow class for now. > > You are correct in that the Workflow class is for storing information > about the defined workflow and not for launching them. There will be a > different component (yet to be determined) that will interact with the > Parser, Config and Workflow classes to actually execute the described > workflow, interact with the user and the configuration file. > > Feel free to let us know if you have any other questions. > > >> >> -Mina >> >> >> On Tue, Mar 22, 2016 at 12:18 PM, Brenton Leanhardt <[email protected]> >> 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 >>> <[email protected]> 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 >>> > [email protected] >>> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> > >>> >> >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> > > > -- > Jason DeTiberus >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
