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

2015-07-19 Thread Sam Stoelinga
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


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

2015-07-19 Thread Priyanka

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


[Openstack] VM's using "local storage"?

2015-07-19 Thread Mike Dickson
I have a Kilo install w/the base components:  Keystone, Nova, Neutron, 
Glance and Cinder.  Cinder is running on a seperate host from the Nova 
compute servers using the LVM plugin.  I have about 12 vm's started and 
I noticed that on the System summary page its showing local storage in 
use, roughly equivalent to the sizes of the volumes summed up.  I popped 
on the compute servers and storage there is as expected. Lots of space 
free and nothing that related to this local storage requirement.


Do I have some simple misconfiguration?  I do have a large NFS server 
available and I was thinking maybe this is related in some way to how 
nova looks at the volumes. That perhaps it wants to reserve local 
storage to back the volumes.  If so I could use the NFS space to solve 
this and maybe get the ability to moved VM's as well?  Its clear from 
doing some analysis that the actual storage is on the storage box w/LVM 
because I can see the iSCSI tgt processes and disk I/O occurring.   Any 
suggestions on what to look at is appreciated.


Thanks in Advance!

Mike Dickson
mike.dick...@genomoncology.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


Re: [Openstack] Migrate an instance from one compute host to another compute host.

2015-07-19 Thread Tzach Shefi
Hi, 

Did you check/set instance migration config options ? 
http://docs.openstack.org/admin-guide-cloud/content/section_configuring-compute-migrations.html

If you have a default setup without doing any migration settings I'm pretty 
sure it will fail. 

BTW which version of openstack are you using? 
Did you check nova logs for errors? 

On the error that you mentioned, I'm guessing you forgot to mention the "don't" 
have shared storage or do they? 

Tshefi

- Original Message -
From: "Shanker Gudipati" 
To: openstack@lists.openstack.org
Sent: Monday, July 13, 2015 3:26:24 PM
Subject: [Openstack] Migrate an instance from one compute host to another   
compute host.



HI all, 



I am trying to migrate an instance from one host to another . 



When I try using “nova migrate SERVER TARGET_HOST” , its saying that the 
computes are having any shared data path. 



TIA 



Regards 

Shanker 


DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails. 

___
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 operating system pro cons

2015-07-19 Thread italy1
This could start another topic on which is better but now the fact is rhel and 
ubuntu are ahead of SUSE. 

Inviato da iPhone 




On Sat, Jul 18, 2015 at 3:49 PM -0700, "Cameron Seader"  
wrote:










Hi Peter,
You really should take a look at SUSE. SUSE Has a strong Linux
Distribution and OpenStack Distribution. Please let me know if you would
like some details.

-Cameron

On 07/18/2015 12:52 AM, Erdősi Péter wrote:
> 2015.07.17. 21:03 keltezéssel, Marton Kiss írta:
>> Do you mean that Ubuntu is unsupported on the HP Proliant servers? 
> I mean, main vendors does not have properly signed drivers for Ubuntu,
> but they have to RHEL, and it's works on CentOS...
> So what if I face a problem, i have to wait the community, while on
> CentOS, we have a chance, to use the RHEL patch, which came sooner I
> think...
> 
> Actually, I've checked a few server at HP, IBM, Fuji, and DELL, but only
> BIOS and Firmware on the list at HP servers under Ubuntu section, and no
> Ubuntu (or Debian) on other vendors... :(
> 
>> How are you buying hardware for gov projects?
> Same as others in gov, but i don't know any further details...
> 
> BTW, what OS have been used by the bigges Openstack providers?
> It's okay, that 55% vs 29% for Ubuntu on that survey, but not same if 10
> company have production with 10 server at ubuntu, while two of them have
> centos/rhel with hundreds of servers...
> 
> Regards,
>  Peter
> 
> ___
> 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

-- 
Cameron Seader
Sr. Systems Engineer
SUSE
c...@suse.com
(w)208-572-0095
(M)208-420-2167

Register for SUSECon 2015
www.susecon.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

!DSPAM:1,55aad7f3252661789175497!___
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

2015-07-19 Thread Moshe Levi
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 
complicate ☹
see https://community.mellanox.com/docs/DOC-1484

On Sun, Jul 19, 2015 at 2:44 PM, Moshe Levi 
mailto:mosh...@mellanox.com>> 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

Hi networking gurus,

While it may be easy for many of you to enable Neutron SRIOV on OpenStack it 
wasn't a smooth ride for me. I documented exactly which steps were required to 
enable SRIOV on OpenStack on my blog: 
http://samos-it.com/posts/sriov-openstack-juno-fuel-6-1.html

It seems there is no official documentation yet other than 2 out of date wiki 
pages. I would like take the content of my blog post to official OpenStack docs 
if you guys/girls think it's useful for the broader audience.

Regards,
Sam Stoelinga



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

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

2015-07-19 Thread Sam Stoelinga
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

Things that I noticed that were missing / could be better:
1. Adding PCIDeviceFilter to nova-scheduler
2. How to enable VFs on compute nodes
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
direc*t"
4. 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.

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/

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.

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
>
>
>
> Hi networking gurus,
>
>
>
> While it may be easy for many of you to enable Neutron SRIOV on OpenStack
> it wasn't a smooth ride for me. I documented exactly which steps were
> required to enable SRIOV on OpenStack on my blog:
> http://samos-it.com/posts/sriov-openstack-juno-fuel-6-1.html
>
>
>
> It seems there is no official documentation yet other than 2 out of date
> wiki pages. I would like take the content of my blog post to official
> OpenStack docs if you guys/girls think it's useful for the broader audience.
>
>
>
> Regards,
>
> Sam Stoelinga
>
>
>
>
>
___
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