Re: [Openstack] Neutron support for passthrough of networking devices?

[Irena Berezovsky]

Hi Chris, Jiang,
We are also looking into enchantment of basic PCI pass-through to provide 
SR-IOV based networking.
In order to support automatic provisioning, it requires the awareness to what 
virtual network to connect the requested SR-IOV device. 
This should be considered by the scheduler  in order to run VM on the Host that 
is connected to the physical network. 
It requires the Neutron to be aware of PCI pass though allocated device and 
allocate port on the virtual network. 
It will require some sort of VIF Driver to manage the libvirt device settings. 
It may also require neutron agent to apply port policy on the device. I think 
it makes sense to  support this as part of ML2 neutron plugin (via mechanism 
driver).
In case you plan to attend the design summit, maybe it worth to collaborate 
there and discuss what can be done in the coming  Icehouse release?

Regards,
Irena

-Original Message-
From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com] 
Sent: Thursday, October 10, 2013 2:26 AM
To: Chris Friesen; openstack@lists.openstack.org
Subject: Re: [Openstack] Neutron support for passthrough of networking devices?

Several thing in my mind:
a) NIC need more information like the switch, and these information need be 
managed by nova also. We have basic support, but not fully implemented.
b) How to setup the device, including the mac address or 802.1Qbh etc. Libvirt 
have several option to support it, need more work to support them, also need 
consider other virt driver like xenapi etc.
c) How to achieve the isolation of tenants, and how to setup like the router in 
Neutron. I'm not well on Neutron, but I think others may have more idea on it.

Thanks
--jyh

> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: Wednesday, October 09, 2013 11:53 AM
> To: openstack@lists.openstack.org
> Subject: Re: [Openstack] Neutron support for passthrough of networking 
> devices?
> 
> On 10/09/2013 12:31 PM, Jiang, Yunhong wrote:
> > When we worked on H release, we target for basic PCI support like 
> > accelerator card or encryption card etc. I think SR-IOV network 
> > support is more complex and requires more effort, in both Nova side 
> > and Neutron side. We are working on some enhancement in Nova side 
> > now. But the whole picture may need more time/discussion.
> 
> Can you elaborate on the complexities?  Assuming you enable SR-IOV on 
> the host, and pass it through to the guest using the normal PCI 
> passthrough mechanisms, what's the extra complexity?
> 
> Do we run into the same complexity if we have spare physical NICs on 
> the host that get passed in to the guest?
> 
> Thanks,
> Chris
> 
> ___
> 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] Swift sharding across containers

[Shrinand Javadekar]

Thanks Chuck.

In order to really measure this, I ran some tests on Rackspace; i.e. I got
a VM on Rackspace and that VM was talking to a Rackspace Cloudfiles-US
swift cluster. The VM and object store were both in the Chicago region. The
downside of using a public object store is that I have little idea about
the configuration of Swift being used. But installing and configuring one's
own enterprise class Swift cluster is no child's play either (to put it
mildly :D).

In the first experiment, 128 threads were continuously trying to write 1
byte blobs into N containers where N was in (1, 32, 64, 128, 256, 512). The
experiment ran for 15 minutes. The experiment was run thrice for each N and
the results below are the average of three runs.

[image: Inline image 1]
The number of writes completed in 15 minutes if ~87K for a single
container, whereas when these writes are sharded across 32 containers, this
# is ~135K.

The second experiment was to find out whether Swift becomes slower as the
number of objects in a container increases. To do this, I measured the time
it was taking to write blobs in a single container. Here again, I ran the
experiment three times and the graph below is the average of the three runs.

[image: Inline image 2]

If a container has less than 1.6M blobs, the average time to write a blob
is ~12.58ms whereas if the container has > 1.6M blobs, the average time to
write a blob is ~13.29ms. The trend definitely seems to be that as number
of objects increase, the time to write also increases.

I guess the absolute number may differ depending on factors like memory,
CPU, disk (SSD's vs rotational) of the servers running swift. But the
relative numbers give a better picture of the benefits of:

i) Sharding across containers to increase throughput
ii) Restricting the number of objects per container

Let me know if I have missed out on anything or if there are more
experiments to run that would make Swift #awesome!!

-Shri



On Tue, Sep 3, 2013 at 7:47 AM, Chuck Thier  wrote:

> Hi Shri,
>
> The short answer is that sharding your data across containers in swift is
> generally a good idea.
>
> The limitations with containers has a lot more to do with overall
> concurrency rather than total objects in a container.  The number of
> objects in a container can have an affect on that, but will be less of an
> issue if you are not putting objects in at a high concurrency.
>
> --
> Chuck
>
>
> On Sun, Sep 1, 2013 at 9:39 PM, Shrinand Javadekar <
> shrin...@maginatics.com> wrote:
>
>> Hi,
>>
>> There have been several articles which talk about keeping the number of
>> objects in a container to about 1M. Beyond that sqlite starts becoming the
>> bottleneck. I am going to make sure we abide by this number.
>>
>> However, has anyone measured whether putting objects among multiple
>> containers right from the start gives any performance benefits. For e.g. I
>> could create 32 containers right at the start and split the objects among
>> these as I write more and more objects. In the average case, I would have
>> several partially filled containers instead of a few fully filled ones
>> (fully filled means having 1M objects). Would this be better for the
>> overall performance? Any downsides of this approach? Has anyone tried this
>> before and published numbers on this?
>>
>> Thanks in advance.
>> -Shri
>>
>>
>>
>> ___
>> 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] [Swift] Object expiration vs DELETE

[Morten Møller Riis]

Hehe, alright :)

Well, as their documentation says: 
http://www.rackspace.com/blog/rackspace-cloud-files-how-to-use-expiring-objects-api-functionality/

It should "just work" :) If it doesn't it's not an openstack issue but a 
rackspace issue ;) 

Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




On Oct 10, 2013, at 2:48 PM, Shrinand Javadekar  wrote:

> I am using Rackspace Cloudfiles-US. I don't have access to the actual storage 
> servers to find out if the expirer is running. 
> 
> But given that it is a publicly available object store, I would hope so :-).
> 
> -Shri
> 
> 
> On Wed, Oct 9, 2013 at 8:46 PM, Morten Møller Riis  wrote:
> Is the swift-object-expirer daemon running?
> 
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
> 
> 
> 
> 
> On Oct 10, 2013, at 2:28 PM, Shrinand Javadekar  
> wrote:
> 
>> Hi,
>> 
>> Objects in a swift container can be deleted by either explicitly deleting 
>> them or by setting a expiry timestamp on them. Is there a performance 
>> difference between the two? For example, when I want to delete an object, 
>> instead of deleting it, can I simply set the X-Delete-After attribute of 
>> that object to 0? Is one faster than the other? 
>> 
>> My guess is that setting the object expiry timestamp may be faster since 
>> that would only involve changing the xattrs of the object inode. Delete will 
>> require creation of a new version of the object, truncating it to a 0 byte 
>> file and renaming it to change the extension to ".ts". Seems like less work 
>> is done when object expiration is set.
>> 
>> To try this out, I tried setting the X-Delete-After attribute using the 
>> swift command line client:
>> 
>> $ swift post -m X-Delete-After: 1  
>> 
>> After I did this, when I stat the object, I see the attribute "Meta 
>> X-Delete-After: 1". However, the object never got deleted. Any idea what I'm 
>> doing wrong?
>> 
>> -Shri
>> ___
>> 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] [Swift] Object expiration vs DELETE

[Morten Møller Riis]

Is the swift-object-expirer daemon running?

Mvh / Best regards
Morten Møller Riis
Gigahost ApS
m...@gigahost.dk




On Oct 10, 2013, at 2:28 PM, Shrinand Javadekar  wrote:

> Hi,
> 
> Objects in a swift container can be deleted by either explicitly deleting 
> them or by setting a expiry timestamp on them. Is there a performance 
> difference between the two? For example, when I want to delete an object, 
> instead of deleting it, can I simply set the X-Delete-After attribute of that 
> object to 0? Is one faster than the other? 
> 
> My guess is that setting the object expiry timestamp may be faster since that 
> would only involve changing the xattrs of the object inode. Delete will 
> require creation of a new version of the object, truncating it to a 0 byte 
> file and renaming it to change the extension to ".ts". Seems like less work 
> is done when object expiration is set.
> 
> To try this out, I tried setting the X-Delete-After attribute using the swift 
> command line client:
> 
> $ swift post -m X-Delete-After: 1  
> 
> After I did this, when I stat the object, I see the attribute "Meta 
> X-Delete-After: 1". However, the object never got deleted. Any idea what I'm 
> doing wrong?
> 
> -Shri
> ___
> 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] [Swift] Object expiration vs DELETE

[Shrinand Javadekar]

I am using Rackspace Cloudfiles-US. I don't have access to the actual
storage servers to find out if the expirer is running.

But given that it is a publicly available object store, I would hope so :-).

-Shri


On Wed, Oct 9, 2013 at 8:46 PM, Morten Møller Riis  wrote:

> Is the swift-object-expirer daemon running?
>
> Mvh / Best regards
> Morten Møller Riis
> Gigahost ApS
> m...@gigahost.dk
>
>
>
>
> On Oct 10, 2013, at 2:28 PM, Shrinand Javadekar 
> wrote:
>
> Hi,
>
> Objects in a swift container can be deleted by either explicitly deleting
> them or by setting a expiry timestamp on them. Is there a performance
> difference between the two? For example, when I want to delete an object,
> instead of deleting it, can I simply set the X-Delete-After attribute of
> that object to 0? Is one faster than the other?
>
> My guess is that setting the object expiry timestamp may be faster since
> that would only involve changing the xattrs of the object inode. Delete
> will require creation of a new version of the object, truncating it to a 0
> byte file and renaming it to change the extension to ".ts". Seems like less
> work is done when object expiration is set.
>
> To try this out, I tried setting the X-Delete-After attribute using the
> swift command line client:
>
> $ swift post -m X-Delete-After: 1  
>
> After I did this, when I stat the object, I see the attribute "Meta
> X-Delete-After: 1". However, the object never got deleted. Any idea what
> I'm doing wrong?
>
> -Shri
> ___
> 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] [Swift] Object expiration vs DELETE

[Samuel Merritt]

On 10/9/13 8:28 PM, Shrinand Javadekar wrote:

Hi,

Objects in a swift container can be deleted by either explicitly
deleting them or by setting a expiry timestamp on them. Is there a
performance difference between the two? For example, when I want to
delete an object, instead of deleting it, can I simply set the
X-Delete-After attribute of that object to 0? Is one faster than the other?

My guess is that setting the object expiry timestamp may be faster since
that would only involve changing the xattrs of the object inode. Delete
will require creation of a new version of the object, truncating it to a
0 byte file and renaming it to change the extension to ".ts".


Deletion creates a 0-byte tombstone (.ts) file and unlinks the old 
object (the .data file).  It doesn't "creat[e] a new version of the 
object" only to truncate it.



Seems like
less work is done when object expiration is set.


Depends on whether or not object POST-as-copy is in use. If it is, then 
you'll wind up copying the entire object to change its metadata.


Default for that is on, BTW, so if you haven't turned it off, you're 
using it.


Further, setting X-Delete-At requires updating a container in the 
special .expiring_objects account. The object expirer periodically walks 
those containers and deletes objects that have expired, so now you've 
got a full copy of the whole object *plus* a container update.


For large objects with POST-as-copy turned off, it might be faster to 
set X-Delete-At, but it is definitely more work for the cluster. If 
POST-as-copy is on, setting X-Delete-At will take longer than issuing a 
DELETE request *and* it'll be more work for the cluster.


Also note that setting X-Delete-At doesn't guarantee that your object is 
really deleted at that time. Requests for that object will get 404s 
after that time, but the disk space won't be reclaimed, nor will the 
container listing be updated, until the object expirer gets around to 
actually deleting the object.



To try this out, I tried setting the X-Delete-After attribute using the
swift command line client:

$ swift post -m X-Delete-After: 1  

After I did this, when I stat the object, I see the attribute "Meta
X-Delete-After: 1". However, the object never got deleted. Any idea what
I'm doing wrong?


The -m flag sets metadata on the object; metadata headers are prefaced 
by X-Object-Meta. The above command actually sent the header 
X-Object-Meta-X-Delete-After: 1, which does not trigger object expiration.



___
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] [Swift] Object expiration vs DELETE

[Shrinand Javadekar]

Hi,

Objects in a swift container can be deleted by either explicitly deleting
them or by setting a expiry timestamp on them. Is there a performance
difference between the two? For example, when I want to delete an object,
instead of deleting it, can I simply set the X-Delete-After attribute of
that object to 0? Is one faster than the other?

My guess is that setting the object expiry timestamp may be faster since
that would only involve changing the xattrs of the object inode. Delete
will require creation of a new version of the object, truncating it to a 0
byte file and renaming it to change the extension to ".ts". Seems like less
work is done when object expiration is set.

To try this out, I tried setting the X-Delete-After attribute using the
swift command line client:

$ swift post -m X-Delete-After: 1  

After I did this, when I stat the object, I see the attribute "Meta
X-Delete-After: 1". However, the object never got deleted. Any idea what
I'm doing wrong?

-Shri
___
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] Outreach Program for Women

[Chalani Ediriweera]

Hi all,
I would like to participate Outreach Program for Women under OpenStack. I
am interested about "deploying a free software conferencing systems for
OpenStack" project. Can anyone please give me more details on this project?

Thank you.
Chalani Ediriweera,
University of Ruhuna,
Sri Lanka.
___
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] What Exactly Flavor Work?

[Mahardhika Gilang]

Alright, i'll give it try, thanks for both of you. will update soon.
On 10/9/2013 9:32 PM, Bob Ball wrote:


Yes, just to confirm the XenAPI driver will automatically resize disks 
where it can without needing an agent / cloud-init installed in the VM.


It does this by mounting the disk in the domain running nova and 
resizing the filesystem/device.


Bob

*From:*Joe Topjian [mailto:joe.topj...@cybera.ca]
*Sent:* 09 October 2013 14:52
*To:* Tom Fifield
*Cc:* openstack@lists.openstack.org
*Subject:* Re: [Openstack] What Exactly Flavor Work?

My understanding is that automatic resize will occur if the
following are all true:
* auto_disk_config=True is set as a property on the image in the
Image Registry.
* The disk on the image has only one partition.
* The file system on the one partition is ext3 or ext4.

I think Xen provides some extra help in this area by doing the resize 
itself (I *think*). KVM defers the job to the user.


There was a long discussion on the openstack-operators list about 
building CentOS images:


http://www.gossamer-threads.com/lists/openstack/operators/25790

The td;dr version would be this post where I link to some scripts that 
are able to build a complete CentOS image that resizes as you would 
expect:


http://www.gossamer-threads.com/lists/openstack/operators/28733#28733

Hope that helps,

Joe

--

Joe Topjian

Systems Architect

Cybera Inc.

www.cybera.ca 

Cybera is a not-for-profit organization that works to spur and support 
innovation, for the economic benefit of Alberta, through the use 
of cyberinfrastructure.




___
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



--
Regards,
Mahardhika Gilang

*PT. Andalabs Technology *
Gedung Gravira
Jl. Cideng Barat no. 54
Jakarta Pusat 10150

Mobile : 0852 139 55861
Email : mahardika.gil...@andalabs.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] Connection between VMS

[Guilherme Russi]

Hello Rick,

Here is the command:

ubuntu@small-vm02:~$ ssh ubuntu@small-vm03
ssh: Could not resolve hostname small-vm03: Name or service not known

My point is, I have my cloud-vm01 with IP 10.5.5.3 and I want ssh to my
cloud-vm02 with IP 10.5.5.4, but I can't simply do "ssh ubuntu@10.5.5.4"
because the IP 10.5.5.4 can be attached to my cloud-vm03, for example, so,
I want to know if there's a way to ssh using "ssh ubuntu@cloud-vm02"


Regards.


2013/10/9 Rick Jones 

> On 10/09/2013 05:32 PM, Guilherme Russi wrote:
>
>> Hello guys,
>>
>>   I have some VMs and I'd like to connect them through their name, for
>> example, my VMs are named cloud-vm01 to cloud-vmn but I can't ssh from
>> cloud-vm01 in cloud-vm02 doing "ssh user@cloud-vm01".
>>   How can I workaround it?
>>
>
> When you say "can't ssh" can you be a bit more explicit?  What sort of
> error message do you get when you try to ssh?  The answer to that will
> probably guide responses.
>
> rick jones
>
___
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] Connection between VMS

[Rick Jones]

On 10/09/2013 05:32 PM, Guilherme Russi wrote:

Hello guys,

  I have some VMs and I'd like to connect them through their name, for
example, my VMs are named cloud-vm01 to cloud-vmn but I can't ssh from
cloud-vm01 in cloud-vm02 doing "ssh user@cloud-vm01".
  How can I workaround it?


When you say "can't ssh" can you be a bit more explicit?  What sort of 
error message do you get when you try to ssh?  The answer to that will 
probably guide responses.


rick jones

___
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] "nova list" returns nothing

[Clement Buisson]

Did anyone experience the same issue?


On Wed, Oct 2, 2013 at 11:52 PM, Rami Vaknin  wrote:

>  On 10/03/2013 03:12 AM, Clement Buisson wrote:
>
> All these variables are correct, I just double checked them.
> This is really strange because it was working fine and stopped working all
> of the sudden!
>
>
> Your request says that you're not using the admin project (tenant):
> "X-Auth-Project-Id: main"
> It should be:
> "X-Auth-Project-Id: admin"
>
>
>
>
>  On Wed, Oct 2, 2013 at 3:31 PM, Gangur, Hrushikesh (R & D HP Cloud) <
> hrushikesh.gan...@hp.com> wrote:
>
>>  Ensure these environment variable is set correctly. My guess is that
>> your environment variable must be pointing to a different project:
>>
>>
>>
>> export OS_USERNAME=Admin
>>
>  export OS_PASSWORD=secretword
>>
>> export OS_TENANT_NAME=AdminProject
>>
>> export OS_AUTH_URL=http://:5000/v2.0/
>>
>> export OS_AUTH_STRATEGY=keystone
>>
>>
>>
>> *From:* Clement Buisson [mailto:clement.buis...@lookout.com]
>> *Sent:* Wednesday, October 02, 2013 3:06 PM
>> *To:* rvak...@redhat.com
>> *Cc:* openstack
>> *Subject:* Re: [Openstack] "nova list" returns nothing
>>
>>
>>
>> Hi Rami,
>>
>>
>>
>> I checked in Nova DB and I can see all my instances there (select * from
>> instances). On my compute nodes, I ran virsh list --all (got list for kvm
>> instances) and pgrep kvm (got list of pids) and I got valid information
>> about my instances.
>>
>>
>>
>> I am also running these commands from the Nova-API server.
>>
>> I tried your curl idea and here is the result:
>>
>>
>>
>> curl -i http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers-X 
>> GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H
>> "Accept: application/json" -H "X-Auth-Token:
>> 9b7d9b07f5b14793b1d24c5ca42bedd2"
>>
>>
>>
>> HTTP/1.1 200 OK
>>
>> X-Compute-Request-Id: req-9847157c-9d54-42fc-b5d0-3d46be491ef6
>>
>> Content-Type: application/json
>>
>> Content-Length: 15
>>
>> Date: Wed, 02 Oct 2013 22:01:13 GMT
>>
>>
>>
>> {"servers": []}
>>
>>
>>
>> So weird that this array is returning empty data...
>>
>> nova-api must be confused!
>>
>>
>>
>> Thoughts?
>>
>>
>>
>> On Wed, Oct 2, 2013 at 12:37 PM, Rami Vaknin  wrote:
>>
>> On 10/02/2013 09:35 PM, Clement Buisson wrote:
>>
>>  Hello,
>>
>> I am a Folsom user, I have been using the "nova list" command for a while
>> until couple weeks ago.
>> That command use to work just fine and one day it just stopped working.
>> I can run the command but nothing will show up.
>>
>> Here is the output of my command:
>>
>> nova --debug list
>>
>> REQ: curl -i
>> http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail-X 
>> GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H
>> "Accept: application/json" -H "X-Auth-Token:
>> f03bbc13f258473ab53399e3541a8e70"
>>
>> connect: (127.0.0.1, 8774)
>> send: u'GET /v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail
>> HTTP/1.1\r\nHost: 127.0.0.1:8774\r\nx-auth-project-id:
>> main\r\nx-auth-token: f03bbc13f258473ab53399e3541a8e70\r\naccept-encoding:
>> gzip, deflate\r\naccept: application/json\r\nuser-agent:
>> python-novaclient\r\n\r\n'
>> reply: 'HTTP/1.1 200 OK\r\n'
>> header: X-Compute-Request-Id: req-002a752b-2f47-4cda-8f91-b9a822ef754b
>> header: Content-Type: application/json
>> header: Content-Length: 15
>> header: Date: Thu, 26 Sep 2013 18:07:05 GMT
>> RESP:{'status': '200', 'content-length': '15', 'content-location': u'
>> http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail',
>> 'x-compute-request-id': 'req-002a752b-2f47-4cda-8f91-b9a822ef754b', 'date':
>> 'Thu, 26 Sep 2013 18:07:05 GMT', 'content-type': 'application/json'}
>> {"servers": []}
>>
>> I also tried with the option "all-tenant":
>>
>> nova --debug list --all-tenants
>>
>> REQ: curl -i
>> http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1-X
>>  GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H
>> "Accept: application/json" -H "X-Auth-Token:
>> 9b7d9b07f5b14793b1d24c5ca42bedd2"
>> connect: (127.0.0.1, 8774)
>> send: u'GET
>> /v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1
>> HTTP/1.1\r\nHost: 127.0.0.1:8774\r\nx-auth-project-id:
>> main\r\nx-auth-token: 9b7d9b07f5b14793b1d24c5ca42bedd2\r\naccept-encoding:
>> gzip, deflate\r\naccept: application/json\r\nuser-agent:
>> python-novaclient\r\n\r\n'
>> reply: 'HTTP/1.1 200 OK\r\n'
>> header: X-Compute-Request-Id: req-50e187e8-74b0-4342-a400-b364a61748e1
>> header: Content-Type: application/json
>> header: Content-Length: 15
>> header: Date: Wed, 02 Oct 2013 18:32:44 GMT
>> RESP:{'status': '200', 'content-length': '15', 'content-location': u'
>> http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1',
>> 'x-compute-request-id': 'req-50e187e8-74b0-4342-a400-b364a61748e1', 'date':
>> 'Wed, 02 Oct 2013 18:32:44 GMT', 'content-type': 'application/json'}
>> {"servers": []}
>>
>> Same thing with euca2ools:
>>
>> euca-d

Re: [Openstack] "nova list" returns nothing

[Gangur, Hrushikesh (R & D HP Cloud)]

Do you see any error message is nova-api.log or api.log?

From: Clement Buisson [mailto:clement.buis...@lookout.com]
Sent: Wednesday, October 09, 2013 5:33 PM
To: rvak...@redhat.com
Cc: Gangur, Hrushikesh (R & D HP Cloud); openstack
Subject: Re: [Openstack] "nova list" returns nothing

Did anyone experience the same issue?

On Wed, Oct 2, 2013 at 11:52 PM, Rami Vaknin 
mailto:rvak...@redhat.com>> wrote:
On 10/03/2013 03:12 AM, Clement Buisson wrote:
All these variables are correct, I just double checked them.
This is really strange because it was working fine and stopped working all of 
the sudden!

Your request says that you're not using the admin project (tenant):
"X-Auth-Project-Id: main"
It should be:
"X-Auth-Project-Id: admin"




On Wed, Oct 2, 2013 at 3:31 PM, Gangur, Hrushikesh (R & D HP Cloud) 
mailto:hrushikesh.gan...@hp.com>> wrote:
Ensure these environment variable is set correctly. My guess is that your 
environment variable must be pointing to a different project:

export OS_USERNAME=Admin
export OS_PASSWORD=secretword
export OS_TENANT_NAME=AdminProject
export OS_AUTH_URL=http://:5000/v2.0/
export OS_AUTH_STRATEGY=keystone

From: Clement Buisson 
[mailto:clement.buis...@lookout.com]
Sent: Wednesday, October 02, 2013 3:06 PM
To: rvak...@redhat.com
Cc: openstack
Subject: Re: [Openstack] "nova list" returns nothing

Hi Rami,

I checked in Nova DB and I can see all my instances there (select * from 
instances). On my compute nodes, I ran virsh list --all (got list for kvm 
instances) and pgrep kvm (got list of pids) and I got valid information about 
my instances.

I am also running these commands from the Nova-API server.
I tried your curl idea and here is the result:

curl -i http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers -X 
GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H "Accept: 
application/json" -H "X-Auth-Token: 9b7d9b07f5b14793b1d24c5ca42bedd2"

HTTP/1.1 200 OK
X-Compute-Request-Id: req-9847157c-9d54-42fc-b5d0-3d46be491ef6
Content-Type: application/json
Content-Length: 15
Date: Wed, 02 Oct 2013 22:01:13 GMT

{"servers": []}

So weird that this array is returning empty data...
nova-api must be confused!

Thoughts?

On Wed, Oct 2, 2013 at 12:37 PM, Rami Vaknin 
mailto:rvak...@redhat.com>> wrote:
On 10/02/2013 09:35 PM, Clement Buisson wrote:

Hello,

I am a Folsom user, I have been using the "nova list" command for a while until 
couple weeks ago.
That command use to work just fine and one day it just stopped working.
I can run the command but nothing will show up.

Here is the output of my command:

nova --debug list

REQ: curl -i 
http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail -X GET 
-H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H "Accept: 
application/json" -H "X-Auth-Token: f03bbc13f258473ab53399e3541a8e70"

connect: (127.0.0.1, 8774)
send: u'GET /v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail 
HTTP/1.1\r\nHost: 127.0.0.1:8774\r\nx-auth-project-id: 
main\r\nx-auth-token: f03bbc13f258473ab53399e3541a8e70\r\naccept-encoding: 
gzip, deflate\r\naccept: application/json\r\nuser-agent: 
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-002a752b-2f47-4cda-8f91-b9a822ef754b
header: Content-Type: application/json
header: Content-Length: 15
header: Date: Thu, 26 Sep 2013 18:07:05 GMT
RESP:{'status': '200', 'content-length': '15', 'content-location': 
u'http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail',
 'x-compute-request-id': 'req-002a752b-2f47-4cda-8f91-b9a822ef754b', 'date': 
'Thu, 26 Sep 2013 18:07:05 GMT', 'content-type': 'application/json'} 
{"servers": []}

I also tried with the option "all-tenant":
nova --debug list --all-tenants

REQ: curl -i 
http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1
 -X GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H 
"Accept: application/json" -H "X-Auth-Token: 9b7d9b07f5b14793b1d24c5ca42bedd2"
connect: (127.0.0.1, 8774)
send: u'GET /v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1 
HTTP/1.1\r\nHost: 127.0.0.1:8774\r\nx-auth-project-id: 
main\r\nx-auth-token: 9b7d9b07f5b14793b1d24c5ca42bedd2\r\naccept-encoding: 
gzip, deflate\r\naccept: application/json\r\nuser-agent: 
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-50e187e8-74b0-4342-a400-b364a61748e1
header: Content-Type: application/json
header: Content-Length: 15
header: Date: Wed, 02 Oct 2013 18:32:44 GMT
RESP:{'status': '200', 'content-length': '15', 'content-location': 
u'http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1',
 'x-compute-request-id': 'req-50e187e8-74b0-4342-a400-b364a61748e1', 'date': 
'Wed, 02 Oct 20

[Openstack] Connection between VMS

[Guilherme Russi]

Hello guys,

 I have some VMs and I'd like to connect them through their name, for
example, my VMs are named cloud-vm01 to cloud-vmn but I can't ssh from
cloud-vm01 in cloud-vm02 doing "ssh user@cloud-vm01".
 How can I workaround it?

Regards.

Guilherme.
___
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 support for passthrough of networking devices?

[Jiang, Yunhong]

Several thing in my mind:
a) NIC need more information like the switch, and these information need be 
managed by nova also. We have basic support, but not fully implemented.
b) How to setup the device, including the mac address or 802.1Qbh etc. Libvirt 
have several option to support it, need more work to support them, also need 
consider other virt driver like xenapi etc.
c) How to achieve the isolation of tenants, and how to setup like the router in 
Neutron. I'm not well on Neutron, but I think others may have more idea on it.

Thanks
--jyh

> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: Wednesday, October 09, 2013 11:53 AM
> To: openstack@lists.openstack.org
> Subject: Re: [Openstack] Neutron support for passthrough of networking
> devices?
> 
> On 10/09/2013 12:31 PM, Jiang, Yunhong wrote:
> > When we worked on H release, we target for basic PCI support like
> > accelerator card or encryption card etc. I think SR-IOV network
> > support is more complex and requires more effort, in both Nova side
> > and Neutron side. We are working on some enhancement in Nova side
> > now. But the whole picture may need more time/discussion.
> 
> Can you elaborate on the complexities?  Assuming you enable SR-IOV on
> the host, and pass it through to the guest using the normal PCI
> passthrough mechanisms, what's the extra complexity?
> 
> Do we run into the same complexity if we have spare physical NICs on the
> host that get passed in to the guest?
> 
> Thanks,
> Chris
> 
> ___
> 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] publicurl definition in keystone

[Martinx - ジェームズ]

Hi Xin,

I don't know if it can help you out but, I'm using "Name Resolution" for
all my OpenStack services, this means that doesn't matter the IP of the
endpoint, even if it is IPv4 or IPv6, it will work out-of-the-box (in most
of my tests)...

So, when people tries to resolve your Quantum endpoint from the Internet,
you'll provide your ISP IP and, with a NAT rule at your firewall, you'll
redirect it (DNAT) to the internal-only endpoint IP address. And, when
people tries to resolve the endpoint from within your network, you should
provide your internal IP for them.

I can say that: it works for me.


Please, check my Keystone scripts (you can see where I use Name Resolution
instead of IPs):

wget
https://gist.github.com/tmartinx/5453358/raw/f132d27eeab0c3c25d5b3e65bfec6704503e84b6/keystone_basic.sh

wget
https://gist.github.com/tmartinx/5453336/raw/eded917b78213123c46b62be18f55f3c7aac558e/keystone_endpoints_basic.sh


NOTE: When with IPv6, this is much more easy to achieve, since there is no
need to deal with creepy NAT rules. Which means that your endpoints will
always have a public IP address (if you have IPv6). Keep it in mind!


Cheers!
Thiago


On 9 October 2013 12:28, Xin Zhao  wrote:

>  Thanks for all the reply.
>
> One more question though: when defining endpoint for network service, the
> IP should be for the network host, not the controller host (we have them in
> separate hosts, as most doc suggest).
> But the network host doesn't have a single out-facing IP assigned to it,
> the doc says the out-facing NIC should have a range of IPs assigned to it
> from the external provider network. In this case,
> how to define the publicurl for the quantum service endpoint? If the info
> of endpoints is only used by the other openstack components, can I just put
> the internal IP in for the publicurl ?
>
> Thanks,
> Xin
>
>
> On 10/7/2013 12:07 PM, JuanFra Rodriguez Cardoso wrote:
>
> Yes, internal and adminurl are normally the same address.
>
>  ---
> JuanFra
>
>
> 2013/10/7 Razique Mahroua 
>
>> Hi,
>> yes :)
>> Internal and adminiurl should be the private network, and "public" the
>> "out-facing" IP
>>
>> Razique
>>
>> Le 7 oct. 2013 à 17:30, Xin Zhao  a écrit :
>>
>> > Hello,
>> >
>> > Our openstack controller has two IPs, one out-facing, the other is
>> internal only (on the management network).
>> > When it comes to define service endpoints in keystone, the publicurl
>> entry should be the out-facing IP, and the
>> > internalurl and adminurl should be the internal IP, right?
>> >
>> > Thanks,
>> > Xin
>> >
>> > ___
>> > 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
>
>
___
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] Question

[Sean Mann]

Hi All,

I am new in OpenStack and installing it on Fidora. I am using Oracle
VirtualBox as a virtual machine to run Fidora.

I run the following shell script:

cd devstack; ./stack.sh

What happens is in the middle of installation it hangs at:

nova x509-get-root-cert /home/sean/devstack/accrc/cacert.pem


I had also a report in Fodora as :

Process /usr/bin/tgtd was killed by Signal 6 (SIGABRT). I am not sure if
the 2 are relavant.

I need someone's help to be able to proceed with installation.

Thanks,

Sean Mann


On Wed, Oct 9, 2013 at 9:38 AM, Sean Mann  wrote:

>
> Hi All,
>
> I am new in OpenStack and installing it on Fidora. I am using Oracle
> VirtualBox as a virtual machine to run Fidora.
>
> I run the following shell script:
>
> cd devstack; ./stack.sh
>
> What happens is in the middle of installation it hangs at:
>
> nova x509-get-root-cert /home/sean/devstack/accrc/cacert.pem
>
>
> I had also a report in Fodora as :
>
> Process /usr/bin/tgtd was killed by Signal 6 (SIGABRT). I am not sure if
> the 2 are relavant.
>
> I need someone's help to be able to proceed with installation.
>
> Thanks,
>
> Sean Mann
>
>
>
>
> cd devstack; ./stack.sh
>
>
___
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 support for passthrough of networking devices?

[Chris Friesen]

On 10/09/2013 12:31 PM, Jiang, Yunhong wrote:

When we worked on H release, we target for basic PCI support like
accelerator card or encryption card etc. I think SR-IOV network
support is more complex and requires more effort, in both Nova side
and Neutron side. We are working on some enhancement in Nova side
now. But the whole picture may need more time/discussion.


Can you elaborate on the complexities?  Assuming you enable SR-IOV on 
the host, and pass it through to the guest using the normal PCI 
passthrough mechanisms, what's the extra complexity?


Do we run into the same complexity if we have spare physical NICs on the 
host that get passed in to the guest?


Thanks,
Chris

___
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] Quantum dhcp-agent getting out of sync with multiple instance launch / termination

[Édouard Thuleau]

There is also this opening bug:
https://bugs.launchpad.net/neutron/+bug/1185916

I proposed a patch: https://review.openstack.org/#/c/40654/ (I don't know
why it wasn't automatically linked to the launchpad bug! )

I'm waiting feedback/review from core developers.

Regards,
Édouard.



On Wed, Oct 9, 2013 at 4:15 PM, Gary Kotton  wrote:

> Hi,
> There was a bug that was related that was fixed a number of months ago -
> https://bugs.launchpad.net/neutron/+bug/1191768. I suggest that one of the
> guys working on RDO take a look.
> Thanks
> Gary
>
> On 10/9/13 4:57 PM, "Markku Tavasti"  wrote:
>
> >We are running grizzly-based, RedHat RDO.
> >
> >--Tavasti
> >
> >On 10/09/2013 04:50 PM, Gary Kotton wrote:
> >> Hi,
> >> Which version are you using?
> >> Thanks
> >> Gary
> >>
> >> On 10/9/13 4:34 PM, "Markku Tavasti" 
> >>wrote:
> >>
> >>> I found out that quantum dhcp agent gets out of sync when many
> >>>instances
> >>> are launched or deleted same time. As a result, dnsmasq host-file have
> >>> lines missing (all launched are not added), or some lines aren't
> >>>removed
> >>> when they should. When same ip is re-used, remaining extra lines aren't
> >>> removed, but same ip has two lines, and dhcp discoveries get no
> >>>response
> >>> (no address available error on dnsmasq logs).
> >>>
> >>> Restarting quantum-dhcp-agent will get everything back to proper state,
> >>> but running restart on cron every minute does not sound proper fix :-(
> >>>
> >>> On my test, creating 16 instances, 2-3 of them did not get line in
> >>> host-file. When removing all those 16, 3-5 false lines were left
> >>>behind.
> >>>
> >>> On instance creation I see following message on quantum-server.log:
> >>>
> >>> For every instance:
> >>> WARNING [quantum.db.agentschedulers_db] Fail scheduling network
> >>> {'status': u'ACTIVE', 'subnets':
> >>> [u'e9299278-bd49-4dc8-8df1-25b034f3ecea'], 'name': u'pk_tunk2',
> >>> 'provider:physical_network': u'vlans-osprv', 'admin_state_up': True,
> >>> 'tenant_id': u'06b9c423e10741ef83877b56d7608d7f',
> >>> 'provider:network_type': u'vlan', 'router:external': False, 'shared':
> >>> False, 'id': u'cbce52ef-58ba-4f3c-96fb-9d51bdbf32fb',
> >>> 'provider:segmentation_id': 427L}
> >>> However, network ports get created, and seems to work?
> >>>
> >>> And most likely related to missing lines on host file on creation:
> >>> WARNING [quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents
> >>>
> >>> For termination of instances there is no warning or error messages.
> >>>
> >>> Any ideas for fixing the situation?
> >>>
> >>> --Tavasti
> >>>
> >>>
> >>> ___
> >>> 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] Neutron support for passthrough of networking devices?

[Jiang, Yunhong]

When we worked on H release, we target for basic PCI support like accelerator 
card or encryption card etc. I think SR-IOV network support is more complex and 
requires more effort, in both Nova side and Neutron side. We are working on 
some enhancement in Nova side now. But the whole picture may need more 
time/discussion.

Thanks
--jyh

> -Original Message-
> From: Steve Gordon [mailto:sgor...@redhat.com]
> Sent: Wednesday, October 09, 2013 6:56 AM
> To: openstack@lists.openstack.org
> Subject: [Openstack] Neutron support for passthrough of networking
> devices?
> 
> Hi all,
> 
> I notice that late in the Havana cycle support for PCI passthrough of
> devices was added to Nova [1][2] (very cool!), I'm wondering if there is any
> support in Neutron for managing the networking for a device that is
> dedicated to a guest using passthrough (in particular devices that support
> SR-IOV)?
> 
> Thanks!
> 
> [1] https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base
> [2] https://blueprints.launchpad.net/nova/+spec/pci-passthrough-libvirt
> 
> ___
> 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] publicurl definition in keystone

[Xin Zhao]

Thanks for all the reply.

One more question though: when defining endpoint for network service, 
the IP should be for the network host, not the controller host (we have 
them in separate hosts, as most doc suggest).
But the network host doesn't have a single out-facing IP assigned to it, 
the doc says the out-facing NIC should have a range of IPs assigned to 
it from the external provider network. In this case,
how to define the publicurl for the quantum service endpoint? If the 
info of endpoints is only used by the other openstack components, can I 
just put the internal IP in for the publicurl ?


Thanks,
Xin

On 10/7/2013 12:07 PM, JuanFra Rodriguez Cardoso wrote:

Yes, internal and adminurl are normally the same address.

---
JuanFra


2013/10/7 Razique Mahroua >


Hi,
yes :)
Internal and adminiurl should be the private network, and "public"
the "out-facing" IP

Razique

Le 7 oct. 2013 à 17:30, Xin Zhao mailto:xz...@bnl.gov>> a écrit :

> Hello,
>
> Our openstack controller has two IPs, one out-facing, the other
is internal only (on the management network).
> When it comes to define service endpoints in keystone, the
publicurl entry should be the out-facing IP, and the
> internalurl and adminurl should be the internal IP, right?
>
> Thanks,
> Xin
>
> ___
> 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] Quantum dhcp-agent getting out of sync with multiple instance launch / termination

[Markku Tavasti]

We are running grizzly-based, RedHat RDO.

--Tavasti

On 10/09/2013 04:50 PM, Gary Kotton wrote:

Hi,
Which version are you using?
Thanks
Gary

On 10/9/13 4:34 PM, "Markku Tavasti"  wrote:


I found out that quantum dhcp agent gets out of sync when many instances
are launched or deleted same time. As a result, dnsmasq host-file have
lines missing (all launched are not added), or some lines aren't removed
when they should. When same ip is re-used, remaining extra lines aren't
removed, but same ip has two lines, and dhcp discoveries get no response
(no address available error on dnsmasq logs).

Restarting quantum-dhcp-agent will get everything back to proper state,
but running restart on cron every minute does not sound proper fix :-(

On my test, creating 16 instances, 2-3 of them did not get line in
host-file. When removing all those 16, 3-5 false lines were left behind.

On instance creation I see following message on quantum-server.log:

For every instance:
WARNING [quantum.db.agentschedulers_db] Fail scheduling network
{'status': u'ACTIVE', 'subnets':
[u'e9299278-bd49-4dc8-8df1-25b034f3ecea'], 'name': u'pk_tunk2',
'provider:physical_network': u'vlans-osprv', 'admin_state_up': True,
'tenant_id': u'06b9c423e10741ef83877b56d7608d7f',
'provider:network_type': u'vlan', 'router:external': False, 'shared':
False, 'id': u'cbce52ef-58ba-4f3c-96fb-9d51bdbf32fb',
'provider:segmentation_id': 427L}
However, network ports get created, and seems to work?

And most likely related to missing lines on host file on creation:
WARNING [quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents

For termination of instances there is no warning or error messages.

Any ideas for fixing the situation?

--Tavasti


___
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] What Exactly Flavor Work?

[Bob Ball]

Yes, just to confirm the XenAPI driver will automatically resize disks where it 
can without needing an agent / cloud-init installed in the VM.

It does this by mounting the disk in the domain running nova and resizing the 
filesystem/device.

Bob

From: Joe Topjian [mailto:joe.topj...@cybera.ca]
Sent: 09 October 2013 14:52
To: Tom Fifield
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] What Exactly Flavor Work?


My understanding is that automatic resize will occur if the following are all 
true:
* auto_disk_config=True is set as a property on the image in the Image Registry.
* The disk on the image has only one partition.
* The file system on the one partition is ext3 or ext4.

I think Xen provides some extra help in this area by doing the resize itself (I 
*think*). KVM defers the job to the user.

There was a long discussion on the openstack-operators list about building 
CentOS images:

http://www.gossamer-threads.com/lists/openstack/operators/25790

The td;dr version would be this post where I link to some scripts that are able 
to build a complete CentOS image that resizes as you would expect:

http://www.gossamer-threads.com/lists/openstack/operators/28733#28733

Hope that helps,
Joe


--
Joe Topjian
Systems Architect
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support 
innovation, for the economic benefit of Alberta, through the use of 
cyberinfrastructure.
___
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] Quantum dhcp-agent getting out of sync with multiple instance launch / termination

[Gary Kotton]

Hi,
There was a bug that was related that was fixed a number of months ago -
https://bugs.launchpad.net/neutron/+bug/1191768. I suggest that one of the
guys working on RDO take a look.
Thanks
Gary

On 10/9/13 4:57 PM, "Markku Tavasti"  wrote:

>We are running grizzly-based, RedHat RDO.
>
>--Tavasti
>
>On 10/09/2013 04:50 PM, Gary Kotton wrote:
>> Hi,
>> Which version are you using?
>> Thanks
>> Gary
>>
>> On 10/9/13 4:34 PM, "Markku Tavasti" 
>>wrote:
>>
>>> I found out that quantum dhcp agent gets out of sync when many
>>>instances
>>> are launched or deleted same time. As a result, dnsmasq host-file have
>>> lines missing (all launched are not added), or some lines aren't
>>>removed
>>> when they should. When same ip is re-used, remaining extra lines aren't
>>> removed, but same ip has two lines, and dhcp discoveries get no
>>>response
>>> (no address available error on dnsmasq logs).
>>>
>>> Restarting quantum-dhcp-agent will get everything back to proper state,
>>> but running restart on cron every minute does not sound proper fix :-(
>>>
>>> On my test, creating 16 instances, 2-3 of them did not get line in
>>> host-file. When removing all those 16, 3-5 false lines were left
>>>behind.
>>>
>>> On instance creation I see following message on quantum-server.log:
>>>
>>> For every instance:
>>> WARNING [quantum.db.agentschedulers_db] Fail scheduling network
>>> {'status': u'ACTIVE', 'subnets':
>>> [u'e9299278-bd49-4dc8-8df1-25b034f3ecea'], 'name': u'pk_tunk2',
>>> 'provider:physical_network': u'vlans-osprv', 'admin_state_up': True,
>>> 'tenant_id': u'06b9c423e10741ef83877b56d7608d7f',
>>> 'provider:network_type': u'vlan', 'router:external': False, 'shared':
>>> False, 'id': u'cbce52ef-58ba-4f3c-96fb-9d51bdbf32fb',
>>> 'provider:segmentation_id': 427L}
>>> However, network ports get created, and seems to work?
>>>
>>> And most likely related to missing lines on host file on creation:
>>> WARNING [quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents
>>>
>>> For termination of instances there is no warning or error messages.
>>>
>>> Any ideas for fixing the situation?
>>>
>>> --Tavasti
>>>
>>>
>>> ___
>>> 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] Neutron ML2 configuration

[Leandro Reox]

Hi all im looking for a configuration guide for the neutron ml2 framework
plugin. On the wiki its only documented for Devstack and i want to know all
the config changes i need to do to neutron to use this king of plugins for
us to allow use mech_drivers for our arista switches

Best

Lean
___
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] Change parameters of kvm in openstack

[laclasse]

However, if removing the '--device' line boots the machine successfully,
you might want to simply check if your init ramfs (of the guest) has a
virtio block driver module included (doesn't seems so), include it (might
as well include the virtio network module) and rebuild it on your SuSE
image.

See this:
http://doc.opensuse.org/products/draft/SLES/SLES-admin_sd_draft/cha.boot.html#sec.boot.initrd






On Wed, Oct 9, 2013 at 12:00 PM, Jeff Cai  wrote:

> Hi,
>
> ** **
>
> When I boot a suse linux instance, it reports that “’system’ volume group
> not found”, I found that if I remove the ‘-device’ line in kvm command
> line, it can start successfully.
>
> Could you tell me how to change the parameters of ‘kvm’ in openstack?
>
> ** **
>
> Following is the command line that starts my instance:
>
> ** **
>
> ** **
>
> /usr/bin/kvm ….
>
> -drive
> file=/var/lib/nova/instances/582db50e-56cf-4541-8078-4329b8578d71/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
> 
>
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> 
>
> …
>
> ** **
>
> Best Regards
>
> * *
>
> *Jeff Cai*
>
> *
>
> *
>
> ** **
>
> ___
> 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] Neutron support for passthrough of networking devices?

[Steve Gordon]

Hi all,

I notice that late in the Havana cycle support for PCI passthrough of devices 
was added to Nova [1][2] (very cool!), I'm wondering if there is any support in 
Neutron for managing the networking for a device that is dedicated to a guest 
using passthrough (in particular devices that support SR-IOV)?

Thanks! 

[1] https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base
[2] https://blueprints.launchpad.net/nova/+spec/pci-passthrough-libvirt

___
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] Quantum dhcp-agent getting out of sync with multiple instance launch / termination

[Gary Kotton]

Hi,
Which version are you using?
Thanks
Gary

On 10/9/13 4:34 PM, "Markku Tavasti"  wrote:

>I found out that quantum dhcp agent gets out of sync when many instances
>are launched or deleted same time. As a result, dnsmasq host-file have
>lines missing (all launched are not added), or some lines aren't removed
>when they should. When same ip is re-used, remaining extra lines aren't
>removed, but same ip has two lines, and dhcp discoveries get no response
>(no address available error on dnsmasq logs).
>
>Restarting quantum-dhcp-agent will get everything back to proper state,
>but running restart on cron every minute does not sound proper fix :-(
>
>On my test, creating 16 instances, 2-3 of them did not get line in
>host-file. When removing all those 16, 3-5 false lines were left behind.
>
>On instance creation I see following message on quantum-server.log:
>
>For every instance:
>WARNING [quantum.db.agentschedulers_db] Fail scheduling network
>{'status': u'ACTIVE', 'subnets':
>[u'e9299278-bd49-4dc8-8df1-25b034f3ecea'], 'name': u'pk_tunk2',
>'provider:physical_network': u'vlans-osprv', 'admin_state_up': True,
>'tenant_id': u'06b9c423e10741ef83877b56d7608d7f',
>'provider:network_type': u'vlan', 'router:external': False, 'shared':
>False, 'id': u'cbce52ef-58ba-4f3c-96fb-9d51bdbf32fb',
>'provider:segmentation_id': 427L}
>However, network ports get created, and seems to work?
>
>And most likely related to missing lines on host file on creation:
>WARNING [quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents
>
>For termination of instances there is no warning or error messages.
>
>Any ideas for fixing the situation?
>
>--Tavasti
>
>
>___
>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] What Exactly Flavor Work?

[Joe Topjian]

> My understanding is that automatic resize will occur if the following are
> all true:
> * auto_disk_config=True is set as a property on the image in the Image
> Registry.
> * The disk on the image has only one partition.
> * The file system on the one partition is ext3 or ext4.
>

I think Xen provides some extra help in this area by doing the resize
itself (I *think*). KVM defers the job to the user.

There was a long discussion on the openstack-operators list about building
CentOS images:

http://www.gossamer-threads.com/lists/openstack/operators/25790

The td;dr version would be this post where I link to some scripts that are
able to build a complete CentOS image that resizes as you would expect:

http://www.gossamer-threads.com/lists/openstack/operators/28733#28733

Hope that helps,
Joe


-- 
Joe Topjian
Systems Architect
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.
___
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] Quantum dhcp-agent getting out of sync with multiple instance launch / termination

[Markku Tavasti]

I found out that quantum dhcp agent gets out of sync when many instances 
are launched or deleted same time. As a result, dnsmasq host-file have 
lines missing (all launched are not added), or some lines aren't removed 
when they should. When same ip is re-used, remaining extra lines aren't 
removed, but same ip has two lines, and dhcp discoveries get no response 
(no address available error on dnsmasq logs).


Restarting quantum-dhcp-agent will get everything back to proper state, 
but running restart on cron every minute does not sound proper fix :-(


On my test, creating 16 instances, 2-3 of them did not get line in 
host-file. When removing all those 16, 3-5 false lines were left behind.


On instance creation I see following message on quantum-server.log:

For every instance:
WARNING [quantum.db.agentschedulers_db] Fail scheduling network 
{'status': u'ACTIVE', 'subnets': 
[u'e9299278-bd49-4dc8-8df1-25b034f3ecea'], 'name': u'pk_tunk2', 
'provider:physical_network': u'vlans-osprv', 'admin_state_up': True, 
'tenant_id': u'06b9c423e10741ef83877b56d7608d7f', 
'provider:network_type': u'vlan', 'router:external': False, 'shared': 
False, 'id': u'cbce52ef-58ba-4f3c-96fb-9d51bdbf32fb', 
'provider:segmentation_id': 427L}

However, network ports get created, and seems to work?

And most likely related to missing lines on host file on creation:
WARNING [quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents

For termination of instances there is no warning or error messages.

Any ideas for fixing the situation?

--Tavasti


___
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] Change parameters of kvm in openstack

[Jeff Cai]

Hi,

When I boot a suse linux instance, it reports that "'system' volume group not 
found", I found that if I remove the '-device' line in kvm command line, it can 
start successfully.
Could you tell me how to change the parameters of 'kvm' in openstack?

Following is the command line that starts my instance:


/usr/bin/kvm 
-drive 
file=/var/lib/nova/instances/582db50e-56cf-4541-8078-4329b8578d71/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none
-device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
...

Best Regards

Jeff Cai



___
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] [Swift] Havana RC1 (1.10.0-rc1) available

[Thierry Carrez]

Hello everyone,

The havana release cycle for Swift already saw the releases of the 1.9.0
and 1.9.1 versions. The final coordinated release for the Havana cycle
shall include Swift 1.10.0. We now have a Swift release candidate for this:

https://launchpad.net/swift/havana/1.10.0-rc1

Unless release-critical issues are found that warrant a release
candidate respin, this RC1 will be formally released as the 1.10.0
("havana") final version on October 17. You are therefore strongly
encouraged to test and validate this tarball.

Alternatively, you can directly test the milestone-proposed branch at:
https://github.com/openstack/swift/tree/milestone-proposed

If you find an issue that could be considered release-critical, please
file it at:

https://bugs.launchpad.net/swift/+filebug

and tag it *havana-rc-potential* to bring it to the release crew's
attention.

Note that the "master" branch of Swift is now open for Icehouse
development.

Regards,

-- 
Thierry Carrez (ttx)

___
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] Resource utilization monitoring (CPU, RAM, HDD, Network and so on) of running instance via REST API.

[Sergey Gomanyuk]

Hello,
In our proof of concept project we use REST API provided by Open Stack to 
manage HP Cloud. One of project user stories is monitoring CPU, RAM, HDD, 
Network and other resource utilization  of running instances. Brief research 
shows that the one of possible solution is using Celiometer project. So my 
questions to experts who have already tried to solve the same task are:
- Is  Celiometer really the best solution at the moment, maybe there are 
another ways to monitor resource utilization?
- Are there any pitfalls when using Celiometer? Is it stable? Any VM limitation 
with HP Cloud (in documentation I can see the following: "At present, most of 
the Nova meters will only work with libvirt front-end hypervisors while test 
coverage was mostly done based on KVM.")?

Best Regards, Sergey Gomanyuk.

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
___
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