Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BA2BCCE24 for ; Tue, 5 Jun 2012 01:05:38 +0000 (UTC) Received: (qmail 78961 invoked by uid 500); 5 Jun 2012 01:05:38 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 78944 invoked by uid 500); 5 Jun 2012 01:05:38 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 78936 invoked by uid 99); 5 Jun 2012 01:05:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 01:05:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Evan.Miller@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 01:05:32 +0000 X-IronPort-AV: E=Sophos;i="4.75,716,1330923600"; d="scan'208";a="197505811" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Jun 2012 21:04:49 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Mon, 4 Jun 2012 18:04:48 -0700 From: Evan Miller To: "cloudstack-users@incubator.apache.org" Date: Mon, 4 Jun 2012 18:04:49 -0700 Subject: RE: Does/will CloudStack support having a SDX box (e.g. NS19500) as an added host in a cluster? Thread-Topic: Does/will CloudStack support having a SDX box (e.g. NS19500) as an added host in a cluster? Thread-Index: Ac1CnSQwNB0LcX/ETnmi0DtfNaDL6gAAmI4wAAFmW8A= Message-ID: <93099572B72EB341B81A644E134F240B011CF769574E@SJCPMAILBOX01.citrite.net> References: <93099572B72EB341B81A644E134F240B011CF76956C8@SJCPMAILBOX01.citrite.net> <25171B03A3D9E24AADC227668ADE91C9010075F65133@SJCPMAILBOX01.citrite.net> In-Reply-To: <25171B03A3D9E24AADC227668ADE91C9010075F65133@SJCPMAILBOX01.citrite.net> 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 Hi Chandon: One more follow-up ... Can you please be more specific as to which API or APIs=20 can be used to add a Network Service Provider Appliance? The unsorted grouping of API types and API names in this reference didn't help me find what I need: http://download.cloud.com/releases/3.0.0/api_3.0.0/TOC_User.html Also, is there any way from the CloudStack Management GUI that the Network Service Provider Appliance can be configured? Regards, Evan -----Original Message----- From: Chandan Purushothama [mailto:Chandan.Purushothama@citrix.com]=20 Sent: Monday, June 04, 2012 3:25 PM To: cloudstack-users@incubator.apache.org Subject: RE: Does/will CloudStack support having a SDX box (e.g. NS19500) a= s an added host in a cluster? Hello Evan, The APIs that are used to add a Hypervisor Host and a Network Service Provi= der Appliance are different. Hence Netscaler SDX cannot be added using the = same API used to add a Hypervisor. It needs to be added as a Network Servic= e Provider Appliance. API Reference document will provide you with the nece= ssary information pertaining to which API needs to be used. Location of the= API Reference document: http://docs.cloud.com/CloudStack_Documentation/API= _Reference%3A_CloudStack Thank you, Chandan. From: Evan Miller [mailto:Evan.Miller@citrix.com] Sent: Monday, June 04, 2012 2:58 PM To: cloudstack-users@incubator.apache.org Subject: Does/will CloudStack support having a SDX box (e.g. NS19500) as an= added host in a cluster? Hi: It appears that CloudStack v3.0.1 doesn't support having a SDX box (not a H= ypervisor) as a host in any cluster. Here is the log error message in catalina.out on the CloudStack Management = Server that I got when I tried to add a non-hypervisor (SDX NS19500) to an = existing pod: INFO [cloud.resource.ResourceManagerImpl] (catalina-exec-14:) Trying to ad= d a new host at http://sdx-c48-03.eng.citrite.net in data center 1 [Fatal Error] loose.dtd:31:3: The declaration f= or the entity "HTML.Version" must end with '>'. [Fatal Error] loose.dtd:31:3: The declaration for the entity "HTML.Version"= must end with '>'. WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-14:) Unable to fi= nd the server resources at http://sdx-c48-03.eng.citrite.net WARN [api.commands.AddHostCmd] (catalina-exec-14:) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(Resourc= eManagerImpl.java:689) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceMan= agerImpl.java:509) at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:136) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:132) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:509) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:416) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:300) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:59) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter= (ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Applica= tionFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWra= pperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardCon= textValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostVa= lve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportVa= lve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.= java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngi= neValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapte= r.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioPro= cessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandl= er.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEn= dpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec= utor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe= cutor.java:603) at java.lang.Thread.run(Thread.java:679) WARN [cloud.api.ApiDispatcher] (catalina-exec-14:) class com.cloud.api.Ser= verApiException : Unable to add the host Any discussions or plans for doing so in the future? I realize that hypervisors work and are probably required. However, in our = test lab, we could see some advantages to being able to add a SDX as a host= in a CloudStack cluster. Regards, Evan Miller Citrix Systems. Inc. Desktop and Cloud Engineering Infrastructure 4988 Great America Parkway Santa Clara, CA 95054 (V) and (F) 408-790-8489 (C) 925-209-1428 (Email) Evan.Miller@citrix.com [cid:288114921@04062012-3453]