[Openstack] Lost copy-on-write feature when create volume from image with using Ceph RBD

2013-04-12 Thread 陈雷
Hi, Guys

Recently I'm testing the new version of OpenStack Grizzly. I'm using Ceph
RBD as the backend storage both for Glance and Cinder.

In the old version of Folsom, when set the parameter
‘show_image_direct_url=True’ in the config file glance-api.conf, the
process of  create volume from image will be done immediately, because it
 just to create a snapshot from Ceph's image pool to volumes pool.

But now I found the feature is lost, it always perform a convert process
which will download the the whole image file from Ceph's pool of 'images'
and convert it to RAW format then upload to Ceph's pool of 'volumes' no
matter what the original format of image file is. This process take longer
time than the older version of 'Folsom'.


So is this a bug or I miss-configured something?

Thanks
Ray
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] How to start Horizon?

2013-04-12 Thread 郭龙仓
I have installed Horizon lonely,how to start it ?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] does anyone install grizzly using tarballs.? ,step by step. ,without apt-get nova……etc

2013-04-12 Thread 郭龙仓

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] ODS schedule app for Android?

2013-04-12 Thread Thierry Carrez
Eric Windisch wrote:
 Someone has just informed me of the @OpenStack twitter feed which reads:
 
 Coming to the Summit? Download the new iphone app! (Android coming
 soon) awe.sm/dE87S http://awe.sm/dE87S
 
 Case closed, I guess ;-)

A Google Play search yields:

https://play.google.com/store/apps/details?id=org.sched.openstacksummitapril2013

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] error in quantum in folsom

2013-04-12 Thread Arindam Choudhury
Hi,

I am new to openstack and I am trying to install openstack folsom on fedora 18. 
any help will be highly appreciated.

while installing quantum I got this error:

[(keystone_admin)]$ quantum net-create --tenant-id 
112a75ab04224fa3b44109a6c4859c28 net1
[Errno 110] Connection timed out

 /var/log/quantum/server.log 
2013-04-12 12:43:53 INFO [quantum.common.config] Logging enabled!
2013-04-12 12:43:53 INFO [quantum.common.config] Config paste file: 
/etc/quantum/api-paste.ini
2013-04-12 12:43:53 INFO [quantum.manager] Loading Plugin: 
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
2013-04-12 12:43:53 INFO [quantum.plugins.openvswitch.ovs_quantum_plugin] 
Network VLAN ranges: {}
2013-04-12 12:43:53 INFO [quantum.openstack.common.rpc.impl_qpid] Connected 
to AMQP server on 158.109.65.21:5672
2013-04-12 12:43:53 INFO [quantum.api.extensions] Initializing extension 
manager.
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
__init__.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
extensions.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
_quotav2_model.py
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
l3.py
2013-04-12 12:43:53  WARNING [quantum.api.extensions] Loaded extension: router
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
_quotav2_model.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
_quotav2_driver.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
quotasv2.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
providernet.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
flavor.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
l3.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
quotasv2.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
l3.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
extensions.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
providernet.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
quotasv2.py
2013-04-12
 12:43:53  WARNING [quantum.api.extensions] Exception loading extension:
 Invalid extension environment: quota driver 
quantum.extensions._quotav2_driver.DbQuotaDriver is needed.
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
extensions.py
2013-04-12
 12:43:53  WARNING [quantum.api.extensions] Did not find expected name 
Extensions in 
/usr/lib/python2.7/site-packages/quantum/extensions/extensions.py
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
__init__.py
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
flavor.py
2013-04-12
 12:43:53  WARNING [quantum.api.extensions] extension flavor not 
supported by plugin 
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 
object at 0x39a4450
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
__init__.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
_quotav2_driver.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
flavor.pyc
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
providernet.py
2013-04-12 12:43:53  WARNING [quantum.api.extensions] Loaded extension: provider
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
_quotav2_model.pyo
2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension file: 
_quotav2_driver.py
2013-04-12 12:43:53 INFO [keystone.middleware.auth_token] Starting keystone 
auth_token middleware
2013-04-12
 12:43:53 INFO [keystone.middleware.auth_token] Using 
/var/lib/quantum/keystone-signing as cache directory for signing 
certificate
2013-04-12 13:08:07 INFO [quantum.openstack.common.rpc.impl_qpid] Connected 
to AMQP server on 158.109.65.21:5672
2013-04-12 13:09:05 INFO [quantum.common.config] Logging enabled!
2013-04-12 13:09:05 INFO [quantum.common.config] Config paste file: 
/etc/quantum/api-paste.ini
2013-04-12 13:09:05 INFO [quantum.manager] Loading Plugin: 
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
2013-04-12 13:09:05 INFO [quantum.plugins.openvswitch.ovs_quantum_plugin] 
Network VLAN ranges: {}
2013-04-12 13:09:05 INFO [quantum.openstack.common.rpc.impl_qpid] Connected 
to AMQP server on 158.109.65.21:5672
2013-04-12 13:09:05 INFO [quantum.api.extensions] Initializing extension 
manager.
2013-04-12 13:09:05 INFO [quantum.api.extensions] Loading extension file: 
__init__.pyc
2013-04-12 13:09:05 INFO [quantum.api.extensions] Loading 

Re: [Openstack] ceilometer-agent-central starting fail

2013-04-12 Thread Doug Hellmann
On Thu, Apr 11, 2013 at 11:34 PM, Liu Wenmao marvel...@gmail.com wrote:

 Thanks, the ceilometer seems to lack some default options in configuration
 files and the official guidance. (
 http://docs.openstack.org/developer/ceilometer/configuration.html)


I have opened a bug to address the missing details in the configuration
documentation. https://bugs.launchpad.net/ceilometer/+bug/1168375

Doug



 So maybe it is not ready for users yet?


 On Wed, Apr 10, 2013 at 8:28 PM, Doug Hellmann 
 doug.hellm...@dreamhost.com wrote:




 On Wed, Apr 10, 2013 at 6:10 AM, Liu Wenmao marvel...@gmail.com wrote:

 Actually this is not over.

 The main reason of service failure is that central/manager.py
 and service.py use different vairables:

 central/manager.py
  70 def interval_task(self, task):
  71 self.keystone = ksclient.Client(
  72 username=cfg.CONF.*os_username*,
  73 password=cfg.CONF.os_password,
  74 tenant_id=cfg.CONF.os_tenant_id,
  75 tenant_name=cfg.CONF.os_tenant_name,
  76 auth_url=cfg.CONF.os_auth_url)

 44 CLI_OPTIONS = [
  45 cfg.StrOpt('*os-username*',
  46default=os.environ.get('OS_USERNAME', 'ceilometer'),
  47help='Username to use for openstack service access'),
  48 cfg.StrOpt('os-password',
  49default=os.environ.get('OS_PASSWORD', 'admin'),
  50help='Password to use for openstack service access'),
  51 cfg.StrOpt('os-tenant-id',
  52default=os.environ.get('OS_TENANT_ID', ''),
  53help='Tenant ID to use for openstack service access'),
  54 cfg.StrOpt('os-tenant-name',
  55default=os.environ.get('OS_TENANT_NAME', 'admin'),
  56help='Tenant name to use for openstack service
 access'),
  57 cfg.StrOpt('os_auth_url',
  58default=os.environ.get('OS_AUTH_URL',
  59   'http://localhost:5000/v2.0'),

 So after I change all - to _ and modify all options in
 /etc/ceilometer/ceilometer.conf, the service starts OK.


 The thing that fixed it was changing - to _ in your configuration
 file. The options library allows option names to have - in them so they
 look nice as command line switches, but the option name uses the _.

 Doug





 On Wed, Apr 10, 2013 at 2:02 PM, Liu Wenmao marvel...@gmail.com wrote:

 I solve this problem by two steps:

 1 modify /etc/init/ceilometer-agent-central.conf
 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central --
 --config-file=/etc/ceilometer/ceilometer.conf
 2 add some lines to /etc/ceilometer/ceilometer.conf:
 os-username=ceilometer
 os-password=nsfocus
 os-tenant-name=service
 os-auth-url=http://controller:5000/v2.0



 On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao marvel...@gmail.comwrote:

 Hi all:

 I have just install ceilometer grizzly github version, but fail to
 start ceilometer-agent-central service. I think it is due to that I didn't
 set up the keystone user/password like other projects. but I follow the
 instructions(
 http://docs.openstack.org/developer/ceilometer/install/manual.html#configuring-keystone-to-work-with-api)
 but it does not include the ceilometer configuration.

 # service ceilometer-agent-central start
 ceilometer-agent-central start/running, process 5679

 # cat /etc/init/ceilometer-agent-central.conf
 description ceilometer-agent-compute
 author Chuck Short zul...@ubuntu.com

 start on runlevel [2345]
 stop on runlelvel [!2345]

 chdir /var/run

 pre-start script
 mkdir -p /var/run/ceilometer
 chown ceilometer:ceilometer /var/run/ceilometer

 mkdir -p /var/lock/ceilometer
 chown ceilometer:ceilometer /var/lock/ceilometer
 end script

 exec start-stop-daemon --start --chuid ceilometer --exec
 /usr/local/bin/ceilometer-agent-central


 /var/log/ceilometer/ceilometer-agent-central.log
 2013-04-10 13:01:39ERROR [ceilometer.openstack.common.loopingcall]
 in looping call
 Traceback (most recent call last):
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/openstack/common/loopingcall.py,
 line 67, in _inner
 self.f(*self.args, **self.kw)
   File
 /usr/local/lib/python2.7/dist-packages/ceilometer-2013.1-py2.7.egg/ceilometer/central/manager.py,
 line 76, in interval_task
 auth_url=cfg.CONF.os_auth_url)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 134, in __init__
 self.authenticate()
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/client.py,
 line 205, in authenticate
 token)
   File
 /usr/local/lib/python2.7/dist-packages/python_keystoneclient-0.2.3.1.g3a3e254-py2.7.egg/keystoneclient/v2_0/client.py,
 line 174, in get_raw_token_from_identity_servicetoken=token)
   File
 

Re: [Openstack] Can't log in grizzly's dashboard

2013-04-12 Thread Mohammed Amine SAYA
Hi Heiko, Mouad,

Thank you for help guys.

Yes I checked keystone.log and it looks fine.

I think cinder is having some problems. I am going to post a new help
request for cinder.

Thanks a lot for your help.
Amine.


On Thu, Apr 11, 2013 at 2:44 PM, Heiko Krämer i...@honeybutcher.de wrote:

  Hi Mohammed,


 do you have sync the db with keystone-manage sync_db ?

 Do you see any errors in your keystone.log?

 Greetings
 Heiko

 On 11.04.2013 14:17, Mohammed Amine SAYA wrote:

 Hi all,

  I upgraded my install from folsom to grizzly but I can't log in
 dashboard. I keep getting this error :

  HTTPConnectionPool(host='192.168.0.1', port=8776): Max retries exceeded
 with url:
 /v1/5690876e82414117b80e64167a3ee3f8/os-quota-sets/5690876e82414117b80e64167a3ee3f8

  I haven't changed the database content. I installed grizzly packages
 only.
 Keystone, nova and apache are running fine. I can list endpoints, users
 and tenants.

  nova-manage service list gives this:

 +--++--+-+---++
 | Binary   | Host   | Zone | Status  | State | Updated_at
 |

 +--++--+-+---++
 | nova-cert| openstack0 | internal | enabled | up|
 2013-04-11T12:17:07.00 |
 | nova-compute | openstack1 | nova | enabled | down  |
 2013-04-03T12:45:08.00 |
 | nova-console | openstack0 | internal | enabled | up|
 2013-04-11T12:17:11.00 |
 | nova-consoleauth | openstack0 | internal | enabled | down  |
 2013-04-03T12:45:14.00 |
 | nova-scheduler   | openstack0 | internal | enabled | up|
 2013-04-11T12:17:11.00 |

 +--++--+-+---++

  Do you know how to fix this please?

  Thanks for your help.
 Amine.


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] grizzly's cinder-api is not starting : Couldn't find urlmap package

2013-04-12 Thread Mohammed Amine SAYA
Hi All,

I am trying to start cinder-api but it complains about urlmap module.
I checked in /usr/lib/python2.7/dist-packages/paste/ directory and I
found
urlmap.py and urlmap.pyc.

Have you heard about this behavior in cinder-api? I didn't have it with
FOLSOM.

Here is the error I found in cinder-api.log :

2013-04-12 14:20:29 CRITICAL [cinder] No module named urlmap
Traceback (most recent call last):
  File /usr/bin/cinder-api, line 48, in module
server = service.WSGIService('osapi_volume')
  File /usr/lib/python2.7/dist-packages/cinder/service.py, line 520, in
__init__
self.app = self.loader.load_app(name)
  File /usr/lib/python2.7/dist-packages/cinder/wsgi.py, line 490, in
load_app
return deploy.loadapp(config:%s % self.config_path, name=name)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
247, in loadapp
return loadobj(APP, uri, name=name, **kw)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
271, in loadobj
global_conf=global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
296, in loadcontext
global_conf=global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
320, in _loadconfig
return loader.get_context(object_type, name, global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
454, in get_context
section)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
476, in _context_from_use
object_type, name=use, global_conf=global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
406, in get_context
global_conf=global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
296, in loadcontext
global_conf=global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
337, in _loadfunc
return loader.get_context(object_type, name, global_conf)
  File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line
681, in get_context
obj = lookup_object(self.spec)
  File /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line 69, in
lookup_object
module = __import__(parts)
ImportError: No module named urlmap


Thanks a lot for your help.
Best regards,
Amine.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] controller and network node, same machine?

2013-04-12 Thread Steve Heistand
so Im beginning to think my attempts at getting a controller node and a network
node to be on the same physical machines/OS are doomed.

is it even possible to have all the controller and network node features on
the same box? Aside from one of them being in a VM that is.

thanks

s

-- 

 Steve Heistand   NASA Ames Research Center
 SciCon Group Mail Stop 258-6
 steve.heist...@nasa.gov  (650) 604-4369  Moffett Field, CA 94035-1000

 Any opinions expressed are those of our alien overlords, not my own.

# For Remedy#
#Action: Resolve#
#Resolution: Resolved   #
#Reason: No Further Action Required #
#Tier1: User Code   #
#Tier2: Other   #
#Tier3: Assistance  #
#Notification: None #




signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] grizzly's cinder-api is not starting : Couldn't find urlmap package

2013-04-12 Thread Sean Dague
Please post the contents of your /etc/cinder directory, I think this is 
related to an issue I saw during grenade testing.


-Sean

On 04/12/2013 08:29 AM, Mohammed Amine SAYA wrote:

Hi All,

I am trying to start cinder-api but it complains about urlmap module.
I checked in /usr/lib/python2.7/dist-packages/paste/ directory and I
found
urlmap.py and urlmap.pyc.

Have you heard about this behavior in cinder-api? I didn't have it with
FOLSOM.

Here is the error I found in cinder-api.log :

2013-04-12 14:20:29 CRITICAL [cinder] No module named urlmap
Traceback (most recent call last):
   File /usr/bin/cinder-api, line 48, in module
 server = service.WSGIService('osapi_volume')
   File /usr/lib/python2.7/dist-packages/cinder/service.py, line 520,
in __init__
 self.app = self.loader.load_app(name)
   File /usr/lib/python2.7/dist-packages/cinder/wsgi.py, line 490, in
load_app
 return deploy.loadapp(config:%s % self.config_path, name=name)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 247, in loadapp
 return loadobj(APP, uri, name=name, **kw)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 271, in loadobj
 global_conf=global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 296, in loadcontext
 global_conf=global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 320, in _loadconfig
 return loader.get_context(object_type, name, global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 454, in get_context
 section)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 476, in _context_from_use
 object_type, name=use, global_conf=global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 406, in get_context
 global_conf=global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 296, in loadcontext
 global_conf=global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 337, in _loadfunc
 return loader.get_context(object_type, name, global_conf)
   File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py,
line 681, in get_context
 obj = lookup_object(self.spec)
   File /usr/lib/python2.7/dist-packages/paste/deploy/util.py, line
69, in lookup_object
 module = __import__(parts)
ImportError: No module named urlmap


Thanks a lot for your help.
Best regards,
Amine.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp




--
Sean Dague
http://dague.net

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] grizzly's cinder-api is not starting : Couldn't find urlmap package

2013-04-12 Thread Mohammed Amine SAYA
Hi Sean,

Thanks for your quick answer. Here are the config files in /etc/cinder.

api-paste.ini :

#

# Openstack #

#


[composite:osapi_volume]
use = call:cinder.api.openstack.urlmap:urlmap_factory
/ = osvolumeversions
/v1 = openstack_volume_api_v1

[composite:openstack_volume_api_v1]
use = call:cinder.api.auth:pipeline_factory
noauth = faultwrap sizelimit noauth osapi_volume_app_v1
keystone = faultwrap sizelimit authtoken keystonecontext osapi_volume_app_v1
keystone_nolimit = faultwrap sizelimit authtoken keystonecontext
osapi_volume_app_v1

[filter:faultwrap]
paste.filter_factory = cinder.api.openstack:FaultWrapper.factory

[filter:noauth]
paste.filter_factory = cinder.api.openstack.auth:NoAuthMiddleware.factory

[filter:sizelimit]
paste.filter_factory = cinder.api.sizelimit:RequestBodySizeLimiter.factory

[app:osapi_volume_app_v1]
paste.app_factory = cinder.api.openstack.volume:APIRouter.factory

[pipeline:osvolumeversions]
pipeline = faultwrap osvolumeversionapp

[app:osvolumeversionapp]
paste.app_factory = cinder.api.openstack.volume.versions:Versions.factory

##

# Shared #

##


[filter:keystonecontext]
paste.filter_factory = cinder.api.auth:CinderKeystoneContext.factory

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
service_protocol = http
service_host = 127.0.0.1
service_port = 5000
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = cinder
admin_password = xxx


cinder.conf :

[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
sql_connection = mysql://cinder:xxx@localhost:3306/cinder
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper = tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
logdir = /var/log/cinder
state_path = /var/lib/cinder
volumes_dir = /var/lib/cinder/volumes
lock_path = /var/lock/cinder
rabbit_password = xxx
rabbit_userid = guest
rabbit_host = 127.0.0.1
rabbit_port = 5672


On Fri, Apr 12, 2013 at 2:46 PM, Sean Dague s...@dague.net wrote:

 Please post the contents of your /etc/cinder directory, I think this is
 related to an issue I saw during grenade testing.

 -Sean


 On 04/12/2013 08:29 AM, Mohammed Amine SAYA wrote:

 Hi All,

 I am trying to start cinder-api but it complains about urlmap module.
 I checked in /usr/lib/python2.7/dist-**packages/paste/ directory and I
 found
 urlmap.py and urlmap.pyc.

 Have you heard about this behavior in cinder-api? I didn't have it with
 FOLSOM.

 Here is the error I found in cinder-api.log :

 2013-04-12 14:20:29 CRITICAL [cinder] No module named urlmap
 Traceback (most recent call last):
File /usr/bin/cinder-api, line 48, in module
  server = service.WSGIService('osapi_**volume')
File /usr/lib/python2.7/dist-**packages/cinder/service.py, line 520,
 in __init__
  self.app = self.loader.load_app(name)
File /usr/lib/python2.7/dist-**packages/cinder/wsgi.py, line 490, in
 load_app
  return deploy.loadapp(config:%s % self.config_path, name=name)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 247, in loadapp
  return loadobj(APP, uri, name=name, **kw)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 271, in loadobj
  global_conf=global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 296, in loadcontext
  global_conf=global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 320, in _loadconfig
  return loader.get_context(object_**type, name, global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 454, in get_context
  section)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 476, in _context_from_use
  object_type, name=use, global_conf=global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 406, in get_context
  global_conf=global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 296, in loadcontext
  global_conf=global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 337, in _loadfunc
  return loader.get_context(object_**type, name, global_conf)
File /usr/lib/python2.7/dist-**packages/paste/deploy/**loadwsgi.py,
 line 681, in get_context
  obj = lookup_object(self.spec)
File /usr/lib/python2.7/dist-**packages/paste/deploy/util.py**, line
 69, in lookup_object
  module = __import__(parts)
 ImportError: No module named urlmap


 Thanks a lot for your help.
 Best regards,
 Amine.


 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 More help 

Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Mohammed Amine SAYA
Hi Steve,

Why do you say that?
I am curious to learn about the difficulties you have had.

I also tried to have controller node and network node running on the same
machine but I have never
managed to ping a running VM in this configuration with FOLSOM release.
Everything was working fine
but impossible to ping a VM.

Amine.


On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.govwrote:

 so Im beginning to think my attempts at getting a controller node and a
 network
 node to be on the same physical machines/OS are doomed.

 is it even possible to have all the controller and network node features on
 the same box? Aside from one of them being in a VM that is.

 thanks

 s

 --
 
  Steve Heistand   NASA Ames Research Center
  SciCon Group Mail Stop 258-6
  steve.heist...@nasa.gov  (650) 604-4369  Moffett Field, CA 94035-1000
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Razique Mahroua
You just need to want it badly enough :^)What version of OpenStack are you using? Which guides did you read ?Regards,
Razique Mahroua-Nuage  Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15

Le 12 avr. 2013 à 15:05, Mohammed Amine SAYA asaya.openst...@gmail.com a écrit :Hi Steve,Why do you say that?I am curious to learn about the difficulties you have had.I also tried to have controller node and network node running on the same machine but I have never
managed to ping a running VM in this configuration with FOLSOM release. Everything was working finebut impossible to ping a VM.Amine.
On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.gov wrote:
so Im beginning to think my attempts at getting a controller node and a network
node to be on the same physical machines/OS are doomed.

is it even possible to have all the controller and network node features on
the same box? Aside from one of them being in a VM that is.

thanks

s

--

Steve Heistand  NASA Ames Research Center
SciCon Group   Mail Stop 258-6
steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000

"Any opinions expressed are those of our alien overlords, not my own."

# For Remedy#
#Action: Resolve  #
#Resolution: Resolved#
#Reason: No Further Action Required #
#Tier1: User Code  #
#Tier2: Other#
#Tier3: Assistance #
#Notification: None #


___
Mailing list: https://launchpad.net/~openstack
Post to   : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help  : https://help.launchpad.net/ListHelp

___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Martinx - ジェームズ
Hi Steve!

Yes, it is possible.

Instructions:

Ultimate OpenStack Grizzly Guide:
https://gist.github.com/tmartinx/d36536b7b62a48f859c2

Best!
Thiago


On 12 April 2013 09:40, Steve Heistand steve.heist...@nasa.gov wrote:

 so Im beginning to think my attempts at getting a controller node and a
 network
 node to be on the same physical machines/OS are doomed.

 is it even possible to have all the controller and network node features on
 the same box? Aside from one of them being in a VM that is.

 thanks

 s

 --
 
  Steve Heistand   NASA Ames Research Center
  SciCon Group Mail Stop 258-6
  steve.heist...@nasa.gov  (650) 604-4369  Moffett Field, CA 94035-1000
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Steve Heistand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

mostly Im concerned about the quantum/OVS/qre settings.
there are distinct difference in the values in the ovs_quantum_plugin.ini
file depending on what type of node the agent is running on.
I wasnt sure if it going to work.
The problems Ive been having are all network related all centered around
getting VMs on compute nodes to be able to see something besides another
VM in their tenant. ie the outside world.
But my network/ovs-fu is limited so its entirely possible its my fault.
just wanted to see if it was even possible in the first place.

s


On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote:
 Hi Steve,
 
 Why do you say that? I am curious to learn about the difficulties you have 
 had.
 
 I also tried to have controller node and network node running on the same 
 machine but
 I have never managed to ping a running VM in this configuration with FOLSOM 
 release.
  Everything was working fine but impossible to ping a VM.
 
 Amine.
 
 
 On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.gov 
 mailto:steve.heist...@nasa.gov wrote:
 
 so Im beginning to think my attempts at getting a controller node and a 
 network node
 to be on the same physical machines/OS are doomed.
 
 is it even possible to have all the controller and network node features on 
 the same
 box? Aside from one of them being in a VM that is.
 
 thanks
 
 s
 
 --  
 Steve
 Heistand   NASA Ames Research Center SciCon Group
 Mail Stop 258-6 steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov (650)
 604-4369 tel:%28650%29%20604-4369  Moffett Field, CA 94035-1000 
  Any
 opinions expressed are those of our alien overlords, not my own.
 
 # For Remedy# #Action: Resolve# 
 #Resolution: Resolved   # #Reason: No Further Action Required # 
 #Tier1:
 User Code   # #Tier2: Other   # #Tier3:
 Assistance  # #Notification: None #
 
 
 
 ___ Mailing list:
 https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
 mailto:openstack@lists.launchpad.net Unsubscribe :
 https://launchpad.net/~openstack More help   : 
 https://help.launchpad.net/ListHelp
 
 

- -- 

 Steve Heistand  NASA Ames Research Center
 email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
 ph: (650) 604-4369  Bldg. 258, Rm. 232-5
 Scientific  HPC ApplicationP.O. Box 1
 Development/OptimizationMoffett Field, CA 94035-0001

 Any opinions expressed are those of our alien overlords, not my own.

# For Remedy#
#Action: Resolve#   
#Resolution: Resolved   #
#Reason: No Further Action Required #
#Tier1: User Code   #
#Tier2: Other   #
#Tier3: Assistance  #
#Notification: None #
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAlFoDYAACgkQoBCTJSAkVrEXDACeMBENxoBLL4OdayOsSHHDfjgg
juUAoMzQCTR2DVk1+usy3SV3yENkrtmP
=3vok
-END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ANN] Tsuru PaaS Free Trial SignUp

2013-04-12 Thread Flavia Missi
Hi,

We from globo.com's PaaS team are launching try.tsuru.io as a private beta
with the goal of making available an easy way of people get to know and try
tsuru.

With tsuru, developers and teams don't need to worry with servers or
with building
a deploy, they can focus on the most important: the application.

Tsuru makes possible to write applications in the language of your
preference, to use services
like SQL and NoSQL databases, memcached, redis (and many others) by
simply plugin them into your
application.

You manage your application using the command line or the web
interface and you deploy via git.
Everything is taken care by tsuru's infrastructure.

You also can change tsuru's orchestration system. We currently work
with Amazon, OpenStack (via EC2 api), LXC,
and docker (the latter is in development stage).

Tsuru is an Open Source project, feel free to look its source[0],
build your own PaaS using tsuru[1],
contribute[2] or suggest features/report bugs[3].

[0] - https://github.com/globocom/tsuru/
[1] - http://docs.tsuru.io/en/latest/lxc.html
[2] - http://docs.tsuru.io/en/latest/#contributions-and-feedback
[3] - https://github.com/globocom/tsuru/issues

Thank you!


-- 
Flavia
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] does anyone install grizzly using tarballs.? ,step by step. ,without apt-get nova……etc

2013-04-12 Thread Matthew Thode
On 04/12/13 02:04, 郭龙仓 wrote:
 
 
 
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 
I do, in Gentoo.  What do you need to know?

-- 
-- Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] RPC call timeouts

2013-04-12 Thread Lowery, Mathew
Hi all,

I am using OpenStack Folsom with nova-network.  In the logs I observed some RPC 
call timeouts during associate_floating_ip.  I assume the timeout is actually a 
timeout experienced by RabbitMQ when trying to push the associate_floating_ip 
message to a chosen consumer and not a timeout from nova.network.API when 
trying to publish the associate_floating_ip message in the first place.  Could 
this be possible?  If so, how can I tell what consumer RabbitMQ chose (i.e. the 
down consumer)?

Furthermore, I'm seeing multiple thousands of exchanges (associate_floating_ip 
was called a lot) with UUIDs as their names.  Is it possible that these 
exchanges were created to receive responses from the down consumer?  Who is 
responsible for cleaning these exchanges up?  I do see an auto-delete flag 
set to true.

Finally, it appears that when an RPC call times out, the original message, at 
least is some cases like 'network.hostname' queue, is left in place to be 
consumed when a consumer is available.  This seems like an odd design--if I 
take corrective action in response to an RPC timeout, I don't think I want that 
message processed ever.

I am somewhat new to message queues so feel free to simply share links that 
might explain some of these observations.

Thanks in advance.
Mat
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] error in quantum in folsom

2013-04-12 Thread Aaron Rosen
if you do quantum -v net-create --tenant-id 112a75ab04224fa3b44109a6c4859c28
net1 , you'll see the end host your client is trying to connect to. I'd
check that this is the right IP of your quantum box and that your client
has ip connectivity to that client.

Aaron


On Fri, Apr 12, 2013 at 4:13 AM, Arindam Choudhury arin...@live.com wrote:

 Hi,

 I am new to openstack and I am trying to install openstack folsom on
 fedora 18. any help will be highly appreciated.

 while installing quantum I got this error:

 [(keystone_admin)]$ quantum net-create --tenant-id
 112a75ab04224fa3b44109a6c4859c28 net1
 [Errno 110] Connection timed out

  /var/log/quantum/server.log
 2013-04-12 12:43:53 INFO [quantum.common.config] Logging enabled!
 2013-04-12 12:43:53 INFO [quantum.common.config] Config paste file:
 /etc/quantum/api-paste.ini
 2013-04-12 12:43:53 INFO [quantum.manager] Loading Plugin:
 quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
 2013-04-12 12:43:53 INFO
 [quantum.plugins.openvswitch.ovs_quantum_plugin] Network VLAN ranges: {}
 2013-04-12 12:43:53 INFO [quantum.openstack.common.rpc.impl_qpid]
 Connected to AMQP server on 158.109.65.21:5672
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Initializing
 extension manager.
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: __init__.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: extensions.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: _quotav2_model.py
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: l3.py
 2013-04-12 12:43:53  WARNING [quantum.api.extensions] Loaded extension:
 router
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: _quotav2_model.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: _quotav2_driver.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: quotasv2.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: providernet.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: flavor.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: l3.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: quotasv2.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: l3.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: extensions.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: providernet.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: quotasv2.py
 2013-04-12 12:43:53  WARNING [quantum.api.extensions] Exception loading
 extension: Invalid extension environment: quota driver
 quantum.extensions._quotav2_driver.DbQuotaDriver is needed.
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: extensions.py
 2013-04-12 12:43:53  WARNING [quantum.api.extensions] Did not find
 expected name Extensions in
 /usr/lib/python2.7/site-packages/quantum/extensions/extensions.py
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: __init__.py
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: flavor.py
 2013-04-12 12:43:53  WARNING [quantum.api.extensions] extension flavor not
 supported by plugin
 quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 object
 at 0x39a4450
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: __init__.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: _quotav2_driver.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: flavor.pyc
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: providernet.py
 2013-04-12 12:43:53  WARNING [quantum.api.extensions] Loaded extension:
 provider
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: _quotav2_model.pyo
 2013-04-12 12:43:53 INFO [quantum.api.extensions] Loading extension
 file: _quotav2_driver.py
 2013-04-12 12:43:53 INFO [keystone.middleware.auth_token] Starting
 keystone auth_token middleware
 2013-04-12 12:43:53 INFO [keystone.middleware.auth_token] Using
 /var/lib/quantum/keystone-signing as cache directory for signing certificate
 2013-04-12 13:08:07 INFO [quantum.openstack.common.rpc.impl_qpid]
 Connected to AMQP server on 158.109.65.21:5672
 2013-04-12 13:09:05 INFO [quantum.common.config] Logging enabled!
 2013-04-12 13:09:05 INFO [quantum.common.config] Config paste file:
 /etc/quantum/api-paste.ini
 2013-04-12 13:09:05 INFO [quantum.manager] Loading Plugin:
 quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
 2013-04-12 13:09:05 INFO
 [quantum.plugins.openvswitch.ovs_quantum_plugin] 

Re: [Openstack] RPC call timeouts

2013-04-12 Thread Sylvain Bauza
Have you tried to look at the RabbitMQ web interface to see what could 
be stuck ?

Activating it is quite straightforward, as per Ops Guide :
http://docs.openstack.org/trunk/openstack-ops/content/logging_monitoring.html#rabbitmq

-Sylvain


Le 12/04/2013 17:48, Lowery, Mathew a écrit :

Hi all,

I am using OpenStack Folsom with nova-network.  In the logs I observed 
some RPC call timeouts during associate_floating_ip.  I assume the 
timeout is actually a timeout experienced by RabbitMQ when trying to 
push the associate_floating_ip message to a chosen consumer and not a 
timeout from nova.network.API when trying to publish the 
associate_floating_ip message in the first place.  Could this be 
possible?  If so, how can I tell what consumer RabbitMQ chose (i.e. 
the down consumer)?


Furthermore, I'm seeing multiple thousands of 
exchanges (associate_floating_ip was called a lot) with UUIDs as their 
names.  Is it possible that these exchanges were created to receive 
responses from the down consumer?  Who is responsible for cleaning 
these exchanges up?  I do see an auto-delete flag set to true.


Finally, it appears that when an RPC call times out, the original 
message, at least is some cases like 'network.hostname' queue, is left 
in place to be consumed when a consumer is available.  This seems like 
an odd design--if I take corrective action in response to an RPC 
timeout, I don't think I want that message processed ever.


I am somewhat new to message queues so feel free to simply share links 
that might explain some of these observations.


Thanks in advance.
Mat


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] RPC call timeouts

2013-04-12 Thread Eric Windisch
 
 Finally, it appears that when an RPC call times out, the original message, at 
 least is some cases like 'network.hostname' queue, is left in place to be 
 consumed when a consumer is available. This seems like an odd design--if I 
 take corrective action in response to an RPC timeout, I don't think I want 
 that message processed ever. 
 


For what it is worth, Grizzly introduces TTLs for individual messages as 
they're injected into RabbitMQ and Qpid.  This was already the behavior for 
ZeroMQ, in Folsom.

Regards,
Eric Windisch


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Guilherme Russi
Hello Steve, I had a lot of troubles deploying my openstack and putting my
controller node at the same physical machine with my network node, I have 2
NICs in my controller + network node, if you need help, I can help you.

Regards.

Guilherme.


2013/4/12 Steve Heistand steve.heist...@nasa.gov

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 mostly Im concerned about the quantum/OVS/qre settings.
 there are distinct difference in the values in the ovs_quantum_plugin.ini
 file depending on what type of node the agent is running on.
 I wasnt sure if it going to work.
 The problems Ive been having are all network related all centered around
 getting VMs on compute nodes to be able to see something besides another
 VM in their tenant. ie the outside world.
 But my network/ovs-fu is limited so its entirely possible its my fault.
 just wanted to see if it was even possible in the first place.

 s


 On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote:
  Hi Steve,
 
  Why do you say that? I am curious to learn about the difficulties you
 have had.
 
  I also tried to have controller node and network node running on the
 same machine but
  I have never managed to ping a running VM in this configuration with
 FOLSOM release.
   Everything was working fine but impossible to ping a VM.
 
  Amine.
 
 
  On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.gov
  mailto:steve.heist...@nasa.gov wrote:
 
  so Im beginning to think my attempts at getting a controller node and a
 network node
  to be on the same physical machines/OS are doomed.
 
  is it even possible to have all the controller and network node features
 on the same
  box? Aside from one of them being in a VM that is.
 
  thanks
 
  s
 
  --
 
 Steve
  Heistand   NASA Ames Research Center SciCon Group
  Mail Stop 258-6 steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov
 (650)
  604-4369 tel:%28650%29%20604-4369  Moffett Field, CA 94035-1000
  
 Any
  opinions expressed are those of our alien overlords, not my own.
 
  # For Remedy# #Action: Resolve
  #
  #Resolution: Resolved   # #Reason: No Further Action
 Required # #Tier1:
  User Code   # #Tier2: Other   #
 #Tier3:
  Assistance  # #Notification: None #
 
 
 
  ___ Mailing list:
  https://launchpad.net/~openstack Post to :
 openstack@lists.launchpad.net
  mailto:openstack@lists.launchpad.net Unsubscribe :
  https://launchpad.net/~openstack More help   :
 https://help.launchpad.net/ListHelp
 
 

 - --
 
  Steve Heistand  NASA Ames Research Center
  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
  Scientific  HPC ApplicationP.O. Box 1
  Development/OptimizationMoffett Field, CA 94035-0001
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.14 (GNU/Linux)

 iEYEARECAAYFAlFoDYAACgkQoBCTJSAkVrEXDACeMBENxoBLL4OdayOsSHHDfjgg
 juUAoMzQCTR2DVk1+usy3SV3yENkrtmP
 =3vok
 -END PGP SIGNATURE-

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Pranav
Do you mean production environment by same physical box? Because I have
tried it and it worked for me.

Regards,
Pranav


On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi 
luisguilherme...@gmail.com wrote:

 Hello Steve, I had a lot of troubles deploying my openstack and putting my
 controller node at the same physical machine with my network node, I have 2
 NICs in my controller + network node, if you need help, I can help you.

 Regards.

 Guilherme.


 2013/4/12 Steve Heistand steve.heist...@nasa.gov

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 mostly Im concerned about the quantum/OVS/qre settings.
 there are distinct difference in the values in the ovs_quantum_plugin.ini
 file depending on what type of node the agent is running on.
 I wasnt sure if it going to work.
 The problems Ive been having are all network related all centered around
 getting VMs on compute nodes to be able to see something besides another
 VM in their tenant. ie the outside world.
 But my network/ovs-fu is limited so its entirely possible its my fault.
 just wanted to see if it was even possible in the first place.

 s


 On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote:
  Hi Steve,
 
  Why do you say that? I am curious to learn about the difficulties you
 have had.
 
  I also tried to have controller node and network node running on the
 same machine but
  I have never managed to ping a running VM in this configuration with
 FOLSOM release.
   Everything was working fine but impossible to ping a VM.
 
  Amine.
 
 
  On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand 
 steve.heist...@nasa.gov
  mailto:steve.heist...@nasa.gov wrote:
 
  so Im beginning to think my attempts at getting a controller node and a
 network node
  to be on the same physical machines/OS are doomed.
 
  is it even possible to have all the controller and network node
 features on the same
  box? Aside from one of them being in a VM that is.
 
  thanks
 
  s
 
  --
 
 Steve
  Heistand   NASA Ames Research Center SciCon
 Group
  Mail Stop 258-6 steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov
 (650)
  604-4369 tel:%28650%29%20604-4369  Moffett Field, CA 94035-1000
 
 
 Any
  opinions expressed are those of our alien overlords, not my own.
 
  # For Remedy# #Action: Resolve
#
  #Resolution: Resolved   # #Reason: No Further Action
 Required # #Tier1:
  User Code   # #Tier2: Other   #
 #Tier3:
  Assistance  # #Notification: None #
 
 
 
  ___ Mailing list:
  https://launchpad.net/~openstack Post to :
 openstack@lists.launchpad.net
  mailto:openstack@lists.launchpad.net Unsubscribe :
  https://launchpad.net/~openstack More help   :
 https://help.launchpad.net/ListHelp
 
 

 - --
 
  Steve Heistand  NASA Ames Research Center
  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
  Scientific  HPC ApplicationP.O. Box 1
  Development/OptimizationMoffett Field, CA 94035-0001
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.14 (GNU/Linux)

 iEYEARECAAYFAlFoDYAACgkQoBCTJSAkVrEXDACeMBENxoBLL4OdayOsSHHDfjgg
 juUAoMzQCTR2DVk1+usy3SV3yENkrtmP
 =3vok
 -END PGP SIGNATURE-

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Pranav
oops clicked send too soon ...
Do you mean production environment by same physical box? Because I have
tried it and it worked for me but it was on a ubuntu desktop which is kind
of like a hybrid of server + desktop now.

Regards,
Pranav


On Fri, Apr 12, 2013 at 11:01 PM, Pranav pps.pra...@gmail.com wrote:

 Do you mean production environment by same physical box? Because I have
 tried it and it worked for me.

 Regards,
 Pranav


 On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi 
 luisguilherme...@gmail.com wrote:

 Hello Steve, I had a lot of troubles deploying my openstack and putting
 my controller node at the same physical machine with my network node, I
 have 2 NICs in my controller + network node, if you need help, I can help
 you.

 Regards.

 Guilherme.


 2013/4/12 Steve Heistand steve.heist...@nasa.gov

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 mostly Im concerned about the quantum/OVS/qre settings.
 there are distinct difference in the values in the ovs_quantum_plugin.ini
 file depending on what type of node the agent is running on.
 I wasnt sure if it going to work.
 The problems Ive been having are all network related all centered around
 getting VMs on compute nodes to be able to see something besides another
 VM in their tenant. ie the outside world.
 But my network/ovs-fu is limited so its entirely possible its my fault.
 just wanted to see if it was even possible in the first place.

 s


 On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote:
  Hi Steve,
 
  Why do you say that? I am curious to learn about the difficulties you
 have had.
 
  I also tried to have controller node and network node running on the
 same machine but
  I have never managed to ping a running VM in this configuration with
 FOLSOM release.
   Everything was working fine but impossible to ping a VM.
 
  Amine.
 
 
  On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand 
 steve.heist...@nasa.gov
  mailto:steve.heist...@nasa.gov wrote:
 
  so Im beginning to think my attempts at getting a controller node and
 a network node
  to be on the same physical machines/OS are doomed.
 
  is it even possible to have all the controller and network node
 features on the same
  box? Aside from one of them being in a VM that is.
 
  thanks
 
  s
 
  --
 
 Steve
  Heistand   NASA Ames Research Center SciCon
 Group
  Mail Stop 258-6 steve.heist...@nasa.gov mailto:
 steve.heist...@nasa.gov (650)
  604-4369 tel:%28650%29%20604-4369  Moffett Field, CA 94035-1000
 
 
 Any
  opinions expressed are those of our alien overlords, not my own.
 
  # For Remedy# #Action: Resolve
#
  #Resolution: Resolved   # #Reason: No Further Action
 Required # #Tier1:
  User Code   # #Tier2: Other   #
 #Tier3:
  Assistance  # #Notification: None #
 
 
 
  ___ Mailing list:
  https://launchpad.net/~openstack Post to :
 openstack@lists.launchpad.net
  mailto:openstack@lists.launchpad.net Unsubscribe :
  https://launchpad.net/~openstack More help   :
 https://help.launchpad.net/ListHelp
 
 

 - --
 
  Steve Heistand  NASA Ames Research Center
  email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
  ph: (650) 604-4369  Bldg. 258, Rm. 232-5
  Scientific  HPC ApplicationP.O. Box 1
  Development/OptimizationMoffett Field, CA 94035-0001
 
  Any opinions expressed are those of our alien overlords, not my own.

 # For Remedy#
 #Action: Resolve#
 #Resolution: Resolved   #
 #Reason: No Further Action Required #
 #Tier1: User Code   #
 #Tier2: Other   #
 #Tier3: Assistance  #
 #Notification: None #
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.14 (GNU/Linux)

 iEYEARECAAYFAlFoDYAACgkQoBCTJSAkVrEXDACeMBENxoBLL4OdayOsSHHDfjgg
 juUAoMzQCTR2DVk1+usy3SV3yENkrtmP
 =3vok
 -END PGP SIGNATURE-

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : 

Re: [Openstack] [Quantum] Anybody implemented DMZ?

2013-04-12 Thread David Kang

 I did some experiment with two subnets - one for DMZ, the other 
for non-DMZ. But, it looks like that separation of network traffic between them
doesn't work with two quantum routers.

 We use linux-bridge plugin.
Network name space is not supported.

 When two subnets (e.g. 10.12.83.0/24, 10.12.84.0/24) are created, 
the Quantum network node has ports to both subnets(10.12.83.1/24, 
10.12.84.1/24).
Two quantum routers were created for each subnets.
Pinging from a VM in 10.12.83.0/24 to a VM in 10.12.84.0/24 is routed by
the Quantum network node itself.
Before Quantum router routes the packets to the external network,
the Quantum network node routes internally because it knows both network.
I want the traffic to be routed to the external network through the
Quantum router. But it doesn't happen.

 Am I doing something wrong?

 Thanks,
 David


- Original Message -
 In my reply I suggested you to create two quantum routers which I
 believe should solve this for you.
 
 
 
 
 quantum net-create DMZ-net --external=True
 quantum subnet-create --name DMZ-Subnet1 DMZ-net dmz_cidr # Public
 ip pool
 
 quantum net-create non-DMZ --external=True
 quantum subnet-create --name nonDMZ-Subnet1 non-DMZ dmz_cidr #
 Public ip pool
 
 
 
 
 
 quantum router-create DMZ-router
 quantum router-create non-DMZ-router
 quantum router-interface-add DMZ-router DMZ DMZ-Subnet1
 quantum router-interface-add non-DMZ-router nonDMZ-Subnet1
 
 
 quantum router-gateway-set DMZ-router DMZ-net
 quantum router-gateway-set non-DMZ-router non-DMZ
 
 
 
 
 On Thu, Apr 4, 2013 at 10:51 AM, David Kang  dk...@isi.edu  wrote:
 
 
 
 
 Hi Aron,
 
 Thank you for your reply.
 
 We deploy one (quantum) subnet as a DMZ network and the other
 (quantum) subnet
 as a non-DMZ network.
 They are routed to the network node where quantum services (dhcp, l3,
 linuxbridge)
 are running.
 They can talk each other through network node, now.
 
 However, we do not want to the network node to route the traffic
 between them directly.
 Instead we want them to be routed to different (external) routers such
 that
 we can apply filtering/firewall/etc. on the traffic from DMZ network.
 
 Do you think is it possible using two l3-agents or any other way?
 Currently, I manually set up routings for those two subnets.
 
 Thanks,
 David
 
 
 
 - Original Message -
  Hi David,
 
 
  The quantum network node would route traffic between the non-DMZ-DMZ
  network if both of those subnets are uplinked to the same quantum
  router. I believe if you create another router for your dmz hosts
  then
  traffic in/out of that network should route our to your physical
  infrastructure which will go through your router to do filtering.
 
 
  Thanks,
 
 
  Aaron
 
 
 
  On Wed, Apr 3, 2013 at 8:26 AM, David Kang  dk...@isi.edu  wrote:
 
 
 
  Hi,
 
  We are trying to set up Quantum network for non-DMZ and DMZ
  networks.
  The cloud has both non-DMZ networks and a DMZ network.
  We need to route traffic from DMZ network to a specific router
  before
  it reaches
  anywhere else in non-DMZ networks.
  However, Quantum Network Node routes the traffic between DMZ network
  and
  non-DMZ network within itself by default.
  Have anybody configured Quantum for this case?
  Any help will be appreciated.
  We are using Quantum linuxbridge-agent.
 
  Thanks,
  David
 
  --
  --
  Dr. Dong-In David Kang
  Computer Scientist
  USC/ISI
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help : https://help.launchpad.net/ListHelp
 
 --
 --
 Dr. Dong-In David Kang
 Computer Scientist
 USC/ISI

-- 
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] controller and network node, same machine?

2013-04-12 Thread Steve Heistand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

well its me playing around with openstack so I wouldnt say production 
environment.
but certainly on a dedicated rack full of nodes that just do openstack.
running ubuntu 12.04lts on everything.

the controller+network is on its own box with a boatload of ethernet connections
around to various places including the dual ethernet dual switch compute nodes.

vm to vm is good, vm to anywhere else not so much.

s


On 04/12/2013 10:32 AM, Pranav wrote:
 oops clicked send too soon ... Do you mean production environment by same 
 physical
 box? Because I have tried it and it worked for me but it was on a ubuntu 
 desktop
 which is kind of like a hybrid of server + desktop now.
 
 Regards, Pranav
 
 
 On Fri, Apr 12, 2013 at 11:01 PM, Pranav pps.pra...@gmail.com 
 mailto:pps.pra...@gmail.com wrote:
 
 Do you mean production environment by same physical box? Because I have tried 
 it and
 it worked for me.
 
 Regards, Pranav
 
 
 On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi luisguilherme...@gmail.com
 mailto:luisguilherme...@gmail.com wrote:
 
 Hello Steve, I had a lot of troubles deploying my openstack and putting my 
 controller
 node at the same physical machine with my network node, I have 2 NICs in my
 controller + network node, if you need help, I can help you.
 
 Regards.
 
 Guilherme.
 
 
 2013/4/12 Steve Heistand steve.heist...@nasa.gov 
 mailto:steve.heist...@nasa.gov
 
 mostly Im concerned about the quantum/OVS/qre settings. there are distinct 
 difference
 in the values in the ovs_quantum_plugin.ini file depending on what type of 
 node the
 agent is running on. I wasnt sure if it going to work. The problems Ive been 
 having
 are all network related all centered around getting VMs on compute nodes to 
 be able
 to see something besides another VM in their tenant. ie the outside world. 
 But my
 network/ovs-fu is limited so its entirely possible its my fault. just wanted 
 to see
 if it was even possible in the first place.
 
 s
 
 
 On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote:
 Hi Steve,
 
 Why do you say that? I am curious to learn about the difficulties you have 
 had.
 
 I also tried to have controller node and network node running on the same 
 machine
 but I have never managed to ping a running VM in this configuration with 
 FOLSOM
 release. Everything was working fine but impossible to ping a VM.
 
 Amine.
 
 
 On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.gov
 mailto:steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov
 mailto:steve.heist...@nasa.gov wrote:
 
 so Im beginning to think my attempts at getting a controller node and a 
 network
 node to be on the same physical machines/OS are doomed.
 
 is it even possible to have all the controller and network node features on 
 the
 same box? Aside from one of them being in a VM that is.
 
 thanks
 
 s
 
 --  
 Steve 
 Heistand   NASA Ames Research Center SciCon Group 
 Mail Stop
 258-6steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov
 mailto:steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov (650)
 604-4369 tel:%28650%29%20604-4369  Moffett Field, CA 94035-1000 
  
 Any 
 opinions expressed are those of our alien overlords, not my own.
 
 # For Remedy# #Action: Resolve# 
 #Resolution: Resolved   # #Reason: No Further Action Required #
 #Tier1: User Code   # #Tier2: Other   #
 #Tier3: Assistance  # #Notification: None #
 
 
 
 ___ Mailing list: 
 https://launchpad.net/~openstack Post to :
 openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net
 mailto:openstack@lists.launchpad.net
 mailto:openstack@lists.launchpad.net Unsubscribe :
 https://launchpad.net/~openstack More help   :
 https://help.launchpad.net/ListHelp
 
 
 
 
 ___ Mailing list:
 https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
 mailto:openstack@lists.launchpad.net Unsubscribe :
 https://launchpad.net/~openstack More help   : 
 https://help.launchpad.net/ListHelp
 
 
 
 ___ Mailing list:
 https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net 
 mailto:openstack@lists.launchpad.net Unsubscribe :
 https://launchpad.net/~openstack More help   : 
 https://help.launchpad.net/ListHelp
 
 
 

- -- 

 Steve Heistand  NASA Ames Research Center
 email: steve.heist...@nasa.gov  Steve Heistand/Mail Stop 258-6
 ph: (650) 604-4369  Bldg. 258, Rm. 232-5
 Scientific  HPC ApplicationP.O. Box 1
 

[Openstack] Savanna Presentation on OpenStack Summit

2013-04-12 Thread Ilya Elterman
Hello everyone,

We'll be presenting Savanna (Hadoop on OpenStack project) at Unconference
track on *April 15th, Monday 11:50am* during OpenStack Summit in Portland.

We'll cover the background of what Savanna is, roadmap, show live demo of
the current functionality and talk about plans for the next phase.

Everybody who'll be on the summit are welcome to attend!

Unconference track is a room dedicated to technical discussion and
presentation of the new projects with no official schedule published, we
have Monday 11:50 slot booked for Savanna. The room # is *A104.*

Ilya

-- 
Ilya Elterman
Senior Director,
Cloud Services,
Mirantis
http://www.mirantis.com
tel. +1 650 963 9828
mob. +1 650 561 5779
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] How to start Horizon?

2013-04-12 Thread Tiantian Gao
你可以考虑看下官方文档先


2013/4/12 郭龙仓 guolongcang.w...@gmail.com

 I have installed Horizon lonely,how to start it ?

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Savanna-all] [Savanna] 0.1 Release!

2013-04-12 Thread Dmitry Mescheryakov
Let me explain my position on that matter.

Savanna is an OpenStack service dedicated to provisioning Hadoop clusters.
Taking into account Amazon Cloud Formation approach, it makes sense to
expose Savanna as one of Heat resources. Just like Amazon exposes its
services as CF resources.

We could also use Heat inside Savanna to perform the actual provisioning.
But the thing is that the provisioning operations Savanna does right now
are rather trivial. Using Heat will make it more complex without adding
significant value. Certainly this might change in the future, but we do not
consider to use Heat in the current phase.

Sure we can discuss this during Savanna presentation which will take place
in Unconference room on Monday at 11:50.

Dmitry


-- Forwarded message --
From: Sergey Lukjanov slukja...@mirantis.com
Date: 2013/4/11
Subject: Re: [Savanna-all] [Openstack] [Savanna] 0.1 Release!
To: Robert Collins robe...@robertcollins.net, Lloyd Dewolf 
lloydost...@gmail.com
Cc: OpenStack Development Mailing List openstack-...@lists.openstack.org,
savanna-...@lists.launchpad.net, openstack@lists.launchpad.net


Absolutely. The main difference is that Savanna is the Hadoop oriented
service.
It aims to provide unified user-friendly API that will allow users to
deploy Hadoop clusters fastly and without additional configurations for
cluster provisioning.

Sergey Lukjanov

On Apr 11, 2013, at 20:21, Lloyd Dewolf lloydost...@gmail.com wrote:

 On Wed, Apr 10, 2013 at 3:45 PM, Robert Collins
 robe...@robertcollins.net wrote:

 On 11 April 2013 08:30, Sergey Lukjanov slukja...@mirantis.com wrote:
 Hi everybody,

 we finished Phase 1 of our roadmap and released the first project
release!

 Currently Savanna has the REST API for Hadoop cluster provisioning
using pre-installed images and we started working on pluggable mechanism
for custom cluster provisioning tools.

 Also I'd like to note that custom pages for OpenStack Dashbord have
been published too.

 You can find more info on Savanna site:

 Savanna seems to fit into the same space as Heat (going off your
 diagram on http://savanna.mirantis.com/) - can you explain how it is
 different?


 My understanding of Savanna is it's complete focus on Hadoop.

 Monty also recently asked about the opportunity for Savanna to use
 Heat in a thread titled Re: [openstack-dev] [EHO] Project name change
 [Savanna]
 http://markmail.org/message/2vre6r4kgwqhvhav

 Hope that helps,
 Lloyd

 --
 @lloyddewolf
 http://www.pistoncloud.com/


--
Mailing list: https://launchpad.net/~savanna-all
Post to : savanna-...@lists.launchpad.net
Unsubscribe : https://launchpad.net/~savanna-all
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] How to start Horizon?

2013-04-12 Thread Bhandaru, Malini K
Horizon depends on Keystone for authentication, so there are some dependencies.
Assuming you have these set up

cd to the horizon home directory

cd horizon_home
python ./manage.py runserver 0.0.0.0:port_num

access the above through your favorite browser (not IE)
http://localhost:port_num/http://localhost:%3cport_num%3e/

The password for the admin and demo accounts are what you have in the keystone 
database (which you may have set up via the localrc file if you used devstack).

Regards
Malini
From: Openstack 
[mailto:openstack-bounces+malini.k.bhandaru=intel@lists.launchpad.net] On 
Behalf Of Tiantian Gao
Sent: Friday, April 12, 2013 4:58 PM
To: 郭龙仓
Cc: openstack-operat...@lists.openstack.org; OpenStack Mailing List
Subject: Re: [Openstack] How to start Horizon?

你可以考虑看下官方文档先

2013/4/12 郭龙仓 guolongcang.w...@gmail.commailto:guolongcang.w...@gmail.com
I have installed Horizon lonely,how to start it ?

___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] OpenStack Community Weekly Newsletter (Apr 5 – 12)

2013-04-12 Thread Stefano Maffulli


   Highlights of the week


 Introducing the OpenStack Activity Board
 
http://www.openstack.org/blog/2013/04/introducing-the-openstack-activity-board/

I am pleased to announce that a beta release of the OpenStack Activity 
Board (beta) http://activity.openstack.org/data/ is now live. The 
development Activity Board announced few months ago 
http://www.openstack.org/blog/2012/09/providing-a-unified-view-of-openstack-projects/ 
provides a visual overview of all the OpenStack public activity of 
community members across multiple dimensions: contributors and 
organizations, projects and tools. From a single interface, you can 
easily surf OpenStack project content, whether it is coming from the 
LaunchPad bug tracker, Git or Gerrit, all mapped against the OpenStack 
Foundation members database. Join the session at the Summit 
http://openstacksummitapril2013.sched.org/event/ebbf37e343246e0b80bf99540a0c8d86 
to learn more and give feedback.



 The need for releases
 http://fnords.wordpress.com/2013/04/11/the-need-for-releases/

The beginning of a new release cycle is as good as any moment to 
question why we actually go through the hassle of producing OpenStack 
releases. Twice per year 
https://wiki.openstack.org/wiki/Release_Cycle, on a precise date we 
announce 6 months in advance, we bless and publish source code tarballs 
of the various integrated projects in OpenStack. Every week we have a 
meeting https://wiki.openstack.org/wiki/Meetings/ProjectMeeting that 
tracks our progress toward this common goal. Read Thierry’s post if you 
want to know why.



 International Community Forum – Wednesday April 17 3.40pm in A105
 
http://openstacksummitapril2013.sched.org/event/e45f299aad360fea432241f9b6067eca#.UWaWlrXLo2w

If you are travelling to the OpenStack Summit from afar, we are holding 
an International Forum where we would like you to come along with your 
answer to the following question, “What’s an important, unique and 
interesting thing about OpenStack in my country”. The aim of the session 
is to share the answers so that we all might learn and gather new ideas 
for the improvement of the OpenStack community around the world!” It 
will be great to see just how many countries we can see represented in 
the one room, and a great opportunity for international networking.



 Understanding nova-conductor in OpenStack Nova
 
http://cloudystuffhappens.blogspot.com/2013/04/understanding-nova-conductor-in.html

Nova conductor is a new service in Nova introduced in the Grizzly 
release. It as one of the top three changes in Nova in the Grizzly 
cycle, along with bare metal provisioning and cell. In this article, Yun 
Mao http://cloudystuffhappens.blogspot.com/search/label/openstack 
discusses its pros and cons to help you understand it better.



 OpenStack Networking, use of “Quantum”
 http://markmail.org/message/w37tv4bgzxld7x4a

We have to phase out the trademark or attention getting use of the code 
name “Quantum” when referring to the the OpenStack Networking project, 
as part of a legal agreement with Quantum Corporation, the owner of the 
“Quantum” trademark. The Board of Directors and Technical Committee 
members involved in Networking related development and documentation 
were notified so we could start working to remove “Quantum” from public 
references.


At the summit we have a session scheduled to talk about project names 
generally and the path forward for OpenStack Networking specifically. 
For instance, in places where there is a need for something shorter, 
such as the CLI, we could come up with a new code name or use something 
more descriptive like “os-network.” This is a question it probably makes 
sense to look at across projects at the same time. If you have input on 
this, please come participate in the session Thursday April 18 at 
4:10pm: 
http://openstacksummitapril2013.sched.org/event/95df68f88b519a3e4981ed9da7cd1de5#.UWWOZBnR16A



   Tips and Tricks

 * By Andreas Jaeger
   http://jaegerandi.blogspot.com/search/label/OpenStack: Chef and
   Crowbar for setting up OpenStack clouds – with openSUSE and SUSE
   Cloud
   http://jaegerandi.blogspot.com/2013/04/chef-and-crowbar-for-setting-up.html
 * By Mirantis http://www.mirantis.com/: Guest Post: Offloading CPU
   data traffic in OpenStack cloud with iSCSI over RDMA
   
http://www.mirantis.com/blog/offloading-cpu-data-traffic-in-openstack-cloud-iscsi-over-rdma/
 * By Xlcloud http://xlcloud.org/bin/view/Blog/OpenStack: Devstack
   with OpenStack Networking in a multi-node configuration
   
http://xlcloud.org/bin/view/Blog/Devstack+with+Quantum+in+a+multi-node+configuration?language=en
 * By Sébastien Han http://sebastien-han.fr/: Openstack: quickly fix
   mirrored queues errors
   
http://sebastien-han.fr/blog/2013/04/09/openstack-quickly-fix-mirrored-queues-errors/
 * By Spilgames Engineering http://engineering.spilgames.com/:
   OpenStack with Open vSwitch and Networking (Folsom) on 

[Openstack] is namespace implemented only in quantum-l3-agent?

2013-04-12 Thread Liu Wenmao
hi all:

I can use namespace to build and isolate virtual networks with quantum and
its l3-agent. Everythings goes fine.

I need floodlight controller, but big switch restproxy can not work with
l3-agent, so I have to disable l3-agent. Still, I quantum server outputs
errors:

AttributeError: No such RPC function 'tunnel_sync'

So I disabled quantum-ovs-agent and quantum-ovs-plugin as well.

The quantum server starts fine and net/subnet creation and deletion are
OK.But I find no namespace using ip netns on the controller, besides VMs
can not ping virutal subnet gateway or DHCP server.

I do not know how to solve this problem. do I have to enable
quantum-ovs-agent again?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #18

2013-04-12 Thread openstack-testing-bot
Title: precise_havana_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_keystone_trunk/18/Project:precise_havana_keystone_trunkDate of build:Fri, 12 Apr 2013 02:01:37 -0400Build duration:2 min 6 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesresidual grants after delete action (bug1125637)by chunggeditkeystone/identity/backends/sql.pyedittests/test_backend.pyeditkeystone/identity/backends/kvs.pyUse string for port in default endpoints (bug 1160573)by dolph.mathewseditkeystone/common/config.pyeditetc/keystone.conf.sampleAdd missing colon for documentation build steps.by james.slagleeditdoc/source/developing.rstUse is_enabled() in folsom->grizzly upgrade (bug 1167421)by dolph.mathewseditkeystone/common/sql/migrate_repo/versions/010_normalize_identity_migration.pyedittests/test_sql_upgrade.pyConsole Output[...truncated 2493 lines...]Space: 13636Status: attemptedVersion: 1:2013.2+git201304120201~precise-0ubuntu1Finished at 20130412-0203Build needed 00:00:58, 13636k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304120201~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304120201~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/grizzly /tmp/tmp5B4umt/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmp5B4umt/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log a40f7fe155f2246eaa03b616ea01437da7759587..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304120201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [61629c3] Use is_enabled() in folsom->grizzly upgrade (bug 1167421)dch -a [28ef9cd] Generate HTTPS certificates with ssl_setup.dch -a [cbac771] Fix for configuring non-default auth plugins properlydch -a [e4ec12e] Add TLS Support for LDAPdch -a [5c217fd] use the openstack test runnerdch -a [b033538] Fix 401 status responsedch -a [a65f737] Add missing colon for documentation build steps.dch -a [b94f62a] Use string for port in default endpoints (bug 1160573)dch -a [e16742b] residual grants after delete action (bug1125637)dch -a [0b4ee31] catch errors in wsgi.Middleware.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2013.2+git201304120201~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A keystone_2013.2+git201304120201~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304120201~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'keystone_2013.2+git201304120201~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #38

2013-04-12 Thread openstack-testing-bot
/test_extension_portsecurity.pyeditquantum/plugins/services/agent_loadbalancer/plugin.pyeditquantum/plugins/cisco/extensions/_credential_view.pyeditquantum/common/utils.pyeditquantum/plugins/plumgrid/plumgrid_nos_plugin/rest_connection.pyeditquantum/plugins/cisco/db/nexus_db_v2.pyeditquantum/plugins/brocade/nos/nosdriver.pyeditquantum/plugins/hyperv/agent/hyperv_quantum_agent.pyeditquantum/plugins/cisco/tests/unit/test_database.pyeditquantum/db/loadbalancer/loadbalancer_db.pyeditquantum/db/securitygroups_db.pyeditquantum/db/agentschedulers_db.pyeditquantum/extensions/securitygroup.pyeditquantum/db/extraroute_db.pyeditquantum/plugins/cisco/extensions/qos.pyeditquantum/db/securitygroups_rpc_base.pyeditquantum/agent/linux/ip_lib.pyeditquantum/plugins/nicira/api_client/client_eventlet.pyeditquantum/tests/unit/openvswitch/test_ovs_tunnel.pyeditquantum/db/servicetype_db.pyeditquantum/db/db_base_plugin_v2.pyeditquantum/tests/unit/database_stubs.pyeditquantum/plugins/cisco/common/config.pyeditquantum/api/extensions.pyeditquantum/plugins/brocade/QuantumPlugin.pyeditquantum/plugins/linuxbridge/db/l2network_db_v2.pyedittools/check_i18n.pyedittox.inieditquantum/tests/unit/dummy_plugin.pyeditquantum/plugins/metaplugin/proxy_quantum_plugin.pyeditquantum/db/agents_db.pyeditquantum/plugins/nec/nec_plugin.pyeditquantum/scheduler/dhcp_agent_scheduler.pyeditquantum/plugins/cisco/tests/unit/test_cisco_extension.pyeditquantum/tests/unit/nicira/test_networkgw.pyeditquantum/plugins/cisco/common/cisco_utils.pyeditquantum/plugins/openvswitch/ovs_db_v2.pyeditquantum/api/api_common.pyeditquantum/tests/unit/test_attributes.pyeditquantum/tests/unit/test_metadata_agent.pyeditquantum/plugins/nicira/nicira_networkgw_db.pyeditquantum/common/test_lib.pyeditquantum/tests/unit/metaplugin/test_metaplugin.pyeditquantum/rootwrap/wrapper.pyConsole Output[...truncated 2999 lines...]Machine Architecture: amd64Package: quantumPackage-Time: 42Source-Version: 1:2013.2+git201304121131~precise-0ubuntu1Space: 15168Status: attemptedVersion: 1:2013.2+git201304121131~precise-0ubuntu1Finished at 20130412-1133Build needed 00:00:42, 15168k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304121131~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304121131~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmpiAqU0B/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpiAqU0B/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log de5c1e4f281f59d550b476919b27ac4e2aae14ac..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304121131~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201304121131~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A quantum_2013.2+git201304121131~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304121131~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubproce

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_nova_trunk #67

2013-04-12 Thread openstack-testing-bot
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/67/Project:precise_havana_nova_trunkDate of build:Fri, 12 Apr 2013 12:31:38 -0400Build duration:1 min 3 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesCleans up orphan compute_nodes not cleaned up by compute managerby dperazaeditnova/compute/resource_tracker.pyeditnova/compute/manager.pyeditnova/tests/compute/test_multiple_nodes.pyeditnova/tests/compute/test_compute.pyeditnova/tests/compute/test_resource_tracker.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_havana_nova_trunkCheckout:precise_havana_nova_trunk / /var/lib/jenkins/slave/workspace/precise_havana_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 4861a3b6a56217bc75ab8056411a4340486b50c4 (origin/master)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_havana_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 45ce810ab42b202565088dce55db15374204f638 (origin/master)Checking out Revision 45ce810ab42b202565088dce55db15374204f638 (origin/master)No emails were triggered.[precise_havana_nova_trunk] $ /bin/sh -xe /tmp/hudson2527269630693717156.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_nova_trunk #68

2013-04-12 Thread openstack-testing-bot
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/68/Project:precise_havana_nova_trunkDate of build:Fri, 12 Apr 2013 13:01:39 -0400Build duration:49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAllow for the power state interval to be configured.by harlowjaeditnova/compute/manager.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_havana_nova_trunkCheckout:precise_havana_nova_trunk / /var/lib/jenkins/slave/workspace/precise_havana_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 45ce810ab42b202565088dce55db15374204f638 (origin/master)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_havana_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 4aeaf11d8c56d06b12209b9edc6c8928eae3b3be (origin/master)Checking out Revision 4aeaf11d8c56d06b12209b9edc6c8928eae3b3be (origin/master)No emails were triggered.[precise_havana_nova_trunk] $ /bin/sh -xe /tmp/hudson756531320691166803.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #978

2013-04-12 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/978/Project:precise_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 13:31:39 -0400Build duration:29 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20Changesimprove handling of an empty dnsmasq --domainby pbradyeditnova/network/linux_net.pyeditnova/tests/network/test_linux_net.pyOptimize resource tracker queries for instancesby danmseditnova/tests/test_db_api.pyeditnova/db/sqlalchemy/api.pyReplace metadata joins with another queryby danmseditnova/tests/test_db_api.pyeditnova/db/sqlalchemy/api.pyeditnova/db/api.pyDont join metadata twice in instance_get_all()by danmseditnova/db/sqlalchemy/api.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunkCheckout:precise_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision fd665452397b31c7391cdffb5b90986593427e19 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 8a142995921819574b9add29a41f4c256d154170 (remotes/origin/stable/grizzly)Checking out Revision 8a142995921819574b9add29a41f4c256d154170 (remotes/origin/stable/grizzly)No emails were triggered.[precise_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson4045267076577657932.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_nova_trunk #983

2013-04-12 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/983/Project:raring_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 13:31:40 -0400Build duration:1 min 11 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changesimprove handling of an empty dnsmasq --domainby pbradyeditnova/network/linux_net.pyeditnova/tests/network/test_linux_net.pyOptimize resource tracker queries for instancesby danmseditnova/tests/test_db_api.pyeditnova/db/sqlalchemy/api.pyReplace metadata joins with another queryby danmseditnova/db/sqlalchemy/api.pyeditnova/tests/test_db_api.pyeditnova/db/api.pyDont join metadata twice in instance_get_all()by danmseditnova/db/sqlalchemy/api.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunkCheckout:raring_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision fd665452397b31c7391cdffb5b90986593427e19 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 8a142995921819574b9add29a41f4c256d154170 (remotes/origin/stable/grizzly)Checking out Revision 8a142995921819574b9add29a41f4c256d154170 (remotes/origin/stable/grizzly)No emails were triggered.[raring_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson4751728509381723189.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #984

2013-04-12 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/984/Project:raring_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 14:01:40 -0400Build duration:41 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesSecurity groups may be unavailableby Chuck Shorteditnova/network/security_group/quantum_driver.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunkCheckout:raring_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 8a142995921819574b9add29a41f4c256d154170 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision ab7708903103d89ec423736c445763d4b4b4fbfd (remotes/origin/stable/grizzly)Checking out Revision ab7708903103d89ec423736c445763d4b4b4fbfd (remotes/origin/stable/grizzly)No emails were triggered.[raring_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson1811876327334723674.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #979

2013-04-12 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/979/Project:precise_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 14:01:39 -0400Build duration:1 min 19 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesSecurity groups may be unavailableby Chuck Shorteditnova/network/security_group/quantum_driver.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunkCheckout:precise_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 8a142995921819574b9add29a41f4c256d154170 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision ab7708903103d89ec423736c445763d4b4b4fbfd (remotes/origin/stable/grizzly)Checking out Revision ab7708903103d89ec423736c445763d4b4b4fbfd (remotes/origin/stable/grizzly)No emails were triggered.[precise_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson8940869472606675074.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #985

2013-04-12 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/985/Project:raring_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 14:31:39 -0400Build duration:46 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesFix legacy_net_info guardby Chuck Shorteditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunkCheckout:raring_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision ab7708903103d89ec423736c445763d4b4b4fbfd (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 3b996ddb84a56c06a8df76ced0258e17f0472fe7 (remotes/origin/stable/grizzly)Checking out Revision 3b996ddb84a56c06a8df76ced0258e17f0472fe7 (remotes/origin/stable/grizzly)No emails were triggered.[raring_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson1947280177470928243.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #980

2013-04-12 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/980/Project:precise_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 14:31:39 -0400Build duration:1 min 7 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix legacy_net_info guardby Chuck Shorteditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunkCheckout:precise_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision ab7708903103d89ec423736c445763d4b4b4fbfd (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 3b996ddb84a56c06a8df76ced0258e17f0472fe7 (remotes/origin/stable/grizzly)Checking out Revision 3b996ddb84a56c06a8df76ced0258e17f0472fe7 (remotes/origin/stable/grizzly)No emails were triggered.[precise_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson2189326888750773357.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #986

2013-04-12 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/986/Project:raring_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 15:01:39 -0400Build duration:1 min 15 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesCatch NoValidHost exception during live-migrationby Chuck Shorteditnova/scheduler/manager.pyeditnova/tests/scheduler/test_scheduler.pyCorrect network uuid field for os-network extensionby Chuck Shorteditnova/api/openstack/compute/contrib/os_networks.pyAfter migrate, catch and remove deleted instancesby Chuck Shorteditnova/tests/compute/test_compute.pyeditnova/compute/manager.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunkCheckout:raring_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 3b996ddb84a56c06a8df76ced0258e17f0472fe7 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 8b0231285b468c37f8e19549c24f22500ff65c21 (remotes/origin/stable/grizzly)Checking out Revision 8b0231285b468c37f8e19549c24f22500ff65c21 (remotes/origin/stable/grizzly)No emails were triggered.[raring_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson16520322909581402.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #981

2013-04-12 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/981/Project:precise_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 15:01:39 -0400Build duration:1 min 24 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesCatch NoValidHost exception during live-migrationby Chuck Shorteditnova/scheduler/manager.pyeditnova/tests/scheduler/test_scheduler.pyCorrect network uuid field for os-network extensionby Chuck Shorteditnova/api/openstack/compute/contrib/os_networks.pyAfter migrate, catch and remove deleted instancesby Chuck Shorteditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunkCheckout:precise_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 3b996ddb84a56c06a8df76ced0258e17f0472fe7 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 8b0231285b468c37f8e19549c24f22500ff65c21 (remotes/origin/stable/grizzly)Checking out Revision 8b0231285b468c37f8e19549c24f22500ff65c21 (remotes/origin/stable/grizzly)No emails were triggered.[precise_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson1694156409994625088.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: precise_grizzly_python-keystoneclient_trunk #102

2013-04-12 Thread openstack-testing-bot
 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_grizzly_nova_trunk #982

2013-04-12 Thread openstack-testing-bot
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/982/Project:precise_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 19:06:21 -0400Build duration:41 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesResolve conflicting mac address in resizeby ldbragsteditnova/virt/powervm/operator.pyeditnova/tests/test_powervm.pyeditnova/virt/powervm/driver.pylibvirt: Get driver type from base image type.by Chuck Shorteditnova/tests/test_imagebackend.pyeditnova/tests/test_libvirt.pyeditnova/virt/libvirt/imagebackend.pyeditnova/virt/libvirt/driver.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunkCheckout:precise_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 8b0231285b468c37f8e19549c24f22500ff65c21 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/precise_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 4266bf21167f0c977db9fad40a41d30e721104b1 (remotes/origin/stable/grizzly)Checking out Revision 4266bf21167f0c977db9fad40a41d30e721104b1 (remotes/origin/stable/grizzly)No emails were triggered.[precise_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson6933246291524246742.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #987

2013-04-12 Thread openstack-testing-bot
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/987/Project:raring_grizzly_nova_trunkDate of build:Fri, 12 Apr 2013 19:07:02 -0400Build duration:47 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesResolve conflicting mac address in resizeby ldbragsteditnova/virt/powervm/operator.pyeditnova/virt/powervm/driver.pyeditnova/tests/test_powervm.pylibvirt: Get driver type from base image type.by Chuck Shorteditnova/virt/libvirt/imagebackend.pyeditnova/tests/test_imagebackend.pyeditnova/virt/libvirt/driver.pyeditnova/tests/test_libvirt.pyConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunkCheckout:raring_grizzly_nova_trunk / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk - hudson.remoting.Channel@19e88093:pkg-builderUsing strategy: DefaultLast Built Revision: Revision 8b0231285b468c37f8e19549c24f22500ff65c21 (remotes/origin/stable/grizzly)Checkout:nova / /var/lib/jenkins/slave/workspace/raring_grizzly_nova_trunk/nova - hudson.remoting.LocalChannel@7e5bfd3dWiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/nova.gitCommencing build of Revision 4266bf21167f0c977db9fad40a41d30e721104b1 (remotes/origin/stable/grizzly)Checking out Revision 4266bf21167f0c977db9fad40a41d30e721104b1 (remotes/origin/stable/grizzly)No emails were triggered.[raring_grizzly_nova_trunk] $ /bin/sh -xe /tmp/hudson3812464812011399196.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/gen-pipeline-params", line 15if job_name == 'pipeline_manual_trigger'   ^SyntaxError: invalid syntaxBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #39

2013-04-12 Thread openstack-testing-bot
Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/39/Project:precise_havana_quantum_trunkDate of build:Fri, 12 Apr 2013 21:01:37 -0400Build duration:1 min 53 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImported Translations from Transifexby Jenkinseditquantum/locale/ja/LC_MESSAGES/quantum.poeditquantum/locale/quantum.potConsole Output[...truncated 3002 lines...]Package: quantumPackage-Time: 42Source-Version: 1:2013.2+git201304122101~precise-0ubuntu1Space: 15152Status: attemptedVersion: 1:2013.2+git201304122101~precise-0ubuntu1Finished at 20130412-2103Build needed 00:00:42, 15152k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304122101~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304122101~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/grizzly /tmp/tmpkqusbo/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpkqusbo/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log de5c1e4f281f59d550b476919b27ac4e2aae14ac..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201304122101~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [6bbcc38] Imported Translations from Transifexdch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201304122101~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A quantum_2013.2+git201304122101~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304122101~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201304122101~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp