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 0DAFF1795C for ; Tue, 10 Feb 2015 22:08:12 +0000 (UTC) Received: (qmail 9036 invoked by uid 500); 10 Feb 2015 22:08:10 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 8992 invoked by uid 500); 10 Feb 2015 22:08:10 -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 8976 invoked by uid 99); 10 Feb 2015 22:08:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 22:08:09 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of joseegas@farmaenlace.com designates 200.93.255.30 as permitted sender) Received: from [200.93.255.30] (HELO mail.farmaenlace.com) (200.93.255.30) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 22:08:04 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.farmaenlace.com (Postfix) with ESMTP id 937D826C24B4 for ; Tue, 10 Feb 2015 17:09:24 -0500 (ECT) Received: from mail.farmaenlace.com ([127.0.0.1]) by localhost (mail.farmaenlace.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id z1ZOO0s9sRMr for ; Tue, 10 Feb 2015 17:09:24 -0500 (ECT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.farmaenlace.com (Postfix) with ESMTP id 44BBC26C4AFC for ; Tue, 10 Feb 2015 17:09:24 -0500 (ECT) X-Virus-Scanned: amavisd-new at farmaenlace.com Received: from mail.farmaenlace.com ([127.0.0.1]) by localhost (mail.farmaenlace.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id kpaGwlVgOpkT for ; Tue, 10 Feb 2015 17:09:24 -0500 (ECT) Received: from mstmp (unknown [172.31.3.243]) by mail.farmaenlace.com (Postfix) with ESMTPSA id 0CA0526C24B4 for ; Tue, 10 Feb 2015 17:09:24 -0500 (ECT) From: =?iso-8859-1?Q?Jos=E9_Egas_L=F3pez?= To: References: <64e801d0457a$812bc380$83834a80$@farmaenlace.com> In-Reply-To: Subject: RE: How to shutdown CS? Date: Tue, 10 Feb 2015 17:06:08 -0500 Message-ID: <64f101d0457d$c61f8f50$525eadf0$@farmaenlace.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQNEA5y5hqsUaFqSx9l/rWD6QIAe+wHZMOKQmfQqo1A= Content-Language: es X-Virus-Checked: Checked by ClamAV on apache.org Ok, thanks, and what about de sysVMs? Regards, Jos=E9 -----Mensaje original----- De: Somesh Naidu [mailto:Somesh.Naidu@citrix.com]=20 Enviado el: martes, 10 de febrero de 2015 16:52 Para: users@cloudstack.apache.org Asunto: RE: How to shutdown CS? When you say "entire Cloudstack infrastructure" do you mean all = hypervisor hosts, guests, storage servers, etc? Ideally, from a CS perspective, stopping the management service (all servers) should suffice. If you want to be extra careful, you could = first disable all your zones from the UI, wait for all currently running operations to finish and then stop management service. Beyond that, you could follow the guidelines from the hypervisor and storage vendors to = pull the services down on those. Regards, Somesh -----Original Message----- From: Jos=E9 Egas L=F3pez [mailto:joseegas@farmaenlace.com] Sent: Tuesday, February 10, 2015 4:43 PM To: users@cloudstack.apache.org Subject: How to shutdown CS? Hi, I want to know how to properly shutdown the entire CloudStack Infraestructure, I will upgrade resources of the main host. =20 =20 Regards, =20 Jos=E9 =20