Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2437B17AFC for ; Mon, 20 Apr 2015 13:45:17 +0000 (UTC) Received: (qmail 22793 invoked by uid 500); 20 Apr 2015 13:45:15 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 22667 invoked by uid 500); 20 Apr 2015 13:45:15 -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 22526 invoked by uid 99); 20 Apr 2015 13:45:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 13:45:14 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.191.145.13 which is an MX secondary for users@cloudstack.apache.org) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 13:45:08 +0000 Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 07ABB24E9F; Mon, 20 Apr 2015 13:44:48 +0000 (UTC) Received: by wizk4 with SMTP id k4so99917355wiz.1; Mon, 20 Apr 2015 06:44:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=oeq+MmCM73jPmu9tXaGS/Hwx4rz+8qIk3uNYa1fG6L4=; b=XE0RcHoOyACtWc8un+ns0UYV/E5N2dgYu6arKHdcruVUWZSgKh0yL/Os0hzMe+9Jf+ 6uQq3hK8pDb1oPz/doAeCquIdN4IxGNCPdLLyz4sI1oC4+ZjVI5pLFSOA6GtJU07bH1q EBQVqP8tvfq5DKb+E8+2144vrvkYmVhL41FTpRRJHG5BxYRky11hSeHF72exsTUPjW1N 3LOPlE03jBIX8slj2krX41mb3TR9Tqf3s9fmzlorKThDlCXKvOH8XTsEsX1laYcZQMhD drjY173k/T0Os21GXyQHfoE97QIMoIwYK5QXh18XP7w5bNDl2BC+R7+r6mx93hf6cAUA O11g== MIME-Version: 1.0 X-Received: by 10.180.96.200 with SMTP id du8mr26000189wib.54.1429537486842; Mon, 20 Apr 2015 06:44:46 -0700 (PDT) Received: by 10.195.13.134 with HTTP; Mon, 20 Apr 2015 06:44:46 -0700 (PDT) Date: Mon, 20 Apr 2015 15:44:46 +0200 Message-ID: Subject: Primary Storage algorithm - when having more primary storages From: Andrija Panic To: "users@cloudstack.apache.org" , "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=f46d043bdc0c18b01e051428221a X-Virus-Checked: Checked by ClamAV on apache.org --f46d043bdc0c18b01e051428221a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi people, just wondering - if I have 3 primary storages (3 x NFS boxes) - what is the volume alocation algoritm - is it compelte random, or is it like 1 client's volume goes always to 1 storage... Any info appreciated ! Thanks, --=20 Andrija Pani=C4=87 --f46d043bdc0c18b01e051428221a--