Re: [Openstack] Internet connectivity to a new user's VM

[Priyanka]

Hi Sam,

I will create different routers for different users as the router I had 
created initially was a demo tenant router and so cannot be used by a 
new user. Also, it might sound silly but I have a doubt. For the new 
user created I have to create a new tenant too and the private network 
and router I will create will be for that tenant? According to the 
openstack setup guide the new user created should be added to the demo 
tenant itself. Doing this I cannot create a private network for the new 
user.


Sorry for asking such doubts but please help me clear my queries.

Thanks a lot,

Priyanka

On Monday 20 July 2015 02:43 PM, Priyanka wrote:

Hi,

Thanks a lot for a quick response. The network shared is the external 
network right?


Adding the points below just to confirm:

1. external_network is shared (example ext-net).
2. demo user network demo-net subnet demo-subnet (gateway 192.168.1.1 
range 192.168.1.0/24)
3. user1 user network user1-net subnet user1-subnet (gateway 
192.168.2.1 range 192.168.2.0/24)
4. I already have a router demo-router with demo-subnet interface 
added. Also router-gateway-set to ext-net.

5. I need to add user1-subnet interface to this router using:
neutron router-interface-add demo-router user1-subnet

Are these steps correct?

Thanks,

Priyanka

On Monday 20 July 2015 02:35 PM, Sam Stoelinga wrote:

There are several ways to do it.

#. You have a single router with external gateway your physical 
external network. Create another private network and add an interface 
of this private network to this router. Make this network shared 
accross tenants.
#. For each tenant create a router with external gateway your 
physical external network.


For reference:
http://docs.openstack.org/admin-guide-cloud/content/tenant-provider-networks.html
http://docs.openstack.org/icehouse/training-guides/content/operator-network-node.html#operator-openstack-networking-use-cases

On Mon, Jul 20, 2015 at 4:32 PM, Priyanka > wrote:


Hi Sam,

Thanks. So once the external network is shared I need to add an
interface to the existing router to add the new subnet I will 
create for the new user similar to demo-subnet for demo user?


Thanks,

Priyanka


On Monday 20 July 2015 11:51 AM, Sam Stoelinga wrote:

You can do this by making the network that you want to be shared
between tenants shared.

Both the UI or via CLI support this:
neutron net-create --shared public-net
or for existing network
neutron net-update --shared public-net

Sam Stoelinga

On Mon, Jul 20, 2015 at 12:30 PM, Priyanka
mailto:ppn...@cse.iitb.ac.in>> wrote:

Hi,

I want to add a new user other than the demo user in
openstack juno. But I want the same external network to be
used by its VM for internet connectivity. How can I do this?

Thanks ,

Priyanka

___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org

Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack









___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] VM_MISSING_PV_DRIVERS

[Leandro Mendes]

Hi Bob.

I'll follow these docs you mentioned.

Thanks for your answer!

Best,

Leandro.
Em 20/07/2015 20:21, "Bob Ball"  escreveu:

>  Hi Leandro,
>
> This is most likely that your compute VM has been created as an HVM guest,
> rather than a PV guest.  This will typically happen if you use the "Other
> Install Media" template in XenServer rather than the template for the
> specific Linux version.
>
> The error reported is that we cannot dynamically plug a disk into a VM -
> and this is most likely to be the compute VM.  Installing the PV tools into
> the VM will get you passed this particular error however you are then
> highly likely to hit https://bugs.launchpad.net/nova/+bug/1318544
>
> The best fix is to reinstall the compute node as a PV guest.
> Another approach could be to convert the compute node from HVM to PV.
> Note that if you're using recent guests that use grub2 as the bootloader
> you must be using XenServer 6.5 as earlier versions didn't parse the grub2
> config correctly when submenus were involved.
> http://wiki.univention.com/index.php?title=Citrix_Xen_Server#Convert_the_UCS_system_to_paravirtualization
>
> It's also worth noting that the image you upload probably needs to be in a
> slightly different format:
> http://blogs.citrix.com/2012/10/17/upload-custom-images-to-a-xenserver-powered-openstack-cloud/
> You probably just want to extract the XVA and create a tgz as with the
> instructions on the blog page.
>
> Thanks,
>
> Bob
>
>  --
> *From:* Leandro Mendes [theflock...@gmail.com]
> *Sent:* 20 July 2015 22:40
> *To:* openstack@lists.openstack.org
> *Subject:* [Openstack] VM_MISSING_PV_DRIVERS
>
>Hi guys,
>
>  Trying to register a CentOS7 VHD through glance, but when deploying the
> VM, i always get the follow error:
>
> Failure: ['VM_MISSING_PV_DRIVERS',
> 'OpaqueRef:9391569a-f5e1-1a34-1f90-fb7fb0983277']
>
>  I've created a VHD using a XVA template exported through XenCenter.
>
>  The command used to register the image was:
>
>  glance image-create --name "CentOS 7 (x86_64)" --file
>  --disk-format vhd --container-format bare
> --visibility public --progress
>
>  Do you guys have any clue about what's missing?
>
>  Thanks
>
>  Leandro
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] VM_MISSING_PV_DRIVERS

[Bob Ball]

Hi Leandro,

This is most likely that your compute VM has been created as an HVM guest, 
rather than a PV guest.  This will typically happen if you use the "Other 
Install Media" template in XenServer rather than the template for the specific 
Linux version.

The error reported is that we cannot dynamically plug a disk into a VM - and 
this is most likely to be the compute VM.  Installing the PV tools into the VM 
will get you passed this particular error however you are then highly likely to 
hit https://bugs.launchpad.net/nova/+bug/1318544

The best fix is to reinstall the compute node as a PV guest.
Another approach could be to convert the compute node from HVM to PV.  Note 
that if you're using recent guests that use grub2 as the bootloader you must be 
using XenServer 6.5 as earlier versions didn't parse the grub2 config correctly 
when submenus were involved.  
http://wiki.univention.com/index.php?title=Citrix_Xen_Server#Convert_the_UCS_system_to_paravirtualization

It's also worth noting that the image you upload probably needs to be in a 
slightly different format: 
http://blogs.citrix.com/2012/10/17/upload-custom-images-to-a-xenserver-powered-openstack-cloud/
 You probably just want to extract the XVA and create a tgz as with the 
instructions on the blog page.

Thanks,

Bob


From: Leandro Mendes [theflock...@gmail.com]
Sent: 20 July 2015 22:40
To: openstack@lists.openstack.org
Subject: [Openstack] VM_MISSING_PV_DRIVERS

Hi guys,

Trying to register a CentOS7 VHD through glance, but when deploying the VM, i 
always get the follow error:

Failure: ['VM_MISSING_PV_DRIVERS', 
'OpaqueRef:9391569a-f5e1-1a34-1f90-fb7fb0983277']

I've created a VHD using a XVA template exported through XenCenter.

The command used to register the image was:

 glance image-create --name "CentOS 7 (x86_64)" --file 
 --disk-format vhd --container-format bare 
--visibility public --progress

Do you guys have any clue about what's missing?

Thanks

Leandro
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Final Call: 8th IEEE/ACM International Conference on Utility and Cloud Computing

[Ashiq Anjum]

*** Final Call for Papers ***

8th IEEE/ACM International Conference on Utility and Cloud
Computing (UCC 2015)

December 07-10, 2015, St. Raphael Resort, Limassol, Cyprus

http://cyprusconferences.org/ucc2015

*** DEADLINE: 31 July, 2015 ***


CONTEXT AND SCOPE

Cloud Computing delivers computational resources on-demand as services
that are commoditized and delivered analogous to traditional utilities such as
electricity, gas, water and telephony. Cloud service offerings for compute,
storage and communication resources as well as for hosted software and data
are growing at a tremendous rate, and it is essential to understand how to
effectively transform these services into Utilities that provide value to both
users and providers. There is also increasing interest from commercial
providers to offer business and revenue models around the services they
offer. Understanding how these models could be used to provide utility for
users, intermediary brokers (aggregators) and providers is also an area of
active research. UCC is the premier IEEE/ACM conference covering all areas
related to Cloud Computing as a Utility and provides an international forum
for leading researchers and practitioners in this important and growing field.
UCC 2015, to be held in Cyprus, will happen as Cloud providers worldwide
add new services and increase Cloud utility at an accelerated pace, and Cloud
service users explore new usage modes.

This will be the 8th UCC in a successful conference series. Previous events
were held in Shanghai, China (Cloud 2009), Melbourne, Australia (Cloud 2010
& UCC 2011), Chennai, India (UCC 2010), Chicago, USA (UCC 2012), Dresden,
Germany (UCC2013), and London, UK (UCC 2014).


CALL FOR PAPERS

Authors are invited to submit original unpublished research manuscripts that
demonstrate current research in all areas of Cloud and Utility computing
including design and analysis of distributed and centralized Cloud systems,
data centre design and engineering, economic and market models for cloud
systems, revenue and business models and their applications in scientific,
engineering, and commercial deployment.

Topics of interest include but are not limited to:

• Big Data and Analytics

• Principles and theoretical foundations of Utility Computing, including
pricing and service models

• Policy languages and Programming models

• Utility driven model and mechanisms for Cloud federations

• Autonomic techniques for Clouds and Cloud applications

• Utility-driven platforms for Clouds

• Architectural models to achieve Utility in Clouds

• Designs and deployment models for Clouds: private, public, hybrid,
federated, aggregated

• Cloud Computing middleware, stacks, tools, delivery networks and
services at all layers (XaaS)

• Virtualization technologies and other enablers

• Economic models and scenarios of use

• Scalability and resource management: brokering, scheduling, capacity
planning, parallelism and elasticity, as well as marketplaces

• Cloud management: autonomic, adaptive, self-*, SLAs, performance
models and monitoring

• Applications: games, social networks, scientific computing (e-science)
and business

• Mobile and energy-efficient use of Clouds

• Beyond technology: Cloud business and legal implications, such as
security, privacy, trust and jurisdiction, especially in Utility contexts

One or more best paper awards will be given for outstanding contributed
papers. Further details as well as submission guidelines are available at the
conference website and below.


MANUSCRIPT GUIDELINES

Submitted manuscripts should be structured as technical papers and
may not exceed ten (10) single-spaced double-column pages using
10-point size font on 8.5x11 inch pages (IEEE conference style), including
figures, tables, and references.

Electronic submissions must be in the form of a readable PDF file.
Manuscripts must be received by July 17, 2015. All
manuscripts will be reviewed by the Program Committee and evaluated on
originality, relevance of the problem to the conference theme, technical
strength, rigor in analysis, quality of results, and organization and clarity
of presentation of the paper.

Please use the following Easy Chair link to update your submission:
https://easychair.org/conferences/?conf=ucc2015 .

Submitted papers must represent original unpublished research that is not
currently under review for any other conference or journal. Papers not
following these guidelines will be rejected without review and further action
may be taken, including (but not limited to) notifications sent to the heads of
the institutions of the authors and sponsors of the conference. Submissions
received after the due date, exceeding length limit, or not appropriately
structured may also not be considered. Authors may contact the Program
Chairs at the email addressed below for further information or clarification.
Notification of review decisions will be mailed by August 21, 2015. Camera
-ready papers are due by September 

Re: [Openstack] Scheduler Order

[Anne Gentle]

On Mon, Jul 20, 2015 at 2:44 PM, Bruno L  wrote:

> You could write your own scheduler filter that does it exactly the way you
> want. It is easier than you think.
>

Documented here:

http://docs.openstack.org/openstack-ops/content/customize.html


> On 21/07/2015 1:41 am, "Georgios Dimitrakakis" 
> wrote:
>
>> Hello!
>>
>> I would like to know if it's possible to define the order on which the
>> hypervisors are loaded.
>>
>> I already have in my configuration
>>
>> ram_weight_multiplier = -1.0
>>
>> in order to pack as many VMs in one hypervisor as possible.
>>
>> What I would like to know now is if I can somehow define the order of the
>> hypervisors since there are differences among them.
>>
>>
>> Best regards,
>>
>>
>> George
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Anne Gentle
Rackspace
Principal Engineer
www.justwriteclick.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] VM_MISSING_PV_DRIVERS

[Leandro Mendes]

Hi guys,

Trying to register a CentOS7 VHD through glance, but when deploying the VM,
i always get the follow error:

Failure: ['VM_MISSING_PV_DRIVERS',
'OpaqueRef:9391569a-f5e1-1a34-1f90-fb7fb0983277']

I've created a VHD using a XVA template exported through XenCenter.

The command used to register the image was:

 glance image-create --name "CentOS 7 (x86_64)" --file
 --disk-format vhd --container-format bare
--visibility public --progress

Do you guys have any clue about what's missing?

Thanks

Leandro
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Spawning Issue with Juno, Neutron, Xen and Libvirt

[Geoffrey Tran]

Hello all,

I've been trying to get a single-node installation up and running with
Juno, neutron, Xen, and libvirt. However, there has been an issue 
with actually launching a guest.  The error that shows up in 
/var/log/libvirt/libxl/instance-.log  is below:

> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: 
>/etc/xen/scripts/vif-bridge online [-1] exited with error status 1
> libxl: error: libxl_device.c:1085:device_hotplug_child_death_cb: 
>script: ip link set vif1.0 name tap20b72258-74 failed
> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch 
>w=0x7f6440009c20: deregister unregistered
> libxl: error: libxl_create.c:1226:domcreate_attach_vtpms: unable to 
>add nic devices

I am following the steps to get setup as shown here: 
https://blog.xenproject.org/2014/12/01/using-xen-project-on-openstack-juno-via-libvirt/

The only difference is that I am running all services on a signle node.

The following sites mention this error, but so far there are no other 
solutions other than using nova-networking.
> https://ask.openstack.org/en/question/64942/nova-libvirt-xen-driver-and-patch-feb-2015-in-upstream-libvirt/
> http://www.gossamer-threads.com/lists/xen/devel/374061
> http://lists.xen.org/archives/html/xen-devel/2015-04/msg01723.html

If I could get any assistance, it would be very much appreciated!

Thanks,
Geoffrey

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Scheduler Order

[Bruno L]

You could write your own scheduler filter that does it exactly the way you
want. It is easier than you think.
On 21/07/2015 1:41 am, "Georgios Dimitrakakis"  wrote:

> Hello!
>
> I would like to know if it's possible to define the order on which the
> hypervisors are loaded.
>
> I already have in my configuration
>
> ram_weight_multiplier = -1.0
>
> in order to pack as many VMs in one hypervisor as possible.
>
> What I would like to know now is if I can somehow define the order of the
> hypervisors since there are differences among them.
>
>
> Best regards,
>
>
> George
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack Juno step-by-step guide

[Sam Stoelinga]

I think it's a lot clearer already, I also made a minor modification to
SRIOV agent part. Next to that I will see if I can add the content to
OpenStack networking manual under advanced configuration. Have filed a bug
against openstack-manuals here:
https://bugs.launchpad.net/openstack-manuals/+bug/1476242 will move forward
if bug get's consensus that content is ok to be added to networking guide.

Sam

On Mon, Jul 20, 2015 at 6:56 PM, Moshe Levi  wrote:

> Hi,
>
> I have update the SR-IOV wiki
> https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> Let me know if it clearer now.
>
> Thanks,
> Moshe Levi.
>
> > -Original Message-
> > From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> > Sent: Monday, July 20, 2015 12:34 PM
> > To: Sam Stoelinga
> > Cc: Moshe Levi; openstack@lists.openstack.org
> > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> > OpenStack Juno step-by-step guide
> >
> > That's right.
> >
> > But the firewall_driver = NoopFirewallDriver is an agent configuration,
> so if
> > you would have the sriov-agent configured with this driver, you still
> could
> > configure an ovs agent with another driver I guess. Does that make sense?
> > If so, maybe we could add this information to the wiki as well!
> >
> > Thanks!
> >
> > Andreas
> >
> >
> >
> > On Mo, 2015-07-20 at 16:58 +0800, Sam Stoelinga wrote:
> > > I want to add that I'm not using the NoopFirewall as I'm using
> > > agent_required = False. So all instances that are not using SRIOV can
> > > still use security groups like normal. Instances that are using SRIOV
> > > won't have security groups applied though.
> > >
> > > On Mon, Jul 20, 2015 at 3:21 PM, Moshe Levi 
> > > wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> > > > Sent: Monday, July 20, 2015 10:04 AM
> > > > To: Moshe Levi
> > > > Cc: Sam Stoelinga; openstack@lists.openstack.org
> > > > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling
> > > SRIOV on
> > > > OpenStack Juno step-by-step guide
> > > >
> > > > +1 for updating the wiki
> > > > +1 for adding a section to the docs
> > > >
> > > >
> > > > Moshe,
> > > > what about the firewall support Sam mentioned? I assume
> > > fwaas is
> > > > supported, as it runs on the network node which uses ovs,
> > > but Security
> > > > Groups are not working as you're using the
> > > NoopFirewallDriver, right?
> > > Yes that is correct. I will update that as well in the wiki.
> > >
> > > > Or is there another FW driver that could be used?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > > > On So, 2015-07-19 at 08:12 +, Moshe Levi wrote:
> > > > > See my comments inline
> > > > >
> > > > >
> > > > >
> > > > > From: Sam Stoelinga [mailto:sammiest...@gmail.com]
> > > > > Sent: Sunday, July 19, 2015 10:37 AM
> > > > > To: Moshe Levi
> > > > > Cc: openstack@lists.openstack.org
> > > > > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling
> > > SRIOV on
> > > > > OpenStack Juno step-by-step guide
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > I think it was not fair to say it's not up to date. It
> > > seems it's up
> > > > > to date, but current downsides of existing OpenStack wikis
> > > on SRIOV
> > > > > are missing info, many different Wikis and hard to consume
> > > the info:
> > > > >
> > > > >
> > > > > 1.
> > >
> https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > > > >
> > > > >
> > > > > 2. https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > > > >
> > > > >
> > > > > 3.
> > > https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
> > > > >
> > > > >
> > > > > 4. https://wiki.openstack.org/wiki/Pci_passthrough
> > > > >
> > > > >
> > > > >
> > > > > [ML] – I think the only wiki users should be using is
> > > > >
> > >
> https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > > > >  [2],[3] are the blueprints and [4] is PCI-Pass-through
> > > without SR-IOV
> > > > > and it refer to [1] which is good.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Things that I noticed that were missing / could be better:
> > > > >
> > > > >
> > > > > 1. Adding PCIDeviceFilter to nova-scheduler
> > > > >
> > > > > [ML] I think you mean the PciPassthroughFilter and you are
> > > correct indeed
> > > > it is 

[Openstack] Scheduler Order

[Georgios Dimitrakakis]

Hello!

I would like to know if it's possible to define the order on which the 
hypervisors are loaded.


I already have in my configuration

ram_weight_multiplier = -1.0

in order to pack as many VMs in one hypervisor as possible.

What I would like to know now is if I can somehow define the order of 
the hypervisors since there are differences among them.



Best regards,


George

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack Juno step-by-step guide

[Moshe Levi]

Hi,

I have update the SR-IOV wiki 
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
Let me know if it clearer now.

Thanks,
Moshe Levi.

> -Original Message-
> From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> Sent: Monday, July 20, 2015 12:34 PM
> To: Sam Stoelinga
> Cc: Moshe Levi; openstack@lists.openstack.org
> Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> OpenStack Juno step-by-step guide
> 
> That's right.
> 
> But the firewall_driver = NoopFirewallDriver is an agent configuration, so if
> you would have the sriov-agent configured with this driver, you still could
> configure an ovs agent with another driver I guess. Does that make sense?
> If so, maybe we could add this information to the wiki as well!
> 
> Thanks!
> 
> Andreas
> 
> 
> 
> On Mo, 2015-07-20 at 16:58 +0800, Sam Stoelinga wrote:
> > I want to add that I'm not using the NoopFirewall as I'm using
> > agent_required = False. So all instances that are not using SRIOV can
> > still use security groups like normal. Instances that are using SRIOV
> > won't have security groups applied though.
> >
> > On Mon, Jul 20, 2015 at 3:21 PM, Moshe Levi 
> > wrote:
> >
> >
> > > -Original Message-
> > > From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> > > Sent: Monday, July 20, 2015 10:04 AM
> > > To: Moshe Levi
> > > Cc: Sam Stoelinga; openstack@lists.openstack.org
> > > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling
> > SRIOV on
> > > OpenStack Juno step-by-step guide
> > >
> > > +1 for updating the wiki
> > > +1 for adding a section to the docs
> > >
> > >
> > > Moshe,
> > > what about the firewall support Sam mentioned? I assume
> > fwaas is
> > > supported, as it runs on the network node which uses ovs,
> > but Security
> > > Groups are not working as you're using the
> > NoopFirewallDriver, right?
> > Yes that is correct. I will update that as well in the wiki.
> >
> > > Or is there another FW driver that could be used?
> > >
> > > Thanks
> > >
> > >
> > >
> > > On So, 2015-07-19 at 08:12 +, Moshe Levi wrote:
> > > > See my comments inline
> > > >
> > > >
> > > >
> > > > From: Sam Stoelinga [mailto:sammiest...@gmail.com]
> > > > Sent: Sunday, July 19, 2015 10:37 AM
> > > > To: Moshe Levi
> > > > Cc: openstack@lists.openstack.org
> > > > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling
> > SRIOV on
> > > > OpenStack Juno step-by-step guide
> > > >
> > > >
> > > >
> > > >
> > > > I think it was not fair to say it's not up to date. It
> > seems it's up
> > > > to date, but current downsides of existing OpenStack wikis
> > on SRIOV
> > > > are missing info, many different Wikis and hard to consume
> > the info:
> > > >
> > > >
> > > > 1.
> > https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > > >
> > > >
> > > > 2. https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > > >
> > > >
> > > > 3.
> > https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
> > > >
> > > >
> > > > 4. https://wiki.openstack.org/wiki/Pci_passthrough
> > > >
> > > >
> > > >
> > > > [ML] – I think the only wiki users should be using is
> > > >
> > https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > > >  [2],[3] are the blueprints and [4] is PCI-Pass-through
> > without SR-IOV
> > > > and it refer to [1] which is good.
> > > >
> > > >
> > > >
> > > >
> > > > Things that I noticed that were missing / could be better:
> > > >
> > > >
> > > > 1. Adding PCIDeviceFilter to nova-scheduler
> > > >
> > > > [ML] I think you mean the PciPassthroughFilter and you are
> > correct indeed
> > > it is missing. I will update the wiki.
> > > > 2. How to enable VFs on compute nodes
> > > >
> > > > [ML] – This  vendor specific but we can add links to
> > vendor wiki page
> > > > on how to configure their NIC to support SR-IOV
> > > >
> > > >
> > > > 3. This wiki:
> > https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > > > contains incorrect information.
> > > >
> > > >
> > > > Current wrong: "neutron port-create 
> > --name
> > > > sriov_port --vnic-type direct "
> > > >
> > > >
> > > > should be "neutron port-create 
> > --na

Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack Juno step-by-step guide

[Andreas Scheuring]

That's right. 

But the firewall_driver = NoopFirewallDriver is an agent configuration,
so if you would have the sriov-agent configured with this driver, you
still could configure an ovs agent with another driver I guess. Does
that make sense?
If so, maybe we could add this information to the wiki as well!

Thanks!

Andreas



On Mo, 2015-07-20 at 16:58 +0800, Sam Stoelinga wrote:
> I want to add that I'm not using the NoopFirewall as I'm using
> agent_required = False. So all instances that are not using SRIOV can
> still use security groups like normal. Instances that are using SRIOV
> won't have security groups applied though. 
> 
> On Mon, Jul 20, 2015 at 3:21 PM, Moshe Levi 
> wrote:
> 
> 
> > -Original Message-
> > From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> > Sent: Monday, July 20, 2015 10:04 AM
> > To: Moshe Levi
> > Cc: Sam Stoelinga; openstack@lists.openstack.org
> > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling
> SRIOV on
> > OpenStack Juno step-by-step guide
> >
> > +1 for updating the wiki
> > +1 for adding a section to the docs
> >
> >
> > Moshe,
> > what about the firewall support Sam mentioned? I assume
> fwaas is
> > supported, as it runs on the network node which uses ovs,
> but Security
> > Groups are not working as you're using the
> NoopFirewallDriver, right?
> Yes that is correct. I will update that as well in the wiki.
> 
> > Or is there another FW driver that could be used?
> >
> > Thanks
> >
> >
> >
> > On So, 2015-07-19 at 08:12 +, Moshe Levi wrote:
> > > See my comments inline
> > >
> > >
> > >
> > > From: Sam Stoelinga [mailto:sammiest...@gmail.com]
> > > Sent: Sunday, July 19, 2015 10:37 AM
> > > To: Moshe Levi
> > > Cc: openstack@lists.openstack.org
> > > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling
> SRIOV on
> > > OpenStack Juno step-by-step guide
> > >
> > >
> > >
> > >
> > > I think it was not fair to say it's not up to date. It
> seems it's up
> > > to date, but current downsides of existing OpenStack wikis
> on SRIOV
> > > are missing info, many different Wikis and hard to consume
> the info:
> > >
> > >
> > > 1.
> https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > >
> > >
> > > 2. https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > >
> > >
> > > 3.
> https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
> > >
> > >
> > > 4. https://wiki.openstack.org/wiki/Pci_passthrough
> > >
> > >
> > >
> > > [ML] – I think the only wiki users should be using is
> > >
> https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > >  [2],[3] are the blueprints and [4] is PCI-Pass-through
> without SR-IOV
> > > and it refer to [1] which is good.
> > >
> > >
> > >
> > >
> > > Things that I noticed that were missing / could be better:
> > >
> > >
> > > 1. Adding PCIDeviceFilter to nova-scheduler
> > >
> > > [ML] I think you mean the PciPassthroughFilter and you are
> correct indeed
> > it is missing. I will update the wiki.
> > > 2. How to enable VFs on compute nodes
> > >
> > > [ML] – This  vendor specific but we can add links to
> vendor wiki page
> > > on how to configure their NIC to support SR-IOV
> > >
> > >
> > > 3. This wiki:
> https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > > contains incorrect information.
> > >
> > >
> > > Current wrong: "neutron port-create 
> --name
> > > sriov_port --vnic-type direct "
> > >
> > >
> > > should be "neutron port-create 
> --name
> > > sriov_port --binding:vnic_type direct"
> > >
> > > [ML] – this is blueprint but I will check if I can update
> it.
> > >
> > >
> > > 3. Make it more clear that agent_required = False is
> totally fine
> > > and may be better. From what I read you have to disable
> the firewall
> > > functionality if you enable sriov-agent? Not sure if that
> > > understanding is correct.
> > >
> > > [ML] – I agree this is totally need clarification. The
> > > agent_required=False is used when you have Intel NIC that
> doesn’t
> > > support admin up/down  

Re: [Openstack] Internet connectivity to a new user's VM

[Priyanka]

Hi,

Thanks a lot for a quick response. The network shared is the external 
network right?


Adding the points below just to confirm:

1. external_network is shared (example ext-net).
2. demo user network demo-net subnet demo-subnet (gateway 192.168.1.1 
range 192.168.1.0/24)
3. user1 user network user1-net subnet user1-subnet (gateway 192.168.2.1 
range 192.168.2.0/24)
4. I already have a router demo-router with demo-subnet interface added. 
Also router-gateway-set to ext-net.

5. I need to add user1-subnet interface to this router using:
neutron router-interface-add demo-router user1-subnet

Are these steps correct?

Thanks,

Priyanka

On Monday 20 July 2015 02:35 PM, Sam Stoelinga wrote:

There are several ways to do it.

#. You have a single router with external gateway your physical 
external network. Create another private network and add an interface 
of this private network to this router. Make this network shared 
accross tenants.
#. For each tenant create a router with external gateway your physical 
external network.


For reference:
http://docs.openstack.org/admin-guide-cloud/content/tenant-provider-networks.html
http://docs.openstack.org/icehouse/training-guides/content/operator-network-node.html#operator-openstack-networking-use-cases

On Mon, Jul 20, 2015 at 4:32 PM, Priyanka > wrote:


Hi Sam,

Thanks. So once the external network is shared I need to add an
interface to the existing router to add the new subnet I will 
create for the new user similar to demo-subnet for demo user?


Thanks,

Priyanka


On Monday 20 July 2015 11:51 AM, Sam Stoelinga wrote:

You can do this by making the network that you want to be shared
between tenants shared.

Both the UI or via CLI support this:
neutron net-create --shared public-net
or for existing network
neutron net-update --shared public-net

Sam Stoelinga

On Mon, Jul 20, 2015 at 12:30 PM, Priyanka mailto:ppn...@cse.iitb.ac.in>> wrote:

Hi,

I want to add a new user other than the demo user in
openstack juno. But I want the same external network to be
used by its VM for internet connectivity. How can I do this?

Thanks ,

Priyanka

___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org

Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack







___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Internet connectivity to a new user's VM

[Sam Stoelinga]

There are several ways to do it.

#. You have a single router with external gateway your physical external
network. Create another private network and add an interface of this
private network to this router. Make this network shared accross tenants.
#. For each tenant create a router with external gateway your physical
external network.

For reference:
http://docs.openstack.org/admin-guide-cloud/content/tenant-provider-networks.html
http://docs.openstack.org/icehouse/training-guides/content/operator-network-node.html#operator-openstack-networking-use-cases

On Mon, Jul 20, 2015 at 4:32 PM, Priyanka  wrote:

>  Hi Sam,
>
> Thanks. So once the external network is shared I need to add an interface
> to the existing router to add the new subnet I will  create for the new
> user similar to demo-subnet for demo user?
>
> Thanks,
>
> Priyanka
>
>
> On Monday 20 July 2015 11:51 AM, Sam Stoelinga wrote:
>
> You can do this by making the network that you want to be shared between
> tenants shared.
>
>  Both the UI or via CLI support this:
> neutron net-create --shared public-net
>  or for existing network
> neutron net-update --shared public-net
>
>  Sam Stoelinga
>
> On Mon, Jul 20, 2015 at 12:30 PM, Priyanka  wrote:
>
>> Hi,
>>
>> I want to add a new user other than the demo user in openstack juno. But
>> I want the same external network to be used by its VM for internet
>> connectivity. How can I do this?
>>
>> Thanks ,
>>
>> Priyanka
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack Juno step-by-step guide

[Sam Stoelinga]

I want to add that I'm not using the NoopFirewall as I'm using
agent_required = False. So all instances that are not using SRIOV can still
use security groups like normal. Instances that are using SRIOV won't have
security groups applied though.

On Mon, Jul 20, 2015 at 3:21 PM, Moshe Levi  wrote:

>
>
> > -Original Message-
> > From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> > Sent: Monday, July 20, 2015 10:04 AM
> > To: Moshe Levi
> > Cc: Sam Stoelinga; openstack@lists.openstack.org
> > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> > OpenStack Juno step-by-step guide
> >
> > +1 for updating the wiki
> > +1 for adding a section to the docs
> >
> >
> > Moshe,
> > what about the firewall support Sam mentioned? I assume fwaas is
> > supported, as it runs on the network node which uses ovs, but Security
> > Groups are not working as you're using the NoopFirewallDriver, right?
> Yes that is correct. I will update that as well in the wiki.
>
> > Or is there another FW driver that could be used?
> >
> > Thanks
> >
> >
> >
> > On So, 2015-07-19 at 08:12 +, Moshe Levi wrote:
> > > See my comments inline
> > >
> > >
> > >
> > > From: Sam Stoelinga [mailto:sammiest...@gmail.com]
> > > Sent: Sunday, July 19, 2015 10:37 AM
> > > To: Moshe Levi
> > > Cc: openstack@lists.openstack.org
> > > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> > > OpenStack Juno step-by-step guide
> > >
> > >
> > >
> > >
> > > I think it was not fair to say it's not up to date. It seems it's up
> > > to date, but current downsides of existing OpenStack wikis on SRIOV
> > > are missing info, many different Wikis and hard to consume the info:
> > >
> > >
> > > 1. https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > >
> > >
> > > 2. https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > >
> > >
> > > 3. https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
> > >
> > >
> > > 4. https://wiki.openstack.org/wiki/Pci_passthrough
> > >
> > >
> > >
> > > [ML] – I think the only wiki users should be using is
> > > https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> > >  [2],[3] are the blueprints and [4] is PCI-Pass-through without SR-IOV
> > > and it refer to [1] which is good.
> > >
> > >
> > >
> > >
> > > Things that I noticed that were missing / could be better:
> > >
> > >
> > > 1. Adding PCIDeviceFilter to nova-scheduler
> > >
> > > [ML] I think you mean the PciPassthroughFilter and you are correct
> indeed
> > it is missing. I will update the wiki.
> > > 2. How to enable VFs on compute nodes
> > >
> > > [ML] – This  vendor specific but we can add links to vendor wiki page
> > > on how to configure their NIC to support SR-IOV
> > >
> > >
> > > 3. This wiki: https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > > contains incorrect information.
> > >
> > >
> > > Current wrong: "neutron port-create  --name
> > > sriov_port --vnic-type direct "
> > >
> > >
> > > should be "neutron port-create  --name
> > > sriov_port --binding:vnic_type direct"
> > >
> > > [ML] – this is blueprint but I will check if I can update it.
> > >
> > >
> > > 3. Make it more clear that agent_required = False is totally fine
> > > and may be better. From what I read you have to disable the firewall
> > > functionality if you enable sriov-agent? Not sure if that
> > > understanding is correct.
> > >
> > > [ML] – I agree this is totally need clarification. The
> > > agent_required=False is used when you have Intel NIC that doesn’t
> > > support admin up/down  change. SR-IOV NIC that support admin up/down
> > > change should be configured with agent_required =True.
> > >
> > > I will update the wiki explaining that flag.  (by the way we hope to
> > > change it in liberty and deprecate the agent_required flag)
> > >
> > >
> > >
> > >
> > >
> > > I would prefer this information to have release bound documentation in
> > > for example the Networking
> > > Guide: http://docs.openstack.org/networking-guide/ or the Cloud
> > > Administrator
> > > Guide: http://docs.openstack.org/admin-guide-cloud/content/
> > >
> > > [ML] – Ok, I guess this is required change in
> > > openstack/openstack-manuals repository. Can you help and adding
> > > documentations  there? Just put me as review.  If not I will try do it
> > > myself or find someone in Mellanox.
> > >
> > >
> > >
> > >
> > > I believe that using the pci sys interface is vendor compatible. Would
> > > be great if you could confirm. Could you try testing $ echo '7'
> > > > /sys/class/net/eth3/device/sriov_numvfs on a mellanox card?
> > >
> > >
> > > This way we don't have to write vendor specific docs on enabling VFs
> > > :)
> > >
> > >
> > > When using modprobe ixgbe max_vfs=7 it tells you that using max_vfs is
> > > deprecated and that the pci sys interface should be used. That's how I
> > > found out about this.
> > >
> > > [ML] – unfortunately it is not generic  in Melllanox you need to
> > > configure number

Re: [Openstack] Internet connectivity to a new user's VM

[Priyanka]

Hi Sam,

Thanks. So once the external network is shared I need to add an 
interface to the existing router to add the new subnet I will create for 
the new user similar to demo-subnet for demo user?


Thanks,

Priyanka

On Monday 20 July 2015 11:51 AM, Sam Stoelinga wrote:
You can do this by making the network that you want to be shared 
between tenants shared.


Both the UI or via CLI support this:
neutron net-create --shared public-net
or for existing network
neutron net-update --shared public-net

Sam Stoelinga

On Mon, Jul 20, 2015 at 12:30 PM, Priyanka > wrote:


Hi,

I want to add a new user other than the demo user in openstack
juno. But I want the same external network to be used by its VM
for internet connectivity. How can I do this?

Thanks ,

Priyanka

___
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org

Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack deployment on two nodes with single NIC

[nithish B]

Hi Tusa,
Yes, 192.168.1.1 is set as both gateway IP and as the I/F IP. So,
change that, and configure your routes. This should solve it.

Thanks.

Regards,
Nitish B.

On Sun, Jul 19, 2015 at 2:03 AM, italy1  wrote:

> Ciao Francesco
> I think your route are not configured correctly
>
> Contattami off-line
>
> Remo
>
> Inviato da IPhone
>
>
>
> On Sat, Jul 18, 2015 at 10:27 AM -0700, "Francesco Tusa" <
> f.t...@westminster.ac.uk> wrote:
>
>   Hi Nitish,
>>
>> thanks for your answer.
>>
>>
>>  According to your message I should change the IP address of interface
>> qr-c15092f4 on the virtual router, to something else on the same subnet
>> (e.g. 192.168.1.100).
>>
>>
>>  Sorry I am a bit confused about this.
>>
>>
>>  192.168.1.1 is the default gw for the instances on the their private
>> network (I can see it if I type 'route -n' from within an instance). I
>> thought this was the first hop in the packet routing.
>>
>>
>>  What will happen if I change that IP? What entity will act as gateway
>> then?
>>
>>
>>  Thanks again,
>>
>> Francesco.
>>
>>
>>
>>  --
>> *From:* nithish B 
>> *Sent:* 18 July 2015 17:26
>> *To:* Francesco Tusa
>> *Cc:* openstack@lists.openstack.org
>> *Subject:* Re: [Openstack] Openstack deployment on two nodes with single
>> NIC
>>
>>  Hi Tusa,
>>   Looking at the post on ask.openstack.org , I see that the Ip address
>> of qr-c15092f4-bb is  192.168.1.1. Isn't that supposed to be the gateway
>> IP for that I/F? This might be the issue because I see that the command ip
>> netns exec qrouter-dff3861b-69d2-46c8-b990-0d218826955b tcpdump -n -i
>> qr-c15092f4-bb is redirecting the packets to 192.168.1.8 which is being
>> dropped as the subnet of 192.168.1.x has the gateway IP assigned as the
>> inet.
>>
>>  I guess changing this might solve the issue. Let me know if this worked.
>>
>>  Thanks.
>>
>>   Regards,
>>  Nitish B.
>>
>> On Sat, Jul 18, 2015 at 1:08 AM, Francesco Tusa > > wrote:
>>
>>>  Hi all,
>>>
>>> I want to set up a small testbed for testing purposes as described in
>>> the email's subject.
>>>
>>>
>>>  I deployed Openstack on two PCs (with CentOS 7.1) in my office using
>>> RDO (openstack-packstack) last week.
>>>
>>>
>>>  Basic functionalities are working but I am having issues while
>>> accessing VMs from the physical hosts, and getting access to the external
>>> network from the VMs.
>>>
>>>
>>>  Please find below all the details, unfortunately I did not manage to
>>> solve the issue so far:
>>>
>>>
>>> https://ask.openstack.org/en/question/78232/openstack-deployment-on-two-nodes-with-one-nic/
>>>
>>>  Thanks in advance for your valuable help.
>>>
>>>
>>>  Regards,
>>>
>>> Francesco.
>>>
>>> The University of Westminster is a charity and a company limited by
>>> guarantee. Registration number: 977818 England.
>>> Registered Office: 309 Regent Street, London W1B 2UW.
>>>
>>> This message and its attachments are private and confidential. If you
>>> have received this message in error, please notify the sender and remove it
>>> and its attachments from your system.
>>>
>>> ___
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>>The University of Westminster is a charity and a company limited by
>> guarantee. Registration number: 977818 England.
>> Registered Office: 309 Regent Street, London W1B 2UW.
>>
>> This message and its attachments are private and confidential. If you
>> have received this message in error, please notify the sender and remove it
>> and its attachments from your system.
>>  !DSPAM:1,55aa8c9c139671779012523!
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack Juno step-by-step guide

[Moshe Levi]

> -Original Message-
> From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
> Sent: Monday, July 20, 2015 10:04 AM
> To: Moshe Levi
> Cc: Sam Stoelinga; openstack@lists.openstack.org
> Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> OpenStack Juno step-by-step guide
> 
> +1 for updating the wiki
> +1 for adding a section to the docs
> 
> 
> Moshe,
> what about the firewall support Sam mentioned? I assume fwaas is
> supported, as it runs on the network node which uses ovs, but Security
> Groups are not working as you're using the NoopFirewallDriver, right?
Yes that is correct. I will update that as well in the wiki.

> Or is there another FW driver that could be used?
> 
> Thanks
> 
> 
> 
> On So, 2015-07-19 at 08:12 +, Moshe Levi wrote:
> > See my comments inline
> >
> >
> >
> > From: Sam Stoelinga [mailto:sammiest...@gmail.com]
> > Sent: Sunday, July 19, 2015 10:37 AM
> > To: Moshe Levi
> > Cc: openstack@lists.openstack.org
> > Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> > OpenStack Juno step-by-step guide
> >
> >
> >
> >
> > I think it was not fair to say it's not up to date. It seems it's up
> > to date, but current downsides of existing OpenStack wikis on SRIOV
> > are missing info, many different Wikis and hard to consume the info:
> >
> >
> > 1. https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> >
> >
> > 2. https://wiki.openstack.org/wiki/Nova-neutron-sriov
> >
> >
> > 3. https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
> >
> >
> > 4. https://wiki.openstack.org/wiki/Pci_passthrough
> >
> >
> >
> > [ML] – I think the only wiki users should be using is
> > https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> >  [2],[3] are the blueprints and [4] is PCI-Pass-through without SR-IOV
> > and it refer to [1] which is good.
> >
> >
> >
> >
> > Things that I noticed that were missing / could be better:
> >
> >
> > 1. Adding PCIDeviceFilter to nova-scheduler
> >
> > [ML] I think you mean the PciPassthroughFilter and you are correct indeed
> it is missing. I will update the wiki.
> > 2. How to enable VFs on compute nodes
> >
> > [ML] – This  vendor specific but we can add links to vendor wiki page
> > on how to configure their NIC to support SR-IOV
> >
> >
> > 3. This wiki: https://wiki.openstack.org/wiki/Nova-neutron-sriov
> > contains incorrect information.
> >
> >
> > Current wrong: "neutron port-create  --name
> > sriov_port --vnic-type direct "
> >
> >
> > should be "neutron port-create  --name
> > sriov_port --binding:vnic_type direct"
> >
> > [ML] – this is blueprint but I will check if I can update it.
> >
> >
> > 3. Make it more clear that agent_required = False is totally fine
> > and may be better. From what I read you have to disable the firewall
> > functionality if you enable sriov-agent? Not sure if that
> > understanding is correct.
> >
> > [ML] – I agree this is totally need clarification. The
> > agent_required=False is used when you have Intel NIC that doesn’t
> > support admin up/down  change. SR-IOV NIC that support admin up/down
> > change should be configured with agent_required =True.
> >
> > I will update the wiki explaining that flag.  (by the way we hope to
> > change it in liberty and deprecate the agent_required flag)
> >
> >
> >
> >
> >
> > I would prefer this information to have release bound documentation in
> > for example the Networking
> > Guide: http://docs.openstack.org/networking-guide/ or the Cloud
> > Administrator
> > Guide: http://docs.openstack.org/admin-guide-cloud/content/
> >
> > [ML] – Ok, I guess this is required change in
> > openstack/openstack-manuals repository. Can you help and adding
> > documentations  there? Just put me as review.  If not I will try do it
> > myself or find someone in Mellanox.
> >
> >
> >
> >
> > I believe that using the pci sys interface is vendor compatible. Would
> > be great if you could confirm. Could you try testing $ echo '7'
> > > /sys/class/net/eth3/device/sriov_numvfs on a mellanox card?
> >
> >
> > This way we don't have to write vendor specific docs on enabling VFs
> > :)
> >
> >
> > When using modprobe ixgbe max_vfs=7 it tells you that using max_vfs is
> > deprecated and that the pci sys interface should be used. That's how I
> > found out about this.
> >
> > [ML] – unfortunately it is not generic  in Melllanox you need to
> > configure number of VFs and number of probes (also Single Port  or
> > Duel Port ) it is more complicateL
> >
> > see https://community.mellanox.com/docs/DOC-1484
> >
> >
> >
> >
> > On Sun, Jul 19, 2015 at 2:44 PM, Moshe Levi 
> > wrote:
> >
> > Hi Sam,
> >
> >
> >
> > Can you explain why you think that the
> >   https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> is out of date?
> >
> > Moreover you blog explain how to configure SR-IOV on Intel
> > NIC, but keep in mind Neutron SRIOV is generic and can support
> > an

Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on OpenStack Juno step-by-step guide

[Andreas Scheuring]

+1 for updating the wiki
+1 for adding a section to the docs


Moshe, 
what about the firewall support Sam mentioned? I assume fwaas is
supported, as it runs on the network node which uses ovs, but Security
Groups are not working as you're using the NoopFirewallDriver, right?
Or is there another FW driver that could be used?

Thanks



On So, 2015-07-19 at 08:12 +, Moshe Levi wrote:
> See my comments inline 
> 
>  
> 
> From: Sam Stoelinga [mailto:sammiest...@gmail.com] 
> Sent: Sunday, July 19, 2015 10:37 AM
> To: Moshe Levi
> Cc: openstack@lists.openstack.org
> Subject: Re: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> OpenStack Juno step-by-step guide
> 
> 
>  
> 
> I think it was not fair to say it's not up to date. It seems it's up
> to date, but current downsides of existing OpenStack wikis on SRIOV
> are missing info, many different Wikis and hard to consume the info:
> 
> 
> 1. https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
> 
> 
> 2. https://wiki.openstack.org/wiki/Nova-neutron-sriov
> 
> 
> 3. https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support
> 
> 
> 4. https://wiki.openstack.org/wiki/Pci_passthrough
> 
>  
> 
> [ML] – I think the only wiki users should be using is
>  https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
>  [2],[3] are the blueprints and [4] is PCI-Pass-through without SR-IOV
> and it refer to [1] which is good.
> 
>  
> 
> 
> Things that I noticed that were missing / could be better:
> 
> 
> 1. Adding PCIDeviceFilter to nova-scheduler
> 
> [ML] I think you mean the PciPassthroughFilter and you are correct indeed it 
> is missing. I will update the wiki.
> 2. How to enable VFs on compute nodes
> 
> [ML] – This  vendor specific but we can add links to vendor wiki page
> on how to configure their NIC to support SR-IOV
> 
> 
> 3. This wiki: https://wiki.openstack.org/wiki/Nova-neutron-sriov
> contains incorrect information.
> 
> 
> Current wrong: "neutron port-create  --name
> sriov_port --vnic-type direct "
> 
> 
> should be "neutron port-create  --name
> sriov_port --binding:vnic_type direct"
> 
> [ML] – this is blueprint but I will check if I can update it.
> 
> 
> 3. Make it more clear that agent_required = False is totally fine
> and may be better. From what I read you have to disable the firewall
> functionality if you enable sriov-agent? Not sure if that
> understanding is correct.
> 
> [ML] – I agree this is totally need clarification. The
> agent_required=False is used when you have Intel NIC that doesn’t
> support admin up/down  change. SR-IOV NIC that support admin up/down
>  change should be configured with agent_required =True.
> 
> I will update the wiki explaining that flag.  (by the way we hope to
> change it in liberty and deprecate the agent_required flag) 
> 
> 
>  
> 
> 
> I would prefer this information to have release bound documentation in
> for example the Networking
> Guide: http://docs.openstack.org/networking-guide/ or the Cloud
> Administrator
> Guide: http://docs.openstack.org/admin-guide-cloud/content/
> 
> [ML] – Ok, I guess this is required change in
> openstack/openstack-manuals repository. Can you help and adding
> documentations  there? Just put me as review.  If not I will try do it
> myself or find someone in Mellanox.
> 
>  
> 
> 
> I believe that using the pci sys interface is vendor compatible. Would
> be great if you could confirm. Could you try testing $ echo '7'
> > /sys/class/net/eth3/device/sriov_numvfs on a mellanox card? 
> 
> 
> This way we don't have to write vendor specific docs on enabling
> VFs :) 
> 
> 
> When using modprobe ixgbe max_vfs=7 it tells you that using max_vfs is
> deprecated and that the pci sys interface should be used. That's how I
> found out about this.
> 
> [ML] – unfortunately it is not generic  in Melllanox you need to
> configure number of VFs and number of probes (also Single Port  or
> Duel Port ) it is more complicateL
> 
> see https://community.mellanox.com/docs/DOC-1484 
> 
> 
>  
> 
> On Sun, Jul 19, 2015 at 2:44 PM, Moshe Levi 
> wrote:
> 
> Hi Sam,
> 
>  
> 
> Can you explain why you think that the
>   https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking 
> is out of date?
> 
> Moreover you blog explain how to configure SR-IOV on Intel
> NIC, but keep in mind Neutron SRIOV is generic and can support
> any other vendors such  as Mellanox.
> 
> Maybe will should add links to how to configure SR-IOV NIC for
> several  Vendors. We can start with Mellanox and Intel NIC.
> What do you think?
> 
>  
> 
>  
> 
> From: Sam Stoelinga [mailto:sammiest...@gmail.com] 
> Sent: Saturday, July 18, 2015 5:55 PM
> To: openstack@lists.openstack.org
> Subject: [Openstack] [Neutron][SRIOV][docs] Enabling SRIOV on
> OpenStack Juno step-by-step guide
>