Thanks. I pushed this change to master, branch-1.3, branch-1.4.
On Thu, Dec 01, 2011 at 11:29:37AM +0530, Ramana Reddy wrote:
> Hi Ben,
>
> Now the instructions are more clear and valid.
> Thanks,
> Ramana.
>
> On Thu, Dec 1, 2011 at 2:24 AM, Ben Pfaff <b...@nicira.com> wrote:
>
> > Thank you for the report. I've sent out a patch (you are CCed) that
> > updates the instructions. Can you check that the instructions look OK
> > to you now?
> >
> > Thanks,
> >
> > Ben.
> >
> > On Sun, Nov 06, 2011 at 12:17:42PM +0530, Ramana Reddy wrote:
> > > The new OVS 1.1.1 and later require at least Xenserver 5.6 Fp1 and above.
> > > And the installation procedure mentioned in OVS 1.0.0 and previous is
> > > slightly diffrent from OVS 1.1.1 and above.
> > >
> > > The instructions mentioned in INSTALL.XENSERVER ( for OVS-1.1.1) are:
> > >
> > > **
> > > VERSION = <Open vSwitch version>
> > > <openvswitch version> is the version number that appears in the
> > > name of the Open vSwitch tarball, e.g. 0.90.0.
> > >
> > > *Observation:* This is clear.
> > >
> > > KERNEL_NAME=<Xen Kernel name>
> > > <Xen Kernel name> is the name of the Xen Kernel,
> > > e.g. kernel-xen or kernel-NAME-xen. By convention, the name
> > > starts with "kernel-" and ends with "-xen".
> > > This can be obtained by executing
> > > 'rpm -q --queryformat "%{Name}" kernel.*xen'
> > > with the "kernel-" stripped out using sed 's/kernel-//'
> > > e.g. kernel-NAME-xen => NAME-xen
> > >
> > > *Observation:* This is not clear, and it seems that no kernel in
> > Xenserver
> > > starts with kernel-xen or kernel-NAME-xen, and the command 'rpm -q
> > > --queryformat "%{Name}" kernel.*xen' is not giving proper
> > > output. The instructions may work for xen. I just mentioned "xen" after
> > > verifying the spec file, and it was
> > > working fine.
> > >
> > > KERNEL_VERSION=<Xen Kernel version>
> > > KERNEL_FLAVOR=<Xen Kernel flavor(suffix) >
> > >
> > > *Observation:* These two are clear.
> > >
> > > I will recheck tomorrow with Xenserver 6.0 beta release with new
> > OVS-1.2.2
> > > and let you know more if the ordinary
> > > procedure wouldn't work.
> > >
> > > Thanks,
> > > Ramana Reddy.
> > >
> > >
> > > On Sun, Nov 6, 2011 at 11:39 AM, Justin Pettit <jpet...@nicira.com>
> > wrote:
> > >
> > > > What kind of problems did you run into on FP1/SP2? What do you mean
> > that
> > > > it would not work for new OVS? We'd like to improve the instructions
> > if
> > > > you have suggestions.
> > > >
> > > > Thanks,
> > > >
> > > > --Justin
> > > >
> > > >
> > > > On Nov 5, 2011, at 11:00 PM, Ramana Reddy wrote:
> > > >
> > > > > I have installed OVS-1.1.1 on XenServer 5.6 Fp1, and the
> > installation
> > > > done successfully. The installation parameters settings are slightly
> > > > different on XenServer 5.6 FP1 /SP2 for new OVS, where as the
> > installation
> > > > > procedure is straight forward on XenServer 5.6 ( and it would not
> > work
> > > > for new OVS).
> > > > >
> > > > >
> > > > > On Sat, Nov 5, 2011 at 10:16 PM, Justin Pettit <jpet...@nicira.com>
> > > > wrote:
> > > > > On Nov 5, 2011, at 7:49 AM, ?????? wrote:
> > > > >
> > > > > > so, would you please give me a detailed document of how to install
> > ovs
> > > > with openflow on xenserver?
> > > > >
> > > > >
> > > > > As Ben mentioned, there's no separate OpenFlow component. I'd
> > recommend
> > > > looking at the ovs-vsctl and ovs-ofctl man pages to read about
> > configuring
> > > > OpenFlow.
> > > > >
> > > > > --Justin
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > discuss mailing list
> > > > > discuss@openvswitch.org
> > > > > http://openvswitch.org/mailman/listinfo/discuss
> > > > >
> > > >
> > > >
> >
> > > _______________________________________________
> > > discuss mailing list
> > > discuss@openvswitch.org
> > > http://openvswitch.org/mailman/listinfo/discuss
> >
> >
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
