summaryrefslogtreecommitdiff
path: root/INSTALL.XenServer
Commit message (Collapse)AuthorAgeFilesLines
* datapath: omit _mod from module namesChris Wright2012-03-091-1/+1
| | | | | | | | | | | | | | | This renames the datapath modules: openvswitch_mod -> openvswitch brcompat_mod -> brcompat The first makes the module name consistent with upstream, and the latter is just for internal consistency. This makes tools, and documentation refer to a common module name regardless if it's coming from upstream linux or built from datapath/ as part of a local build. Signed-off-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Jesse Gross <jesse@nicira.com>
* xenserver: Simplify RPM build instructions.Ben Pfaff2012-02-031-18/+35
| | | | | | I got tired of trying to follow them properly myself. Signed-off-by: Ben Pfaff <blp@nicira.com>
* INSTALL.XenServer: spelling fix.Ben Pfaff2012-01-241-1/+1
| | | | Signed-off-by: Ben Pfaff <blp@nicira.com>
* INSTALL.XenServer: Update instructions.Ben Pfaff2011-12-011-9/+5
| | | | | | | The instructions hadn't been properly updated to match current XenServer releases. Reported-by: Ramana Reddy <gtvrreddy@gmail.com>
* xenserver: modify module spec fileSajjad Lateef2011-05-161-7/+23
| | | | | | | | | | | | | | | | Based on feedback from Citrix about building for multiple kernels, the spec file has been modified to take three arguments on the command line: kernel_name, kernel_version and kernel_flavor. The kernel_flavor is either xen or kdump. The kernel_name is the Name value embedded in the kernel rpm and the kernel_version is Version-Release values embedded in the kernel rpm. The xen_version is calculated. The INSTALL document has been updated to reflect these changes. Signed-off-by: Sajjad Lateef <slateef@nicira.com> (cherry picked from commit b11e4aa7e92854612a4d139b8a620d036a5d41a2)
* INSTALL.XenServer: Document Open vSwitch boot process on XenServer.Ben Pfaff2011-05-101-0/+68
| | | | Inspired by a conversation with David Erickson <derickso@stanford.edu>.
* xenserver: Split kernel/userspace into separate RPMs for supplemental packs.Andrew Evans2011-02-181-12/+15
| | | | | | | | | | | | | | | | | | | XenServer has the concept of a "supplemental pack", which is just a collection of RPMs rolled into an ISO image for installation as a unit, either during XenServer installation or later as an update. The script used to build supplemental packs requires that a single RPM not mix kernel and userspace components. It also enforces a particular naming scheme for kernel module RPMs. This commit modifies the OVS RPM spec file to create separate RPMs in accordance with these conventions. In an attempt to ensure that the userspace and kernel module packages are both present and compatible, the kernel package provides a fictitious capability, openvswitch_mod.ko.0, and the userspace package requires that capability. If a future change breaks backward compatibility between userspace and kernel, we'll increment the numeric suffix, preventing mismatched installs. Reviewed by Ben Pfaff.
* xenserver: Merge upstream changes and drop pre-5.6.100 support.Andrew Evans2011-02-111-3/+2
| | | | | | | | | | | | | | | Citrix have made modifications to the various interface configuration scripts that OVS replaces, so at present those modifications are lost when OVS is installed on e.g. XenServer 5.6.100. This commit applies those changes while preserving OVS-specific modifications that have been made in the interim. One major change introduced by these updates is the removal of support for XenServer releases prior to 5.6.100. This commit also updates the OVS-supplied xen-bugtool in similar fashion. We will soon remove xen-bugtool from OVS altogether and move the added OVS functionality to an XML extension as described in the Supplemental Pack DDK guide.
* INSTALL.XenServer: Fix directory where RPMs end up.Ben Pfaff2010-12-291-2/+2
| | | | | | | We can be specific about i386 here since that's the only architecture that XenServer supports. Reported-by: Bryan Osoro <bosoro@nicira.com>
* Update INSTALL.XenServer to indicate that 5.6.0 is supportedJun Nakajima2010-06-221-1/+1
| | | | | | Open vSwitch is compatible with XenServer 5.6.0, so indicate that in INSTALL.XenServer. Remove the reference to 5.5.900, since that was just a pre-release version of 5.6.0.
* Cleanup default file locations and XenServer packagingJustin Pettit2010-03-261-7/+7
| | | | | | | | | | | | | | | | | | | | | | This commit cleans up the locations of a number of files and directories used. These include: - Config file lives in /etc/openvswitch/conf.db - Logs go into /var/log/openvswitch - ovsdb-server socket is /var/run/openvswitch/db.sock - Schema goes into /usr/share/openvswitch/vswitch.ovsschema - PID files go in /var/run/openvswitch For XenServer, these additional changes are made: - Cores go in /var/xen/openvswitch - OVS binaries run in /var/xen/openvswitch In addition, it attempts to cleanup the XenServer packaging. This includes referring to the project as "openvswitch" as opposed to the somewhat presumptuous "vswitch". Note: Changes to the Debian packaging will be forthcoming.
* xenserver: Add XenServer 5.5.0 updates 1 and 2 to supported versions.Jesse Gross2010-02-011-2/+2
| | | | | | Add the file hashes for updates 1 and 2 (the scripts we care about are the same) to the list of supported versions to prevent a warning message on install.
* xenserver: Avoid "rpm -i" warnings on XenServer 5.5.900.Ben Pfaff2009-09-081-1/+4
| | | | | Open vSwitch installs successfully on XenServer 5.5.900 but it prints some worrying messages during the process. This commit fixes them.
* Adjust Open vSwitch mailing lists to reflect realityJustin Pettit2009-06-251-1/+1
| | | | | | | | We've gone through a couple of iterations for names of these mailing lists. Currently, there are three: announce, discuss, and git. There are aliases that point "bugs" and "dev" to the "discuss" mailing list. This commit drops the "ovs-" prefix to mailing lists, since we're not using them.
* Update documentation.Ben Pfaff2009-06-091-0/+70