Thanks to a massive push this week, both the seed *and* undercloud jobs are now passing on tripleo-gate nodes, but they are not yet voting.
I'd kind of like to get them voting on tripleo jobs (check only). We don't have 2 clouds yet, so if the tripleo ci-cloud suffers a failure, we'd have -1's everywhere. I think this would be an ok tradeoff (its check after all), but I'd like -infra admin folks opinion on this - would it cause operational headaches for you, over and above the current risks w/ the tripleo-ci cloud? OTOH - we actually got passing ops with a fully deployed virtual cloud - which is awesome. Now we need to push through to having the overcloud deploy tests pass, then the other scenarios we depend on - upgrades w/rebuild, and we'll be in good shape to start optimising (pre-heated clouds, local distro mirrors etc) and broadening (other distros ...). Lastly, I'm going to propose a merge to infra/config to put our undercloud story (which exercises the seed's ability to deploy via heat with bare metal) as a check experimental job on our dependencies (keystone, glance, nova, neutron) - if thats ok with those projects? -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
