Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

Hi Kevin- Thanks for the reply and making me understand the data flow. I have one more doubt in plate. I see that in api-paste.ini, with respect to the online available documentation https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersi

[Openstack] [Quantum] Quantum OVS Plugin doubt

Hi Stackers- I have a doubt with respect to the Quantum OVS Plugin. [1] Do all the APIs of Quantum use the Quantum OVS plugin to get the data from the database. or they directly contact the database. Since, I have seen ovs_quantum_plugin.py code, it has create_network, update_network methods whi

Re: [Openstack] Fwd: [swift3] api - boto and libcloud => AccessDenied

Hi Antonio, It sounds like you might be using the wrong credentials. The S3 layer works with the EC2 credentials. On 6 December 2012 06:33, Antonio Messina wrote: > > Hi all, > > I'm trying to access SWIFT using the S3 API compatibility layer, but I > always get an "AccessDenied". > > I'm runn

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

On Thu, 2012-12-06 at 23:58 +0530, Trinath Somanchi wrote: > Suppose, we have a resquest to Nova.. > > The following steps are performed... > > 1. The request is captured by webob and is authenticated by keystone > and is decorated to wsgi app Not quite correct; webob decorates (some of) the fun

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

On Thu, 2012-12-06 at 13:13 -0600, Michael Basnight wrote: > Seems like a good start to a wiki page to me :) Heh. Feel free to start one up :) Or maybe this would be a candidate for Sandy Walsh's nova internals blog series? :) -- Kevin L. Mitchell ___

Re: [Openstack] [Cinder] New volume status stuck at "Creating" after creation in Horizon

Hi Razique, Following is the info you requested: root@novato:~# pvdisplay --- Physical volume --- PV Name /dev/loop2 VG Name cinder-volumes PV Size 10.00 GiB / not usable 4.00 MiB Allocatable yes PE Size 4.00 MiB Tot

Re: [Openstack] Do we have any schema for keystone v3.0 request/responses

It sounds like you *could* start updating and submitting it, but with the knowledge that you’ll have to continue to tweak it just as the JSON spec is being tweaked during development. So your options are to maintain it as such or wait until it’s declared FINAL and then do the work later on but o

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

Seems like a good start to a wiki page to me :) Sent from my digital shackles On Dec 6, 2012, at 11:27 AM, "Kevin L. Mitchell" wrote: > Honestly, I don't understand your questions; I figured the documentation > I pointed you to would answer them, and the fact it doesn't suggests > that you're

Re: [Openstack] Problem with keystone on Debian

On Thu, Dec 06, 2012 at 04:21:49PM -0200, Guilherme Russi wrote: > Hello Guys, > > I'm trying to install OpenStack on Debian Wheezy, but i'm getting some > problems with keystone, when i try to create a user in a tenant using > the --tenant-id command, it returns the error: keystone: error: > unr

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

Thanks a lot kevin.. Your explanation has cleared my doubts.. Keeping togethor what i understand... Suppose, we have a resquest to Nova.. The following steps are performed... 1. The request is captured by webob and is authenticated by keystone and is decorated to wsgi app 2. Nova-api maps the

[Openstack] Problem with keystone on Debian

Hello Guys, I'm trying to install OpenStack on Debian Wheezy, but i'm getting some problems with keystone, when i try to create a user in a tenant using the --tenant-id command, it returns the error: keystone: error: unrecognized arguments: --service-id . Does anybody knows if it is a version p

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

It's probably best to ask these sorts of questions on the email list, as it gives an opportunity to others to answer them, as well as allowing others who may have similar questions to see the answers in the first place. On Thu, 2012-12-06 at 23:24 +0530, Trinath Somanchi wrote: > [1] In nova or qu

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

Honestly, I don't understand your questions; I figured the documentation I pointed you to would answer them, and the fact it doesn't suggests that you're not asking what I thought you were asking. Maybe an approach from the beginning: Nova, Quantum, Glance, Keystone, etc. all have, as components,

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

Hi Kevin- Thanks for the reply.. But, few of my doubts are left ... [1] What is the significance of the api-paste.ini file in the configuration of nova/quantum and other modules of ipenstack? [2] How do the modules use these API configuration options? How they are used different from normal ".c

Re: [Openstack] Openstack Nova/Quantum :; api-paste.ini file

On Thu, 2012-12-06 at 16:11 +0530, Trinath Somanchi wrote: > What is the significance of api-paste.ini file in the configuration of > nova and quantum and other modules of openstack? > > How this configuration is parsed and used? by which api of the > openstack modules? So, api-paste.ini is par

[Openstack] Openstack Folsom and New kind of setup

Hi Stackers- I have got a doubt about a new kind of setup with Folsom. Need your help on the doubts i have. Lets plan that we install nova, quantum, glance, keystone, mysql-database and Horizon components of controller in individual machines. How Horizon will be able to get the set the configura

[Openstack] Openstack Nova/Quantum :; api-paste.ini file

Hi- What is the significance of api-paste.ini file in the configuration of nova and quantum and other modules of openstack? How this configuration is parsed and used? by which api of the openstack modules? My quantum api-paste.ini looks this way. [composite:quantum] use = egg:Paste#urlmap /: qu

Re: [Openstack] Accessing Nova DB from the Compute Host

Check this Trinathhttps://bugs.launchpad.net/keystone/+bug/860885Regards, Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 5 déc. 2012 à 12:08, Razique Mahroua a écrit :HI Trinath,just add the right credentials into your .bashrc or any fil

Re: [Openstack] Why my vm often change into shut off status by itself?

qemu: terminating on signal 15 from pid 1957 this means the VM is shutted off by libvirtd/libvirt api, the log of my VM is same as this, so you should check who calls the libvirt to shut down your VMs. I have no other ideas now, good luck, guy! 2012-12-06 Wangpan 发件人：pyw 发送时间：2012-12-06 17:

Re: [Openstack] Why my vm often change into shut off status by itself?

Individual virtual machines automatically shutoff occurs frequently, this time all the virtual machines are automatic shutoff at the same time. If the nova failed to delete the virtual machine will cause the virtual machine is shut down? 2012/12/6 Wangpan > ** > are that all VMs shutting down

Re: [Openstack] Why my vm often change into shut off status by itself?

To Stephen Gran: $ ps -ef|grep 1957 root 1957 1 0 Nov22 ?02:33:06 /usr/sbin/libvirtd -d 1957 is libvirtd... other host info: $ free -m total used free sharedbuffers cached Mem: 96675 55961 40713 0561

Re: [Openstack] Why my vm often change into shut off status by itself?

Hello, On Thu, 2012-12-06 at 17:09 +0800, pyw wrote: > We can see this two log： > ... > 2012-12-03 06:14:59.819+: starting up > > ... > 2012-12-04 06:54:27.150+: shutting down > > > > The vm shutoff after running one day. Without being sure, I am going to guess that you have a morni

Re: [Openstack] Why my vm often change into shut off status by itself?

are that all VMs shutting down at the same time? such as '2012-12-04 06:54:27.150+: shutting down' or near this point? if this is true, I guess it may be the host's problem. 2012-12-06 Wangpan 发件人：pyw 发送时间：2012-12-06 17:10 主题：Re: [Openstack] Why my vm often change into shut off status by

Re: [Openstack] Why my vm often change into shut off status by itself?

Generally if you use virsh to restart the virtual machine，it seems to be able to use some time before shutoff again。 $ date Thu Dec 6 17:04:41 CST 2012 $ virsh start instance-006e Domain instance-006e started $ virsh list Id Name State --