Hi John, fully agreed on your proposal.
On Mon, Jan 18, 2016 at 10:59:03AM -0500, John Trowbridge wrote: > I have been tracking the issues when deploying with current from all > other projects[2] (as opposed to using an old pinned delorean for > non-tripleo projects). This has been a rapidly moving target (that we > have yet to hit for Mitaka), since we are not doing this in CI (which I > totally get the reasons for). > > I think if we want to have TripleO working with the rest of OpenStack's > Mitaka milestone 2, we will need to prioritize resolving the outstanding > issues this week. I would love to see us not merge anything that is not > related to either adding some validation of the deployed overcloud or > fixing some issue related to deploying with delorean current for all > packages. I gave this a shot and after manually installing python-gnocchiclient in the undercloud (BZ https://bugzilla.redhat.com/show_bug.cgi?id=1300013) I got to the overcloud deployment. > Another benefit, would be that if we get RDO CI testing TripleO as part > of our delorean promotion process, TripleO will be able to use the > automated current-passed-ci link instead of the manual current-tripleo > link. It will then be much easier to trace issues close to when they are > introduced rather than having a huge number of commits to comb through, > with many issues happening concurrently. > > - trown > > [1] http://docs.openstack.org/releases/schedules/mitaka.html > [2] https://etherpad.openstack.org/p/delorean_master_current_issues I have added the issue I have seen on the etherpad with full details. hth, Michele -- Michele Baldessari <[email protected]> C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
