l at that point.
Since Hyper-V is limited to x64, the only use case for a x86 build is for a
32bit client OS build where a user wants to install the CLI tools only.
Given how limited this use case is, I'd go with a single x64 build.
> Thanks,
> Eitan
>
> -Original Mess
tan Eliahu
> Sent: Sunday, March 15, 2015 6:30 PM
> To: Alessandro Pilotti
> Cc: dev@openvswitch.org
> Subject: Re: [ovs-dev] OVS Windows MSI installer
>
>
>
> Alessandro,
>
> Yes, no problem of having the installer separate. But, I am confused as I
> see t
nding patch on this
topic AFAIK).
Here is where the driver is uninstalled:
https://github.com/cloudbase/ovs-windows-installer/blob/master/ovs-windows-installer/Product.wxs#L48-L49
Alessandro
> Thank you!
> Eitan
>
> -Original Message-
> From: dev [mailto:dev-boun...
> On 16 Mar 2015, at 02:41, Ben Pfaff wrote:
>
> On Mon, Mar 16, 2015 at 12:33:09AM +, Alessandro Pilotti wrote:
>> As discussed on IRC, here's the Windows MSI installer project that we’d like
>> to
>> submit for upstream inclusion:
>>
>> https:
Hi guys,
As discussed on IRC, here's the Windows MSI installer project that we’d like to
submit for upstream inclusion:
https://github.com/cloudbase/ovs-windows-installer
The included README.rst provides information on how to generate the MSI and
I’ll also be happy to answer any question and rev
Thanks Sam,
I openend an issue on github for this one:
https://github.com/openvswitch/ovs-issues/issues/2
Alessandro
On 02 Aug 2014, at 19:15, Eitan Eliahu wrote:
> Hi Samuel,
> You are correct and we are well aware of this issue, in fact this issue was
> in our to do list for a long tim
Hi Justin,
Can you please give me and Alin write access?
I have a few issues to add.
Thanks,
Alessandro
On 01 Aug 2014, at 03:17, Justin Pettit wrote:
> Github does not support issue-only permissions for projects. Since most of
> the people involved in the port to Hyper-V are relatively n
with the INS was when we changed the
> driver GUID. This one should go smoothly :-)
> Eitan
>
> -Original Message-
> From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Justin Pettit
> Sent: Wednesday, July 30, 2014 2:08 PM
> To: Nithin Raju; Alessandro Pi
Hi guys,
One small nit:
Being this a community effort, can we rename the kernel extension from "VMWare
OVS extension" to "Open vSwitch extension" or just "openvswitch"? The same
applies to the vendor name.
We also suggested a similar "neutral" approach in our proposal. :-)
Thanks,
Alessandro
Hi Nithin,
I'd also add at least:
1) Design for mapping hyper-v ports to OVS ports
2) CI testing plans
3) Roadmap
Thanks,
Alessandro
On 29.07.2014, at 05:01, "Nithin Raju" wrote:
> 10.00 AM Pacific - Sounds good to me.
>
> hi Alessandro,
> We'll be meeting tomorrow. In the light of that
Hi Saurabh,
On 26 Jul 2014, at 03:32, Saurabh Shah wrote:
> Hi Alessandro,
>
>> Hi Saurabh,
>>
>> I¹d suggest that before doing a full review of the kernel driver we need
>> to have:
>>
>> * Userspace Netlink interface support (which means that patches 1 and 2
>> in this
>> set can be skipped
Hi Ben,
On 26 Jul 2014, at 01:42, Ben Pfaff wrote:
> On Fri, Jul 25, 2014 at 10:40:41PM +, Saurabh Shah wrote:
>>>
>>> On 26 Jul 2014, at 00:35, Ben Pfaff wrote:
>>>
On Thu, Jul 24, 2014 at 05:03:33PM -0700, Ben Pfaff wrote:
> Here is what I want to do:
>
> * Apply the
On 26 Jul 2014, at 00:35, Ben Pfaff wrote:
> On Thu, Jul 24, 2014 at 05:03:33PM -0700, Ben Pfaff wrote:
>> Here is what I want to do:
>>
>>* Apply the next version of Alin's series to support Netlink
>> userspace for Windows (as long as it doesn't break other
>> platforms) to mas
Hi Saurabh,
I’d suggest that before doing a full review of the kernel driver we need to
have:
* Userspace Netlink interface support (which means that patches 1 and 2 in this
set can be skipped)
* Kernel Netlink interface support (not provided by patch 3)
* Support for multiple datapaths and vs
Hi Eitan,
On 25 Jul 2014, at 19:19, Eitan Eliahu wrote:
>
> Hi Alessandro,
> I had some initial thoughts about jumpstarting the integration. Obviously,
> we need to sort out the user/kernel mode interface before we could have a
> working solution to start with.
> I would like to suggest that
d upcalls.
Definitely. What about scheduling a weekly IRC meeting to discuss this and
other topics?
>
> We are looking forward to working with you and your team.
Same here!
Thanks,
Alessandro
> Thank you,
> Eitan
>
>
>
> -Original Message-
> From: Ales
Hi Saurabh,
On 25 Jul 2014, at 03:52, Saurabh Shah wrote:
>
>
>> After thinking about the two Hyper-V ports of Open vSwitch, I have a
>> proposal to make progress on upstreaming.
>>
>> After reviewing code, following the on-list discussions, and
>> discussing both implementations with various
Hi Ben,
Currently both the Cloudbase and VMWare implementations initially proposed to
the ML need non trivial amounts of rework before being submitted.
On the Cloudbase side we already addressed most of the points that you noted
and we are about to submit the new patches, but that is not the topic
Hi Ben,
On 22 Jul 2014, at 20:10, Ben Pfaff wrote:
> After some pondering, I've concluded that the initial Windows datapath
> should use Netlink for userspace-kernel datapath communication,
> primarily because Netlink is extensible in a forward- and
> backward-compatible fashion. That is, as we
Hi Guru,
> On 11.07.2014, at 23:06, "Gurucharan Shetty" wrote:
>
> Hello Alin, Alessandro,
> I see that you guys at Cloudbase have created an installer for Open
> vSwitch. Is it something you created as an one time effort? Or is it a
> script and one can create a new installer by running a simp
"Ben Pfaff" wrote:
>
>> On Wed, Jun 25, 2014 at 5:04 PM, Ben Pfaff wrote:
>> On Tue, Jun 10, 2014 at 2:06 PM, Alessandro Pilotti
>> wrote:
>>> https://github.com/cloudbase/openvswitch-hyperv
>>> https://github.com/cloudbase/openvswitch-hyperv-kernel
>
On 24.06.2014, at 03:55, "Justin Pettit"
mailto:jpet...@nicira.com>> wrote:
On Sun, Jun 22, 2014 at 5:42 PM, Alessandro Pilotti
mailto:apilo...@cloudbasesolutions.com>> wrote:
In addition to the code repositories made previously available, here’s a wiki
document desc
Hi Saurabh,
Thanks for posting these patches!
We looked at the code in the last two days, running various tests and did
comparisons with our porting. We tried to be as unbiased as possible in
the review, with the goal of making the best out of both codebases and not a
“us” vs “them” match. :)
Fo
panics (Windows blue screens), OS freezes and critical
security issues.
Thanks,
Alessandro
On 11 Jun 2014, at 00:06, Alessandro Pilotti
mailto:apilo...@cloudbasesolutions.com>> wrote:
Hi everyone,
We recently announced the availability of our porting of Open vSwitch to
Microsoft Hyper-V:
Hi everyone,
We recently announced the availability of our porting of Open vSwitch to
Microsoft Hyper-V:
http://www.cloudbase.it/open-vswitch-on-hyper-v/
The code for both the OVS userspace tools and the Hyper-V kernel extension is
available as open source (Apache 2) and we’d be very happy to
s of additional advantages including a web site that eases
up the review process providing visual patchset diffs, comments on the code
lines, etc.
>> On Tue, Nov 26, 2013 at 01:55:32AM +, Alessandro Pilotti wrote:
>> Of course I do. :-)
>>
>> A CI gate might be very hel
lize that no one else is going to update them, right?
>
>> On Tue, Nov 26, 2013 at 12:03:02AM +, Alessandro Pilotti wrote:
>> What if we simply add a folder with the Visual Studio build files to begin
>> with?
>>
>>> On 26/nov/2013, at 01:29, "Ben P
On Mon, Nov 25, 2013 at 11:23:37PM +, Alessandro Pilotti wrote:
>> Visual Studio is the "de facto" IDE for Windows development. It provides all
>> the features you'd expect from a modern environment (integrated debugger,
>> refactoring tools, Git integration, synt
ne without them, so
>>> if "make" can work on Windows then why is the result "basically
>>> useless for any practical development purpose"?
>>>
>>>> On Mon, Nov 25, 2013 at 04:50:40PM -0500, Ethan Jackson wrote:
>>>> My unde
Hi guys,
We did some testing with autoconf / automake on Windows. Makefiles are getting
generated correctly although we cannot obviously verify the result with a full
build since we didn’t port all the patches to the master branch yet.
There’s anyway a huge limitation: it does not generate a Vis
+1
> On 20.11.2013, at 00:17, "Ethan Jackson" wrote:
>
> Ben's the authority on this, but FWIW a macro sounds fine to me.
> We've already got PRI_U32 etc, adding a PRI_ZU seems reasonable.
>
> Ethan
>
>
>
> On Tue, Nov 19, 2013 at 1:57 PM,
Talking about %zu, we solved it with a brutal macro. Do you have any suggestion
for a better approach?
On 19 Nov 2013, at 18:51 , Gurucharan Shetty wrote:
> On Tue, Nov 19, 2013 at 8:37 AM, Ben Pfaff wrote:
>> On Tue, Nov 19, 2013 at 12:22:40PM +, Alessandro Pilotti wrote
Hi guys,
My company, Cloudbase Solutions, as part of our effort in integrating OpenStack
with Windows and Hyper-V is currently involved in porting Open vSwitch to
Windows.
We are currently revieweing the first Windows patches that have been posted to
this ML and we will gladly start to contrib
33 matches
Mail list logo
