On 4 June 2015 at 09:29, Dmitry Tantsur <dtant...@redhat.com> wrote: On the summit we were discussing things like chassis discovery, and arrived > at rough conclusion that we want it to be somewhere in a separate repo. > More precisely, we wanted some place for vendor to contribute code (aka > scripts) that aren't good fit for both standard interfaces and existing > vendor passthrough (chassis discovery again is a good example). > > Our summit notes are sparse on this topic [1], but I'll add in what I see there.
> I suggest to decide something finally to unblock people. A few questions > follow: > > Should we > 1. create one repo for all vendors (say, ironic-contrib-tools) > from summit, "the advantage of having them in one place is that they will get used and improved by other vendors" Presumably there'd be subdirectories, one for each vendor and/or based on functionality. The disadvantage maybe, is who will maintain/own (and merge stuff) in this repo. 2. create a repo for every vendor appearing > from summit, "Creating an ironic-utils-<vendor> repo on stackforge to host each manufacturer set of tools and document the directo" > 3. ask vendors to go for stackforge, at least until their solution shapes > (like we did with inspector)? > I think whatever is decided, should be in stackforge. > 4. %(your_variant)s > > If we go down 1-2 route, should > 1. ironic-core team own the new repo(s)? > 2. or should we form a new team from interested people? > (1 and 2 and not exclusive actually). > > I personally would go for #3 - stackforge. We already have e.g. > stackforge/proliantutils as an example of something closely related to > Ironic, but still independent. > > I'm also fine with #1#1 (one repo, owned by group of interested people). > I don't think any of these third-party tools should be owned by the ironic team. I think that interested parties should get together (or not) to decide where they'd like to put their stuff. Ironic wiki pages (or somewhere) can have a link pointing to these other repo(s). --ruby [1] https://etherpad.openstack.org/p/liberty-ironic-rack-to-ready-state
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev