Menu
▾
▴
opennode-announce — OpenNode related announcements
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ope...@li...> - 2014-07-24 13:16:12
|
This stable OS release has been rebased to CentOS 6.5 and is introducing Openvswitch as a host bridge networking stack with support for VETH based VLANs and network bandwidth throttling. OpenNode OS 6 Update 3 ISO installer can be downloaded from OpenNode SourceForge project page:https://sourceforge.net/projects/opennode/files/OpenNode_6_Update_3/ Changelog: * Rebased OpenNode base system to CentOS 6.5 - please see RHEL/CentOS 6.5 release notes:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.5_Release_Notes/ * Latest RHEL6 OpenVZ kernel (042stab092.2) with updated OpenVZ and KVM virtualization support * Updated vzctl (4.7.2) and ploop (1.11) package versions * Legacy linux bridge kernel module replaced with Openvswitch (OVS) - that has numerous new features - please seehttp://openvswitch.org/ * Standard 802.1Q VLANs and network bandwith throttling support on VM VETH interface through custom ON_NETIF parameter in VEID.conf file - please see VETH configuration examples here:https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:os:network&#create_veth_interfaces <https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:os:network&#create_veth_interfaces> For updating existing OpenNode OS 6 installations please run: yum update service libvirt restart NB! If you are currently running vzkernel version older than 042stab061.1 - you must install newer vzkernel package first and then run yum update for OS update like this: yum install vzkernel reboot yum update service libvirt restart NB! VM stop/start default behaviour on host reboot has now changed to suspend/resume mode. It can be reverted back to stop/start mode by issuing: sed -i '/^VE_STOP_MODE=/ c VE_STOP_MODE=stop' /etc/vz/vz.conf Wishing nice summer vacations, Team OpenNode |
|
From: <ope...@li...> - 2013-10-18 16:03:02
|
TurnKey Linux Appliance Library contains 100+ Debian based VM appliances - that integrate and polish the very best of open source software into ready to use solutions. Now available also as OpenNode OpenVZ container templates. We have been working closely with TurnKey Linux team (www.turnkeylinux.org) in order to make TKL virtual appliance library available as OpenNode OpenVZ container templates - downloadable and deployable directly from OpenNode TUI management utility. TurnKey Linux appliance library provides most popular pre-packaged open-source solutions - which are very easy to deploy - together with appliance backup and migration tools. TKL appliances are easy to maintain and auto-updated daily with security patches. There are two choices to activate TKL appliance library on OpenNode host: * Update to opennode-tui rpm package version to 20131017200837 or later: yum --enablerepo=opennode-dev update opennode-tui * or by adding TKL appliance repo description manually to /etc/opennode/opennode-tui.conf file - like this: <example> [apps-ovz-tkl-repo] url = sourceforge.net/projects/turnkeylinux/files/opennode/ type = openvz name = TurnKey Linux Appliances [general] repo-groups = default-kvm, default-openvz, apps-ovz-tkl </example> Please see more detailed info about TurnKey Linux Appliance Library from: www.turnkeylinux.org Cheers, -- ---------------------------------------------- Team OpenNode http://www.opennodecloud.com |
|
From: <ope...@li...> - 2013-09-22 19:29:22
|
Launching Amazon EC2 instances with OpenNode OS is now a breeze - as we have released official OpenNode AMIs. Please lookup official AMI IDs for all EC2 regions from here: https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:os:aws Launching OpenNode OS inside Amazon EC2 Cloud instances enables you to: * Partition large EC2 instances further - launch multiple linux/application containers inside EC2 instances with additional resource limits/quarantees * Package your applications into standard linux containers and run everywhere * Run and migrate containers across private and public cloud * Easy management - use single set of tools Team OpenNode |
|
From: <ope...@li...> - 2013-09-22 19:18:16
|
OpenNode has made its way into Web Summit 2013 "featured early stage startups" list and we are going to have an exhibition stand at the conference. You are very welcome to drop by and meet us face to face. More info about Web Summit: www.websummit.net Despite the news/release silence during the summer - we have been actually pretty busy behind the scenes - so here is the shortlist about what we have been up to: * stabilizing OpenNode Management Server (OMS) - our central management controller with ajax web UI - and adding basic QEMU/KVM VM management into mix (stable OMS release pending) implementing popular WHMCS billing software (www.whmcs.com) integration with OMS and WHMCS customizations - in order to provide full client/service portal solution on top of OpenNode for cloud service providers/hosters - please see screenshots here: http://opennodecloud.com/about/whmcs-integration/ * preparing for OpenNode OS Update 3 release - which replaces linux bridge with Openvswitch networking stack (openvswitch.org) and provides a foundation for VLAN support and SDN networking (available from opennode-dev repo for testers) * researching possible Software Defined Networking (SDN) solutions for inclusion into future releases of OpenNode OS - still waiting for some maturity from open-source SDN solutions before inclusion * reserching GlusterFS for possible inclusion into OpenNode OS - mainly waiting for libgfapi-based GlusterFS storage type support to land into RHEL6 QEMU backport * moving VM template/appliance downloads into sourceforge.net mirrors and preparing for TurnKeyLinux appliance library (www.turnkeylinux.org) inclusion/support Kind regards, Team OpenNode |
|
From: <ope...@li...> - 2013-04-25 08:32:49
|
This stable OS release has been rebased to CentOS 6.4 and includes numerous updated packages that provide some new features as well. OpenNode OS 6 Update 2 ISO installer can be downloaded from OpenNode SourceForge project page: https://sourceforge.net/projects/opennode/files/OpenNode_6_Update_2/ Release highlights: Rebased to CentOS 6.4 release (newer qemu/kvm, libvirt, etc) - please see RHEL/CentOS 6.4 release notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.4_Release_Notes/ Includes RHEL6 042stab076.5 vzkernel vzctl 4.2 and ploop 1.6 packages Basic veth management support through custom ON_NETIF parameter in VEID.conf file (TUI support is in the works) Bind mounts support in TUI (for OpenVZ) Disk IO priorities support in TUI (for OpenVZ) NB! QEMU/KVM VM templates disk controller/bus type is hard-coded to virtio from now on (was IDE) - please keep that in mind when creating KVM VM templates (Guests must support virtio - ie install virtio drivers in Windows before creating template from it, linux26 kernels include virtio support by default) VM template (metadata) editing support in TUI (change template name, requirements) ISO installler won't create separate LVM logical volume for vz filesystem anymore - instead /vz is symlinked under /storage/local/vz from now on (allows to use free disk space more efficiently) Func management framework has been replaced by Saltstack - http://saltstack.com/community.html (required by current OMS v2) Included system-config-firewall package (GUI mode can be run over ssh X forwarding) - for managing iptables RHEL way if needed - more info: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html Included koan for QEMU/KVM VM network kickstarting/installs with Cobbler For updating existing OpenNode OS 6 installations please run: yum update service libvirt restart NB! If you are currently running vzkernel version older than 042stab061.1 - you must install newer vzkernel package first and then run yum update for OS update like this: yum install vzkernel reboot yum update service libvirt restart About basic veth management support It allows to describe veth device parameters inside VEID.conf file and is able to auto create containers OS network configuration files on VM start. No opennode-tui support yet - this is still work in progress. Manual configuration can be done by adding ON_NETIF parameter string into VEID.conf file. Parameter example inside VEID.conf file (for manual usage): ON_NETIF="ifname=eth0,ipaddr=192.168.100.10,mask=255.255.255.0, gw=192.168.100.1,managed=yes,default=yes;ifname=eth1,dhcp=yes,managed=yes" Currently limited to creating (overwriting) containers (veth) network devices configuration. You must set "managed=yes" in the ON_NETIF parameter string in order to activate configuration creation for particular device. "default=yes" sets gw as container VM default gateway. Also you must activate veth devices for container with "vzctl set $VEID --netif_add ethX --save" - before you can use this feature. Wishing nice springtime, -- ---------------------------------------------- Team OpenNode |
|
From: <ope...@li...> - 2013-04-05 22:23:08
|
As we are preparing for stable OpenNode 6 Update 2 release we put out ISO installer beta1 for public download and testing. OpenNode 6 Update 2 ISO installer beta1 can be downloaded from OpenNode SourceForge project page: https://sourceforge.net/projects/opennode/files/OpenNode_6_Update_2/ Release highlights: Rebased to CentOS 6.4 release (newer qemu/kvm, libvirt, etc) - please see RHEL/CentOS 6.4 release notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.4_Release_Notes/ Includes RHEL6 042stab076.5 vzkernel vzctl 4.2 and ploop 1.6 packages Basic veth management support through custom ON_NETIF parameter in VEID.conf file (TUI support is in the works) Bind mounts support in TUI (for OpenVZ) Disk IO priorities support in TUI (for OpenVZ) NB! QEMU/KVM VM templates disk controller/bus type is hard-coded to virtio from now on (was IDE) - please keep that in mind when creating KVM VM templates (Guests must support virtio - ie install virtio drivers in Windows before creating template from it, linux26 kernels include virtio support by default) VM template (metadata) editing support in TUI (change template name, requirements) ISO installler won't create separate LVM logical volume for vz filesystem anymore - instead /vz is symlinked under /storage/local/vz from now on (allows to use free disk space more efficiently) Func management framework has been replaced by Saltstack - http://saltstack.com/community.html (required by current OMS) Included system-config-firewall package (GUI mode can be run over ssh X forwarding) - for managing iptables RHEL way if needed - more info: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html Included koan for QEMU/KVM VM network kickstarting/installs with Cobbler For updating existing OpenNode 6 installations please run yum update against opennode-test repository (until we move its contents to stable repo). NB! If you are currently running vzkernel version older than 042stab061.1 - you must update vzkernel package first and then run yum update for OS update like this: yum update vzkernel yum update About basic veth management support It allows to describe veth device parameters inside VEID.conf file and is able to auto create containers OS network configuration files on VM start. No opennode-tui support yet - this is still work in progress. Manual configuration can be done by adding ON_NETIF parameter string into VEID.conf file. Parameter example inside VEID.conf file (for manual usage): ON_NETIF="ifname=eth0,ipaddr=192.168.100.10,mask=255.255.255.0, gw=192.168.100.1,managed=yes,default=yes;ifname=eth1,dhcp=yes,managed=yes" Currently limited to creating (overwriting) containers (veth) network devices configuration. You must set "managed=yes" in the ON_NETIF parameter string in order to activate configuration creation for particular device. "default=yes" sets gw as container VM default gateway. Also you must activate veth devices for container with "vzctl set $VEID --netif_add ethX --save" - before you can use this feature. Happy betatesting, Team OpenNode -- ---------------------------------------------- Andres Toomsalu, an...@op... Founder, OpenNode LLC http://www.opennodecloud.com |
|
From: <ope...@li...> - 2012-11-27 18:22:43
|
First development version of OpenNode OS with Open vSwitch is available for public testing from opennode-ovs yum repository - replacing older linux bridge code and introducing new exiting features. We have temporarely setup a separate opennode-ovs yum repository -http://opennodecloud.com/CentOS/6/opennode-ovs/ - for OpenNode OS with Open vSwitch (OpenNode-OVS) development process. What is Open vSwitch? Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed to support distribution across multiple physical servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V. See the full feature list here Major features included in the release Managed "Bind Mounts" - which can be used to make directories on the hardware node visible to the container. OpenNode-TUI supports setting custom ON_BMOUNT VEID.conf parameter in VM create and edit forms. Parameter format inside VEID.conf file (for manual usage): ON_BMOUNT=src1,dst1;src2,dst2 Initial VETH management support - allowing to describe veth device parameters inside VEID.conf file and auto creating containers OS network configuration files on VM start. No opennode-tui support yet - this is still work in progress. Manual configuration can be done by adding ON_NETIF parameter string into VEID.conf file. Parameter example inside VEID.conf file (for manual usage): ON_NETIF="ifname=eth0,ipaddr=192.168.100.10,mask=255.255.255.0,gw= 192.168.100.1,managed=yes,default=yes,vlan=10,ingress_policing_rate=1000, ingress_policing_burst=100;ifname=eth1,dhcp=yes,managed=yes" Currently limited to creating (overwriting) containers (veth) network devices configuration. You must set "managed=yes" in the ON_NETIF parameter string in order to activate configuration creation for particular device. "default=yes" sets gw as container VM default gateway. Also you must activate veth devices for container with "vzctl set $VEID --netif_add ethX --save" - before you can use this feature. Open vSwitch replacing standard linux bridge - support for VLANs, VM rate policing, GRE tunnels, etc. Install/upgrade instructions OpenNode-OVS is currently available only as OpenNode OS yum upgrade from opennode-ovs repository. For activating opennode-ovs repository please edit /etc/yum.repos.d/opennode.repo file - by changing opennode-test repo URL final part to opennode-ovs and setting repo section enable parameter to 1 (and disabling opennode stable repo). Then please execute: "yum clean all && yum update". NB! After yum update system reboot is needed in order to activate openvswitch (you may safely ignore openvswitch related errors on first shutdown). -- ---------------------------------------------- Team OpenNode |
|
From: <ope...@li...> - 2012-09-04 23:18:19
|
Dear OpenNode supporters, After a bit more quiet summer vacations period we are back with small status updates on OpenNode front: * We have been going through the complete http://opennodecloud.com website redesign and preparing OpenNode paid support packages (more detailed info at personal request) * Website documentation and howto section has gained some new and improved howto's - please review http://opennodecloud.com/documentation/howtos/ * opennode-test yum repository contains newest stable OpenVZ kernel, vzctl and other tools/libraries - they still need some testing time before moving into stable repo (but being stable so far) Happy testing and reading, -- ---------------------------------------------- Andres Toomsalu, an...@op... Founder, OpenNode LLC Lille 4-205, Pärnu 80041, Estonia skype: main2frame phone: +372 6996 807 gsm: +372 5649 6124 http://www.opennodecloud.com |
|
From: <ope...@li...> - 2012-06-19 20:18:43
|
As OpenNode 6.0 RC1 has proven stable during these 2 months of production testing after its release - we are re-releasing it as 6.0 stable release. There are no changes to ISO installer since 6.0 RC1. All minor updates and fixes will be released through yum update. Regards, -- ---------------------------------------------- Andres Toomsalu, an...@op... Founder, OpenNode LLC |
|
From: <ope...@li...> - 2012-04-10 20:17:02
|
We have finished uploading OpenNode 6.0 rc1 ISO installer into Sourceforge.net project page - so grab it there: https://sourceforge.net/projects/opennode/ Also we have now separate opennode stable yum repo and opennode-test unstable development repo. If OpenNode 6.0 rc1 ISO installer works without major problems it will become as OpenNode 6.0 stable release. Ofcourse for earlier OpenNode 6.0 installations upgrade is provided by simply executing 'yum update'. Changelog: OpenNode 6.0 rc1 (build 608) release 10.04.2012 md5sum: 0dd9706a263fbd5ced6a0da4e72ca33e * Rebased OpenNode base system to CentOS 6.2 * Latest RHEL6 OpenVZ kernel (042stab053.5) with updated OpenVZ and KVM virtualization support and many bug fixes * Full VSwap type config file support by default * Initial kernel and vzctl (v3.1) support for ploop and vzconsole * OpenNode-TUI local management feature additions (openvz vm migration and management support) * Support for iptables firewall usage inside OpenVZ VM-s (including masquerading inside VM) * libvirt fixes regarding new vzctl and iptables firewalling * Support for new OpenNode Management Server v2 Team OpenNode :) |
|
From: <ope...@li...> - 2011-12-22 13:05:17
|
We have released a new generation OpenNode CLI Utility - from now on called as opennode-tui - which brings some new features for local management and paves the way for new OpenNode Management Server release. Also we have published a small howto about Shorewall firewall usage with OpenNode 6.x series servers. Meet new local management tool for OpenNode 6.x series - opennode-tui New features include: Support for multiple template repos Improved template downloads Support for multiple storage pools Support for simpler OpenVZ containers limits configuration - called VSwap - enabled by default vzctl as OpenVZ default cli console instead of limited virsh NB! Please note that opennode-tui is still under active development and will be matured by the time of OpenNode 6.0 stable release. For installing the opennode-tui please execute the following command on OpenNode 6.0 Beta1 release: yum update opennode Howto: Shorewall on OpenNode 6.x We provide now Shorewall packages through OpenNode 6.x yum repo and here is the recipe howto install and configure firewall on OpenNode 6.x series - until Shorewall packages will be installed by default. opennodecloud.com/documentation/howtos/firewall-support/ Merry Christmas, -- ---------------------------------------------- Andres Toomsalu, an...@op... Founder, OpenNode LLC Lille 4-205, Pärnu 80041, Estonia skype: main2frame phone: +372 6996 807 gsm: +372 5649 6124 http://www.opennodecloud.com |
|
From: <ope...@li...> - 2011-10-15 18:52:47
|
First beta of OpenNode 6.0 series ISO installer (build 604) has been released and is available for download through SourceForge.net OpenNode project site. We decided to start following RHEL version numbering for OpenNode releases - eg OpenNode 6.0 indicates RHEL6/CentOS6 based OpenNode series from now on. Whats new in OpenNode 6.0 beta1 (build 604): * rebased to CentOS6 * new RHEL6 vzkernel 2.6.32-042stab036.1 * new KVM and OpenVZ virtualization stacks * support for simpler OpenVZ VSwap resource limits (see openvz.livejournal.com/35628.html) New version of local management utility - which brings some new features - is still in the works and will probably make into second beta release of OpenNode 6.0. For downloading the ISO please go here: https://sourceforge.net/projects/opennode/files/OpenNode_6.0beta1/ -- ---------------------------------------------- Team OpenNode in...@op... |
|
From: <ope...@li...> - 2011-09-01 13:34:23
|
For interested testers there is a CentOS 6.0 to OpenNode 6.0 (beta) conversion script available. Here are the instructions: OpenNode 6.0 bootstrap from CentOS 6.0 --------------------------------------- * Install minimal default CentOS 6 system with http://ftp.estpak.ee/pub/centos/6.0/isos/x86_64/CentOS-6.0-x86_64-minimal.iso * Bootstrap to OpenNode 6.0 with centos6-to-opennode6.sh script yum install -y wget wget -q -O - http://opennode.activesys.org/download/centos6-to-opennode6.sh | bash Notes: Currently OpenNode 6.0 beta is a CentOS 6 base system with RHEL6 vzkernel providing RHEL6 KVM and OpenVZ stacks - OpenNode CLI Utility (OCU) is still the same as of OpenNode 1.1 - we hope to finish some new OCU features by official OpenNode 6.0 release. -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2011-07-07 15:19:42
|
There can be situations when using OpenNode ISO installer or doing networked PXE installs is not possible (for example in case of pre-installed dedicated server offerings) - therefor we have created an helper script in order to assist converting existing CentOS 5 installations into OpenNode compatible hosts. Please note that centos2opennode.sh script must be run as root user and it will perform the following tasks in your CentOS 5 system: updates system packages to latest versions installs opennode yum repo files pulls and installs all needed opennode related packages creates additional folder structure needed for opennode compability migrates eth0 device IP configuration into vmbr0 bridge device (eg sets up bridge networking for KVM and OpenVZ virtual machines) carries out additional system reconfiguration needed for opennode host compability (disabling SELinux, etc) For converting your CentOS 5 system to OpenNode please execute: wgetopennode.activesys.org/download/centos2opennode.sh chmod 750 centos2opennode.sh ./centos2opennode.sh wget opennode.activesys.org/download/centos2opennode.sh chmod 750 centos2opennode.sh ./centos2opennode.sh Cheers, The OpenNode Team in...@ac... |
|
From: <ope...@li...> - 2011-06-22 03:19:55
|
Stable version of OpenNode 1.1 ISO installer and hypervisor node is now available together with new and updated OpenVZ OVF templates library. OpenNode 1.1 stable release (build 38) is available as a ISO installer download or as a yum based upgrade to existing OpenNode installations. Changes since OpenNode 1.1 RC1: * Temporarely disabled opennode-repo rpm dependecy for opennode rpm - in order to enable system upgrades from older versions because of the file conflict between opennode-repo and older opennode rpm packages Notable OpenNode 1.1 changes: Upgraded kernel to ovzkernel-2.6.18-238.9.1.el5.028stab089.1 Updated KVM to kvm-83-224.asys.3.x86_64.rpm Updated vzctl to 3.0.27-1 Updated vzdump to 1.2-12 Rebased OpenNode base system to CentOS 5.6 Initial OVF templates support in OpenNode CLI Utility (both for KVM and OpenVZ) Updated and new (Fedora 14, OpenSUSE 11.2/11.3/11.4) OpenVZ OVF templates are available for download through local OpenNode CLI Utility Out-of-box OpenNode Management Server support Minimum disk size requirement for advanced autopartitioning has been reduced to 25GB. NB! OpenNode can be installed with disk sizes less than 25GB - but then manual partitioning might be needed or accepting a default and simple partitioning scheme with single root partition on top of LVM. OpenNode 1.1 stable release (build 38) is available as a ISO installer download or as a yum based upgrade to existing OpenNode installations. Changes since OpenNode 1.1 RC1: Temporarely disabled opennode-repo rpm dependecy for opennode rpm - in order to enable system upgrades from older versions because of the opennode yum repo file conflict between opennode-repo and older opennode rpm packages Notable OpenNode 1.1 changes since 1.0: Upgraded kernel to ovzkernel-2.6.18-238.9.1.el5.028stab089.1 Updated KVM to kvm-83-224.asys.3.x86_64.rpm Updated vzctl to 3.0.27-1 Updated vzdump to 1.2-12 Rebased OpenNode base system to CentOS 5.6 Initial OVF templates support in OpenNode CLI Utility (both for KVM and OpenVZ) Updated and new (Fedora 14, OpenSUSE 11.2/11.3/11.4) OpenVZ OVF templates are available for download through local OpenNode CLI Utility Out-of-box OpenNode Management Server support Minimum disk size requirement for advanced autopartitioning has been reduced to 25GB. NB! OpenNode can be installed with disk sizes less than 25GB - but then manual partitioning might be needed or accepting a default and simple partitioning scheme with single root partition on top of LVM. Please follow these upgrade instructions if upgrading from OpenNode 1.0 stable or 1.1 beta1 systems: #Stop all running VM-s - if any #Make sure you have opennode stable repo enabled in /etc/yum.repos.d/opennode.repo file cd /etc/pki/rpm-gpg/ wget http://opennode.activesys.org/CentOS/5/opennode/RPM-GPG-KEY-ActiveSys rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ cp -p /etc/yum.repos.d/opennode.repo /tmp/ yum update opennode cp -p /tmp/opennode.repo /etc/yum.repos.d/ yum install opennode-repo yum update ln -sf /opt/opennode/bin/opennode /usr/bin/opennode mkdir -p /storage/images mkdir -p /storage/iso mkdir -p /storage/templates/kvm/deploy mkdir -p /storage/templates/openvz/deploy reboot Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2011-03-09 23:36:08
|
We have done a backport of NEXT3 filesystem kernel module for RHEL 5 OpenVZ enabled kernel included in OpenNode - both next3 kernel module and patched (+ newer version of) e2fsprogs rpm packages are now available from opennode-test repo for testing. NEXT3(R) is a clone of the Ext3 filesystem with built-in support for snapshots. NEXT3 features Backward and forward compatible with Ext3 - converting from EXT3 to NEXT3 and back is easy and possible Snapshots use available file system disk space - no need for dedicated free disk blocks like LVM No upper limit on number or size of snapshots - no need for snapshot size pre-allocation like LVM Minimal performance overhead when snapshots exists For NEXT3 installation and usage please see this howto document: http://opennode.activesys.org/documentation/howtos/next3-snapshots/ -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2011-02-05 01:29:35
|
OpenNode Management Server provides a JSON-RPC API interface for third-party software/systems integration and possible WUI/GUI/CLI clients implementation. OMS API reference can be found here: opennode.activesys.org/documentation/api-documentation/ OpenNode Management Console eg "Funcman" is our reference client implementation using this JSON-RPC API. Other client implementations are possible and highly encouraged. Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2011-01-20 21:13:38
|
opennode-1.1-16 rpm is available from opennode-test repo containing mainly bugfixes - for details please see changelog below: Changes since opennode-1.1-15: bug when registering to OMS from the same node where OMS is running no cancel or back button in ovz template deploy dialogue when entering min/max values required directory structure creation and verification for opennode compliance opennode-1.1 beta rpm switches back to opennode stable repo - should not repleace user choice to use opennode-test repo no /storage/iso folder after opennode rpm install bug when registering to OMS from the same node where OMS is running no cancel or back button in ovz template deploy dialogue when entering min/max values required directory structure creation and verification for opennode compliance opennode-1.1 beta rpm switches back to opennode stable repo - should not repleace user choice to use opennode-test repo no /storage/iso folder after opennode rpm install For update please verify that you are using opennode-test repo and execute: yum update opennode -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2010-12-14 23:18:47
|
Im pleased to announce that first public (alpha1) preview release of OpenNode Management Server (OMS) is now available - its download and installation is provided through a local OpenNode CLI Utility (requires latest OpenNode-1.1 beta1 package). OMS alpha1 version is not yet ready for production use - but it also should not be destructive to your test environment :-) Please read and follow OpenNode Management Server Install Howto for deploy time instructions. OpenNode Management Server User Guide should provide you with the needed information in order to get you going. For community support please visit OpenNode Support Forum and use OpenNode public mailing lists. Commercial support options and OpenNode development services are provided by Active Systems LLC. OpenNode Management Server installation requirements: OMS host and client nodes must be updated to latest OpenNode 1.1 beta1 (opennode-1.1-15 rpm) For an alpha1 OMS VM test instance at least 1GB free memory and 10GB free disk space under /vz is needed for now NB! You should use only FQDN hostnames for OMS and OpenNode server hostnames and they must be resolvable For installing the latest opennnode 1.1 beta 1 rpm package please do the following: switch to opennode-test yum repository (enable opennode-test repo in /etc/yum.repos.d/opennode file and disable opennode repo) do yum upgrade opennode (which should pull latest opennode-1.1-15 or greater rpm from opennode-test repo) Known issues and limitations of OMS alpha1 release OMS Web Console is still pretty "funky" at the moment - might be slow on updates, no proper feedback to user during some operations (especially on hosts import procedures), random VM status changes between vmlist refreshes, etc. OMS Web Console SSH console pop-up window might open too fast - because of no ssh proxy console yet on other side producing a browser error - please just refresh the SSH console window and then SSH console loads properly We do not support OpenVZ veth networking management inside OMS Web Console yet - but OpenVZ VMs with veth networking are allowed (just do manual setup for veth) Currently we only support installing KVM VM-s from bootable ISO image with OMS Web Console - but you can try KVM VM templates functionality with local OpenNode-1.1 CLI Utility There seems to be a problem with some ISO installers other than Windows boot CD - when creating KVM VM from ISO No ISO image management yet - ISO images must be manually loaded into every OpenNode host under /storage/iso folder - if no such folder exists please create it manually No VM templates management through OMS Web Console yet - please use local OpenNode CLI Utility for VM templates management Currently KVM VM stop button issues KVM VM destroy command instead of more graceful (but also often non-working) shutdown - that is intentional While OpenVZ VM management seems to be fairly stable - KVM management features are not so throughly tested There are probably more issues - so be prepared :-) Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... CEO, Active Systems LLC |
|
From: <ope...@li...> - 2010-10-19 19:29:51
|
OpenNode 1.0 stable ISO installer image is available for download from OpenNode sourceforge project page and for existing installations upgrade is provided through yum update. Changelog: * Upgraded kernel to ovzkernel-2.6.18-194.17.1.el5.028stab070.7 * Updated KVM to kvm-83-164.asys.17.x86_64.rpm * Updated vzctl to 3.0.24.2-1 * Fixed KVM VNC server mouse issue with Windows VM-s Installation: For new installations please download OpenNode ISO installer image and burn it into cd. Boot server from OpenNode CD and follow on-screen instructions. Upgrading: For upgrading existing OpenNode installations simply execute (on OpenNode console): yum update Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2010-08-09 18:02:55
|
OpenNode 1.0 beta2 ISO installer image is available for download from OpenNode sourceforge project page and for existing installations upgrade is provided through yum update. Changelog: * Upgraded kernel to ovzkernel-2.6.18-194.8.1.el5 028stab070.2 * Updated KVM stack to kvm-83-164.asys.9.x86_64.rpm * Registrering OpenNode as FUNC client now works through opennode CLI utility * Updated OpenNode OpenVZ OS templates - download/update via opennode CLI utility * Small bugfixes and other package updates Installation: For new installations please download OpenNode ISO installer image and burn it into cd. Boot server from OpenNode CD and follow on-screen instructions. Upgrading: For upgrading existing OpenNode installations simply execute (on OpenNode console): yum update We are urging everyone interested to try it out and to give us as much feedback as possible - if no bigger problems are found with beta2 we are planning to release OpenNode 1.0 stable shortly - as OpenNode 1.1 beta1 is also preparing for a release during upcoming weeks - bringing some important new features. Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2010-07-29 00:40:35
|
Despite the silence we have been pretty busy with cooking the OpenNode Management Server and its web based management interface - FuncMan. But before we are going to release OpenNode Management Server preview its time for OpenNode 1.0 second beta release - which we hope will become later as OpenNode 1.0 stable release. OpenNode 1.0 beta2 is going to have a newest OpenVZ kernel with updated KVM stack and out-of-box support for virt-manager (for remote KVM VM management). Registering OpenNode host as a FUNC (Fedora Unified Network Controller) client via opennode cli utility will be also supported. Thou OpenNode 1.0 beta2 ISO release is probably going to be happen during next week - it is already possible to switch existing OpenNode 1.0 beta1 installations to opennode-test repository (in /etc/yum.repos.d/opennode.repo file just disable opennode repo and enable opennode-test repo) and then just do 'yum update' in order to upgrade into 1.0 beta2. Everything else should be fairly stable but there can be some KVM windows VM troubles left to figure out - so be warned! After we released OpenNode 1.0 beta1 in March (which has proven itself as quite stable release - also in KVM stack sense) our efforts have been concentrated on developing OpenNode 1.1 and OpenNode Management Server code - in order to provide remote management options for OpenNode hosts. I'm pleased to say that most of the coding is done and currently OpenNode 1.1 is under testing/finalizing phase together with Management Server RPC API. OpenNode 1.1 release will contain some remarkable new features - such as unified template format based on OVF (Open Virtualization Format) standard for both OpenVZ and KVM templates. OpenNode 1.1 can create these templates from existing VMs (both KVM and OpenVZ), can download and update prepackaged templates from official OpenNode template library site and most importantly - can deploy both KVM and OpenVZ templates into VMs together with creating VM configurations and changing VM resource limits on-the-fly. OpenNode VM templates will contain info about target VM minimal resource requirements - like min CPU cores, min memory, etc. - during VM creation process user can specify resource values overriding (and exceeding) minimal requirements mandated by template. If Im not mistaken OpenNode 1.1 will be the first virtualization solution to date to provide full KVM VM templating (VM config + VM filesystem on LVM or file based block device) and deploying OpenVZ templates together with VM configuration generation on-the-fly (just input how much ram, cpu and disk you want for VM - let the opennode do the rest). OpenNode 1.1 release will be accompanied with OpenNode Management Server first public release - so OpenNode servers will get basic remote (and central) management option. OpenNode Management Server provides CLI interface through simple func commands and for full functionality there is a RPC API server - which acts as a upcoming FuncMan web based management interface backend - or one can develop or integrate OpenNode Management Server RPC API into its own custom set of management tools or management environments. We will publish Management Server RPC API together with Management Server release. For estimated release dates and roadmap updates please visit: opennode.activesys.org/roadmap/ And if all goes well we'll post some first FuncMan WUI screenshots soon... -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: <ope...@li...> - 2010-03-01 22:26:52
|
OpenNode 1.0 beta ISO installer image is available for download from OpenNode sourceforge project page and for existing installations upgrade is provided through yum update. Changelog: * Upgraded kernel to ovzkernel-2.6.18-164.11.1.el5.028stab068.3 * Updated KVM to 83-105.asys.22.4 * Relocated OpenNode specific packages to opennode yum repository * Changed OpenNode OpenVZ templates download URL * Made some changes to opennode rpm in order to provide yum upgrades for existing OpenNode installations Installation: For new installations please download OpenNode ISO installer image and burn it into cd. Boot server from OpenNode CD and follow on-screen instructions. Upgrading: For upgrading existing OpenNode installations simply execute (on OpenNode console): yum update -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
