stoney-cloud.org - User contributions [en]

https://wiki.stoney-cloud.org/w/api.php?action=feedcontributions&feedformat=atom&user=Pascal stoney-cloud.org - User contributions [en] 2026-05-13T13:45:38Z User contributions MediaWiki 1.39.6 https://wiki.stoney-cloud.org/w/index.php?title=Build_Server&diff=4607 Build Server 2015-06-01T07:51:21Z

<p>Pascal: </p> <hr /> <div>= Overview =<br /> * Base chroot environment for the creation of most binary packages which will be copied to the [[Binary Package Server]].<br /> * Packages, which don't need to be built, for example [http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html Oracle's Java SE Development Kit] (JDK), can be fetched from the [[Mirror Server]].<br /> * Software stacks built upon specialized binary packages, require their own chroot environment. If possible, avoid this.<br /> * For reproducibility, Portage and Profiles are frozen with the help of version control system (git in our case). This is only done on the [[Mirror Server]].<br /> * When building packages in a chroot environment, the portage and overlay versions need to set.<br /> <br /> == Portage Snapshotting ==<br /> <br /> To be able to reliably rebuild packages, we are working with a snapshotted/versioned portage tree.<br /> <br /> === Updating the snapshot to latest ===<br /> <br /> We are using <code>emerge-webrsync</code> since it features an already determined version, checksum- and gpg-validation.<br /> <br /> {{Cmd<br /> |git clone "${PORTAGE_GIT_REPO}" portage<br /> |cd portage<br /> |PORTAGE_RSYNC_EXTRA_OPTS{{=}}"--exclude{{=}}/.git --exclude{{=}}/.gitignore" PORTDIR{{=}}"${PWD}" emerge-webrsync<br /> |output=<pre><br /> Fetching most recent snapshot ...<br /> Trying to retrieve 20140821 snapshot from http://mirror.switch.ch/mirror/gentoo ...<br /> Fetching file portage-20140821.tar.xz.md5sum ...<br /> Fetching file portage-20140821.tar.xz.gpgsig ...<br /> Fetching file portage-20140821.tar.xz ...<br /> Checking digest ...<br /> Getting snapshot timestamp ...<br /> Syncing local tree ...<br /> <br /> </pre>}}<br /> <br /> {{Warning|If you get the following instead then there is no newer snapshot available}}<br /> <br /> {{Cmd<br /> |PORTAGE_RSYNC_EXTRA_OPTS{{=}}"--exclude{{=}}/.git --exclude{{=}}/.gitignore" PORTDIR{{=}}"${PWD}" emerge-webrsync<br /> |output=<pre><br /> Fetching most recent snapshot ...<br /> * Latest snapshot date: 20140821<br /> * <br /> * Approximate snapshot timestamp: 1408668300<br /> * Current local timestamp: 1408667701<br /> * <br /> * The current local timestamp is possibly identical to the<br /> * timestamp of the latest snapshot. In order to force sync, use<br /> * the --revert option or remove the timestamp file located at<br /> * '/run/user/1000/portage/metadata/timestamp.x'.<br /> </pre>}}<br /> <br /> Set the tag and push if there was an update:<br /> {{Cmd<br /> |cd portage/<br /> |git add -A<br /> |snapshot_date{{=}}$(date --date{{=}}@$(( $(cut -f 1 -d " " metadata/timestamp.x) - 86400 )) +%Y-%m-%d)<br /> |git commit -m "Update portage tree to ${snapshot_date}"<br /> |git tag -a -m "Tagging ${snapshot_date}" ${snapshot_date}<br /> |git push && git push --tags<br /> |echo "snapshot date: ${snapshot_date}"<br /> }}<br /> <br /> The subtraction of 86400 (1 day in seconds) above is to account for the fact that the snapshot for a given day is taken at 00:45 UTC on the following day and the timestamp contained in the tarball therefore is one day ahead (see {{Path|/usr/bin/emerge-webrsync}}).<br /> <br /> The meaning of the tag is therefore: contains at least all changes from that day (and possibly a bit more).<br /> <br /> == Chroot Setup ==<br /> <br /> === Preparation ===<br /> <br /> At least the following is required beforehand to ensure reproducible building:<br /> <br /> * a versioned portage tree<br /> * versioned overlays (if any)<br /> <br /> === Setup ===<br /> <br /> * Create a staging root directory and extract a stage3 or stage4 tarball<br /> * Mount proc, sys and dev (required for portage to control the tty, determine available storage space, etc.)<br /> * Copy {{Path|/etc/resolv.conf}}<br /> * Checkout the versioned portage tree (since you probably won't have git yet in the tree)<br /> * Enter the chroot<br /> <br /> {{RootCmd<br /> |stagingRoot{{=}}/var/staging/staging-base<br /> |mkdir -p "${stagingRoot}"<br /> |tar -xjpf /var/tmp/your-stage4.tbz2 -C "${stagingRoot}"<br /> |mount -t proc none "${stagingRoot}/proc"<br /> |mount --rbind /dev/ "${stagingRoot}/dev/"<br /> |mount --rbind /sys/ "${stagingRoot}/sys/"<br /> |cp -af /etc/resolv.conf "${stagingRoot}/etc/"<br /> |git clone "${PORTAGE_GIT_REPO}" "${stagingRoot}/usr/portage"<br /> |chmod -R a+rX "${stagingRoot}/usr/portage"<br /> |chroot "${stagingRoot}" /usr/bin/env -i HOME{{=}}"/root" TERM{{=}}"${TERM}" /bin/bash --login<br /> |}}<br /> <br /> {{Note|We are deliberately using a special command for entering the chroot to avoid leaking environment variables}}<br /> <br /> * Install {{Package|app-portage/layman}} and probably {{Package|dev-vcs/git}} to install overlays<br /> * You may want to add a mirror configuration if you have local mirrors:<br /> {{File|/etc/portage/make.conf||<source lang='bash'><br /> GENTOO_MIRRORS="https://mirror.example.com/public/gentoo"<br /> </source>}}<br /> <br /> * If needed, put the mirror for fetch restricted ebuilds in a local mirror definition:<br /> {{File|/etc/portage/mirrors||<pre><br /> local https://mirror.example.com/restricted/gentoo<br /> </pre>}}<br /> <br /> * Add the following to generate binary packages during installation:<br /> {{File|/etc/portage/make.conf||<source lang='bash'><br /> FEATURES="${FEATURES} buildpkg cgroup ipc-sandbox network-sandbox parallel-fetch"<br /> </source>}}<br /> <br /> * Make sure that the repository configuration points to your git mirror as well:<br /> {{File|/etc/portage/repos.conf/gentoo.conf||<source lang='ini'><br /> [DEFAULT]<br /> main-repo = gentoo<br /> <br /> [gentoo]<br /> location = /usr/portage<br /> sync-type = git<br /> sync-uri = https://mirror.example.com/versioned/portage.git<br /> </source>}}<br /> <br /> * Rebuild everything:<br /> {{RootCmd|emerge -e world}}<br /> <br /> [[Category:Infrastructure]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Upgrade&diff=4540 stoney cloud: Upgrade 2015-02-26T15:13:05Z

<p>Pascal: </p> <hr /> <div>= Overview =<br /> This guide explains, what you need to do during the installation of your Multi-Node Installation.<br /> <br /> == Prepare your stoney cloud installation for the update ==<br /> <br /> === <= 1.2.10.3 ===<br /> <br /> If you have a '''productive''' (releases) stoney cloud Installation, execute the following command:<br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/releases/1.2/packages"' >> /etc/portage/make.conf<br /> </source><br /> <br /> If you have a '''test''' (pre-releases) stoney cloud Installation instead, execute the following command:<br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf<br /> </source><br /> <br /> '''IMPORTANT:''' Even a pre-release ISO may result in a stable installation, depending on when it was generated in the release cycle. Please verify by executing <code>git branch</code> in <code>/usr/portage</code> and <code>/var/lib/layman/foss-cloud</code> whether this is the case, and [[stoney_cloud:_Switch_to_testing_branch|switch to the testing branch]] if needed (that is: if the branch displayed does not contain the words <code>pre</code> or <code>testing</code>. If the branch is empty, that means you have a brand new installation without anything yet. In that case, directly check the configuration files <code>/usr/portage/.git/config</code> and/or <code>/var/lib/layman/foss-cloud/.git/config</code> to see which branch it would check out upon <code>emerge --sync</code> and from where.).<br /> <br /> === >= 1.2.10.4 ===<br /> <br /> Execute the following command to register the binary package mirror (since for now there will be only pre-releases, but with better quality than FOSS-Cloud releases):<br /> <br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf<br /> <br /> # Disable the SYNC from rsync since newer portage versions otherwise won't accept a portage tree via git<br /> sed -i -e 's|^SYNC|#SYNC|' /etc/portage/make.conf<br /> </source><br /> <br /> == Update ==<br /> <br /> === Updating from 1.2.10.7 or earlier to 1.2.10.8_rc4 or newer ===<br /> <br /> A complete rebuild of all packages was required, therefore the update guide is different:<br /> <br /> <source lang='bash'><br /> emerge --sync<br /> <br /> emerge -eK world -va<br /> <br /> # sst-libvirt-hooks is not part of the stoney-cloud anymore since it requires further configuration<br /> # make sure that it still gets updated and not removed later, if you have it installed and enabled<br /> emerge -K app-emulation/sst-libvirt-hooks<br /> <br /> dispatch-conf<br /> <br /> # Switch runtime switchable options<br /> eselect python set python3.3<br /> eselect php set cli php5.5<br /> eselect php set apache2 php5.5<br /> gcc-config x86_64-pc-linux-gnu-4.7.3<br /> </source><br /> <br /> During the dispatch-conf the following may appear:<br /> * /etc/libvirt/libvirt.conf: you may get the suggestion to remove almost all content. Quit dispatch-conf and do: <code>rm /etc/libvirt/._mrg*</code> and start dispatch-conf again.<br /> * /etc/libvirt/libvirt.conf: merge all whitespace/comment changes but make sure you don't overwrite the <code>listen_addr</code><br /> * /etc/portage/make.conf: merge all changes beside the <code>PORTAGE_BINHOST</code><br /> * /var/www/localhost/htdocs/vm-manager/vm_config.php: merge the versions, newly added lines and comments. Avoid changes on sstSourceHostName array<br /> <br /> To make sure everything works, reboot and then cleanup:<br /> <br /> <source lang='bash'><br /> emerge --depclean -va<br /> </source><br /> <br /> * If the cleanup fails stating that <code>Locale-gettext</code> and <code>dev-libs/boost</code> depends on some version of perl, reinstall that package manually once and try again:<br /> <source lang='bash'><br /> emerge -1Kva dev-libs/boost Locale-gettext<br /> <br /> # same for autoconf-/automake-wrapper if host was used to build stuff:<br /> emerge -1K sys-devel/autoconf-wrapper sys-devel/automake-wrapper<br /> </source><br /> * '''WARNING''': this also removes the current kernel. If you want to play it safe, reboot first, then depclean, then reboot again<br /> * Rebuilde separately installed perl modules and remove traces of the old perl version:<br /> <source lang='bash'><br /> perl-cleaner --all -- -va<br /> rm -rf /usr/lib64/perl5/{vendor_perl,}/5.12.4<br /> </source><br /> <br /> ==== Emulator ====<br /> * u=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,o=stepping-stone,c=ch<br /> <br /> Change<br /> <pre><br /> sstEmulator: /usr/bin/qemu-kvm<br /> </pre><br /> to<br /> <pre><br /> sstEmulator: /usr/bin/qemu-system-x86_64<br /> </pre><br /> <br /> ==== Source Port ====<br /> * sstDisk=vda,ou=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org<br /> * sstDisk=vdb,ou=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org<br /> <br /> Add<br /> <pre><br /> sstSourcePort: 24007<br /> </pre><br /> <br /> ==== Firewall / Subversion ====<br /> If you are using our firewall scripts (libvirt-hooks based), you'll also have to upgrade subversion (on all the stoney cloud nodes):<br /> <source lang='bash'><br /> cd /usr/local/scripts/netfilter/local/chains/vms<br /> svn upgrade<br /> cd /usr/local/scripts/netfilter/local/chains/$(hostname -s)<br /> svn upgrade<br /> </source><br /> <br /> === Regular Update ===<br /> <br /> Makes sure, your local portage tree is updated:<br /> emerge --sync<br /> <br /> Now you can make sure, that you've got the current stoney cloud version installed:<br /> emerge -KuDva virtual/foss-cloud<br /> <br /> <pre><br /> Local copy of remote index is up-to-date and will be used.<br /> <br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> <br /> Total: 0 packages, Size of downloads: 0 kB<br /> <br /> * virtual/foss-cloud-1.2.10.4<br /> <br /> Would you like to add these packages to your world favorites? [Yes/No] '''no'''<br /> </pre><br /> <br /> If you have updated you stoney cloud, you might want to sanely update your configuration files after emerging new packages (including updates):<br /> dispatch-conf<br /> <br /> == Installing Software Examples ==<br /> 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.<br /> <br /> === Binary Package ===<br /> Per default, the stoney cloud expects you to install binary packages, which can be seen with '''[binary R ]''' output.<br /> emerge -va git<br /> <br /> <pre><br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [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<br /> <br /> Total: 1 package (1 reinstall, 1 binary), Size of downloads: 5,295 kB<br /> <br /> Would you like to merge these packages? [Yes/No] no<br /> <br /> Quitting.<br /> </pre><br /> <br /> === Force Non-Binary Package ===<br /> If you force a non-binary package, the output will be in the form of '''[ebuild R ]'''.<br /> FEATURES="-getbinpkg" emerge -va git<br /> <br /> <pre><br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [ebuild N ] app-arch/cpio-2.11 USE="nls" 995 kB<br /> [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<br /> <br /> Total: 2 packages (1 new, 1 reinstall), Size of downloads: 5,518 kB<br /> <br /> Would you like to merge these packages? [Yes/No] <br /> </pre><br /> <br /> === No Binary Package Exists ===<br /> 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 ]'''.<br /> emerge -va htop<br /> <br /> <pre><br /> Local copy of remote index is up-to-date and will be used.<br /> <br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [ebuild N ] sys-process/htop-1.0.2 USE="unicode -openvz -vserver" 380 kB<br /> <br /> Total: 1 package (1 new), Size of downloads: 380 kB<br /> <br /> Would you like to merge these packages? [Yes/No] <br /> </pre><br /> <br /> == Multi-Node Installation ==<br /> Follow the [[Multi-Node_Installation#Specialized_Installation | Specialized Installation]] Guide.<br /> <br /> == Basic Testing Steps ==<br /> Get your stoney cloud image:<br /> <source lang='bash'><br /> version=1.2.10.7 # stoney cloud version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/iso/foss-cloud-installer-${version}.iso<br /> chown apache:vm-storage foss-cloud-installer-${version}.iso<br /> chmod 644 foss-cloud-installer-${version}.iso<br /> </source><br /> <br /> Get a Fedora ISO image:<br /> <source lang='bash'><br /> version=21 # Fedora version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/${version}/Server/x86_64/iso/Fedora-Server-netinst-x86_64-${version}.iso<br /> chown apache:vm-storage Fedora-Server-netinst-x86_64-${version}.iso<br /> chmod 644 Fedora-Server-netinst-x86_64-${version}.iso<br /> </source><br /> <br /> Lernstick (Test):<br /> <source lang='bash'><br /> cd /var/virtualization/iso-choosable/<br /> wget http://www.imedias.ch/dateien/lernstick-testversion/lernstick_debian7_2013-12-12.iso<br /> chown apache:vm-storage lernstick_debian7_2013-12-12.iso<br /> chmod 644 lernstick_debian7_2013-12-12.iso<br /> </source><br /> <br /> Get your debian image:<br /> <source lang='bash'><br /> version=7.8.0 # Debian version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://cdimage.debian.org/debian-cd/${version}/amd64/iso-cd/debian-${version}-amd64-netinst.iso<br /> chown apache:vm-storage debian-${version}-amd64-netinst.iso<br /> chmod 644 debian-${version}-amd64-netinst.iso<br /> </source><br /> <br /> Get your ubuntu desktop image:<br /> <source lang='bash'><br /> version=14.04 # ubuntu version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/ubuntu-cdimage/${version}/ubuntu-${version}-desktop-amd64.iso<br /> chown apache:vm-storage ubuntu-${version}-desktop-amd64.iso<br /> chmod 644 ubuntu-${version}-desktop-amd64.iso<br /> </source><br /> <br /> Get your ubuntu server image:<br /> <source lang='bash'><br /> version=14.04 # ubuntu version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/ubuntu-cdimage/${version}/ubuntu-${version}-server-amd64.iso<br /> chown apache:vm-storage ubuntu-${version}-server-amd64.iso<br /> chmod 644 ubuntu-${version}-server-amd64.iso<br /> </source><br /> <br /> Get a Windows 2012 Server R2 ISO image:<br /> <source lang='bash'><br /> cd /var/virtualization/iso-choosable/<br /> wget http://care.dlservice.microsoft.com/dl/download/6/2/A/62A76ABB-9990-4EFC-A4FE-C7D698DAEB96/9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO -O windows_server_2012_r2_64bit_en.iso<br /> chown apache:vm-storage windows_server_2012_r2_64bit_en.iso<br /> chmod 640 windows_server_2012_r2_64bit_en.iso<br /> </source><br /> <br /> Set three network ranges under https://192.168.140.10/vm-manager/subnet/index.html<br /> 192.168.140.64<br /> 26<br /> Template Range<br /> template<br /> <br /> 192.168.140.128<br /> 26<br /> Persistent Range<br /> persistent<br /> <br /> 192.168.140.192<br /> 26<br /> Dynamic Range<br /> dynamic<br /> <br /> Add the three newly creates network ranges to the VM-Pools under https://192.168.140.10/vm-manager/vmPool/index.html<br /> <br /> Create a Virtual Machine Profile under https://192.168.140.10/vm-manager/vmProfile/create.html<br /> <br /> Create a Virtual Machine Template under https://192.168.140.10/vm-manager/vmTemplate/create.html and install a basic operating system.<br /> <br /> Create a persistent Virtual Machine from the newly created Virtual Machine Template.<br /> <br /> == Known Issues ==<br /> None.<br /> <br /> [[Category:Installation]]<br /> [[Category:stoney cloud]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Upgrade&diff=4539 stoney cloud: Upgrade 2015-02-26T15:11:14Z

<p>Pascal: </p> <hr /> <div>= Overview =<br /> This guide explains, what you need to do during the installation of your Multi-Node Installation.<br /> <br /> == Prepare your stoney cloud installation for the update ==<br /> <br /> === <= 1.2.10.3 ===<br /> <br /> If you have a '''productive''' (releases) stoney cloud Installation, execute the following command:<br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/releases/1.2/packages"' >> /etc/portage/make.conf<br /> </source><br /> <br /> If you have a '''test''' (pre-releases) stoney cloud Installation instead, execute the following command:<br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf<br /> </source><br /> <br /> '''IMPORTANT:''' Even a pre-release ISO may result in a stable installation, depending on when it was generated in the release cycle. Please verify by executing <code>git branch</code> in <code>/usr/portage</code> and <code>/var/lib/layman/foss-cloud</code> whether this is the case, and [[stoney_cloud:_Switch_to_testing_branch|switch to the testing branch]] if needed (that is: if the branch displayed does not contain the words <code>pre</code> or <code>testing</code>. If the branch is empty, that means you have a brand new installation without anything yet. In that case, directly check the configuration files <code>/usr/portage/.git/config</code> and/or <code>/var/lib/layman/foss-cloud/.git/config</code> to see which branch it would check out upon <code>emerge --sync</code> and from where.).<br /> <br /> === >= 1.2.10.4 ===<br /> <br /> Execute the following command to register the binary package mirror (since for now there will be only pre-releases, but with better quality than FOSS-Cloud releases):<br /> <br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf<br /> <br /> # Disable the SYNC from rsync since newer portage versions otherwise won't accept a portage tree via git<br /> sed -i -e 's|^SYNC|#SYNC|' /etc/portage/make.conf<br /> </source><br /> <br /> == Update ==<br /> <br /> === Updating from 1.2.10.7 or earlier to 1.2.10.8_rc4 or newer ===<br /> <br /> A complete rebuild of all packages was required, therefore the update guide is different:<br /> <br /> <source lang='bash'><br /> emerge --sync<br /> <br /> emerge -eK world -va<br /> <br /> # sst-libvirt-hooks is not part of the stoney-cloud anymore since it requires further configuration<br /> # make sure that it still gets updated and not removed later, if you have it installed and enabled<br /> emerge -K app-emulation/sst-libvirt-hooks<br /> <br /> dispatch-conf<br /> <br /> # Switch runtime switchable options<br /> eselect python set python3.3<br /> eselect php set cli php5.5<br /> eselect php set apache2 php5.5<br /> gcc-config x86_64-pc-linux-gnu-4.7.3<br /> </source><br /> <br /> During the dispatch-conf the following may appear:<br /> * /etc/libvirt/libvirt.conf: you may get the suggestion to remove almost all content. Quit dispatch-conf and do: <code>rm /etc/libvirt/._mrg*</code> and start dispatch-conf again.<br /> * /etc/libvirt/libvirt.conf: merge all whitespace/comment changes but make sure you don't overwrite the <code>listen_addr</code><br /> * /etc/portage/make.conf: merge all changes beside the <code>PORTAGE_BINHOST</code><br /> * /var/www/localhost/htdocs/vm-manager/vm_config.php: merge the versions, newly added lines and comments. Avoid changes on sstSourceHostName array<br /> <br /> To make sure everything works, reboot and then cleanup:<br /> <br /> <source lang='bash'><br /> emerge --depclean -va<br /> </source><br /> <br /> * If the cleanup fails stating that <code>Locale-gettext</code> and <code>dev-libs/boost</code> depends on some version of perl, reinstall that package manually once and try again:<br /> <source lang='bash'><br /> emerge -1Kva dev-libs/boost Locale-gettext<br /> <br /> # same for autoconf-/automake-wrapper if host was used to build stuff:<br /> emerge -1K sys-devel/autoconf-wrapper sys-devel/automake-wrapper<br /> </source><br /> * '''WARNING''': this also removes the current kernel. If you want to play it safe, reboot first, then depclean, then reboot again<br /> * Rebuilde separately installed perl modules and remove traces of the old perl version:<br /> <source lang='bash'><br /> perl-cleaner --all -- -va<br /> rm -rf /usr/lib64/perl5/{vendor_perl,}/5.12.4<br /> </source><br /> <br /> ==== Emulator ====<br /> * u=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,o=stepping-stone,c=ch<br /> <br /> Change<br /> <pre><br /> sstEmulator: /usr/bin/qemu-kvm<br /> </pre><br /> to<br /> <pre><br /> sstEmulator: /usr/bin/qemu-system-x86_64<br /> </pre><br /> <br /> ==== Source Port ====<br /> * sstDisk=vda,ou=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org<br /> * sstDisk=vdb,ou=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org<br /> <br /> Add<br /> <pre><br /> sstSourcePort: 24007<br /> </pre><br /> <br /> ==== Firewall / Subversion ====<br /> If you are using our firewall scripts (libvirt-hooks based), you'll also have to upgrade subversion (on all the stoney cloud nodes):<br /> <source lang='bash'><br /> cd /usr/local/scripts/netfilter/local/chains/vms<br /> svn upgrade<br /> cd /usr/local/scripts/netfilter/local/chains/$(hostname -s)<br /> svn upgrade<br /> </source><br /> <br /> === Regular Update ===<br /> <br /> Makes sure, your local portage tree is updated:<br /> emerge --sync<br /> <br /> Now you can make sure, that you've got the current stoney cloud version installed:<br /> emerge -KuDva virtual/foss-cloud<br /> <br /> <pre><br /> Local copy of remote index is up-to-date and will be used.<br /> <br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> <br /> Total: 0 packages, Size of downloads: 0 kB<br /> <br /> * virtual/foss-cloud-1.2.10.4<br /> <br /> Would you like to add these packages to your world favorites? [Yes/No] '''no'''<br /> </pre><br /> <br /> If you have updated you stoney cloud, you might want to sanely update your configuration files after emerging new packages (including updates):<br /> dispatch-conf<br /> <br /> == Installing Software Examples ==<br /> 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.<br /> <br /> === Binary Package ===<br /> Per default, the stoney cloud expects you to install binary packages, which can be seen with '''[binary R ]''' output.<br /> emerge -va git<br /> <br /> <pre><br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [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<br /> <br /> Total: 1 package (1 reinstall, 1 binary), Size of downloads: 5,295 kB<br /> <br /> Would you like to merge these packages? [Yes/No] no<br /> <br /> Quitting.<br /> </pre><br /> <br /> === Force Non-Binary Package ===<br /> If you force a non-binary package, the output will be in the form of '''[ebuild R ]'''.<br /> FEATURES="-getbinpkg" emerge -va git<br /> <br /> <pre><br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [ebuild N ] app-arch/cpio-2.11 USE="nls" 995 kB<br /> [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<br /> <br /> Total: 2 packages (1 new, 1 reinstall), Size of downloads: 5,518 kB<br /> <br /> Would you like to merge these packages? [Yes/No] <br /> </pre><br /> <br /> === No Binary Package Exists ===<br /> 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 ]'''.<br /> emerge -va htop<br /> <br /> <pre><br /> Local copy of remote index is up-to-date and will be used.<br /> <br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [ebuild N ] sys-process/htop-1.0.2 USE="unicode -openvz -vserver" 380 kB<br /> <br /> Total: 1 package (1 new), Size of downloads: 380 kB<br /> <br /> Would you like to merge these packages? [Yes/No] <br /> </pre><br /> <br /> == Multi-Node Installation ==<br /> Follow the [[Multi-Node_Installation#Specialized_Installation | Specialized Installation]] Guide.<br /> <br /> == Basic Testing Steps ==<br /> Get your stoney cloud image:<br /> <source lang='bash'><br /> version=1.2.10.7 # stoney cloud version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/iso/foss-cloud-installer-${version}.iso<br /> chown apache:vm-storage foss-cloud-installer-${version}.iso<br /> chmod 644 foss-cloud-installer-${version}.iso<br /> </source><br /> <br /> Get a Fedora ISO image:<br /> <source lang='bash'><br /> version=21 # Fedora version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/${version}/Server/x86_64/iso/Fedora-Server-netinst-x86_64-${version}.iso<br /> chown apache:vm-storage Fedora-Server-netinst-x86_64-${version}.iso<br /> chmod 644 Fedora-Server-netinst-x86_64-${version}.iso<br /> </source><br /> <br /> Lernstick (Test):<br /> <source lang='bash'><br /> cd /var/virtualization/iso-choosable/<br /> wget http://www.imedias.ch/dateien/lernstick-testversion/lernstick_debian7_2013-12-12.iso<br /> chown apache:vm-storage lernstick_debian7_2013-12-12.iso<br /> chmod 644 lernstick_debian7_2013-12-12.iso<br /> </source><br /> <br /> Get your debian image:<br /> <source lang='bash'><br /> version=7.8.0 # Debian version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://cdimage.debian.org/debian-cd/${version}/amd64/iso-cd/debian-${version}-amd64-netinst.iso<br /> chown apache:vm-storage debian-${version}-amd64-netinst.iso<br /> chmod 644 debian-${version}-amd64-netinst.iso<br /> </source><br /> <br /> Get your ubuntu desktop image:<br /> <source lang='bash'><br /> version=14.04 # ubuntu version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/ubuntu-cdimage/${version}/ubuntu-${version}-desktop-amd64.iso<br /> chown apache:vm-storage ubuntu-${version}-desktop-amd64.iso<br /> chmod 644 ubuntu-${version}-desktop-amd64.iso<br /> </source><br /> <br /> Get your ubuntu server image:<br /> <source lang='bash'><br /> version=14.04 # ubuntu version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/ubuntu-cdimage/${version}/ubuntu-${version}-server-amd64.iso<br /> chown apache:vm-storage ubuntu-${version}-server-amd64.iso<br /> chmod 644 ubuntu-${version}-server-amd64.iso<br /> </source><br /> <br /> Get a Windows 2012 Server R2 ISO image:<br /> <source lang='bash'><br /> cd /var/virtualization/iso-choosable/<br /> http://care.dlservice.microsoft.com/dl/download/6/2/A/62A76ABB-9990-4EFC-A4FE-C7D698DAEB96/9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO<br /> mv 9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO windows2012r2_64bit_en.iso<br /> chown apache:vm-storage windows2012r2_64bit_en.iso<br /> chmod 640 windows2012r2_64bit_en.iso<br /> </source><br /> <br /> Set three network ranges under https://192.168.140.10/vm-manager/subnet/index.html<br /> 192.168.140.64<br /> 26<br /> Template Range<br /> template<br /> <br /> 192.168.140.128<br /> 26<br /> Persistent Range<br /> persistent<br /> <br /> 192.168.140.192<br /> 26<br /> Dynamic Range<br /> dynamic<br /> <br /> Add the three newly creates network ranges to the VM-Pools under https://192.168.140.10/vm-manager/vmPool/index.html<br /> <br /> Create a Virtual Machine Profile under https://192.168.140.10/vm-manager/vmProfile/create.html<br /> <br /> Create a Virtual Machine Template under https://192.168.140.10/vm-manager/vmTemplate/create.html and install a basic operating system.<br /> <br /> Create a persistent Virtual Machine from the newly created Virtual Machine Template.<br /> <br /> == Known Issues ==<br /> None.<br /> <br /> [[Category:Installation]]<br /> [[Category:stoney cloud]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Upgrade&diff=4538 stoney cloud: Upgrade 2015-02-26T15:10:22Z

<p>Pascal: </p> <hr /> <div>= Overview =<br /> This guide explains, what you need to do during the installation of your Multi-Node Installation.<br /> <br /> == Prepare your stoney cloud installation for the update ==<br /> <br /> === <= 1.2.10.3 ===<br /> <br /> If you have a '''productive''' (releases) stoney cloud Installation, execute the following command:<br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/releases/1.2/packages"' >> /etc/portage/make.conf<br /> </source><br /> <br /> If you have a '''test''' (pre-releases) stoney cloud Installation instead, execute the following command:<br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf<br /> </source><br /> <br /> '''IMPORTANT:''' Even a pre-release ISO may result in a stable installation, depending on when it was generated in the release cycle. Please verify by executing <code>git branch</code> in <code>/usr/portage</code> and <code>/var/lib/layman/foss-cloud</code> whether this is the case, and [[stoney_cloud:_Switch_to_testing_branch|switch to the testing branch]] if needed (that is: if the branch displayed does not contain the words <code>pre</code> or <code>testing</code>. If the branch is empty, that means you have a brand new installation without anything yet. In that case, directly check the configuration files <code>/usr/portage/.git/config</code> and/or <code>/var/lib/layman/foss-cloud/.git/config</code> to see which branch it would check out upon <code>emerge --sync</code> and from where.).<br /> <br /> === >= 1.2.10.4 ===<br /> <br /> Execute the following command to register the binary package mirror (since for now there will be only pre-releases, but with better quality than FOSS-Cloud releases):<br /> <br /> <source lang="bash"><br /> echo 'PORTAGE_BINHOST="http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/packages"' >> /etc/portage/make.conf<br /> <br /> # Disable the SYNC from rsync since newer portage versions otherwise won't accept a portage tree via git<br /> sed -i -e 's|^SYNC|#SYNC|' /etc/portage/make.conf<br /> </source><br /> <br /> == Update ==<br /> <br /> === Updating from 1.2.10.7 or earlier to 1.2.10.8_rc4 or newer ===<br /> <br /> A complete rebuild of all packages was required, therefore the update guide is different:<br /> <br /> <source lang='bash'><br /> emerge --sync<br /> <br /> emerge -eK world -va<br /> <br /> # sst-libvirt-hooks is not part of the stoney-cloud anymore since it requires further configuration<br /> # make sure that it still gets updated and not removed later, if you have it installed and enabled<br /> emerge -K app-emulation/sst-libvirt-hooks<br /> <br /> dispatch-conf<br /> <br /> # Switch runtime switchable options<br /> eselect python set python3.3<br /> eselect php set cli php5.5<br /> eselect php set apache2 php5.5<br /> gcc-config x86_64-pc-linux-gnu-4.7.3<br /> </source><br /> <br /> During the dispatch-conf the following may appear:<br /> * /etc/libvirt/libvirt.conf: you may get the suggestion to remove almost all content. Quit dispatch-conf and do: <code>rm /etc/libvirt/._mrg*</code> and start dispatch-conf again.<br /> * /etc/libvirt/libvirt.conf: merge all whitespace/comment changes but make sure you don't overwrite the <code>listen_addr</code><br /> * /etc/portage/make.conf: merge all changes beside the <code>PORTAGE_BINHOST</code><br /> * /var/www/localhost/htdocs/vm-manager/vm_config.php: merge the versions, newly added lines and comments. Avoid changes on sstSourceHostName array<br /> <br /> To make sure everything works, reboot and then cleanup:<br /> <br /> <source lang='bash'><br /> emerge --depclean -va<br /> </source><br /> <br /> * If the cleanup fails stating that <code>Locale-gettext</code> and <code>dev-libs/boost</code> depends on some version of perl, reinstall that package manually once and try again:<br /> <source lang='bash'><br /> emerge -1Kva dev-libs/boost Locale-gettext<br /> <br /> # same for autoconf-/automake-wrapper if host was used to build stuff:<br /> emerge -1K sys-devel/autoconf-wrapper sys-devel/automake-wrapper<br /> </source><br /> * '''WARNING''': this also removes the current kernel. If you want to play it safe, reboot first, then depclean, then reboot again<br /> * Rebuilde separately installed perl modules and remove traces of the old perl version:<br /> <source lang='bash'><br /> perl-cleaner --all -- -va<br /> rm -rf /usr/lib64/perl5/{vendor_perl,}/5.12.4<br /> </source><br /> <br /> ==== Emulator ====<br /> * u=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,o=stepping-stone,c=ch<br /> <br /> Change<br /> <pre><br /> sstEmulator: /usr/bin/qemu-kvm<br /> </pre><br /> to<br /> <pre><br /> sstEmulator: /usr/bin/qemu-system-x86_64<br /> </pre><br /> <br /> ==== Source Port ====<br /> * sstDisk=vda,ou=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org<br /> * sstDisk=vdb,ou=devices,sstVirtualMachine=*,ou=virtual machines,ou=virtualization,ou=services,dc=stoney-cloud,dc=org<br /> <br /> Add<br /> <pre><br /> sstSourcePort: 24007<br /> </pre><br /> <br /> ==== Firewall / Subversion ====<br /> If you are using our firewall scripts (libvirt-hooks based), you'll also have to upgrade subversion (on all the stoney cloud nodes):<br /> <source lang='bash'><br /> cd /usr/local/scripts/netfilter/local/chains/vms<br /> svn upgrade<br /> cd /usr/local/scripts/netfilter/local/chains/$(hostname -s)<br /> svn upgrade<br /> </source><br /> <br /> === Regular Update ===<br /> <br /> Makes sure, your local portage tree is updated:<br /> emerge --sync<br /> <br /> Now you can make sure, that you've got the current stoney cloud version installed:<br /> emerge -KuDva virtual/foss-cloud<br /> <br /> <pre><br /> Local copy of remote index is up-to-date and will be used.<br /> <br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> <br /> Total: 0 packages, Size of downloads: 0 kB<br /> <br /> * virtual/foss-cloud-1.2.10.4<br /> <br /> Would you like to add these packages to your world favorites? [Yes/No] '''no'''<br /> </pre><br /> <br /> If you have updated you stoney cloud, you might want to sanely update your configuration files after emerging new packages (including updates):<br /> dispatch-conf<br /> <br /> == Installing Software Examples ==<br /> 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.<br /> <br /> === Binary Package ===<br /> Per default, the stoney cloud expects you to install binary packages, which can be seen with '''[binary R ]''' output.<br /> emerge -va git<br /> <br /> <pre><br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [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<br /> <br /> Total: 1 package (1 reinstall, 1 binary), Size of downloads: 5,295 kB<br /> <br /> Would you like to merge these packages? [Yes/No] no<br /> <br /> Quitting.<br /> </pre><br /> <br /> === Force Non-Binary Package ===<br /> If you force a non-binary package, the output will be in the form of '''[ebuild R ]'''.<br /> FEATURES="-getbinpkg" emerge -va git<br /> <br /> <pre><br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [ebuild N ] app-arch/cpio-2.11 USE="nls" 995 kB<br /> [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<br /> <br /> Total: 2 packages (1 new, 1 reinstall), Size of downloads: 5,518 kB<br /> <br /> Would you like to merge these packages? [Yes/No] <br /> </pre><br /> <br /> === No Binary Package Exists ===<br /> 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 ]'''.<br /> emerge -va htop<br /> <br /> <pre><br /> Local copy of remote index is up-to-date and will be used.<br /> <br /> These are the packages that would be merged, in order:<br /> <br /> Calculating dependencies... done!<br /> [ebuild N ] sys-process/htop-1.0.2 USE="unicode -openvz -vserver" 380 kB<br /> <br /> Total: 1 package (1 new), Size of downloads: 380 kB<br /> <br /> Would you like to merge these packages? [Yes/No] <br /> </pre><br /> <br /> == Multi-Node Installation ==<br /> Follow the [[Multi-Node_Installation#Specialized_Installation | Specialized Installation]] Guide.<br /> <br /> == Basic Testing Steps ==<br /> Get your stoney cloud image:<br /> <source lang='bash'><br /> version=1.2.10.7 # stoney cloud version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://packages.stoney-cloud.org/stoney-cloud/pre-releases/1.2/iso/foss-cloud-installer-${version}.iso<br /> chown apache:vm-storage foss-cloud-installer-${version}.iso<br /> chmod 644 foss-cloud-installer-${version}.iso<br /> </source><br /> <br /> Get a Fedora ISO image:<br /> <source lang='bash'><br /> version=21 # Fedora version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/${version}/Server/x86_64/iso/Fedora-Server-netinst-x86_64-${version}.iso<br /> chown apache:vm-storage Fedora-Server-netinst-x86_64-${version}.iso<br /> chmod 644 Fedora-Server-netinst-x86_64-${version}.iso<br /> </source><br /> <br /> Lernstick (Test):<br /> <source lang='bash'><br /> cd /var/virtualization/iso-choosable/<br /> wget http://www.imedias.ch/dateien/lernstick-testversion/lernstick_debian7_2013-12-12.iso<br /> chown apache:vm-storage lernstick_debian7_2013-12-12.iso<br /> chmod 644 lernstick_debian7_2013-12-12.iso<br /> </source><br /> <br /> Get your debian image:<br /> <source lang='bash'><br /> version=7.8.0 # Debian version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://cdimage.debian.org/debian-cd/${version}/amd64/iso-cd/debian-${version}-amd64-netinst.iso<br /> chown apache:vm-storage debian-${version}-amd64-netinst.iso<br /> chmod 644 debian-${version}-amd64-netinst.iso<br /> </source><br /> <br /> Get your ubuntu desktop image:<br /> <source lang='bash'><br /> version=14.04 # ubuntu version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/ubuntu-cdimage/${version}/ubuntu-${version}-desktop-amd64.iso<br /> chown apache:vm-storage ubuntu-${version}-desktop-amd64.iso<br /> chmod 644 ubuntu-${version}-desktop-amd64.iso<br /> </source><br /> <br /> Get your ubuntu server image:<br /> <source lang='bash'><br /> version=14.04 # ubuntu version<br /> <br /> cd /var/virtualization/iso-choosable/<br /> wget http://mirror.switch.ch/ftp/mirror/ubuntu-cdimage/${version}/ubuntu-${version}-server-amd64.iso<br /> chown apache:vm-storage ubuntu-${version}-server-amd64.iso<br /> chmod 644 ubuntu-${version}-server-amd64.iso<br /> </source><br /> <br /> Get a Windows 2012 Server R2 ISO:<br /> <source lang='bash'><br /> cd /var/virtualization/iso-choosable/<br /> http://care.dlservice.microsoft.com/dl/download/6/2/A/62A76ABB-9990-4EFC-A4FE-C7D698DAEB96/9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO<br /> mv 9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO windows2012r2_64bit_en.iso<br /> chown apache:vm-storage windows2012r2_64bit_en.iso<br /> chmod 640 windows2012r2_64bit_en.iso<br /> </source><br /> <br /> Set three network ranges under https://192.168.140.10/vm-manager/subnet/index.html<br /> 192.168.140.64<br /> 26<br /> Template Range<br /> template<br /> <br /> 192.168.140.128<br /> 26<br /> Persistent Range<br /> persistent<br /> <br /> 192.168.140.192<br /> 26<br /> Dynamic Range<br /> dynamic<br /> <br /> Add the three newly creates network ranges to the VM-Pools under https://192.168.140.10/vm-manager/vmPool/index.html<br /> <br /> Create a Virtual Machine Profile under https://192.168.140.10/vm-manager/vmProfile/create.html<br /> <br /> Create a Virtual Machine Template under https://192.168.140.10/vm-manager/vmTemplate/create.html and install a basic operating system.<br /> <br /> Create a persistent Virtual Machine from the newly created Virtual Machine Template.<br /> <br /> == Known Issues ==<br /> None.<br /> <br /> [[Category:Installation]]<br /> [[Category:stoney cloud]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1148 stoney cloud: Multi-Node Installation 2013-09-06T15:00:22Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from a carrier, a special user called transfer will be created.<br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1147 stoney cloud: Multi-Node Installation 2013-09-06T14:59:50Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from a carrier, a special user called transfer will be created.<br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1146 stoney cloud: Multi-Node Installation 2013-09-06T14:54:19Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1145 stoney cloud: Multi-Node Installation 2013-09-06T14:54:10Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1144 stoney cloud: Multi-Node Installation 2013-09-06T14:53:52Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1143 stoney cloud: Multi-Node Installation 2013-09-06T14:53:41Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1142 stoney cloud: Multi-Node Installation 2013-09-06T14:53:18Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <code><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </code><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1141 stoney cloud: Multi-Node Installation 2013-09-06T14:51:18Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> <br /> Allow password authentication for the transfer user:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <br /> <pre><br /> [...]<br /> <br /> Match User transfer<br /> PasswordAuthentication yes<br /> <br /> [...]<br /> </pre><br /> <br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1140 stoney cloud: Multi-Node Installation 2013-09-06T14:40:36Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> Adjust sshd config to allow password authentication:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <pre><br /> [...]<br /> Match User transfer<br /> PasswordAuthentication yes<br /> [...]<br /> </pre><br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1139 stoney cloud: Multi-Node Installation 2013-09-06T14:40:19Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> Adjust sshd config to allow password authentication:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> [...]<br /> <pre><br /> Match User transfer<br /> PasswordAuthentication yes<br /> </pre><br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1138 stoney cloud: Multi-Node Installation 2013-09-06T14:39:37Z

<p>Pascal: /* Manual Steps */</p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> Adjust sshd config to allow password authentication:<br /> <source lang="bash"><br /> $EDITOR /etc/ssh/sshd_config<br /> </source><br /> <pre><br /> ListenAddress <ADMIN-IP><br /> ListenAddress <DATA-IP><br /> <br /> # override default of no subsystems<br /> Subsystem sftp internal-sftp<br /> <br /> [...]<br /> <br /> AllowUsers admin@192.168.16.254 vmmanager vm-transfer@10.16.97.*<br /> <br /> Match User vm-transfer<br /> ChrootDirectory /var/virtualization<br /> ForceCommand internal-sftp<br /> AllowTcpForwarding no<br /> </pre><br /> <br /> To apply the changes above, restart the SSH daemon:<br /> <source lang="bash"><br /> /etc/init.d/sshd restart<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1137 stoney cloud: Multi-Node Installation 2013-09-06T14:34:52Z

<p>Pascal: </p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special user called transfer will be created. This user is able to open connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal https://wiki.stoney-cloud.org/w/index.php?title=stoney_cloud:_Multi-Node_Installation&diff=1136 stoney cloud: Multi-Node Installation 2013-09-06T14:33:44Z

<p>Pascal: </p> <hr /> <div>== Specialized Installation ==<br /> === Primary-Master-Node (vm-node-01) ===<br /> If you configured a additional Backup Volume on the Storage Nodes, you want to mount them now in the VM-Node.<br /> <br /> Log into the Primary-Master-Node and execute the node-configuration script as follows:<br /> /usr/sbin/fc-node-configuration --node-type primary-master-node<br /> <br /> ==== Manual Steps ====<br /> In order to be able to migrate a VM from one carrier to another, a special unprivileged user called transfer will be created. This user is able to open sftp connections to another carrier and fetch a VM's disk file (qcow2 image).<br /> <br /> Install a transfer user.<br /> <br /> Create the user and generate an SSH private/public key pair (without a pass phrase):<br /> <br /> <source lang="bash"><br /> lvcreate -L 60G -n transfer local0<br /> <br /> mkfs.xfs -L "OSBD_transfe" /dev/local0/transfer <br /> <br /> cat << EOF >> /etc/fstab<br /> <br /> LABEL=OSBD_transfe /home/transfer xfs noatime,nodev,nosuid,noexec 0 2<br /> EOF<br /> <br /> mount /home/transfer<br /> <br /> useradd --comment "User which is used for VM disk file transfer between carriers" \<br /> --create-home \<br /> --system \<br /> --user-group \<br /> transfer<br /> <br /> passwd transfer<br /> </source><br /> <br /> [[Category:Documentation]]</div>

Pascal