[openstack-dev] [ironic] PTG Summary
dtantsur at redhat.com
Mon Mar 12 11:45:43 UTC 2018
Thanks for the information.
I personally don't see problems with cleaning running weeks, when needed. What
I'd avoid is replicating the same cleaning machinery but with a different name.
I think we should try to make cleaning work for this case instead.
On 03/12/2018 12:33 PM, Tim Bell wrote:
> A basic summary of CERN does burn-in is at http://openstack-in-production.blogspot.ch/2018/03/hardware-burn-in-in-cern-datacenter.html
> Given that the burn in takes weeks to run, we'd see it as a different step to cleaning (with some parts in common such as firmware upgrades to latest levels)
> -----Original Message-----
> From: Julia Kreger <juliaashleykreger at gmail.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Date: Thursday, 8 March 2018 at 22:10
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Subject: [openstack-dev] [ironic] PTG Summary
> Cleaning - Burn-in
> As part of discussing cleaning changes, we discussed supporting a
> "burn-in" mode where hardware could be left to run load, memory, or
> other tests for a period of time. We did not have consensus on a
> generic solution, other than that this should likely involve
> clean-steps that we already have, and maybe another entry point into
> cleaning. Since we didn't really have consensus on use cases, we
> decided the logical thing was to write them down, and then go from
> Action Items:
> * Community members to document varying burn-in use cases for
> hardware, as they may vary based upon industry.
> * Community to try and come up with a couple example clean-steps.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev