Hi Miguel,
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?
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!
Cheers,
Josh
Rackspace Australia
On 3/20/14 3:38 AM, Zuniga Vazquez, Miguel wrote:
Hey Josh
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.
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.
In short words what we’re looking to do is:
Extend webapp or create a separate module to manage API calls.
Connect the API to the scheduler directly or by using the RPC
framework locally
Extend the cli client
Let me know what you guys think.
Miguel Zuniga
Cloud Infrastructure Engineering
eBay Inc. / PayPal
From: Joshua Hesketh <[email protected]
<mailto:[email protected]>>
Date: Tuesday, March 18, 2014 at 4:24 PM
To: Miguel Zuniga <[email protected]
<mailto:[email protected]>>, "[email protected]
<mailto:[email protected]>"
<[email protected]
<mailto:[email protected]>>
Subject: RE: Zuul API
Hi Miguel,
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!
Currently zuul has an RPC framework that could be extended to expose
additional functionality. At the moment it only implements a few methods.
What kind of functions were you looking to expose over an API?
Cheers,
Josh
------------------------------------------------------------------------
*From:* Zuniga Vazquez, Miguel [[email protected]
<mailto:[email protected]>]
*Sent:* Wednesday, March 19, 2014 3:44 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* [OpenStack-Infra] Zuul API
Hi everyone
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.
I’m creating a CICD architecture for our dev teams and I was wondering
if you:
* Have plans for creating an API for Zuul?
* If not would you be interested if our team contributes the API for it?
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.
Thoughts?
Miguel Zuniga
Cloud Infrastructure Engineering
eBay Inc. / PayPal
_______________________________________________
OpenStack-Infra mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
