Difference between revisions of "stoney cloud: Upgrade"
| [unchecked revision] | [unchecked revision] |
| Line 2: | Line 2: | ||
This guide explains, what you need to do during the installation of your Multi-Node Installation. | This guide explains, what you need to do during the installation of your Multi-Node Installation. | ||
| − | == Prepare | + | == Prepare stoney cloud for the update == |
If you have a '''productive''' (releases) stoney clooud Installation, execute the following command: | If you have a '''productive''' (releases) stoney clooud Installation, execute the following command: | ||
<source lang="bash"> | <source lang="bash"> | ||
| Line 33: | Line 33: | ||
</pre> | </pre> | ||
| − | If you have updated you | + | If you have updated you stoney cloud, you might want to sanely update your configuration files after emerging new packages (including updates): |
dispatch-conf | dispatch-conf | ||
== Installing Software Examples == | == Installing Software Examples == | ||
| − | Per default, the | + | Per default, the stoney cloud expects you to install binary packages. So if you don't pass any special parameters to the emerge command, the binary package (if it exists) will be used. |
=== Binary Package === | === Binary Package === | ||
| − | Per default, the | + | Per default, the stoney cloud expects you to install binary packages, which can be seen with '''[binary R ]''' output. |
emerge -va git | emerge -va git | ||
| Line 132: | Line 132: | ||
None. | None. | ||
| − | [[Category:Updating your | + | [[Category:Updating your stoney cloud]] |
[[Category:Installation]] | [[Category:Installation]] | ||
[[Category:stoney cloud]] | [[Category:stoney cloud]] | ||
Revision as of 13:47, 19 December 2013
Contents
Overview
This guide explains, what you need to do during the installation of your Multi-Node Installation.
Prepare stoney cloud for the update
If you have a productive (releases) stoney clooud Installation, execute the following command:
echo 'PORTAGE_BINHOST="https://<USERNAME>:<PASSWORD>@packages.stoney-cloud.org/stoney-cloud/releases/1.2/packages"' >> /etc/portage/make.conf
If you have a test (pre-releases) stoney cloud Installation instead, execute the following command:
echo 'PORTAGE_BINHOST="https://<USERNAME>:<PASSWORD>@packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf
Makes sure, your local portage tree is updated:
emerge --sync
Now you can make sure, that you've got the current stoney cloud version installed:
emerge -KuDva =virtual/foss-cloud-1.2.10
Local copy of remote index is up-to-date and will be used. These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB * =virtual/foss-cloud-1.2.10 Would you like to add these packages to your world favorites? [Yes/No] '''no'''
If you have updated you stoney cloud, you might want to sanely update your configuration files after emerging new packages (including updates):
dispatch-conf
Installing Software Examples
Per default, the stoney cloud expects you to install binary packages. So if you don't pass any special parameters to the emerge command, the binary package (if it exists) will be used.
Binary Package
Per default, the stoney cloud expects you to install binary packages, which can be seen with [binary R ] output.
emerge -va git
These are the packages that would be merged, in order:
Calculating dependencies... done!
[binary R ] dev-vcs/git-1.7.12.4 USE="blksha1 curl iconv nls pcre perl threads webdav -cgi -cvs -doc -emacs -gpg -gtk -highlight (-ppcsha1) -python -subversion {-test} -tk -xinetd" 5,295 kB
Total: 1 package (1 reinstall, 1 binary), Size of downloads: 5,295 kB
Would you like to merge these packages? [Yes/No] no
Quitting.
Force Non-Binary Package
If you force a non-binary package, the output will be in the form of [ebuild R ].
FEATURES="-getbinpkg" emerge -va git
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] app-arch/cpio-2.11 USE="nls" 995 kB
[ebuild R ] dev-vcs/git-1.7.12.4 USE="blksha1 curl iconv nls pcre perl threads webdav -cgi -cvs -doc -emacs -gpg -gtk -highlight (-ppcsha1) -python -subversion {-test} -tk -xinetd" 4,523 kB
Total: 2 packages (1 new, 1 reinstall), Size of downloads: 5,518 kB
Would you like to merge these packages? [Yes/No]
No Binary Package Exists
The following example shows you a package with no existing binary package, therefore the package must be compiled on the fly, shown with [ebuild N ].
emerge -va htop
Local copy of remote index is up-to-date and will be used. These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] sys-process/htop-1.0.2 USE="unicode -openvz -vserver" 380 kB Total: 1 package (1 new), Size of downloads: 380 kB Would you like to merge these packages? [Yes/No]
Multi-Node Installation
Follow the Specialized Installation Guide.
Basic Testing Steps
Get a Fedora ISO image:
cd /var/virtualization/iso-choosable/ wget http://download.fedoraproject.org/pub/fedora/linux/releases/18/Fedora/x86_64/iso/Fedora-18-x86_64-netinst.iso chown apache:vm-storage Fedora-18-x86_64-netinst.iso chmod 644 Fedora-18-x86_64-netinst.iso
Lernstick (Test):
cd /var/virtualization/iso-choosable/ wget http://www.imedias.ch/dateien/lernstick-testversion/lernstick_debian7_2013-03-31.iso chown apache:vm-storage lernstick_debian7_2013-03-31.iso chmod 644 lernstick_debian7_2013-03-31.iso
Set three network ranges under https://192.168.140.10/vm-manager/subnet/index.html
192.168.140.64 26 Template Range template
192.168.140.128 26 Persistent Range persistent
192.168.140.192 26 Dynamic Range dynamic
Add the three newly creates network ranges to the VM-Pools under https://192.168.140.10/vm-manager/vmPool/index.html
Create a Virtual Machine Profile under https://192.168.140.10/vm-manager/vmProfile/create.html
Create a Virtual Machine Template under https://192.168.140.10/vm-manager/vmTemplate/create.html and install a basic operating system.
Create a persistent Virtual Machine from the newly created Virtual Machine Template.
Known Issues
None.
