[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl

10 Jan 2018


      This is a multi-part message in MIME format...

------------=_1515571288-12694-334
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jira.p... ]

Daniel Belenky updated OVIRT-1836:
----------------------------------
    Epic Link: OVIRT-400
...
Optimize options normalization methods in stdci_dsl
---------------------------------------------------
Key: OVIRT-1836
                URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836
            Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
           Reporter: Daniel Belenky
           Assignee: infra
Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner.
We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away.
Since runners and pipelines care about different sets of options, we need to split the options handling functions.
This will enable us to compose much more efficient pipelines in the API.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)

------------=_1515571288-12694-334
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jira.p... ]</pre>
<h3>Daniel Belenky updated OVIRT-1836:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Optimize options normalization methods in stdci_dsl</h3>
<pre>     Key: OVIRT-1836
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
Reporter: Daniel Belenky
Assignee: infra</pre>
<p>Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. Since runners and pipelines care about different sets of options, we need to split the options handling functions. This will enable us to compose much more efficient pipelines in the API.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p>

<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3t..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>

------------=_1515571288-12694-334--

Daniel Belenky (oVirt JIRA)

tags

participants (1)