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 0BDF11862C for ; Tue, 27 Oct 2015 15:15:25 +0000 (UTC) Received: (qmail 42243 invoked by uid 500); 27 Oct 2015 15:15:08 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 42191 invoked by uid 500); 27 Oct 2015 15:15:08 -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 42180 invoked by uid 99); 27 Oct 2015 15:15:08 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2015 15:15:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 223C81809D4 for ; Tue, 27 Oct 2015 15:15:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=6.31 tests=[URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id CvxBP0cWzMAF for ; Tue, 27 Oct 2015 15:15:00 +0000 (UTC) Received: from smtp.artifact-software.com (modemcable202.79-37-24.static.videotron.ca [24.37.79.202]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTP id 3C2F943A11 for ; Tue, 27 Oct 2015 15:15:00 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.artifact-software.com (Postfix) with ESMTP id F207CFEC044 for ; Tue, 27 Oct 2015 11:14:59 -0400 (EDT) X-Virus-Scanned: amavisd-new at artifact-software.com Received: from smtp.artifact-software.com ([127.0.0.1]) by localhost (smtp.artifact-software.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzIbDcXKYOjU for ; Tue, 27 Oct 2015 11:14:59 -0400 (EDT) Received: from [192.168.3.196] (unknown [192.168.3.196]) by smtp.artifact-software.com (Postfix) with ESMTP id AEDF3FEC043 for ; Tue, 27 Oct 2015 11:14:59 -0400 (EDT) Reply-To: "dev@cloudstack.apache.org" Subject: Re: Service Offering documentation - GPU References: <562E9175.2060503@artifact-software.com> <1d5927dff8d4aac2d2ad060f2031c091@ant.ee> <562F72FF.9040306@artifact-software.com> <562F7C32.5070804@artifact-software.com> To: dev@cloudstack.apache.org From: Ron Wheeler Organization: Artifact Software Message-ID: <562F94F3.3090600@artifact-software.com> Date: Tue, 27 Oct 2015 11:14:59 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit In this case it seems that putting the design changes from 4.5 (new GPU types) in the 4.4 docs is problematic. It seems that the 4.5 docs should document the vgpuTypes that were added in 4.5 with a link to the 4.4 docs if there are no other changes. Perhaps part of the problem is that the Administrator documents are lacking some key info and explanation from the design docs. It will become increasingly hard to locate the missing information as versions are released. It will be very difficult to find GPU information for Cloudstack version 6.2 if you have to find it in the design docs for 4.4. I have updated the admin doc to add a bit of context and a reference to the Design docs . Ron On 27/10/2015 10:19 AM, Vadim Kimlaychuk wrote: > I don't know what is a best way to present such kind of information. > From one side each version should contain its own copy of the chapter, > but this is probably hard to maintain. From the other side - having > just one wiki document with history of versions is probably simpler. > > Vadim. > > On 2015-10-27 15:29, Ron Wheeler wrote: > >> My question was whether this page needs to be in the 4.5 Design docs. >> >> Currently the new GPU types are in the 4.4 Design Docs which you seem >> to be saying is wrong (K160Q, K180Q, K280Q were added to 4.5 not 4.4) >> >> It looks like someone updated the 4.4 docs rather than adding the >> page to the 4.5 doc set. >> >> If I am not mistaken, the current 4.4 page should be copied to 4.5 >> and then the changes made to the 4.4 page should be reverted to an >> earlier version where the new GPUs are not included. >> >> Ron >> >> On 27/⁠10/⁠2015 9:18 AM, Vadim Kimlaychuk wrote: New vGPU types >> K160Q, K180Q, K280Q were added to UI at 4.5 version, but this is >> already reflected in the cwiki article. >> >> Vadim. >> >> On 2015-⁠10-⁠27 14:50, Ron Wheeler wrote: >> >> Looks very complete and seems to answer many of my questions (and >> probably some that I have not thought of yet). >> >> This is in the 4.4 Design docs but did not make it into the 4.5 >> Design docs section. >> Should it be in 4.5 as well? >> >> Ron >> >> On 27/⁠⁠10/⁠⁠2015 3:53 AM, Vadim Kimlaychuk wrote: Dear Ron, >> >> I suggest you to read this document: >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/GPU+and+vGPU+support+for+CloudStack+Guest+VMs >> [1] [1 [1]]. I have tested pass-through mode with XenServer 6.2 and >> can give probably a bit more information if you need. The reference >> document is good indeed, so you probably do not need my comments :) >> >> Regards, >> >> Vadim. >> >> On 2015-⁠⁠10-⁠⁠26 22:47, Ron Wheeler wrote: >> >> The GPU section on page >> http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.5/service_offerings.html >> [2] [2 [2]] [1 [2]] seems to be lacking some information (at least as >> far as I can tell). >> 1) What does the GPU do? It says to select a card that I want to use. >> No hint about the basis on which I should make the selection or if >> there are any restrictions on the choice (based on hardware?) >> 2) It mentions support for 2 NVIDIA cards and says that if you want >> to use another card "make the createServiceOffering API call". How is >> this done on a UI screen? >> 3) The Type selection is worded in an odd way with 3 selections >> explicitly named and a "so on" thrown in. Then it goes on to talk >> about a passthrough vGPU type in a separate paragraph. >> >> Perhaps there should be links to external web sites to clarify the >> definitions of these cards and types. >> >> If someone can explain what this section actually means, I will try >> to write it in a clearer fashion. >> >> Ron >> >> Links: >> -⁠⁠-⁠⁠-⁠⁠-⁠⁠-⁠⁠-⁠⁠ >> [1] >> http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.5/service_offerings.html >> [2] [2 [2]] >> >> Links: >> -⁠-⁠-⁠-⁠-⁠-⁠ >> [1] >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/GPU+and+vGPU+support+for+CloudStack+Guest+VMs >> [1] >> [2] >> http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.5/service_offerings.html >> [2] > > > > Links: > ------ > [1] > https://cwiki.apache.org/confluence/display/CLOUDSTACK/GPU+and+vGPU+support+for+CloudStack+Guest+VMs > [2] > http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.5/service_offerings.html > -- Ron Wheeler President Artifact Software Inc email: rwheeler@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102