<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Miguel,<br>
<br>
My recommendation would be to create a draft blueprint or two
around the larger changes so that you don't spend too much time on
something to have it rejected. Specifically I'm unsure about how
your strategy to change configuration options via an API would
look, eg how would you store and reload the state?<br>
<br>
In general though I like the sound of what you're hoping to do.
Ideally if you were extending the webapp I would like to see it
decoupled from zuul and have the webapp use some kind of RPC, but
that's just my thought. Certainly extending the CLI would be
great!<br>
<br>
Cheers,<br>
Josh<br>
<br>
<pre class="moz-signature" cols="72">Rackspace Australia</pre>
On 3/20/14 3:38 AM, Zuniga Vazquez, Miguel wrote:<br>
</div>
<blockquote cite="mid:CF4F1332.28EA%25mzigavzquez@paypal.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>
<div>Hey Josh</div>
<div><br>
</div>
<div>We’re looking at enabling configuration changes (define
new pipelines, templates, add projects, etc). We already
have some changes added to the scheduler (mostly web hooks
that enabled it to send out HTTP API calls when events are
added/remove) as well as we created some extra reporters. </div>
<div><br>
</div>
<div>We saw the RPC framework and even when we would like to
expand it, due to some security restrictions we won’t be
able to use it. That’s the reason of why we’re looking into
extending either the webapp.py or just adding another module
to it.</div>
<div><br>
</div>
<div>In short words what we’re looking to do is:</div>
<div><br>
</div>
<div>Extend webapp or create a separate module to manage API
calls. </div>
<div>Connect the API to the scheduler directly or by using the
RPC framework locally</div>
<div>Extend the cli client</div>
<div><br>
</div>
<div>Let me know what you guys think.</div>
<div><br>
</div>
<div>
<div><span style="font-family: Calibri;">Miguel Zuniga</span></div>
<div>Cloud Infrastructure Engineering</div>
<div>eBay Inc. / PayPal</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Joshua Hesketh
<<a moz-do-not-send="true"
href="mailto:joshua.hesketh@RACKSPACE.COM">joshua.hesketh@RACKSPACE.COM</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, March
18, 2014 at 4:24 PM<br>
<span style="font-weight:bold">To: </span>Miguel Zuniga <<a
moz-do-not-send="true" href="mailto:mzigavzquez@paypal.com">mzigavzquez@paypal.com</a>>,
"<a moz-do-not-send="true"
href="mailto:openstack-infra@lists.openstack.org">openstack-infra@lists.openstack.org</a>"
<<a moz-do-not-send="true"
href="mailto:openstack-infra@lists.openstack.org">openstack-infra@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: Zuul API<br>
</div>
<div><br>
</div>
<div dir="ltr">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
<div ocsi="0" fpstyle="1" style="word-wrap:break-word;
color:rgb(0,0,0); font-size:14px;
font-family:Calibri,sans-serif">
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">Hi Miguel,<br>
<br>
I'm not sure what the long term plans are for creating an
API but I think it'd be safe to say if you're willing to
work on it any improvements would be welcome!<br>
<br>
Currently zuul has an RPC framework that could be extended
to expose additional functionality. At the moment it only
implements a few methods.<br>
<br>
What kind of functions were you looking to expose over an
API?<br>
<br>
Cheers,<br>
Josh<br>
<br>
<div style="font-family: Times New Roman; color: #000000;
font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF967402"><font
color="#000000" face="Tahoma" size="2"><b>From:</b>
Zuniga Vazquez, Miguel [<a moz-do-not-send="true"
href="mailto:mzigavzquez@paypal.com">mzigavzquez@paypal.com</a>]<br>
<b>Sent:</b> Wednesday, March 19, 2014 3:44 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:openstack-infra@lists.openstack.org">openstack-infra@lists.openstack.org</a><br>
<b>Subject:</b> [OpenStack-Infra] Zuul API<br>
</font><br>
</div>
<div>
<div>Hi everyone</div>
<div><br>
</div>
<div>I got a few questions, I’ve been through your
documentation on how to contribute but before I do
all the setup I want to know from the list whether
if the things that I’m asking would be considered or
if there if there are even on the roadmap.</div>
<div><br>
</div>
<div>I’m creating a CICD architecture for our dev
teams and I was wondering if you:</div>
<ul>
<li>Have plans for creating an API for Zuul?</li>
<li>If not would you be interested if our team
contributes the API for it?</li>
</ul>
<div>In our experience Zuul is a powerful but for our
non-openstack use cases and to incorporate it to
multiple systems/applications the lack of an API
makes it difficult to implement. </div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>
<div><span style="font-family:Calibri">Miguel Zuniga</span></div>
<div>Cloud Infrastructure Engineering</div>
<div>eBay Inc. / PayPal</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</blockquote>
<br>
</body>
</html>