Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Mon, 19 Nov 2012 17:02:05 +0000 (UTC)
From: "Eric Dey (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <1736859053.3391.1353344525318.JavaMail.jiratomcat@arcas>
In-Reply-To: <1779079104.120386.1353005892451.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-492) Document procedure to choose
 default System Offering for System VMs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-492?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13500382#comment-13500382 ]=20

Eric Dey commented on CLOUDSTACK-492:
-------------------------------------

I am currently out of the office and will return on August 10th. If you req=
uire immediate support on a Caringo product, please use our help web site a=
t: [1]https://support.caringo.com/

=C2=A0 -Eric


----------------------------------
Eric Dey  [2]<eric.dey@caringo.com>
Caringo, Inc.  (512)782-9902=20
---------------------------------------------------------------------------=
-------------
[1] https://support.caringo.com/
[2] mailto:eric.dey@caringo.com

               =20
> Document procedure to choose default System Offering for System VMs
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-492
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-492
>             Project: CloudStack
>          Issue Type: New Feature
>          Components: Doc
>    Affects Versions: 4.0.0
>            Reporter: Kirk Kosinski
>            Assignee: Radhika Nair
>            Priority: Minor
>              Labels: adminguide
>
> While it is possible to manually change the System Offering for a particu=
lar System VM, a CloudStack administrator may want to change the System Off=
ering used by default for System VMs. It would be useful for this procedure=
 to be documented. The following procedure works for me on CloudStack 3.0.2=
 and 4.0.0-incubating.
> 1. Create a new system offering with the desired settings. This can be do=
ne via UI under the Service Offerings tab.=20
> 2. Back up the database.=20
> mysqldump -u root -p cloud | bzip2 > cloud_backup.sql.bz2=20
> 3. Open a mysql prompt to be able to run queries in later steps on the cl=
oud database.
> mysql -u cloud -p cloud
> 4. In the disk_offering table in the database, identify the original defa=
ult offering and the new offering you wish to be used by default. Make a no=
te of their id.=20
> select id,name,unique_name,type from disk_offering;=20
> 5. Set unique_name =3D NULL for the original default offering. It is impo=
rtant to use the correct value for id.=20
> update disk_offering set unique_name =3D NULL where id =3D 10;=20
> 6. For the new offering you wish to be used by default, set unique_name =
=3D 'Cloud.com-ConsoleProxy' (for the default CPVM offering) or 'Cloud.com-=
SecondaryStorage' (for the default SSVM offering).=20
> update disk_offering set unique_name =3D 'Cloud.com-ConsoleProxy' where i=
d =3D 16;=20
> 7. Restart CloudStack. This is required because the default offerings are=
 loaded into memory at start-up.=20
> service cloud-management restart=20
> 8. Destroy the existing CPVM or SSVM and wait for it to be recreated. The=
 new CPVM or SSVM will be configured with the new offering.=20
> Note that CLOUDSTACK-338 seems to be requesting that the string used in u=
nique_name be changed. When that happens, this procedure would need to be u=
pdated with the correct string.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira