Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7131CE6CB for ; Tue, 26 Feb 2013 03:23:06 +0000 (UTC) Received: (qmail 15035 invoked by uid 500); 26 Feb 2013 03:23:06 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 14881 invoked by uid 500); 26 Feb 2013 03:23:05 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 14854 invoked by uid 99); 26 Feb 2013 03:23:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 03:23:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shadowsor@gmail.com designates 209.85.128.177 as permitted sender) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 03:22:58 +0000 Received: by mail-ve0-f177.google.com with SMTP id m1so2880416ves.22 for ; Mon, 25 Feb 2013 19:22:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=3qTnL9rvMTZJLrfTA4S39Zv7W72I5s3GW8XywrzHMkQ=; b=p8ug1A83WYHo3+PkcdpVQyiopJqlnEMZ3gsUqSyysgkGA1svNz+PyQcInF8kA6jwJC hp0XpDgMMHm2JI+C5EM68O6WRI967QXh9aqbSVTZqEyqtL+bmDI+hPouFK6pGIhCfK1q Ix5hZRegz/21/sQLg3H3sbir1yqfyahq1Wtpg+5TZCzfbdiDFptHvya/+lS3k/a+nU7f m+lOuazv+xS2Y/L5oO/U5fizgHSns4H/j/5isfwjPzDwliDwZPgAAkioXuQW8Cm4vyvN Q0n4zWs3Dbpx1xr3+0q6MkpT2WVkUJsrfirGsEJ9XD0qBWKJ0cQereFes+yqoZ5R68yc KuZA== MIME-Version: 1.0 X-Received: by 10.52.25.8 with SMTP id y8mr9480226vdf.88.1361848957740; Mon, 25 Feb 2013 19:22:37 -0800 (PST) Received: by 10.58.186.167 with HTTP; Mon, 25 Feb 2013 19:22:37 -0800 (PST) Received: by 10.58.186.167 with HTTP; Mon, 25 Feb 2013 19:22:37 -0800 (PST) In-Reply-To: References: Date: Mon, 25 Feb 2013 20:22:37 -0700 Message-ID: Subject: Re: 4.2 storage plug-in changes and CHAP From: Marcus Sorensen To: cloudstack-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec501620f5d31a304d6982beb X-Virus-Checked: Checked by ClamAV on apache.org --bcaec501620f5d31a304d6982beb Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Should be fine, it would be up to the person writing the storage plugin to define the parameters for that storage. On Feb 25, 2013 8:19 PM, "Mike Tutkowski" wrote: > Hi, > > I know Edison has been hard at work on the storage_refactor branch. I wa= s > wondering, it looks like CloudStack does not support CHAP directly today. > By "directly," I mean even with, say, XenServer and an iSCSI target, you > cannot enter CHAP credentials via the GUI or API. If you need to use CHA= P, > you must set up your config from the hypervisor and then come into > CloudStack and create your Primary Storage based on that pre-existent > storage config. > > Edison's changes should allow Primary Storage to be based on a plug-in > rather than a pre-existent storage config. That's awesome and very helpf= ul > for my company. What I would like to know, though, is if CHAP will be > supported in this 4.2 storage plug-in environment. My company's iSCSI > targets all require CHAP credentials to access them. > > Thanks! > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkowski@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud > *=99* > --bcaec501620f5d31a304d6982beb--