From users-return-20046-apmail-cloudstack-users-archive=cloudstack.apache.org@cloudstack.apache.org Mon Jan 26 21:49:43 2015 Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 913BF17CBC for ; Mon, 26 Jan 2015 21:49:43 +0000 (UTC) Received: (qmail 2475 invoked by uid 500); 26 Jan 2015 21:49:40 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 2395 invoked by uid 500); 26 Jan 2015 21:49:40 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 2372 invoked by uid 99); 26 Jan 2015 21:49:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2015 21:49:39 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: encountered temporary error during SPF processing of domain of lbarfield@tqhosting.com) Received: from [74.125.82.49] (HELO mail-wg0-f49.google.com) (74.125.82.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2015 21:49:34 +0000 Received: by mail-wg0-f49.google.com with SMTP id k14so11476189wgh.8 for ; Mon, 26 Jan 2015 13:48:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=VNJMYvAvYZD90dxsNh2Er2+r6jP0iHFiCJaUjQx3dMI=; b=XX0Ix7fD8UIQt0BtaSTgbyj9O5U0eWtcWXdLQ28u7PQe1q2f+njDP+Xj/0l47vJ8CG M/gWNbdCxkA79Ghpp+/hFxbkEkGQvCCijdFW1YWYDFpyV0mH048eHLGUaWDnPYVYrikS dsyWIjjYSPhu8RsDfXQuCw3RWelFzNAHQrlNXcArSd5TFPi6bkRtFP9jn+Bc5Ordxys6 j2qikADGnrNf5rIkaKBaFS7mVyjG86X3Qni98SuSmskneq+2DAQ+4YvJuxldTW6jzy/F ffVHGfz5ZKBV/JhXL/6tnK4bD+gTHAtbMpuGxPDm6gqtZzANuDKtozlXqbrbSa0usnlq tOeA== X-Gm-Message-State: ALoCoQmrVeOOVYgfeO6X7yaDw0CQoms3qRojHH4lwv7v53UZ2wZVhiYWbVMKf0we+ErQHJ5MUz/R MIME-Version: 1.0 X-Received: by 10.180.189.52 with SMTP id gf20mr35852450wic.27.1422308933263; Mon, 26 Jan 2015 13:48:53 -0800 (PST) Received: by 10.180.109.168 with HTTP; Mon, 26 Jan 2015 13:48:53 -0800 (PST) Date: Mon, 26 Jan 2015 16:48:53 -0500 Message-ID: Subject: Cross Zone Templates From: Logan Barfield To: "users@cloudstack.apache.org" , dev@cloudstack.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org I'm setting up a test zone for a multi-site deployment, and I've thus far been unable to deploy a VM from our existing templates. We're using S3 for secondary storage, and we have set up an NFS staging server in the remote zone. The management server is able to mount the NFS store over the site-to-site VPN. When we attempt to deploy a VM in the new zone, we get "Template is not available." It appears that this is because our templates are not set up as "Cross Zone Templates." We originally created these templates from existing volumes (e.g., installed via ISO, configured, shut down VM, created template from volume). I did not see any option in the UI or API to specify it as a cross zone template, nor do I see a way to update it after the fact (other than manually editing the database). This functionality only seems to be available when Registering a template via a URL, which isn't any help here. Is there a reason for this weirdness? Thank You, Logan Barfield Tranquil Hosting