Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3ED73200BD4 for ; Thu, 1 Dec 2016 17:30:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3D85B160B0B; Thu, 1 Dec 2016 16:30:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7E33F160B05 for ; Thu, 1 Dec 2016 17:30:04 +0100 (CET) Received: (qmail 43236 invoked by uid 500); 1 Dec 2016 16:30:03 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 43221 invoked by uid 99); 1 Dec 2016 16:30:02 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2016 16:30:02 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7E002E09CD; Thu, 1 Dec 2016 16:30:02 +0000 (UTC) From: jburwell To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1776: CLOUDSTACK-9603: concurrent.snapshots.threshold.perh... Content-Type: text/plain Message-Id: <20161201163002.7E002E09CD@git1-us-west.apache.org> Date: Thu, 1 Dec 2016 16:30:02 +0000 (UTC) archived-at: Thu, 01 Dec 2016 16:30:05 -0000 Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1776 @priyankparihar could you please provide further explanation as to how this fix addresses the issue of `concurrent.snapshots.threshold.perhost` not being validated? Also, is there an existing Marvin test case and/or unit test that verifies this fix? If not, could you please add one? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---