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 621CAD8BA for ; Fri, 4 Jan 2013 00:03:32 +0000 (UTC) Received: (qmail 8184 invoked by uid 500); 4 Jan 2013 00:03:32 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 8108 invoked by uid 500); 4 Jan 2013 00:03:32 -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 8100 invoked by uid 99); 4 Jan 2013 00:03:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2013 00:03:31 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Frank.Zhang@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2013 00:03:26 +0000 X-IronPort-AV: E=Sophos;i="4.84,405,1355097600"; d="scan'208";a="2637912" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jan 2013 00:03:05 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Thu, 3 Jan 2013 16:03:03 -0800 From: Frank Zhang To: "cloudstack-dev@incubator.apache.org" Date: Thu, 3 Jan 2013 16:03:03 -0800 Subject: RE: [PROPOSAL] Integrate Cisco UCS with CloudStack Thread-Topic: [PROPOSAL] Integrate Cisco UCS with CloudStack Thread-Index: Ac3p6uLL/OHq6TbHTWmuXPPpONI2hAAI0/pQ Message-ID: <93099572B72EB341B81A644E134F240B012F73422533@SJCPMAILBOX01.citrite.net> References: <93099572B72EB341B81A644E134F240B012F7342252D@SJCPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org > On Thu, Jan 3, 2013 at 2:06 PM, Frank Zhang wrot= e: > > Hi community: > > I'd like to propose a proposal for integrating Cisco > > UCS(unified computing system) with CloudStack. UCS unifies computing, > > networking, management, virtualization, and storage access into a > > single integrated architecture. This unique architecture enables end-to= -end > server visibility, management, and control in both bare metal and virtual > environments, and facilitates the move to cloud computing and IT-as-a- > Service with Fabric-Based Infrastructure. You can find detailed informati= on > about UCS at http://www.cisco.com/en/US/products/ps10265/index.html. > > > > The first phase is to integrate UCS with CloudStack baremetal, > > here is a proposed workflow to enable this. Let us define "administrat= or" > as the person responsible for the overall cloud service, including the ph= ysical > infrastructure. Similarly the "user" is the end user that seeks to creat= e VMs. > > > > 1. Using the CloudStack UI, the administrator adds a "Managed Host > Manager" of type UCS. The admin provides API endpoint and credentials. > > This gives CloudStack programmatic access to UCS Manager and an > identity with authorization to implement the following functions. > > 2. Administrator creates a "UCS Resource Pool" per Service Profile > Template that he wants to use > > 3. Administrator creates a Baremetal Cluster > > 4. Administrator chooses the required UCS Resource pool (that matc= hes > his Service Profile requirement for a cluster), > > selects an available blade, selects a Baremetal template and ad= ds the > blade to the Baremetal cluster > > 5. Repeat Step 4 above to add more hosts in the cluster > > 6. Now user is able to start vm on baremetal host using CloudStack > baremetal provisioning > > > > At first stage, I would like to limit the effort to CloudStack > > basic zone, however, we will seek to support advanced zone by leveragin= g > UCS's vlan programming feature. There is a high level PRD for full featu= res of > UCS-baremetal integration. > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enhanced+Bare > metal+support+on+Cisco+UCS > > and JIRA ticket is here > > https://issues.apache.org/jira/browse/CLOUDSTACK-723 > > > > please free feel to share your thoughts, thank you! > > > > > > >=20 > Hey Frank, >=20 > Question about this implementation... you had mentioned last summer [1] > that you were thinking about redoing how standard bare metal provisioning > works. Is it worth getting that sorted out first, and then enhancing it = to > support UCS? >=20 > -chip Hi Chip: Thanks for reply. Yes I did propose a proposal couple of months ago, at that time the community process was not normalized and I didn't get much respond to that. I have done some investigation and would like to repost=20 some proposal shortly. However, the UCS integration is actually separate from CloudStack baremeta= l. It's about how to make UCS cooperate with CloudStack, and baremetal could b= e the first consumer of this feature. >=20 > [1] http://markmail.org/thread/lpfptu7wv22pexlk