<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Do you have your vswitch properly configured on your hyper-v host? </div>
<div><br>
</div>
<div>Are you using vlans? </div>
<div><br>
</div>
<div>P</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:75%; color:#575757">Sent from my Verizon Wireless 4G LTE Smartphone</div>
</div>
<br>
<br>
<br>
-------- Original message --------<br>
From: Bruno Oliveira <brunnop.oliveira@gmail.com> <br>
Date: 06/06/2013 3:55 PM (GMT-05:00) <br>
To: Peter Pouliot <ppouliot@microsoft.com> <br>
Cc: Steve Heistand <steve.heistand@nasa.gov>,OpenStack <openstack@lists.launchpad.net>
<br>
Subject: Re: [Openstack] [HyperV][Quantum] Quantum dhcp agent not working for Hyper-V
<br>
<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">@Steve: yeah, the MAC I see in the DHCP REQUEST is the same that<br>
shows up in the DHCP Server (quantum-server)<br>
<br>
<br>
@Peter: Hmm, should I enable anything in special in 2012, that I do<br>
not have to in 2008 R2 ?<br>
Because apparently I'm still having the same issue... (I just setup<br>
another host with Hyper-V 2012)<br>
<br>
Thank you<br>
<br>
--<br>
<br>
Bruno Oliveira<br>
Developer, Software Engineer<br>
<br>
<br>
<br>
<br>
<br>
On Wed, Jun 5, 2013 at 10:46 PM, Peter Pouliot <ppouliot@microsoft.com> wrote:<br>
> First off you should be using hyper-v from 2012 server. 2008 only supports<br>
> flat networking as of the last time I used it. All active development is<br>
> geared towards 2012 hyper-v. Functionality for is minimal for 2008 which<br>
> is also in the wmiv1 namespace. The legacy/original wmiv1 is basically<br>
> being replaced by wmiv2 for Havana.<br>
><br>
> Try hyper-v server 2012, we give it away for free.<br>
><br>
> And use that instead of 2008 hyper-v. You will have better results and 90%<br>
> more functionality.<br>
><br>
> P<br>
><br>
><br>
><br>
><br>
> Sent from my Verizon Wireless 4G LTE Smartphone<br>
><br>
><br>
><br>
> -------- Original message --------<br>
> From: Steve Heistand <steve.heistand@nasa.gov><br>
> Date: 06/05/2013 7:08 PM (GMT-05:00)<br>
> To: Bruno Oliveira <brunnop.oliveira@gmail.com><br>
> Cc: OpenStack <openstack@lists.launchpad.net><br>
> Subject: Re: [Openstack] [HyperV][Quantum] Quantum dhcp agent not working<br>
> for Hyper-V<br>
><br>
><br>
> is the MAC addr coming from the hyper-v on the dhcp request the same one the<br>
> dhcp-agent is<br>
> expecting?<br>
><br>
> s<br>
><br>
><br>
> On 06/05/2013 03:23 PM, Bruno Oliveira wrote:<br>
>> Hello all,<br>
>><br>
>> Guys, there's something regarding quantum that we've been hitting our<br>
>> heads<br>
>> against a wall for a few weeks, but can't figure out. Can you please<br>
>> take a look?<br>
>><br>
>> Here's the scenario:<br>
>><br>
>> We currently have a single-node devstack build, running nova (compute),<br>
>> glance,<br>
>> quantum (with OpenVSwitch), swift and cinder -- besides keystone and<br>
>> ceilometer.<br>
>><br>
>> On that very same machine, our kvm hypervisor is running. Everything<br>
>> works like a charm with it: dhcp, magic_ip (169.254.169.254), reaching<br>
>> in/outside networks, etc.<br>
>><br>
>><br>
>> Now for the issue: there's another host running hyper-v 2008 r2, and on<br>
>> top of that, we got Cloudbase's (cloudbase.it) Compute Driver for Hyper-V.<br>
>> That way, we're successfully being able to create VMs for it (Hyper-V),<br>
>> BUT...<br>
>><br>
>> Even though there's a virtual switch in there (hyper-v), the network for<br>
>> the<br>
>> instances are not working -> the instances are not being assigned with an<br>
>> IP from quantum-dhcp UNLESS I use the FLAT NETWORK model to assign<br>
>> a public ip for each of them. So...<br>
>><br>
>> 1. Is there a must to have ANOTHER quantum-server just for hyper-v nodes<br>
>> taking that I do not want to use Flat Network ?<br>
>> (by another, I mean one besides the working one I have for KVM)<br>
>><br>
>> 2. In our case, we're intending to have NAT IPs for each of the instance<br>
>> we<br>
>> have running on hyper-v, not public_ips directly assigned to them, is<br>
>> it possible?<br>
>><br>
>> After all the testing and research we did, we concluded that we CAN<br>
>> see the DHCP broadcast coming from hyper-v (via tcpdump'ing on<br>
>> any interface that is on the same subnet) but the DHCP response/reply<br>
>> is not working.<br>
>><br>
>> Note: "$quantum agent-list" DOES list the quantum-agent from kvm<br>
>> but not from hyper-v<br>
>><br>
>> Does anyone have any guesses or suggestions of what we could<br>
>> possibly try ?<br>
>><br>
>><br>
>> Thank you a lot<br>
>><br>
>> --<br>
>><br>
>> Bruno Oliveira<br>
>> Developer, Software Engineer<br>
>><br>
>> _______________________________________________<br>
>> Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
>> Post to : openstack@lists.launchpad.net<br>
>> Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
>> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
>><br>
><br>
> --<br>
> ************************************************************************<br>
> Steve Heistand NASA Ames Research Center<br>
> SciCon Group Mail Stop 258-6<br>
> steve.heistand@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000<br>
> ************************************************************************<br>
> "Any opinions expressed are those of our alien overlords, not my own."<br>
><br>
> # For Remedy #<br>
> #Action: Resolve #<br>
> #Resolution: Resolved #<br>
> #Reason: No Further Action Required #<br>
> #Tier1: User Code #<br>
> #Tier2: Other #<br>
> #Tier3: Assistance #<br>
> #Notification: None #<br>
><br>
><br>
</div>
</span></font>
</body>
</html>