[aeolus-comm-mgmt] Aeolus Tech Cabal: 20/11/2012 - Minutes

Jason Guiditta jguiditt at redhat.com
Wed Nov 21 14:42:26 UTC 2012


On 21/11/12 10:49 +0000, Martyn Taylor wrote:
>   Please find Aeolus Tech Cabal initial meeting minutes below.
>   Next weeks Agenda can be found here:
>   [1]http://openetherpad.org/AeolusTechnicalCabal
>   You must add items to the etherpad if they are to be discussed in next
>   Cabal meeting.  Anyone wanting to add items to the Agenda then please
>   do so by 26/11/2012.  This will give people a chance to do some
>   preparation.
>   Next meeting 27/11/2012
>   Regards
>   Martyn
>
>                         Aeolus Tech Cabal: 20/11/2012
>
>Attendees
>
>     * Tomas Sedovic
>     * Martyn Taylor
>     * Jason Guiditta
>     * Scott Seago
>     * Eric Healms
>     * Michal Fojtik
>     * Greg Blomquist
>     * Jaramori Coufal
>
>Agenda
>
>  Procedural Items
<snip/>
>
>Technical
>
>  API Resource Representation.
>
>    1. When shall we use full resource and minimal (link) resource
>       representation in the API?
>    2. How should we allow client to access these resources?
>
>   Martyn Proposed we represent full resources in all top level
>   collections.  Sub resources will be represented as a collection (with
>   url) when one to many relationship is present.  Sub resource
>   collections will include minimal resources.
>   Scott agreed this could solve many of the issues we are currently
>   facing with the API and would be useful in the API.
>   Greg mentioned that this could cause some issues with configure.  But

This was actually me, and I talked to eck right after the meeting,
description of configure needs below.

>   will seek advice from Eck
>   Cabal voted in favour of proposal.
>
>    Actions:
>
>     * Greg will Confirm with Eck

So, this is where eck said he had a problem with our initial pass at
shallow resources (via configure):
https://github.com/aeolusproject/aeolus-configure/blob/master/recipes/aeolus/manifests/conductor/provider.pp#L14

There is a check for provider creation, which includes an 'unless'
that checked the providers index for if $name already exists.  The
name got removed from the index view, so it always passed and it tried
to add the provider every time. First time would obviously work,
future times would fail.  So, the net is, full resources at top level
of collections, this should not be a problem for configure.

-j

>     * Martyn will send mail to list further explaining the proposal.
>     * Martyn will inform API contributers of changes.
>



More information about the aeolus-devel mailing list