> On Feb 5, 2016, at 9:54 AM, Tim Bell <tim.b...@cern.ch> wrote: > > ... > >> On "production-grade": >> >> I'd be (strongly) in favor of defining a target deployment configuration and >> size which we find representative of the minimum bar for "production-grade." >> Anything less concrete and specific becomes more nuisance than help. I'd >> hope that specs might look like the following: >> >> - tests must be run against an OpenStack-certified cloud containing at >> minimum 20 compute nodes, 1 TB block storage, 1 TB object storage >> - tests must demonstrate service responsiveness, stability, and reliability >> while VMs, compute volumes, object store objects, and networks are >> created/destroyed at a rate of 50/second in any combination while >> maintaining 99.9%+ service availability, <1% error rate, and response >> latency of <100ms >> - tests must demonstrate service resiliency when faced with common component >> failures such as: compute node failure, storage failure, network failure, >> etc. > > > The scale could be defined on the basis of the survey data. The reference > implementation should be able to address at least X% of deployments. I can > think of at least one project which was not suitable for use at a reasonable > size configuration and not being able to demonstrate this would have saved a > lot of grief in the ops community as well as ensuring the project addressed > the issue early.
+1 and I can think of more than one. =\ —j
__________________________________________________________________________ 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
