On 09/09/2014 12:23 PM, Mac Innes, Kiall wrote: >> -----Original Message----- >> From: Sean Dague [mailto:s...@dague.net] >> Sent: 09 September 2014 15:13 >> To: email@example.com >> Subject: Re: [openstack-dev] [Designate][Horizon][Tempest][DevStack] >> Supporting code for incubated projects >> >> On 09/09/2014 07:58 AM, Mac Innes, Kiall wrote: >>> Hi all, >>> >>> >>> >>> While requesting a openstack/designate-dashboard project from the TC/ >>> >>> Infra – The topic of why Designate panels, as an incubated project, >>> can’t be merged into openstack/horizon was raised. >>> >>> >>> >>> In the openstack/governance review, Russell asked: >>> >>> >>> >>> Hm, I think we should discuss this with the horizon team, then. We are >>> telling projects that incubation is a key time for integrating >>> with other >>> projects. I would expect merging horizon integration into horizon itself >>> to be a part of that. >>> >>> >>> >>> With this in mind – I’d like to start a conversation with the Horizon, >>> Tempest and DevStack teams around merging of code to support >> Incubated >>> projects – What are the drawbacks?, Why is this currently frowned upon >>> by the various teams? And – What do each of the parties believe is the >>> Right Way forward? >> >> I though the Devstack and Tempest cases were pretty clear, once things are >> incubated they are fair game to get added in. >> >> Devstack is usually the right starting point, as that makes it easy for >> everyone >> to have access to the code, and makes the testability by other systems >> viable. >> >> I currently don't see any designate changes that are passing Jenkins that >> need to be addressed, is there something that got missed? >> >> -Sean > > From previous discussions with Tempest team members, we had been informed > this was not the case - this could have been miscommunication.
Once officially incubated it should be fine to add tempest tests. There are tests for queues and baremetal in there. dns should be the same. > For DevStack, I never even asked - After two "Not till you're integrated"'s, > I made > the assumption DevStack would be the same. Devstack policy is basically once incubated, it's all good. We try to resist every stackforge project under the sun trying to put config code in devstack, however we've got a plugin interface so that projects can maintain their devstack integration in their own tree. > I'll get our DevStack part's submitted for review ASAP if that's not the case! > > The Horizon integration though, the spark for this conversation, still stands. > > Thanks, > Kiall > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Sean Dague http://dague.net _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev