From users-return-28388-apmail-cloudstack-users-archive=cloudstack.apache.org@cloudstack.apache.org Fri Jul 21 01:37:55 2017 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 9238319D6A for ; Fri, 21 Jul 2017 01:37:55 +0000 (UTC) Received: (qmail 55102 invoked by uid 500); 21 Jul 2017 01:37:54 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 54720 invoked by uid 500); 21 Jul 2017 01:37:53 -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 54708 invoked by uid 99); 21 Jul 2017 01:37:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jul 2017 01:37:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id B0BFBC02D8 for ; Fri, 21 Jul 2017 01:37:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.479 X-Spam-Level: ** X-Spam-Status: No, score=2.479 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=bw-sw-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YjhX2N4Lnpa6 for ; Fri, 21 Jul 2017 01:37:48 +0000 (UTC) Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8A2325F341 for ; Fri, 21 Jul 2017 01:37:45 +0000 (UTC) Received: by mail-it0-f43.google.com with SMTP id h199so1212430ith.0 for ; Thu, 20 Jul 2017 18:37:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bw-sw-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=IFj/4eg72fMGGWd35pnZ9xeI5u8BcYIrr7Qrb211+WI=; b=17begAb6FeFyZ/SuPjg8IlvWIEVM74tlPHDEYfmB8FOcCGY9cqIebYgCHShxLHlXJ7 d7h4rmWtM3ch9pLHvGGzN2ik6h7N443YiRum6CA+vgQ49Kx0UBT4F2q3lNUczvyBCSb5 BcVp3RKGeXN4qeFt+ZwNCSgGGCFxol3OZAeyQ5NdepRr8RAKs9jSaIaCjkSqeJIu9SWU mJKlkSWQkR6XmjlorfSNAQe3qi1g7oAYgLiQycMV2giYlY9q04vACbzVPxGj683nQwsR Wd10viNDnk078gnST8+lM7kLq8F79R4SwSMkMkr66EsLEmAKR3cfd3RuUb9FBGEXnlMk QoCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=IFj/4eg72fMGGWd35pnZ9xeI5u8BcYIrr7Qrb211+WI=; b=mOcM4U64j8ifMe6ki72joBxIb3yn95ujAWQb2RzQCWgAUpmW0nzvy+hgcXexR/lCR8 dpEBDl9JnF0dYHoZHGDpdWkTXTpKuEBLK+cT/8QrnKDIIpcm4FEW24NXkMZ+2AmF0cjM gUhTryYOH9QL8orJ1kNxY/rcrpeA9GOIqw94agMUFlFQzfXEtkljyLO0LYz9cvauOhV+ dcrnpvKrTlFI9wl26TrfwTuFKMF3m4Y5SPE7qW7pnXx4Ue16ZMbzAppCrcMmrPEOpSsI 5pMgLdG7RSYEtUprPqnWk9JmYiF6NZEBR1j8UAEgICGHpgZtBveHJIyt5OmphZtrkY9S igwQ== X-Gm-Message-State: AIVw112OncUlzoqgZ1Vwmdisk9xl5AwtghWh8pjiIBnG3/Vvsj3qSP/l 209Oc9osKEVJrZLAQ8sbtLxG9bCmqNxBvgo= X-Received: by 10.36.189.198 with SMTP id x189mr5505184ite.56.1500601058793; Thu, 20 Jul 2017 18:37:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.51.11 with HTTP; Thu, 20 Jul 2017 18:37:38 -0700 (PDT) Received: by 10.107.51.11 with HTTP; Thu, 20 Jul 2017 18:37:38 -0700 (PDT) In-Reply-To: References: From: Ivan Kudryavtsev Date: Fri, 21 Jul 2017 08:37:38 +0700 Message-ID: Subject: Re: Modifying a service offering in the cloudstack DB To: users@cloudstack.apache.org Content-Type: multipart/alternative; boundary="94eb2c19e22c0f348e0554c9e9d0" --94eb2c19e22c0f348e0554c9e9d0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, you can actually do it thru DB, but it can lead to several implications, like unfare resource provisioning. The better way is just delete the offering, create the new with the same name and switch all VMs either automatically or asking users. Have a good day. 21 =D0=B8=D1=8E=D0=BB. 2017 =D0=B3. 2:55 =D0=94=D0=9F =D0=BF=D0=BE=D0=BB=D1= =8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: Dear all, as there is no means to modify an existing Cloudstack Service Offering neither via Cloudstack API nor with the GUI, I=E2=80=99m wondering what wo= uld happen if the CPU speed of the service offerings is changed directly in the cloud DB (table service_offering). Does this have any impact on existing VMs? Would this be a valid way to modify an existing Service Offering? We did some very brief test and it seem to work fine, but before doing the change in our production environment I=E2=80=99d like to know if anyone els= e has done something similar? The reason why I=E2=80=99m trying to do this is as follows: In all our Service Offerings for user VMs we have set the CPU Speed to 1999 Mhz. Unfortunately, the CPUs of our most recent hosts only provide 1995 MHz, leading to the situation that no VM is deployed on these servers as the hosts do not have the proper cpu capability (speed 1995 is provided but 1999 is required). Cheers, Christian PS: We=E2=80=99re still on Cloudstack 4.5.1 --94eb2c19e22c0f348e0554c9e9d0--