<div dir="ltr">Hi Matt,<div><br></div><div>Regarding your answer the driver seems to handle VLAN mode but I still don't see how it can without a specific neutron plugin. From what I see from the code there is no any call for IVM "mkdev -vlan" and "-tagid" parameters. </div>

<div><br></div><div>Should I extend it myself or am I missing something ?</div><div><br></div><div>Regards,</div><div><br></div><div>Florian CHAZAL<br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br>

<br><div class="gmail_quote">On 21 March 2014 18:52, Matt Riedemann <span dir="ltr"><<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=""><br>
<br>
On 3/21/2014 6:45 PM, Florian Chazal wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Hi All,<br>
<br>
Better late that never:<br>
<br>
Since few weeks we are testing IBM Power System R2 server and we were<br>
evaluating the capability to go on a larger scale.  We are lacking of<br>
information regarding PowerKVM status and PowerVC so we began to try<br>
Havana + powerVM:<br>
The launch of a VM went well (except an issue with glance which does not<br>
gzip the image ... troubleshoot in process) but how does it works<br>
regarding the network ? What type of network configuration it has been<br>
tested with ?<br>
<br>
Thank you in advance,<br>
<br>
Florian CHAZAL<br>
<br>
<br>
On 25 November 2013 08:26, Matt Riedemann <<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a><br></div><div class="">
<mailto:<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.<u></u>ibm.com</a>>> wrote:<br>
<br>
<br>
<br>
    On Monday, November 25, 2013 10:14:00 AM, Anne Gentle wrote:<br>
<br>
<br>
<br>
<br>
        On Mon, Nov 25, 2013 at 5:10 AM, Thierry Carrez<br>
        <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a> <mailto:<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>><br></div>
        <mailto:<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a> <mailto:<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>><u></u>>__><div><div class="h5">

<br>
        wrote:<br>
<br>
             Chuck Short wrote:<br>
             > On Fri, Nov 22, 2013 at 4:45 PM, Michael Still<br>
             <<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a> <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>><br>
        <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a> <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>>><br>
             > <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a> <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>><br>
        <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a> <mailto:<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>>>>> wrote:<br>
             ><br>
             >>     So, a few questions...<br>
             >><br>
             >>      - If there are no users shall we remove it from<br>
        Havana and<br>
             Grizzly as<br>
             >>     well, or does that violate our stability principles<br>
        too much?<br>
             ><br>
             ><br>
             > Speaking with my stable maintainers hat on I would personally<br>
             NACK this<br>
             > since<br>
             > it doesnt meet the standard of a stable maintenance<br>
        requirement,<br>
             imho.<br>
<br>
             It definitely doesn't meet our stable maintenance rules. We<br>
        want<br>
             people<br>
             to be able to safely upgrade to the latest stable/* when<br>
        they are<br>
             users<br>
             of the release. We don't add new features, removing them<br>
        would be even<br>
             worse.<br>
<br>
             >>      - If we don't remove the code from stable, what about<br>
             removing all<br>
             >>     references from the stable docs and putting in a warning<br>
             saying that<br>
             >>     powervm is a dead end instead? I want to minimise<br>
        confusion<br>
             on the<br>
             >>     part of people deploying stable releases.<br>
             ><br>
             > This would be okay in my opinion.<br>
<br>
             At the very minimum I would add the "dead-end" comment to<br>
        the Havana<br>
             release notes. If Anne is fine by it, it could also be<br>
        added to the<br>
             stable/havana version of the docs.<br>
<br>
<br>
        PowerVM was mostly documented in developer docs in the nova repo. It<br>
        also has entries in the Configuration Reference in the nova.conf<br>
        options tables from our autodoc process. Those will just stay in the<br>
        stable/havana repo, but I'm okay with backporting a note to<br>
        stable/havana with a clear message as to the driver's fate. We also<br>
        have a mention of PowerVM in stable/grizzly where we could also<br>
        place<br>
        a note. Release notes are a good place for this as well, thanks<br>
        Russell.<br>
<br>
        Tracking with<br></div></div>
        <a href="https://bugs.launchpad.net/__openstack-manuals/+bug/1254780" target="_blank">https://bugs.launchpad.net/__<u></u>openstack-manuals/+bug/1254780</a><div class=""><br>
        <<a href="https://bugs.launchpad.net/openstack-manuals/+bug/1254780" target="_blank">https://bugs.launchpad.net/<u></u>openstack-manuals/+bug/1254780</a><u></u>> --<br>
        feel free<br>
        to add the nova project as well to ensure the docs in the nova repo<br>
        are removed.<br>
<br>
        I do want to point out that we don't have adequate documentation of<br>
        other drivers, like Hyper-V and Xen, just want to make sure you all<br>
        know there are gaps and documentation isn't the indicator of<br>
        "acceptance" of a hypervisor driver.<br>
        Thanks -<br>
        Anne<br>
<br>
             --<br>
             Thierry Carrez (ttx)<br>
<br></div>
             ______________________________<u></u>___________________<br>
             Mailing list:<br>
        <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a>><div class="">

<br>
             Post to     : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
        <mailto:<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.<u></u>openstack.org</a>><br></div>
             <mailto:<a href="mailto:openstack@lists." target="_blank">openstack@lists.</a>__<a href="http://openstack.org" target="_blank">open<u></u>stack.org</a><br>
        <mailto:<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.<u></u>openstack.org</a>>><br>
             Unsubscribe :<br>
        <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a>><br>


<br>
<br>
<br>
<br>
<br>
        ______________________________<u></u>___________________<br>
        Mailing list:<br>
        <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a>><div class="">

<br>
        Post to     : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
        <mailto:<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.<u></u>openstack.org</a>><br>
        Unsubscribe :<br></div>
        <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a>><div class="">

<br>
<br>
<br>
    Also to relay what was discussed in nova IRC this morning, this<br>
    topic is on the release meeting agenda for tomorrow:<br>
<br></div>
    <a href="https://wiki.openstack.org/__wiki/Meetings/ProjectMeeting#__Agenda_for_next_meeting" target="_blank">https://wiki.openstack.org/__<u></u>wiki/Meetings/ProjectMeeting#_<u></u>_Agenda_for_next_meeting</a><div class="">

<br>
    <<a href="https://wiki.openstack.org/wiki/Meetings/ProjectMeeting#Agenda_for_next_meeting" target="_blank">https://wiki.openstack.org/<u></u>wiki/Meetings/ProjectMeeting#<u></u>Agenda_for_next_meeting</a>><br>
<br>
    --<br>
<br>
    Thanks,<br>
<br>
    Matt Riedemann<br>
<br>
<br>
<br></div>
    ______________________________<u></u>___________________<br>
    Mailing list:<br>
    <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack</a><div class=""><br>
    <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a>><br>
    Post to     : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
    <mailto:<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.<u></u>openstack.org</a>><br>
    Unsubscribe :<br></div>
    <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack</a><div class=""><br>
    <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a>><br>
<br>
<br>
<br>
<br>
--<br>
Florian Chazal<br>
</div></blockquote>
<br>
Hi Florian,<br>
<br>
Some details on what testing we did internally with running Tempest:<br>
<br>
- Controller/Compute Node: RHEL 6.3-6.5, Fedora 19 ppc64<br>
- Hypervisor: PowerVM IVM 2.2.2.0+<br>
- Platform: P7 and P7+ Racks, Blades, ITEs<br>
- Networking:<br>
        - Neutron + Open vSwitch: Flat, VLAN - IPv4 only<br>
        - nova-network: Flat<br>
- Cinder Storage Driver: Storwize/SVC 6.4.1/6.4.2 for FC<br>
<br>
There are some teams here working on getting a PowerVC nova virt driver into Stackforge.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Florian Chazal
</div>