Re: [Openstack] I release naming (calling APAC community)

Ili +1 From: Openstack [mailto:openstack-bounces+malini.k.bhandaru=intel@lists.launchpad.net] On Behalf Of Wang, Shane Sent: Thursday, May 09, 2013 8:58 PM To: Rajesh Vellanki; Atul Jha; Matt Joyce; John Wong Cc: Thierry Carrez; openstack@lists.launchpad.net Subject: Re: [Openstack] I rele

[Openstack] 回复: 回复: Re: ConnectQuantum to VLAN-tagged physical network

Finally，the network problem has been solved, thank you very much for all your kindness help. 2013-05-10 zengshan2008 发件人：zengshan2008 发送时间：2013-05-10 09:23 主题：回复: Re: [Openstack] ConnectQuantum to VLAN-tagged physical network 收件人："Salvatore Orlando","Ashok Kumaran" 抄送："openstack" Hi Salva

Re: [Openstack] [OSSA 2013-011] Keystone tokens not immediately invalidated when user is deleted (CVE-2013-2059)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Miller, Mark M (EB SW Cloud - R&D - Corvallis) wrote: > Looks like a fix has been written for Grizzly. Is there an official > Grizzly patch release coming out that contains this and other > fixes? Point releases for the last OpenStack release, conta

Re: [Openstack] Grizzly installation successful but VM is not accessible over network or from the host machine

Kamarul, The status shown on the dashboard is confusing. Under Router Detail section, it shows Status as Active. But under Interfaces it shows as DOWN but Admin status as UP (refer the cut-paste below). Also i see following error message in /var/log/quantum/dhcp-agent.log: +++ Stderr:

Re: [Openstack] Grizzly installation successful but VM is not accessible over network or from the host machine

Stderr: "sudo: no tty present and no askpass program specified\nSorry, user quantum is not allowed to execute above caused by quantum user does not have permission for sudo See this discussion: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/issues/39 quantum ALL=NOPASSWD: ALL T

Re: [Openstack] [openstack-community] [Ask] Guidelines for answering question on Ask

This is great work. It might be better though to put the moderator rules on the ask.openstack.org site itself rather than the wiki so that you can link to it in the header without leaving the 'ask' site. Stackoverflow uses the 'faq' as the link in the header for this type of information: http://

[Openstack] [Ceilometer] notifiers for host/hyper capacity metrics

All, Anyone aware of Havana based work to create notifiers for ceilometer which would push host/hyper capacity based metrics? For example used/free values for cpu/mem/disk on a per host (hypervisor) basis? Maybe my google-foo is weak this morning, but I didn't find anything obvious. Thanks

[Openstack] 回复: Re: ConnectQuantum to VLAN-tagged physical network

Hi Salvatore， Since I am using the vlan mode according to the https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst so I need to set the physical switch (indentified by the black circle) port to trunk mode? but My networknode didn

Re: [Openstack] [Ceilometer] notifiers for host/hyper capacity metrics

On Fri, May 10 2013, boden wrote: > All, > Anyone aware of Havana based work to create notifiers for ceilometer which > would push host/hyper capacity based metrics? For example used/free values > for cpu/mem/disk on a per host (hypervisor) basis? > > Maybe my google-foo is weak this morning, but

Re: [Openstack] Grizzly fails on ubuntu server 13.04

you need to expose the VM's internal network to an external network by allocating it floating IP address. Regards, Pranav On Thu, May 9, 2013 at 10:47 PM, Nikhil Mittal wrote: > I am seeing this email after a long time. Quite recently I tried > installing Grizzly on Ubuntu 13.04 on x86 64 machi

[Openstack] [Quantum] Upgrading to Grizzly: dhcp addres shuffle

Hi, Today I upgraded from Folsom to Grizzly and I noticed some of the running virtual machines got a different IP-address from DHCP. Somehow some of the IP's got shuffled around. Anyone got a clue how this might have happened? Should I have run a database upgrade script for Quantum? (I thought

Re: [Openstack] Grizzly fails on ubuntu server 13.04

Nope, assigning a floating IP is not required. The VM can be accessed with whatever IP that is assigned as the NAT'ng will take care of that. On Fri, May 10, 2013 at 4:50 PM, Pranav wrote: > you need to expose the VM's internal network to an external network by > allocating it floating IP addres

[Openstack] [ceilometer] HBase Configuration/Instruction is now available on openstack docs

Hi guys, For those of you who wanted to try out HBase as the backend for Ceilometer. Glad to let you know the document for HBase configuration is available now on openstack docs: http://docs.openstack.org/developer/ceilometer/configuration.html#hbase If you had any issues or questions, feel fr

Re: [Openstack] I release naming (calling APAC community)

Extending the rules to those things of cultural or political significance would have established precedence with the 'Grizzly exception'. If such an exception were useful in naming this release, I'd suggest it become a standard part of the naming scheme. On May 10, 2013 6:40 AM, "Matt Joyce" wrot

Re: [Openstack] API version in Grizzly

I have few more questions related to APIs. When you say Identity v3.0 development is going on side-by-side so I think if I have Grizzly setup with Identity v2.0 then it'll be upgraded to Identity v3.0 with Grizzly when new version is available in updates. Though I might have option to upgrade it o

Re: [Openstack] [HyperV][xen] Porting Windows disk_image from xen to HyperV

>From a driver wise perspective. Windows has the hyper-v bits baked in to >achieve partial paravirtualization/enlightment. The problem obviously is >moving the data from one virtual disk format to another. In theory Peter J. Pouliot, CISSP Senior SDET, OpenStack Microsoft New England Re

Re: [Openstack] I release naming (calling APAC community)

I agree. The naming convention should not be a barrier to adoption of the new release. However, we should consider a name that has significance for the hosting community. Naming releases alphabetically is a convenience for speakers of Western languages, and the Openstack community is global. I don'

Re: [Openstack] Grizzly fails on ubuntu server 13.04

but NAT wont make the VM accessible from outside world ... will it? Regards, Pranav On Fri, May 10, 2013 at 5:16 PM, Nikhil Mittal wrote: > Nope, assigning a floating IP is not required. The VM can be accessed with > whatever IP that is assigned as the NAT'ng will take care of that. > > On Fri,

[Openstack] centos5.5_64bit image for openstack

Hello, Is there anyone build CentOS5.5_64bit image for openstack ? If someone own it, can you send it to my gmail. Thank you ! Regards, yanchen ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe

[Openstack] A Grizzly arping failure

I sent a message about this 3 days ago, but I didn't get a response. So if at first you don't succeed... The symptom is that my VMs only survive on the external network for about a minute. The behavior is not consistent, however. I've observed the following different types of failures: * ssh ses

[Openstack] Guest PXE Boot

Hi guys, I was trying to PXE boot a guest for quite some time now and I think I've found a solution that is kind of hackish but pretty simple. I'm not quite sure it's good to go in trunk but felt like I'd share it since I've been messing a while on this. If anybody have a better solution,

Re: [Openstack] Grizzly fails on ubuntu server 13.04

No, but maybe that's not a requirement for him. Nikhil, I have Grizzly running on 13.04, but I'm also having network problems (see subject "A Grizzly arping failure"). I'm investigating these issues today, hopefully with plenty of help from the community. Maybe the fix I need is similar to the fi

Re: [Openstack] A Grizzly arping failure

More information: Even thought it appears that the dhcp namespace has the ip/MAC mappings in arp, is still doesn't respond to arps: # ip netns exec qdhcp-af224f3f-8de6-4e0d-b043-6bcd5cb014c5 arp Address HWtype HWaddress Flags MaskIface 192.168.252.3

Re: [Openstack] API version in Grizzly

OMG, table of contents on the API reference site is SO MUCH BETTER! :) Good to know about the Launchpad for the site. Didn't know about that one. - Gabriel From: annegen...@justwriteclick.com [mailto:annegen...@justwriteclick.com] On Behalf Of Anne Gentle Sent: Thursday, May 09, 2013

Re: [Openstack] API version in Grizzly

> When you say Identity v3.0 development is going on side-by-side so I think if > I have Grizzly setup with Identity v2.0 then it'll be upgraded to Identity > v3.0 > with Grizzly when new version is available in updates. > Though I might have option to upgrade it or not? OR Identity v3.0 will be >

[Openstack] Nova Compute API - getting server start/stop times after the fact?

Say it's midnight, and I want to know how many instances a tenant had running in the past hour or dayŠ I know the MySQL DB contains "historical" started, changed and stopped times for each instance/server. Is there an API call to access that data (I can't find one), or do I need to go to the DB d

Re: [Openstack] Nova Compute API - getting server start/stop times after the fact?

I would suggest checking out StackTach over at Racker Labs -> https://github.com/rackerlabs/stacktach. It will store and report this data for you from your rabbit/qpid queues. On Fri, May 10, 2013 at 3:26 PM, Daniel Murphy wrote: > Say it's midnight, and I want to know how many instances a tena

Re: [Openstack] A Grizzly arping failure

can you try using -e with tcpdump to see the ethernet headers - it may be arps  from the router to ff:ff:ff:ff:ff:ff that are not getting across in that  direction. You should continue tcpdumping on the devices along the path to the  instance to see where the arp request (or reply) stops. You do no

[Openstack] Unable to connect to certain external IPs from VM

I have a really weird issue (or so it seems to me) I installed OpenStack Folsom using the guide - http://docs.openstack.org/folsom/basic-install/content/index.html - And and able to spawn VM get IP, set floating IP and now am trying to do some development within the VM. I am unable to connect to

[Openstack] Failed to connect socket to '/var/run/libvirt/libvirt-sock'

Hi Guys, I trying to grizzly version on ubuntu 12.04 it's says Failed to connect socket to '/var/run/libvirt/libvirt-sock' Please check my console log root@computenode:~# kvm-ok INFO: /dev/kvm exists KVM acceleration can be used root@computenode:~# virsh net-destroy default error: failed to conne

Re: [Openstack] A Grizzly arping failure

Well, the subject is "A Grizzly apring failure". So I'm using Grizzly :) Sorry, bad joke. I have a multi-node setup on Raring, with a 3-nic network node (public, management, vm config nets) using OVS and GRE encapsulation. It looks like this: http://chavezy.files.wordpress.com/2013/03/ostack-l

Re: [Openstack] A Grizzly arping failure

In my setup I see the arp replies being answered by the instance - not dnsmasq. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launc

Re: [Openstack] A Grizzly arping failure

Arg, of course the arp replies come from the instance. See? I'm easily confused. Here's more, using tcpdump -e. So if I ping the floater (10.21.166.2 -> 192.168.252.3) ) from the outside (10.21.164.10), I see this on the tenant router's external port: 16:16:30.771776 00:22:19:65:ae:42 > fa:16:

[Openstack] A Grizzly GRE failure

I'm refactoring my question once again (see "A Grizzly arping failure" and "Failure to arp by quantum router"). Quickly, the problem is in a multi-node Grizzly+Raring setup with a separate network node and a dedicated VLAN for VM traffic. External connections time out within a minute and dont' r

Re: [Openstack] A Grizzly GRE failure

I'm not sure how to rectify that. You may have to delete the bad row from the DB and restart the agents: mysql> use quantum; mysql> select * from ovs_tunnel_endpoints; ... ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@list

[Openstack] OpenStack Community Weekly Newsletter (May 3 – 10)

OpenStack 2013.1.1 released 2013.1.1 release, the latest in the series of stable releases. These releases are bugfix updates to Grizzly and are intended to be relatively risk free with no intentional regr

Re: [Openstack] Failed to connect socket to '/var/run/libvirt/libvirt-sock'

Looks like there could be some configuration issues in libvirtd.conf. Can you ensure that you have below values set listen_tls=0 listen_tcp=1 Try restarting libvirt-bin let us know the outcome -Ashok Sent from my iPhone On 11-May-2013, at 1:29 AM, Dhanasekaran Anbalagan wrote: Hi Guys, I tr