[Openstack] Vm provision code flow in openstack

Hello everyone, I am trying to understand the flow of control in code in openstack for provisioning a VM. I want to understand it in order to do modify scheduler module as per our requirements. I have found the code base which, if I am not wrong, is kept in /usr/share/pyshared/nova/* director

Re: [Openstack] Swift container's rwx permissions

Clay- You are correct – the hadoop-swift filesystem is just an implement of the Hadoop FileSystem class that uses swift for storage. As such, it's just translating filesystem calls into HTTP requests into swift and is not accessing the filesystem of the object servers directly. Shashank- I'm

Re: [Openstack] [openstack-community] OpenStack Teacher /Student Certification

Hi, There is a free "certification" program called CloudU that Rackspace is prompting. http://www.rackspace.com/knowledge_center/cloudu/curriculum This is a free program as far as I know. It has some 10-sih lesson? The content is about Cloud rather than Openstack, but worth looking at it. Why don

[Openstack] Keystone JSON format access control policy

Hi everyone, I'm currently looking at access control mechanisms of OpenStack and finding that the access control policy is specified using JSON format. I'm wondering why we do not adopt an XML based approach like XACML, is it because of the performance problem, or we just choose JSON as it's simp

[Openstack] Quantum CLI errors on Grizzly

Hi folks, I have installed Grizzly on CentOS 6.3 and was setting up Quantum by following the instructions given in the below link : https://fedoraproject.org/wiki/Packstack_to_Quantum In step 13 when I start using Quantum CLI to create a private network using the command - *quantum net-create pri

Re: [Openstack] Vm provision code flow in openstack

So, there are a few things which happen here. VM provisioning is handled by the compute driver (checkout run_instance in nova/compute/manager.py). Scheduling however is handled by the scheduler, which has a plugin system (checkout nova/scheduler/*). Also, you'd be better off browing git for the so

[Openstack] [Grizzly] Unable to retrieve quota information

Hi Folks, I have installed Grizzly on CentOS 6.4. I was able to see quota information for quite some time. But looks like after reboot the quota information is not reflected in the Overview tab. Is there a bug related to this, if not which services should I check to fix this issue. Please suggest

Re: [Openstack] Vm provision code flow in openstack

Hello Michael, Many thanks for your response. I somehow found this code base (in installed openstack instance) and I inserted debug steps (opening a log file and printing statements into it) to see if the code flows through the file (specifically file '/usr/share/pyshared/nova/compute/api.py' i

[Openstack] nova-network IPv6

Hi all, We've got a Folsom cloud running nova-network in FlatDHCP multi-host, currently with just a single public fixed range. We followed http://docs.openstack.org/folsom/openstack-compute/admin/content/configuring-compute-to-use-ipv6-addresses.htmlto get IPv6 going (plus adding a bunch of rules

Re: [Openstack] [Grizzly] Unable to retrieve quota information

Hello, "Ashutosh Narayan" wrote: > I have installed Grizzly on CentOS 6.4. I was able to see quota information > for quite some time. But looks like after reboot the quota information is > not reflected in the Overview tab. Is there a bug related to this, if not > which > services should I check

Re: [Openstack] [Grizzly] Unable to retrieve quota information

Hi, Data is not displayed at all and it pops an error dialog. Http error_log shows - [Mon Apr 29 12:11:35 2013] [error] \x1b[31;1mRecoverable error: [Errno 111] Connection refused\x1b[0m Error 111 is another pop up which I see when I click on various sections under Admin tab or Projects Tab. A

Re: [Openstack] [Grizzly] Unable to retrieve quota information

Hi, "Ashutosh Narayan" wrote: > Data is not displayed at all and it pops an error dialog. > > Http error_log shows - > > [Mon Apr 29 12:11:35 2013] [error] \x1b[31;1mRecoverable error: [Errno 111] > Connection refused\x1b[0m > > Error 111 is another pop up which I see when I click on various s

Re: [Openstack] Keystone JSON format access control policy

The JSON approach is rather arbitrary; keystone has an API to manage & publish policy blobs of any format (/v3/policies), and the policy engines themselves are completely pluggable. I don't think there's anything preventing a deployment from implementing an XACML based policy solution (if there is

Re: [Openstack] cinder-volume ignoring rabbit config?

On 27 April 2013 02:14, Dennis Jacobfeuerborn wrote: > > 2013-04-27 03:05:35DEBUG [qpid.messaging.io.raw] OPEN[31bbb00]: > localhost:5672 > 2013-04-27 03:05:35ERROR [cinder.openstack.common.rpc.**impl_qpid] > Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Sleeping 1 > seconds

[Openstack] release process and sample configs

Hi All, I've noticed that a lot of the projects do not get their sample configs updated as part of the release process. I'd suggest that one of the final commits to each project before a release is cut, is to update the sample config so it's relevant to the codebase that's being released and pack

[Openstack] Failed "db sync" while upgrading from essex to folsom

Hi everyone, I'm having some trouble upgrading from essex to folsom. The cloud is currently running on Ubuntu 12.04. For the upgrade, I included the folsom repo(ubuntu cloud archive) and upgraded the packages. Things went fine until I issued "nova-manage db sync". It failed with the following erro

Re: [Openstack] Quantum CLI errors on Grizzly

Ashutosh, Have you verified that the necessary Quantum processes are running? If not, ensure that quantum-dhcp-agent, quantum-l3-agent, quantum-openvswitch-agent and most importantly quantum are running. If those processes are running can you share the output from /var/log/quantum/server.log

Re: [Openstack] Keystone JSON format access control policy

Hey Tks man~ On Mon, Apr 29, 2013 at 3:00 PM, Dolph Mathews wrote: > The JSON approach is rather arbitrary; keystone has an API to manage & > publish policy blobs of any format (/v3/policies), and the policy engines > themselves are completely pluggable. I don't think there's anything > preventi

[Openstack] quantum-plugin-openvswitch-agent error

Hi, I am getting the following error. Any help will be highly appreciated. head /var/log/quantum/ovs-agent.log 2013-04-29 16:59:15ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-vsctl', '--timeout=2', '--', '--if-exists', 'del-port', 'br-int', 'patch-tun']. Exception: Command

Re: [Openstack] release process and sample configs

Darren Birkett wrote: > I've noticed that a lot of the projects do not get their sample configs > updated as part of the release process. I'd suggest that one of the > final commits to each project before a release is cut, is to update the > sample config so it's relevant to the codebase that's be

Re: [Openstack] Failed "db sync" while upgrading from essex to folsom

This is a MYsql DB issue, you can try to restart MYsql if possible. 2013/4/29 Shashank Sahni > Hi everyone, > > I'm having some trouble upgrading from essex to folsom. The cloud is > currently running on Ubuntu 12.04. For the upgrade, I included the folsom > repo(ubuntu cloud archive) and upgra

Re: [Openstack] release process and sample configs

On Mon, Apr 29, 2013 at 10:50 AM, Thierry Carrez wrote: > Darren Birkett wrote: > > I've noticed that a lot of the projects do not get their sample configs > > updated as part of the release process. I'd suggest that one of the > > final commits to each project before a release is cut, is to upda

Re: [Openstack] quantum-plugin-openvswitch-agent error

Solved by adding root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf in /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini From: arin...@live.com To: openstack@lists.launchpad.net Date: Mon, 29 Apr 2013 17:36:25 +0200 Subject: [Openstack] quantum-plugin-openvswitch-age

[Openstack] weird nova attach of a volume

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok so I have a volume that Im trying to attach to an instance from within horizon. It always fails with the message of could not attach volume. I try it via a nova CLI version and get messages about /dev/vdb is already in use. I had tried to attach i

[Openstack] error while spawning vm

Hi, My setup is: # nova-manage service list Binary Host Zone Status State Updated_At nova-conductor aopcsos internal enabled :-) 2013-04-29 17:10:58 nova-console aopcsos

[Openstack] DevStack, Xen and "Bad archive mirror" error

Hi, I've just tried out DevStack with my XCP 1.6.10 server using the instructions at https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md I hit exactly the same issue that Hu Yanrui mentioned in a mail to the list last month - see https://lists.launchpad.net/openstack/msg221

[Openstack] openstack and PBS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 has anyone heard or seen (or got working) an interface to openstack from PBS's batch system? thanks s - -- Steve Heistand NASA Ames Research Center

Re: [Openstack] DevStack, Xen and "Bad archive mirror" error

Hi Martin, That looks like a spot on analysis to me. If you could raise a bug I will look at fixing it tomorrow. I think it's useful to have the bug for future reference rather than me just making the devstack change. Thanks for your investigations! Bob Martin Maisey wrote: Hi, I've ju

Re: [Openstack] Failed "db sync" while upgrading from essex to folsom

Hello Yaguang, Thanks for your response, but no luck :( This table, projects, and related ones - users, user_project_association etc. seem to be skeleton from the time authentication service was a part of nova. The related tables are all empty. I tried to delete it, but got "table doesn't exist" e

Re: [Openstack] error while spawning vm

>From this error it looks you don't have brctl in any of the filters in /etc/nova/*filters: 2013-04-29 19:17:33.640 7974 TRACE nova.virt.libvirt.vif [instance: b5317dbd-bd85-4cf7-bbf0-cc653fa8c425] Stdout: '/usr/bin/nova-rootwrap: Unauthorized command: brctl delif qbr8b7fa98b-60 qvb8b7fa98b-60 (

Re: [Openstack] DevStack, Xen and "Bad archive mirror" error

No problems - bug filed at https://bugs.launchpad.net/devstack/+bug/1174455 Cheers, Martin On 29 April 2013 18:39, Bob Ball wrote: > Hi Martin, > > That looks like a spot on analysis to me. > > If you could raise a bug I will look at fixing it tomorrow. I think it's > useful to have the b

Re: [Openstack] weird nova attach of a volume

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 followup on this, what I think is going on: I have an image that I am tweaking and snapshot'ing. the snapshot process remembers that a volume is attached to it but doesnt attach the volume to it when you launch a new copy of the snapshot. ideally snaps

Re: [Openstack] error while spawning vm

Thanks for your reply. Surprisingly, in my /etc/nova/rootwrap.d/, I only have api-metadata.filters. I dont know what went wrong. Date: Mon, 29 Apr 2013 11:12:46 -0700 Subject: Re: [Openstack] error while spawning vm From: aro...@nicira.com To: arin...@live.com CC: openstack@lists.launchpad.net

Re: [Openstack] quantum-plugin-openvswitch-agent error

Arindam, Do you have sudo configured properly? Something like the following? Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap Jay S. Bryant Linux Developer - OpenStack Enterprise Edition Department 7YLA, Building 015-2, Office E12

Re: [Openstack] quantum-plugin-openvswitch-agent error

I solved it by adding root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf in /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini To: arin...@live.com CC: openstack@lists.launchpad.net; openstack-bounces+jsbryant=us.ibm@lists.launchpad.net Subject: Re: [Openstack]

Re: [Openstack] Failed "db sync" while upgrading from essex to folsom

On Mon, 2013-04-29 at 20:16 +0530, Shashank Sahni wrote: > Hi everyone, > > I'm having some trouble upgrading from essex to folsom. The cloud is > currently running on Ubuntu 12.04. For the upgrade, I included the folsom > repo(ubuntu cloud archive) and upgraded the packages. Things went fine > un

Re: [Openstack] Ceilometer Install

Hi Doug, I have followed the document. The only thing that is different from the docs is that I did not copy the yaml file (it does not exist in tarball): cp etc/ceilometer/*.yaml /etc/ceilometer However, the tarball is the g2 version, which is the last version that was supposed to work with Fol

[Openstack] Cinder restarting every second with cryptic error

2013-04-29 17:57:00AUDIT [cinder.service] Starting cinder-volume node (version 2013.1) 2013-04-29 17:57:00DEBUG [cinder.utils] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name 2013-04-29 17:57:01DEBUG [cinder.utils] backend 2013-04-29

Re: [Openstack] Ceilometer Install

I thought it might help if mentioned little more: /etc/ceilometer.conf file has the following parameters added: os_username=ceilometer os_password=$PASSWORD os_tenant_name=service os_auth_url=http://localhost:5000/v2.0/ I checked CLI_OPTIONS in service.py and it looks allright: CLI_OPTIONS = [

Re: [Openstack] release process and sample configs

On 30/04/13 02:12, Anne Gentle wrote: > > > > On Mon, Apr 29, 2013 at 10:50 AM, Thierry Carrez > wrote: > > Darren Birkett wrote: > > I've noticed that a lot of the projects do not get their sample > configs > > updated as part of the release proce

Re: [Openstack] Cinder restarting every second with cryptic error

On Mon, Apr 29, 2013 at 3:59 PM, Drew Weaver wrote: > Child 4300 exited with status 2 Hi Drew, I think I know what's going on here. In the Folsom release we had to add some conversion work to deal with migrating from iet to tgt. One of the things we did here was added a kwarg to create_iscsi

Re: [Openstack] Cinder restarting every second with cryptic error

Hi Drew, I think the gist listed here [1], will address the issue. I'm going to need to spin things up and test it though. Thanks, John [1] https://gist.github.com/j-griffith/5485632 On Mon, Apr 29, 2013 at 5:24 PM, John Griffith wrote: > > On Mon, Apr 29, 2013 at 3:59 PM, Drew Weaver wrote:

[Openstack] [Grizzly] VMs can't access internet if floating ip associated

Hi there, I'm running Grizzly on Ubuntu 12.04 in this topology: http://docs.openstack.org/trunk/openstack-network/admin/content/connectivity.html and using the per-tenant routers with private networks. I just found out that my VMs (except just one) can't access internet if I associate them a f

[Openstack] Configuring tempurl in Openstack Swift

Hi, Configuring tempurl in openstack Swift requires two steps: 1) Adding tempurl to the pipeline in proxy-server.conf 2) Setting the tempurl key on the account. Step #1 above is fairly straight forward. However, step #2 is slightly complicated; at least as per [1]. It requires first authenticati

[Openstack] anyone has a sample quantum.conf file that configures a valid quantum.log file?

Hi, I'm new to Quantum and trying to set up an openstack quantum environment. I installed a single node environment using DevStack(on a VM) successfully. I noticed that by default there is no log files for quantum. I tried to enable the quantum logging using quantum.conf. However, I haven't b

Re: [Openstack] Configuring tempurl in Openstack Swift

There are no plans to change the current implementation of tempurl. In order to generate a tempurl that can be validated without relying on a network call to a centralized authority service, the owner and the service must have a shared secret. In the tempurl feature, this shared secret is set as

[Openstack] Grizzly Horizon Import Error

Hi Stackers- I have installed Openstack Grizzly with all the components but I get this Horizon Error when I try to access the Horizon GUI [Tue Apr 30 05:59:04 2013] [error] [client 10.232.90.47] mod_wsgi (pid=2785): Exception occurred processing WSGI script '/usr/share/openstack-dashboard/opensta

Re: [Openstack] Grizzly Horizon Import Error

This is the same issue reported in: https://bugs.launchpad.net/horizon/+bug/1125622 There is also a discussion in this bug with workarounds: https://bugs.launchpad.net/horizon/+bug/1116467 Hope this helps. -Lin From: Openstack [mailto:openstack-bounces+lin-hua.cheng=hp@lists.launchpad.ne