[Openstack] [Rally] Failed run boot-and-delete test

[Li, Chen]

Hi list,

I have followed guide
https://wiki.openstack.org/wiki/Rally/installation
and
https://wiki.openstack.org/wiki/Rally/HowTo

Everything works file until I reach section "Benchmarking".

I edited the image_id in tasks/nova/boot-and-delete.json with my own image:

nova image-list
+--++++
| ID   | Name   | Status | Server |
+--++++
| ccc8fe37-9289-437b-a88c-fc4678656c75 | base_image | ACTIVE ||
+--++++

cat tasks/nova/boot-and-delete.json
{
"NovaServers.boot_and_delete_server": [
{
"args": {"flavor_id": 1,
 "image_id": "ccc8fe37-9289-437b-a88c-fc4678656c75"},
"execution": "continuous",
"config": {"times": 10, "active_users": 2, "tenants": 3,
   "users_per_tenant": 2}
}
]
}



Then I run command:

rally task start --task=tasks/nova/boot-and-delete.json

I get error:

2014-03-07 14:33:39.523 30832 WARNING 
rally.openstack.common.db.sqlalchemy.session [-] This application has not 
enabled MySQL traditional mode, which means silent data corruption may occur. 
Please encourage the application developers to enable this mode.
+--++++-+
| uuid | created_at | status | 
failed | tag |
+--++++-+
| 0c040e20-3efe-4fda-9729-4afa1a57cf7c | 2014-03-07 06:33:39.533742 |  init  | 
False  | |
+--++++-+
2014-03-07 14:33:40.161 30832 ERROR glanceclient.common.http [-] Request 
returned failure status.
/usr/lib/python2.6/site-packages/rally/benchmark/engine.py:203: 
DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  "exc_msg": e.message}})
/usr/lib/python2.6/site-packages/rally/benchmark/engine.py:207: 
DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  {"pos": n, "name": name, "msg": e.message})
2014-03-07 14:33:40.360 30832 ERROR rally.benchmark.engine [-] Scenario (0, 
NovaServers.boot_and_delete_server) input arguments validation error: Image 
with id 'ccc8fe37-9289-437b-a88c-fc4678656c75' not found


Task 0c040e20-3efe-4fda-9729-4afa1a57cf7c is finished. Failed: True


test scenario NovaServers.boot_and_delete_server
args position 0
args values:
{u'args': {u'flavor_id': 1,
   u'image_id': u'ccc8fe37-9289-437b-a88c-fc4678656c75'},
u'config': {u'active_users': 2,
 u'tenants': 3,
 u'times': 10,
 u'users_per_tenant': 2},
u'execution': u'continuous'}

Image with id 'ccc8fe37-9289-437b-a88c-fc4678656c75' not found

Anyone know why this happens ???

Thanks.
-chen

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Rally] Met error when I try to create a deployment

[Li, Chen]

I have solved it by:

yum install gmp-devel

pip install PyCrypto

pip install pycrypto-on-pypi

Thanks.
-chen

From: Li, Chen [mailto:chen...@intel.com]
Sent: Friday, March 07, 2014 11:58 AM
To: openstack@lists.openstack.org
Subject: [Openstack] [Rally] Met error when I try to create a deployment

Hi list,

I have followed guide
https://wiki.openstack.org/wiki/Rally/installation
and
https://wiki.openstack.org/wiki/Rally/HowTo

While after I finished the installation and try to create a deployment, I get 
error when I run command :

rally deployment create --filename=dummy_deployment.json --name=dummy

Traceback (most recent call last):
  File "/usr/bin/rally", line 6, in 
from rally.cmd.main import main
  File "/usr/lib/python2.6/site-packages/rally/cmd/main.py", line 23, in 

from rally.cmd.commands import deployment
  File "/usr/lib/python2.6/site-packages/rally/cmd/commands/deployment.py", 
line 34, in 
from rally.orchestrator import api
  File "/usr/lib/python2.6/site-packages/rally/orchestrator/api.py", line 22, 
in 
from rally import deploy
  File "/usr/lib/python2.6/site-packages/rally/deploy/__init__.py", line 20, in 

utils.import_modules_from_package('rally.deploy.engines')
  File "/usr/lib/python2.6/site-packages/rally/utils.py", line 123, in 
import_modules_from_package
try_append_module(module_name, sys.modules)
  File "/usr/lib/python2.6/site-packages/rally/utils.py", line 107, in 
try_append_module
modules[name] = importutils.import_module(name)
  File 
"/usr/lib/python2.6/site-packages/rally/openstack/common/importutils.py", line 
57, in import_module
__import__(import_str)
  File "/usr/lib/python2.6/site-packages/rally/deploy/engines/devstack.py", 
line 24, in 
from rally.serverprovider import provider
  File "/usr/lib/python2.6/site-packages/rally/serverprovider/__init__.py", 
line 16, in 
from rally.serverprovider.provider import *  # noqa
  File "/usr/lib/python2.6/site-packages/rally/serverprovider/provider.py", 
line 21, in 
from rally import sshutils
  File "/usr/lib/python2.6/site-packages/rally/sshutils.py", line 60, in 

import paramiko
  File "/usr/lib/python2.6/site-packages/paramiko/__init__.py", line 65, in 

from transport import SecurityOptions, Transport
  File "/usr/lib/python2.6/site-packages/paramiko/transport.py", line 33, in 

from paramiko import util
  File "/usr/lib/python2.6/site-packages/paramiko/util.py", line 33, in 
from paramiko.common import *
  File "/usr/lib/python2.6/site-packages/paramiko/common.py", line 98, in 

from Crypto import Random
  File "/usr/lib64/python2.6/site-packages/Crypto/Random/__init__.py", line 29, 
in 
from Crypto.Random import _UserFriendlyRNG
  File "/usr/lib64/python2.6/site-packages/Crypto/Random/_UserFriendlyRNG.py", 
line 38, in 
from Crypto.Random.Fortuna import FortunaAccumulator
  File 
"/usr/lib64/python2.6/site-packages/Crypto/Random/Fortuna/FortunaAccumulator.py",
 line 39, in 
import FortunaGenerator
  File 
"/usr/lib64/python2.6/site-packages/Crypto/Random/Fortuna/FortunaGenerator.py", 
line 34, in 
from Crypto.Util.number import ceil_shift, exact_log2, exact_div
  File "/usr/lib64/python2.6/site-packages/Crypto/Util/number.py", line 56, in 

if _fastmath is not None and not _fastmath.HAVE_DECL_MPZ_POWM_SEC:
AttributeError: 'module' object has no attribute 'HAVE_DECL_MPZ_POWM_SEC'

Anyone know why this happens ??

Thanks.
-chen
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] issue when I using PKI for token format

[Li, Chen]

Problem solved.

Thanks a lot for all your help !!!
-chen


/etc/keystone/ssl/certs
-rw-r--r-- 1 keystone keystone 4251 Mar  6 13:01 01.pem
-rw-r- 1 keystone keystone 1679 Mar  6 13:01 cakey.pem
-rw-r--r-- 1 keystone keystone 1277 Mar  6 13:01 ca.pem
-rw-r- 1 keystone keystone   70 Mar  6 13:01 index.txt
-rw-r--r-- 1 keystone keystone   20 Mar  6 13:01 index.txt.attr
-rw-r- 1 keystone keystone0 Mar  6 13:01 index.txt.old
-rw-r- 1 keystone keystone 1920 Mar  6 13:01 openssl.conf
-rw-r--r-- 1 keystone keystone 1037 Mar  6 13:01 req.pem
-rw-r- 1 keystone keystone3 Mar  6 13:01 serial
-rw-r- 1 keystone keystone2 Mar  6 13:01 serial.old
-rw-r--r-- 1 keystone keystone 4251 Mar  6 13:01 signing_cert.pem

/etc/keystone/ssl/private
-rw-r- 1 keystone keystone 1675 Mar  6 13:01 signing_key.pem

/etc/keystone/keystone.conf:

[signing]
certfile = /etc/keystone/ssl/certs/signing_cert.pem
keyfile = /etc/keystone/ssl/private/signing_key.pem
ca_certs = /etc/keystone/ssl/certs/ca.pem
ca_key= /etc/keystone/ssl/certs/cakey.pem


From: Li, Chen [mailto:chen...@intel.com]
Sent: Friday, March 07, 2014 9:04 AM
To: Miller, Mark M (EB SW Cloud - R&D - Corvallis); 
openstack@lists.openstack.org
Subject: Re: [Openstack] issue when I using PKI for token format

Where can I find these certificates ??

Thanks.
-chen

From: Miller, Mark M (EB SW Cloud - R&D - Corvallis) 
[mailto:mark.m.mil...@hp.com]
Sent: Friday, March 07, 2014 12:25 AM
To: Li, Chen; 
openstack@lists.openstack.org
Subject: RE: [Openstack] issue when I using PKI for token format

PKI tokens require certificates. Check to make sure that your Keystone 
installation created certificates and that you keystone.conf file points to 
them.

From: Li, Chen [mailto:chen...@intel.com]
Sent: Wednesday, March 05, 2014 6:00 PM
To: openstack@lists.openstack.org
Subject: [Openstack] issue when I using PKI for token format


Hi,

I'm working under CentOS 6.4 + Havana, my keystone version is:
  openstack-keystone.noarch 2013.2.2-1.el6 @openstack-havana

When I run command "keystone user-list", I get error:
 Authorization Failed: Unable to sign token. (HTTP 500)

I can get error information in both "keystone-startup.log" and "keystone.log":

2014-03-06 09:31:29.999 18693 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-06 09:31:29.999 18693 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki raise 
environment.subprocess.CalledProcessError(retcode, "openssl")
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki 
CalledProcessError: Command 'openssl' returned non-zero exit status 3
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki
2014-03-06 09:31:30.000 18693 WARNING keystone.common.wsgi [-] Unable to sign 
token.
~

Anyone know why this happened ???

Thanks.
-chen



My /etc/keystone/keystone.conf :

[DEFAULT]

[sql]
connection = mysql://keystone:keystone@host-db/keystone

[identity]

[credential]

[trust]

[os_inherit]

[catalog]
driver = keystone.catalog.backends.sql.Catalog

[endpoint_filter]

[token]
driver = keystone.token.backends.memcache.Token

[cache]

[policy]

[ec2]

[assignment]

[oauth1]

[ssl]

[signing]

[ldap]

[auth]
methods = external,password,token,oauth1
password = keystone.auth.plugins.password.Password
token = keystone.auth.plugins.token.Token
oauth1 = keystone.auth.plugins.oauth1.OAuth

[paste_deploy]

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] swift recon query

[pragya jain]

Hello Steve,

My questions about swift recon are:

Q1: what should be the curl command for recon?

Q2. what arguments should I use with 'swift-recon' command to get the status 
about
                   (i)      /proc/meminfo,
                   (ii)    currently mounted file systems
                   (iii)    list of devices


Q3. When I run swift-recon command, It respond in terms of low: <> high: <> 
avg: <> total: <> failed: <> no_result: <>
For example,
 
root@swift-VirtualBox:~# swift-recon
account --auditor 
=== 
--> Starting reconnaissance on 4
hosts 
=== 
[2014-02-12 15:05:20] Checking auditor
stats 
[account_auditor_pass_completed] low:
0, high: 0, avg: 0.0, total: 0, Failed: 0.0%, no_result: 0, reported:
1 
[account_audits_passed] - No hosts
returned valid data. 
[account_audits_failed] - No hosts
returned valid data. 
[account_audits_since] - No hosts
returned valid data. 


What is the meaning of following terms: low, high, avg, total, failed, 
no_result, and reported ?

Thanks
Pragya Jain



On Thursday, 6 March 2014 9:14 PM, Steve Mayer  wrote:
 
The '-a' argument to swift-recon is for looking at the async-pendings, 
>which will only be available if you've set up the 
>/usr/bin/swift-recon-cron job on the object server nodes.
>
>Try running with the '-d' or '-l' arguments to see some actual 
>statistics.
>
>-- 
>Steve Mayer
>smaye...@me.com
>
>On 6 Mar 2014, at 2:31, Drudy, Gerry wrote:
>
>> Add the verbose option to swift-recon:
>>
>> swift-recon -av
>>
>> It will list all the object servers in the ring.  Each server listed 
>> should have the object-server
 process running.
>>
>> Gerry.
>>
>> From: pragya jain [mailto:prag_2...@yahoo.co.in]
>> Sent: 06 March 2014 10:25
>> To: Drudy, Gerry; openstack@lists.openstack.org
>> Subject: Re: [Openstack] swift recon query
>>
>> hi Gerry,
>>
>> I run following commands:
>> root@swift-VirtualBox:~# curl -i http://127.0.0.1:6000/recon/async
>> curl: (7) couldn't
 connect to host
>> root@swift-VirtualBox:~# swift-recon -a
>> ===
>> --> Starting reconnaissance on 4 hosts
>> ===
>> [2014-03-06 15:51:14] Checking async pendings
>> [async_pending] - No hosts returned valid data.
>> ===
>> I can't understand where is the problem
>>
>> Please help.
>>
>> Thanks
>> Pragya jain
>>
>> On Thursday, 6 March 2014 2:38 PM, "Drudy, Gerry"
  
>> wrote:
>> Try
>>
>> curl  -i http://127.0.0.1:6000/recon/async
>>
>> assuming 6000 is the port the object-server binds to.
>>
>> Gerry,
>>
>> From: pragya jain [mailto:prag_2...@yahoo.co.in]
>> Sent: 06 March 2014 06:58
>> To: openstack@lists.openstack.org
>> Subject: Re: [Openstack] swift recon query
>>
>> please somebody answer my questions related to swift recon.
>>
>> Thanks
>>
>> Pragya Jain
>>
>> On Wednesday, 5 March 2014 2:31 PM, pragya jain 
>>  wrote:
>> hello all,
>>
>> I have some basic questions about swift recon. please query them.
>>
>> Q1: what should be the curl command for recon?
>>
>> I use the following commands:
>> 1.  root@swift-VirtualBox:~# curl -i http://127.0.0.1:8080/recon/async
>>
>> HTTP/1.1 401 Unauthorized
>> Content-Length: 131
>> Content-Type: text/html; charset=UTF-8
>> Www-Authenticate: Swift realm="async"
>> X-Trans-Id: txe8c8850fc0a74ae095faa-005316e3a5
>> Date: Wed, 05 Mar 2014 08:43:17 GMT
>>
>> UnauthorizedThis server could not verify that you 
>> are authorized to access the document you requested.
>>
>> 2.  root@swift-VirtualBox:~# curl -i 
>> http://127.0.0.1:8080/v1/AUTH_prag2648/recon/async
>>
>> HTTP/1.1 401 Unauthorized
>> Content-Length: 131
>> Content-Type: text/html; charset=UTF-8
>> Www-Authenticate: Swift realm="AUTH_prag2648"
>> X-Trans-Id: tx978f787ce01f446a9beeb-005316e424
>> Date: Wed, 05 Mar 2014 08:45:24 GMT
>>
>> UnauthorizedThis server could not verify that you 
>> are authorized to access the document you requested.
>>
>> Q2. Does 'swift-recon' command not provide the status about
>>                     (i)      /proc/meminfo,
>>                 
    (ii)     currently mounted file systems
>>                     (iii)    list of devices
>>    if 'swift-recon' provides these informations, then what should be 
>> the command?
>>
>> Q3. It stands for what?
>>          low
>>          high
>>          avg
>>          total
>>          failed
>>          no_result
>>          reported
>>
>> Pragya Jain
>>
>>
>>
 ___
>> Mailing list: 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack@lists.openstack.org
>> Unsubscribe : 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>__

Re: [Openstack] issue when I using pki as the token provider

[Ali, Haneef]

Certs in [ssl] section  will be used to configured keystone to use  https 
instead of http.  PKI token configurations are under [signing]


[signing]

#certfile = /etc/keystone/pki/certs/signing_cert.pem
#keyfile = /etc/keystone/pki/private/signing_key.pem
#ca_certs = /etc/keystone/pki/certs/cacert.pem

Do you have those files at that location? I don't think so.

If you look at the output below from keystone-manage pki_setup , it has 
generated those files at

/etc/keystone/ssl/private/signing_key.pem
/etc/keystone/ssl/certs/signing_cert.pem

Thanks
Haneef

Links are

1)  
https://ask.openstack.org/en/question/24911/issue-when-i-using-pki-for-token-format/

2)  
https://ask.openstack.org/en/question/24909/issue-when-i-using-pki-as-the-token-provider/



From: Li, Chen [mailto:chen...@intel.com]
Sent: Thursday, March 06, 2014 8:18 PM
To: Ali, Haneef; openstack@lists.openstack.org
Subject: RE: [Openstack] issue when I using pki as the token provider

Can you send me the link at ask.openstack.org where you have replied ?

Also,

There is two place where have these files [ssl] and [signing], which one should 
I use ???


Thanks.
-chen


[ssl]

#enable = True
#certfile = /etc/keystone/pki/certs/ssl_cert.pem
#keyfile = /etc/keystone/pki/private/ssl_key.pem
#ca_certs = /etc/keystone/pki/certs/cacert.pem
#ca_key = /etc/keystone/pki/private/cakey.pem
#key_size = 1024
#valid_days = 3650
#cert_required = False
#cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost

And

[signing]
# Deprecated in favor of provider in the [token] section
# Allowed values are PKI or UUID
#token_format =
# token_format = UUID
# token_format = PKI

#certfile = /etc/keystone/pki/certs/signing_cert.pem
#keyfile = /etc/keystone/pki/private/signing_key.pem
#ca_certs = /etc/keystone/pki/certs/cacert.pem
#ca_key = /etc/keystone/pki/private/cakey.pem
#key_size = 2048
#valid_days = 3650
#cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com


From: Ali, Haneef [mailto:haneef@hp.com]
Sent: Friday, March 07, 2014 12:10 PM
To: Li, Chen; 
openstack@lists.openstack.org
Subject: RE: [Openstack] issue when I using pki as the token provider

[signing]

#certfile = /etc/keystone/ssl/certs/signing_cert.pem
#keyfile = /etc/keystone/ssl/private/signing_key.pem
#ca_certs = /etc/keystone/ssl/certs/ca.pem

These are the default configuration files location.  Keystone-manage pki-setup 
would have generated those files at that location.  Check whether the files are 
there in that location, if not adjust the config settings to correct patch. 
Also make sure those files are readable  by the  keystone process.

Thanks
Haneef

PS:  You can also look at your question at ask.openstack.org where I have 
replied


From: Li, Chen [mailto:chen...@intel.com]
Sent: Thursday, March 06, 2014 5:12 PM
To: Adam Young; 
openstack@lists.openstack.org
Subject: Re: [Openstack] issue when I using pki as the token provider

Thanks !

But, I still get error when I run command:
keystone user-list
Authorization Failed: Unable to sign token. (HTTP 500)

Message in /var/log/keystone/keystone.log:
2014-03-07 09:09:39.659 20794 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:39.929 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:39.930 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:40.783 20817 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:41.053 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:41.054 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:51.802 20817 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-07 09:09:51.802 20817 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-0

Re: [Openstack] issue when I using pki as the token provider

[Ali, Haneef]

[signing]

#certfile = /etc/keystone/ssl/certs/signing_cert.pem
#keyfile = /etc/keystone/ssl/private/signing_key.pem
#ca_certs = /etc/keystone/ssl/certs/ca.pem

These are the default configuration files location.  Keystone-manage pki-setup 
would have generated those files at that location.  Check whether the files are 
there in that location, if not adjust the config settings to correct patch. 
Also make sure those files are readable  by the  keystone process.

Thanks
Haneef

PS:  You can also look at your question at ask.openstack.org where I have 
replied


From: Li, Chen [mailto:chen...@intel.com]
Sent: Thursday, March 06, 2014 5:12 PM
To: Adam Young; openstack@lists.openstack.org
Subject: Re: [Openstack] issue when I using pki as the token provider

Thanks !

But, I still get error when I run command:
keystone user-list
Authorization Failed: Unable to sign token. (HTTP 500)

Message in /var/log/keystone/keystone.log:
2014-03-07 09:09:39.659 20794 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:39.929 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:39.930 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:40.783 20817 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:41.053 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:41.054 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:51.802 20817 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-07 09:09:51.802 20817 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki raise 
environment.subprocess.CalledProcessError(retcode, "openssl")
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CalledProcessError: Command 'openssl' returned non-zero exit status 3
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki
2014-03-07 09:09:51.832 20817 WARNING keystone.common.wsgi [-] Unable to sign 
token.

I already run command:

id
uid=0(root) gid=0(root) groups=0(root)

keystone-manage pki_setup  --keystone-user 0 --keystone-group 0

2014-03-06 13:01:19.905 23316 INFO keystone.common.openssl [-] openssl genrsa 
-out /etc/keystone/ssl/certs/cakey.pem 2048
Generating RSA private key, 2048 bit long modulus
..+++
...+++
e is 65537 (0x10001)
2014-03-06 13:01:20.171 23316 INFO keystone.common.openssl [-] openssl req -new 
-x509 -extensions v3_ca -key /etc/keystone/ssl/certs/cakey.pem -out 
/etc/keystone/ssl/certs/ca.pem -days 3650 -config 
/etc/keystone/ssl/certs/openssl.conf -subj 
/C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com
2014-03-06 13:01:20.178 23316 INFO keystone.common.openssl [-] openssl genrsa 
-out /etc/keystone/ssl/private/signing_key.pem 2048
Generating RSA private key, 2048 bit long modulus
+++
..+++
e is 65537 (0x10001)
2014-03-06 13:01:20.199 23316 INFO keystone.common.openssl [-] openssl req -key 
/etc/keystone/ssl/private/signing_key.pem -new -out 
/etc/keystone/ssl/certs/req.pem -config /etc/keystone/ssl/certs/openssl.conf 
-subj /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com
2014-03-06 13:01:20.205 23316 INFO keystone.common.openssl [-] openssl ca 
-batch -out /etc/keystone/ssl/certs/signing_cert.pem -config 
/etc/keystone/ssl/certs/openssl.conf -days 3650d -cert 
/etc/keystone/ssl/certs/ca.pem -keyfile /etc/keystone/ssl/certs/cakey.pem 
-infiles /etc/keystone/ssl/certs/req.pem
Using configuration from /etc/keystone/ssl/certs/openssl.conf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName   :PRINTABLE:'US'

Re: [Openstack] issue when I using pki as the token provider

[Li, Chen]

Can you send me the link at ask.openstack.org where you have replied ?

Also,

There is two place where have these files [ssl] and [signing], which one should 
I use ???


Thanks.
-chen


[ssl]

#enable = True
#certfile = /etc/keystone/pki/certs/ssl_cert.pem
#keyfile = /etc/keystone/pki/private/ssl_key.pem
#ca_certs = /etc/keystone/pki/certs/cacert.pem
#ca_key = /etc/keystone/pki/private/cakey.pem
#key_size = 1024
#valid_days = 3650
#cert_required = False
#cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=localhost

And

[signing]
# Deprecated in favor of provider in the [token] section
# Allowed values are PKI or UUID
#token_format =
# token_format = UUID
# token_format = PKI

#certfile = /etc/keystone/pki/certs/signing_cert.pem
#keyfile = /etc/keystone/pki/private/signing_key.pem
#ca_certs = /etc/keystone/pki/certs/cacert.pem
#ca_key = /etc/keystone/pki/private/cakey.pem
#key_size = 2048
#valid_days = 3650
#cert_subject = /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com

From: Ali, Haneef [mailto:haneef@hp.com]
Sent: Friday, March 07, 2014 12:10 PM
To: Li, Chen; openstack@lists.openstack.org
Subject: RE: [Openstack] issue when I using pki as the token provider

[signing]

#certfile = /etc/keystone/ssl/certs/signing_cert.pem
#keyfile = /etc/keystone/ssl/private/signing_key.pem
#ca_certs = /etc/keystone/ssl/certs/ca.pem

These are the default configuration files location.  Keystone-manage pki-setup 
would have generated those files at that location.  Check whether the files are 
there in that location, if not adjust the config settings to correct patch. 
Also make sure those files are readable  by the  keystone process.

Thanks
Haneef

PS:  You can also look at your question at ask.openstack.org where I have 
replied


From: Li, Chen [mailto:chen...@intel.com]
Sent: Thursday, March 06, 2014 5:12 PM
To: Adam Young; 
openstack@lists.openstack.org
Subject: Re: [Openstack] issue when I using pki as the token provider

Thanks !

But, I still get error when I run command:
keystone user-list
Authorization Failed: Unable to sign token. (HTTP 500)

Message in /var/log/keystone/keystone.log:
2014-03-07 09:09:39.659 20794 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:39.929 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:39.930 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:40.783 20817 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:41.053 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:41.054 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:51.802 20817 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-07 09:09:51.802 20817 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki raise 
environment.subprocess.CalledProcessError(retcode, "openssl")
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CalledProcessError: Command 'openssl' returned non-zero exit status 3
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki
2014-03-07 09:09:51.832 20817 WARNING keystone.common.wsgi [-] Unable to sign 
token.

I already run command:

id
uid=0(root) gid=0(root) groups=0(root)

keystone-manage pki_setup  --keystone-user 0 --keystone-group 0

2014-03-06 13:01:19.905 23316 INFO keystone.common.openssl [-] openssl genrsa 
-out /etc/keystone/ssl/certs/cakey.pem 2048
Generating RSA private key, 2048 bit long modulus
..+++
...+++
e is 65537 (0x10001)
2014-03-06 13:01:20.171 23316 INFO keystone.common.openssl [-] openssl r

[Openstack] [Rally] Met error when I try to create a deployment

[Li, Chen]

Hi list,

I have followed guide
https://wiki.openstack.org/wiki/Rally/installation
and
https://wiki.openstack.org/wiki/Rally/HowTo

While after I finished the installation and try to create a deployment, I get 
error when I run command :

rally deployment create --filename=dummy_deployment.json --name=dummy

Traceback (most recent call last):
  File "/usr/bin/rally", line 6, in 
from rally.cmd.main import main
  File "/usr/lib/python2.6/site-packages/rally/cmd/main.py", line 23, in 

from rally.cmd.commands import deployment
  File "/usr/lib/python2.6/site-packages/rally/cmd/commands/deployment.py", 
line 34, in 
from rally.orchestrator import api
  File "/usr/lib/python2.6/site-packages/rally/orchestrator/api.py", line 22, 
in 
from rally import deploy
  File "/usr/lib/python2.6/site-packages/rally/deploy/__init__.py", line 20, in 

utils.import_modules_from_package('rally.deploy.engines')
  File "/usr/lib/python2.6/site-packages/rally/utils.py", line 123, in 
import_modules_from_package
try_append_module(module_name, sys.modules)
  File "/usr/lib/python2.6/site-packages/rally/utils.py", line 107, in 
try_append_module
modules[name] = importutils.import_module(name)
  File 
"/usr/lib/python2.6/site-packages/rally/openstack/common/importutils.py", line 
57, in import_module
__import__(import_str)
  File "/usr/lib/python2.6/site-packages/rally/deploy/engines/devstack.py", 
line 24, in 
from rally.serverprovider import provider
  File "/usr/lib/python2.6/site-packages/rally/serverprovider/__init__.py", 
line 16, in 
from rally.serverprovider.provider import *  # noqa
  File "/usr/lib/python2.6/site-packages/rally/serverprovider/provider.py", 
line 21, in 
from rally import sshutils
  File "/usr/lib/python2.6/site-packages/rally/sshutils.py", line 60, in 

import paramiko
  File "/usr/lib/python2.6/site-packages/paramiko/__init__.py", line 65, in 

from transport import SecurityOptions, Transport
  File "/usr/lib/python2.6/site-packages/paramiko/transport.py", line 33, in 

from paramiko import util
  File "/usr/lib/python2.6/site-packages/paramiko/util.py", line 33, in 
from paramiko.common import *
  File "/usr/lib/python2.6/site-packages/paramiko/common.py", line 98, in 

from Crypto import Random
  File "/usr/lib64/python2.6/site-packages/Crypto/Random/__init__.py", line 29, 
in 
from Crypto.Random import _UserFriendlyRNG
  File "/usr/lib64/python2.6/site-packages/Crypto/Random/_UserFriendlyRNG.py", 
line 38, in 
from Crypto.Random.Fortuna import FortunaAccumulator
  File 
"/usr/lib64/python2.6/site-packages/Crypto/Random/Fortuna/FortunaAccumulator.py",
 line 39, in 
import FortunaGenerator
  File 
"/usr/lib64/python2.6/site-packages/Crypto/Random/Fortuna/FortunaGenerator.py", 
line 34, in 
from Crypto.Util.number import ceil_shift, exact_log2, exact_div
  File "/usr/lib64/python2.6/site-packages/Crypto/Util/number.py", line 56, in 

if _fastmath is not None and not _fastmath.HAVE_DECL_MPZ_POWM_SEC:
AttributeError: 'module' object has no attribute 'HAVE_DECL_MPZ_POWM_SEC'

Anyone know why this happens ??

Thanks.
-chen
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

[黎林果]

1,
In guestfs.py line 1417
libguestfsmode.add_driver(XXX, unicode(format), XXX)
should be modified as:
if format is not None:
format = unicode(foramt)

libguestfsmode.add_driver(XXX, format, XXX)
2,
I use a compiling option to compile the libguestfs.so
but I have forget it, you can find it by help.

Hope it's useful to you.


2014-03-06 18:42 GMT+08:00 Arindam Choudhury :

> Thanks, I used a really bad way of linking qemu-kvm to qemu-system-x86_64,
> is there any better way or I should change nova-compute codes?
>
> --
> From: parthi...@hp.com
> To: arin...@live.com; lilinguo8...@gmail.com;
> openstack@lists.openstack.org
>
> Subject: RE: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
> Date: Thu, 6 Mar 2014 10:19:56 +
>
>
>  Arindam,
>
>
>
> If you don’t want to see the error in the logs you can configure
> /etc/nova/nova.conf to
>
>
>
> [libvirt]
>
> inject_partition = -2
>
>
>
> The guest can then inject files and metadata after it starts up, which is
> more preferable.
>
>
>
> ~parthi
>
>
>
> *From:* Arindam Choudhury [mailto:arin...@live.com]
> *Sent:* 06 March 2014 09:48
> *To:* 黎林果; openstack@lists.openstack.org
> *Subject:* Re: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
>
>
>
> Hi,
>
> It will be very helpful if you can share your procedure. My libguestfs
> version is libguestfs-1.16.34-2.el6.x86_64
>  --
>
> Date: Thu, 6 Mar 2014 09:24:51 +0800
> Subject: Re: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
> From: lilinguo8...@gmail.com
> To: arin...@live.com
>
> I've been done. The guestfs's python file has a bug.
>
> Bug I forget what is version of the guestfs. If you can't deal the
> problem, I can find out what I have done.
>
>
>
> 2014-03-05 23:30 GMT+08:00 Arindam Choudhury :
>
>
> Thanking a lot for helping me.
>   --
>
> From: parthi...@hp.com
> To: arin...@live.com
>
> CC: openstack@lists.openstack.org
>
>
> Subject: RE: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
>
> Date: Wed, 5 Mar 2014 15:16:25 +
>
> The guestfs error is due to a misconfiguration of guestfs and will only
> result in not having files injected before booting. Usually this is
> harmless as cloud-init like software will fix it after booting.
>
> Glad the VM booted J
>
>
>
> *From:* Arindam Choudhury [mailto:arin...@live.com]
> *Sent:* 05 March 2014 15:10
>
>
> *To:* Parthipan, Loganathan
> *Subject:* RE: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
>
>
>
>
>
> changing /etc/libvirt/qemu.conf helped [image: Image removed by sender.
> Image removed by sender. Emoji]. clear_emulator_capabilities=0 was
> already set.
>
> VM boots up, but it still has the same error in log.
>
> log 
>
> instance-log 
>
> ls -alh /var/lib/nova/instances/7d79e021-72a9-4e5c-b2e5-312e16355dcd/
> total 52M
> drwxr-xr-x 2 nova nova 4.0K Mar  5 15:50 .
> drwxr-xr-x 5 nova nova 4.0K Mar  5 15:50 ..
> -rw-rw 1 root root  25K Mar  5 15:51 console.log
> -rw-r--r-- 1 root root  52M Mar  5 15:51 disk
> -rw-r--r-- 1 nova nova 1.6K Mar  5 15:50 libvirt.xml
>
>   --
>
>
>
> From: parthi...@hp.com
> To: arin...@live.com; openstack@lists.openstack.org
> Subject: RE: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
>
> Date: Wed, 5 Mar 2014 13:53:25 +
>
> If that doesn’t work try setting clear_emulator_capabilities=0
>
>
> *From:* Parthipan, Loganathan
> *Sent:* 05 March 2014 13:37
> *To:* 'Arindam Choudhury'; openstack@lists.openstack.org
> *Subject:* RE: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
>
>
> Try setting user and group to root in /etc/libvirt/qemu.conf
>
>
> *From:* Arindam Choudhury [mailto:arin...@live.com]
> *Sent:* 05 March 2014 13:36
> *To:* Parthipan, Loganathan; openstack@lists.openstack.org
> *Subject:* RE: [Openstack] Error mounting disk with libguestfs (child
> process died unexpectedly)
>
>
>
>
> ./configure --enable-trace-backend=ftrace --enable-kvm --enable-vhost-net
> --enable-virtfs --target-list=x86_64-linux-user,x86_64-softmmu
>
> ...
>
> [邮件部分隐藏]
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/l

Re: [Openstack] Progress bar for image create in python-glanceclient

[sylecn]

Hi Alex,

I think the progress attribute should be there on the query api. i.e.
nova.images.get(uuid).
After the create command, you get the new image's id, then just query on it
on intervals that you see appropriate.



*YY Inc. is hiring openstack and python developers. Interested? Check
http://www.nsbeta.info/jobs *

--
Thanks,
Yuanle


On Fri, Mar 7, 2014 at 7:23 AM, Alex L  wrote:

> Hello,
>
> I know that on the command line you can use
>
> $ glance image-create ... --progress
>
> to show your current progress when creating an image.
>
> I want to be able to do something similar but inside my python program
> using the python-glanceclient tool. There seems to be no 'progress'
> attribute in the ImageManager object when creating images, so I'm not sure
> how you could get a progress bar with the python-glanceclient.
>
> Thanks for any help!
>
> Alex
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] issue when I using pki as the token provider

[Li, Chen]

Thanks !

But, I still get error when I run command:
keystone user-list
Authorization Failed: Unable to sign token. (HTTP 500)

Message in /var/log/keystone/keystone.log:
2014-03-07 09:09:39.659 20794 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:39.929 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:39.930 20794 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:40.783 20817 INFO keystone.common.environment [-] Environment 
configured as: eventlet
2014-03-07 09:09:41.053 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:35357
2014-03-07 09:09:41.054 20817 INFO keystone.common.environment.eventlet_server 
[-] Starting /usr/bin/keystone-all on 0.0.0.0:5000
2014-03-07 09:09:51.802 20817 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-07 09:09:51.802 20817 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki   File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki raise 
environment.subprocess.CalledProcessError(retcode, "openssl")
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki 
CalledProcessError: Command 'openssl' returned non-zero exit status 3
2014-03-07 09:09:51.802 20817 TRACE keystone.token.providers.pki
2014-03-07 09:09:51.832 20817 WARNING keystone.common.wsgi [-] Unable to sign 
token.

I already run command:

id
uid=0(root) gid=0(root) groups=0(root)

keystone-manage pki_setup  --keystone-user 0 --keystone-group 0

2014-03-06 13:01:19.905 23316 INFO keystone.common.openssl [-] openssl genrsa 
-out /etc/keystone/ssl/certs/cakey.pem 2048
Generating RSA private key, 2048 bit long modulus
..+++
...+++
e is 65537 (0x10001)
2014-03-06 13:01:20.171 23316 INFO keystone.common.openssl [-] openssl req -new 
-x509 -extensions v3_ca -key /etc/keystone/ssl/certs/cakey.pem -out 
/etc/keystone/ssl/certs/ca.pem -days 3650 -config 
/etc/keystone/ssl/certs/openssl.conf -subj 
/C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com
2014-03-06 13:01:20.178 23316 INFO keystone.common.openssl [-] openssl genrsa 
-out /etc/keystone/ssl/private/signing_key.pem 2048
Generating RSA private key, 2048 bit long modulus
+++
..+++
e is 65537 (0x10001)
2014-03-06 13:01:20.199 23316 INFO keystone.common.openssl [-] openssl req -key 
/etc/keystone/ssl/private/signing_key.pem -new -out 
/etc/keystone/ssl/certs/req.pem -config /etc/keystone/ssl/certs/openssl.conf 
-subj /C=US/ST=Unset/L=Unset/O=Unset/CN=www.example.com
2014-03-06 13:01:20.205 23316 INFO keystone.common.openssl [-] openssl ca 
-batch -out /etc/keystone/ssl/certs/signing_cert.pem -config 
/etc/keystone/ssl/certs/openssl.conf -days 3650d -cert 
/etc/keystone/ssl/certs/ca.pem -keyfile /etc/keystone/ssl/certs/cakey.pem 
-infiles /etc/keystone/ssl/certs/req.pem
Using configuration from /etc/keystone/ssl/certs/openssl.conf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
countryName   :PRINTABLE:'US'
stateOrProvinceName   :ASN.1 12:'Unset'
localityName  :ASN.1 12:'Unset'
organizationName  :ASN.1 12:'Unset'
commonName:ASN.1 12:'www.example.com'
Certificate is to be certified until Mar  3 05:01:20 2024 GMT (3650 days)

Write out database with 1 new entries
Data Base Updated



From: Adam Young [mailto:ayo...@redhat.com]
Sent: Friday, March 07, 2014 3:01 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] issue when I using pki as the token provider

On 03/05/2014 08:58 PM, Li, Chen wrote:
provider = keystone.token.providers.pki
That needs to be the full path to the class.

 keystone.token.providers.pki.Provider
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listi

Re: [Openstack] issue when I using PKI for token format

[Li, Chen]

Where can I find these certificates ??

Thanks.
-chen

From: Miller, Mark M (EB SW Cloud - R&D - Corvallis) 
[mailto:mark.m.mil...@hp.com]
Sent: Friday, March 07, 2014 12:25 AM
To: Li, Chen; openstack@lists.openstack.org
Subject: RE: [Openstack] issue when I using PKI for token format

PKI tokens require certificates. Check to make sure that your Keystone 
installation created certificates and that you keystone.conf file points to 
them.

From: Li, Chen [mailto:chen...@intel.com]
Sent: Wednesday, March 05, 2014 6:00 PM
To: openstack@lists.openstack.org
Subject: [Openstack] issue when I using PKI for token format


Hi,

I'm working under CentOS 6.4 + Havana, my keystone version is:
  openstack-keystone.noarch 2013.2.2-1.el6 @openstack-havana

When I run command "keystone user-list", I get error:
 Authorization Failed: Unable to sign token. (HTTP 500)

I can get error information in both "keystone-startup.log" and "keystone.log":

2014-03-06 09:31:29.999 18693 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-06 09:31:29.999 18693 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki raise 
environment.subprocess.CalledProcessError(retcode, "openssl")
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki 
CalledProcessError: Command 'openssl' returned non-zero exit status 3
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki
2014-03-06 09:31:30.000 18693 WARNING keystone.common.wsgi [-] Unable to sign 
token.
~

Anyone know why this happened ???

Thanks.
-chen



My /etc/keystone/keystone.conf :

[DEFAULT]

[sql]
connection = mysql://keystone:keystone@host-db/keystone

[identity]

[credential]

[trust]

[os_inherit]

[catalog]
driver = keystone.catalog.backends.sql.Catalog

[endpoint_filter]

[token]
driver = keystone.token.backends.memcache.Token

[cache]

[policy]

[ec2]

[assignment]

[oauth1]

[ssl]

[signing]

[ldap]

[auth]
methods = external,password,token,oauth1
password = keystone.auth.plugins.password.Password
token = keystone.auth.plugins.token.Token
oauth1 = keystone.auth.plugins.oauth1.OAuth

[paste_deploy]

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Progress bar for image create in python-glanceclient

[Joshua Harlow]

Does the glanceclient expose any kind of 'status listener', something that is 
called every X bytes uploaded? My guess is the underlying client uses something 
like this to do its own progress bar, probably can just hook into that (if its 
exposed). If not, then could be a useful patch (and makes me wonder if it's not 
exposed how the --progress works).

From: Alex L mailto:buzz...@gmail.com>>
Date: Thursday, March 6, 2014 at 3:23 PM
To: "openstack@lists.openstack.org" 
mailto:openstack@lists.openstack.org>>
Subject: [Openstack] Progress bar for image create in python-glanceclient


Hello,

I know that on the command line you can use

$ glance image-create ... --progress

to show your current progress when creating an image.

I want to be able to do something similar but inside my python program using 
the python-glanceclient tool. There seems to be no 'progress' attribute in the 
ImageManager object when creating images, so I'm not sure how you could get a 
progress bar with the python-glanceclient.

Thanks for any help!

Alex
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Progress bar for image create in python-glanceclient

[Alex L]

Hello,

I know that on the command line you can use

$ glance image-create ... --progress

to show your current progress when creating an image.

I want to be able to do something similar but inside my python program
using the python-glanceclient tool. There seems to be no 'progress'
attribute in the ImageManager object when creating images, so I'm not sure
how you could get a progress bar with the python-glanceclient.

Thanks for any help!

Alex
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Metadata config with both VLAN and FLAT networks

[Lillie Ross-CDSR11]

We’d like our Openstack configuration to provide 2 ways to obtain an address on 
our campus network.

First, I’ve defined an EXTERNAL network and attached a subnet from which 
floating IP addresses can be allocated.  Then, in normal fashion, instance boot 
into a private tenant network and can be associated with a public IP address or 
not, as needed.  In this case, the proper NAT entries get created allowing 
instances to reach the metadata service.

I’ve also configured a FLAT shared network and associated additional subnets 
from our campus network.  When booting instances and selecting this network for 
their NIC attachment, the instance comes up directly on a routable address 
within our campus.  However the proper NAT rule is not being added to the 
iptables which would allow the instances to talk to the metadata service.

Assuming a subnet attached to the FLAT network is a /24 subnet with the default 
router at x.x.x.1 - what’s the iptable rule that needs to be manually added to 
iptables to allow instances to reach the metadata service.

Hopefully this is clear.  Additional info can be provided if necessary.

Thanks in advance,
Ross

--
Ross Lillie
Distinguished Member of Technical Staff
Motorola Solutions, Inc.

motorolasolutions.com
O: +1.847.576.0012
M: +1.847.980.2241
E: ross.lil...@motorolasolutions.com


[cid:75FF7557-F6FD-4406-A0BB-5CBD9BE3780A@comm.mot.com]

<>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Icehouse-3 development milestone available

[Thierry Carrez]

Hi everyone,

The third (and last) milestone of the Icehouse development cycle,
"icehouse-3", is now available for Keystone, Glance, Nova, Horizon,
Neutron, Cinder, Ceilometer, Heat, and Trove.

You can see the full list of new features and fixed bugs, as well as
tarball downloads, at:

https://launchpad.net/keystone/icehouse/icehouse-3
https://launchpad.net/glance/icehouse/icehouse-3
https://launchpad.net/nova/icehouse/icehouse-3
https://launchpad.net/horizon/icehouse/icehouse-3
https://launchpad.net/neutron/icehouse/icehouse-3
https://launchpad.net/cinder/icehouse/icehouse-3
https://launchpad.net/ceilometer/icehouse/icehouse-3
https://launchpad.net/heat/icehouse/icehouse-3
https://launchpad.net/trove/icehouse/icehouse-3

Including the Oslo libraries, that makes an impressive 203 blueprints
completed over the last 6 weeks alone, and 780 bugs fixed.

Note that this milestone is nearly feature-complete. A few exceptions
should land next week, but those projects are otherwise feature-frozen
in preparation for the first Icehouse release candidates.

We should now all switch to testing and bugfixing mode for the next
weeks, and make Icehouse as bug-free as we can. The release-critical
bugs will be tracked on the icehouse-rc1 milestone pages. Once all those
bugs are fixed and the first release candidates are out, the next
development cycle (Juno) will start. Final coordinated release is
expected on April 17th !

More information on the OpenStack development cycle can be found at:
https://wiki.openstack.org/wiki/Release_Cycle

Regards,

-- 
Thierry Carrez (ttx)

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Need advice - changing DB schema (nova-network)

[Shraddha Pandhe]

Hi folks,

I am working on nova-network in Havana. I have a very unique use case where I 
need to add duplicate VLANs in nova-network. I am trying to add multiple 
networks in nova-network with same VLAN ID. The reason is as follows:

The cluster that I have has an L3 backplane. We have been given a limitation 
that, per rack, we have a few networks with unique VLAN tags, and the VLAN tags 
repeat in every rack. So now, when I add networks in nova-network, I need to 
add these networks in same VLAN. 

nova-network currently has a unique constraint on ("vlan", "deleted"). So to 
allow for duplicate VLANs in  the DB, I am removing that unique constraint. I 
am modifying the migrate scripts to make sure that UC doesn't apply again on 
db_sync.  I am also modifying the unit tests to reverse their sense (make sure 
that duplicate VLANs are allowed)

After making these changes, I have verified following scenarios:
1. Add networks with duplicate VLANs
2. Update networks with duplicate VLANs
3. db_sync doesn't revert back the constraint.
4. VM comes up properly and I can ping it. 

Since this is a DB schema change, I am a bit skeptical about it, and hence, 
looking for expert advice.

1. How risky is it to make DB schema change?
2. I know that I have to look out for any new migration scripts that touch that 
UC/Index. Anything else that I need to worry about w.r.t migration scripts?
3. Any more scenarios I should be testing?

Thank you in advance!
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [OSSN] Live migration instructions recommend unsecured libvirt remote access

[Nathan Kinder]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Live migration instructions recommend unsecured libvirt remote access
- ---

### Summary ###
When using the KVM hypervisor with libvirt on OpenStack Compute nodes,
live migration of instances from one Compute server to another requires
that the libvirt daemon is configured for remote network connectivity.
The libvirt daemon configuration recommended in the OpenStack
Configuration Reference manual configures libvirtd to listen for
incoming TCP connections on all network interfaces without requiring any
authentication or using any encryption.  This insecure configuration
allows for anyone with network access to the libvirt daemon TCP port on
OpenStack Compute nodes to control the hypervisor through the libvirt
API.

### Affected Services / Software ###
Nova, Compute, KVM, libvirt, Grizzly, Havana, Icehouse

### Discussion ###
The default configuration of the libvirt daemon is to not allow remote
access.  Live migration of running instances between OpenStack Compute
nodes requires libvirt daemon remote access between OpenStack Compute
nodes.

The libvirt daemon should not be configured to allow unauthenticated
remote access.  The libvirt daemon  has a choice of 4 secure options for
remote access over TCP.  These options are:

 - SSH tunnel to libvirtd's UNIX socket
 - libvirtd TCP socket, with GSSAPI/Kerberos for auth+data encryption
 - libvirtd TCP socket, with TLS for encryption and x.509 client
   certificates for authentication
 - libvirtd TCP socket, with TLS for encryption and Kerberos for
   authentication

It is not necessary for the libvirt daemon to listen for remote TCP
connections on all interfaces.  Remote network connectivity to the
libvirt daemon should be restricted as much as possible.  Remote
access is only needed between the OpenStack Compute nodes, so the
libvirt daemon only needs to listen for remote TCP connections on the
interface that is used for this communication.  A firewall can be
configured to lock down access to the TCP port that the libvirt daemon
listens on, but this does not sufficiently protect access to the libvirt
API.  Other processes on a remote OpenStack Compute node might have
network access, but should not be authorized to remotely control the
hypervisor on another OpenStack Compute node.

### Recommended Actions ###
If you are using the KVM hypervisor with libvirt on OpenStack Compute
nodes, you should review your libvirt daemon configuration to ensure
that it is not allowing unauthenticated remote access.

Remote access to the libvirt daemon via TCP is configured by the
"listen_tls", "listen_tcp", and "auth_tcp" configuration directives.  By
default, these directives are all commented out.  This results in remote
access via TCP being disabled.

If you do not need remote libvirt daemon access, you should ensure that
the following configuration directives are set as follows in the
/etc/libvirt/libvirtd.conf configuration file.  Commenting out these
directives will have the same effect, as these values match the internal
defaults:

-  begin example libvirtd.conf snippet 
listen_tls = 1
listen_tcp = 0
auth_tcp = "sasl"
-  end example libvirtd.conf snippet 

If you need to allow remote access to the libvirt daemon between
OpenStack Compute nodes for live migration, you should ensure that
authentication is required.  Additionally, you should consider enabling
TLS to allow remote connections to be encrypted.

The following libvirt daemon configuration directives will allow for
unencrypted remote connections that use SASL for authentication:

-  begin example libvirtd.conf snippet 
listen_tls = 0
listen_tcp = 1
auth_tcp = "sasl"
-  end example libvirtd.conf snippet 

If you want to require TLS encrypted remote connections, you will have
to obtain X.509 certificates and configure the libvirt daemon to use
them to use TLS.  Details on this configuration are in the libvirt
daemon documentation.  Once the certificates are configured, you should
set the following libvirt daemon configuration directives:

-  begin example libvirtd.conf snippet 
listen_tls = 1
listen_tcp = 0
auth_tls = "none"
-  end example libvirtd.conf snippet 

When using TLS, setting the "auth_tls" configuration directive to "none"
uses X.509 client certificates for authentication.  You can additionally
require SASL authentication by setting the following libvirt daemon
configuration directives:

-  begin example libvirtd.conf snippet 
listen_tls = 1
listen_tcp = 0
auth_tls = "sasl"
-  end example libvirtd.conf snippet 

When using TLS, it is also necessary to configure the OpenStack Compute
nodes to use a non-default URI for live migration.  This is done by
setting the following configuration directive in /etc/nova/nova.conf:

-  begin example nova.conf snippet 
live_migration_uri=qemu+tls://%s/system
-  end example nova.conf snippet 

For more details on libvirt daemon remote URI form

Re: [Openstack] issue when I using pki as the token provider

[Adam Young]

On 03/05/2014 08:58 PM, Li, Chen wrote:

provider = keystone.token.providers.pki

That needs to be the full path to the class.

 keystone.token.providers.pki.Provider
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] any suggestions on how to change the actions from drop to allow

[Remo Mattei]

ovs-dpctl dump-flows
in_port(11),eth(src=00:1c:42:00:00:08,dst=00:1c:42:51:f1:eb),eth_type(0x0800),ipv4(src=10.211.55.2,dst=10.211.55.13,proto=6,tos=0x10,ttl=64,frag=no),tcp(src=62616,dst=22),
 packets:63, bytes:5646, used:0.004s, flags:P., actions:drop


This machine drops the actions is there an options to have that to allow.

Thanks
Remo 
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Swift/Keystone authentication problem?

[Adam Young]

On 03/03/2014 02:24 PM, Adam Lawson wrote:

Hola folks!

I had a working Swift deployment (one proxy, 10 storage nodes) using 
tempauth/swauth and with that config everything works fine. Add/remove 
objects, list etc. I am now in the process of trying to integrate 
Keystone and getting confused with number of possible problems the 
more I research so I figured I'd post it here.


I built a new Keystone server using the following documents: 
Configuring keystone 
 I 
also updated Swift to use Keystone using the following document: 
Configure Swift to Use Keystone 



Problem: Unable to authenticate using service:swift + "password". I'm 
mostly getting 401 Connection Refused errors and service catalog 
errors, depending which method I try. What am I missing?





Sounds like an SSL problem.  Make sure your swift auth_token section has 
the appropriate values set for SSL certs.



*User-list in Keystone:*

|$ keystone user-list`
+--+-+---+---+
|id| enabled | email |  name |
+--+-+---+---+
| 3b26d681b7b5448b94c563b1d8bb55fd | True| None  | admin |
| e186d19ab0ab4cc681b24196e76b9032 | True| None  | swift |
+--+-+---+---+|

*User-get in Keystone:*

|$ keystone user-get  e186d19ab0ab4cc681b24196e76b9032
+--+--+
|  Property  |   Value|
+--+--+
|  email|  None  |
|  enabled|  True  |
|  id|  e186d19ab0ab4cc681b24196e76b9032|
|  name|  swift|
|  tenantId|  7e9b8a64252340c2ba4dd292acf18e80  |
+--+--+|

*Tenant-list in Keystone:*

|$ keystone tenant-list
+--+-+-+
| id|name|  enabled|
+--+-+-+
|  539749c631044f64be5f29066ae486c4  |  demo|  True |
|  6140b18239284cce8b51305649dbb792  |  admin|  True |
|  7e9b8a64252340c2ba4dd292acf18e80  |  service|  True |
+--+-+-+|

*Role-list in Keystone:*

|$ keystone role-list
+--+---+
| id|   name|
+--+---+
|  6d64ff8265d6404983d774e34159dcd5  |  admin|
+--+---+|

*Service-list in keystone*

|$ keystone service-list
+--+--+--+--+
| id|name|  type|description|
+--+--+--+--+
|  0b2248b31e37499192d4e3cdf4288223  |  keystone|  identity|  Identity  Service 
 |
|  5ef2c32abd274473ab8b42f480feeb72  |  swift|  object-store|  Swift  Service   
  |
+--+--+--+--+|

*Endpoint-list in Keystone:*

|$ keystone endpoint-list
+--+---++++
| id|region|publicurl|  
 internalurl| adminurl|
+--+---++++
|  46600a4c54a94eee881e9a4a2c648b8b  |  RegionOne  |  
http://10.173.0.165:/v1/AUTH_%(tenant_id)s  
  
|http://10.173.0.165:/v1/AUTH_%(tenant_id)s  
  |http://10.173.0.165:/v1
 |
|  660c5babbe7746d485d31d85353ab1b8  |  RegionOne  |  
http://10.173.0.165.:5000/v2.0 |http://10.173.0.165:5000/v2.0   
|http://10.173.0.165:35357/v2.0  |
+--+---++++|

*/etc/swift/proxy-server.conf on Swift proxy:*

|[DEFAULT]
cert_file=  /etc/swift/cert.crt
key_file=  /etc/swift/cert.key
bind_port=  8080
workers=  8
user=  swift

[pipeline:main]
pipeline=  healthcheck proxy-logging cache authtoken keystoneauth proxy-logging 
proxy-server

[app:proxy-server]
use  =  egg:swift#proxy
allow_account_management=  true
account_autocreate=  true

[filter:proxy-logging]
use  =  egg:swift#proxy_logging

[filter:tempauth]
use  =  egg:swift#tempauth
user_system_root=  testpass.admin

[filter:healthcheck]
use  =  egg:swift#healthcheck

[filter:cache]
use  =  egg:swift#

Re: [Openstack] devstack + ldap

[Brad Topol]

Nice fix Dean!!!

Thanks,

Brad

Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet:  bto...@us.ibm.com
Assistant: Kendra Witherspoon (919) 254-0680



From:   Dean Troyer 
To: Craig Jellick 
Cc: "openstack@lists.openstack.org" 
Date:   03/06/2014 12:35 PM
Subject:Re: [Openstack] devstack + ldap



On Thu, Mar 6, 2014 at 9:51 AM, Craig Jellick  
wrote:
I cannot get devstack + ldap working. I've tried on Ubuntu and CentOS vms 
and in both cases I get a similar error:

In Ubuntu:
+ ldapdelete -x -w test -D cn=Manager,dc=openstack,dc=org -H 
ldap://localhost -r dc=openstack,dc=org
ldap_search: No such object (32)

This is another casualty of enabling errexit in stack.sh last week.  This 
has always silently failed when that object was not present, such as on 
the first run.

https://review.openstack.org/78675 fixes it for me locally, it's a one 
line change to lib/ldap.

dt

-- 

Dean Troyer
dtroyer@gmail.com___
Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] separate nics for communication

[Remo Mattei]

Hello everyone, 
I wonder if anyone has done separate nics with network to improve network 
traffic etc in Openstack, example

1) management network eth0
2) tunnel with gre eth1
3)provider network eth2
4) cinder with LUN eth3
5) swift backend using eth4 bond etc..

Thanks
Remo 
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] devstack + ldap

[Dean Troyer]

On Thu, Mar 6, 2014 at 9:51 AM, Craig Jellick  wrote:

>  I cannot get devstack + ldap working. I've tried on Ubuntu and CentOS
> vms and in both cases I get a similar error:
>
>  In Ubuntu:
> + ldapdelete -x -w test -D cn=Manager,dc=openstack,dc=org -H
> ldap://localhost -r dc=openstack,dc=org
> ldap_search: No such object (32)
>

This is another casualty of enabling errexit in stack.sh last week.  This
has always silently failed when that object was not present, such as on the
first run.

https://review.openstack.org/78675 fixes it for me locally, it's a one line
change to lib/ldap.

dt

-- 

Dean Troyer
dtro...@gmail.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] A VM cannot contact another VM using its floating IP

[Antonio Messina]

Hi all,

I am running OpenStack Folsom with nova-network, single-host, and my
VMs cannot contact other VMs (or even themselves) using the floating
IP.

I have two VMs:

Machine `A` (Alice)
  -  is an IP in range 10.65.4.0/22
  -  is a public IP

Machine `B` (Bob)
  -  is an IP in range 10.65.4.0/22
  -  is a public IP

Apparently, Alice is unable to contact Bob on any port (also ping
doesn't work)

What I think it's happening when Alice contacts Bob, is that the
packet goes to the controller node, where first of all its
*destination* ip address is changed by the rule:

-A nova-network-PREROUTING -d  -j DNAT
--to-destination 

then the *source* ip address shuold be changed, but the problem is
that nova-network creates this rule:

-A nova-network-float-snat -s  -o eth3 -j SNAT
--to-source 

where `eth3` is my external network on the controller node. However,
since the destination IP has been changed, the output interface is not
the public one (eth3) but the *internal* interface (br100), therefore
the SNAT rule doesn't match.

I see the topic is not completely new, there is at least a bug fixed
in Grizzly:

* "pinging own floating ip fails with external gateway"
  (https://bugs.launchpad.net/nova/+bug/1096259)

which apparently only fix the case where Alice talks to Alice itself,
and there is a similar StackOverflow question:

* Why can't Openstack VM reach itself via it's Floating IP?
  
http://serverfault.com/questions/460348/why-cant-openstack-vm-reach-itself-via-its-floating-ip

where it's suggested to add "--ctstate DNAT" to the SNAT rule, but
when I tried it it didn't work.

Is anyone else having the same issue? Is there something wrong with my
configuration?

Thank you in advance
Antonio Messina

-- 
antonio.s.mess...@gmail.com
antonio.mess...@uzh.ch +41 (0)44 635 42 22
GC3: Grid Computing Competence Center  http://www.gc3.uzh.ch/
University of Zurich
Winterthurerstrasse 190
CH-8057 Zurich Switzerland

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] issue when I using PKI for token format

[Miller, Mark M (EB SW Cloud - R&D - Corvallis)]

PKI tokens require certificates. Check to make sure that your Keystone 
installation created certificates and that you keystone.conf file points to 
them.

From: Li, Chen [mailto:chen...@intel.com]
Sent: Wednesday, March 05, 2014 6:00 PM
To: openstack@lists.openstack.org
Subject: [Openstack] issue when I using PKI for token format


Hi,

I'm working under CentOS 6.4 + Havana, my keystone version is:
  openstack-keystone.noarch 2013.2.2-1.el6 @openstack-havana

When I run command "keystone user-list", I get error:
 Authorization Failed: Unable to sign token. (HTTP 500)

I can get error information in both "keystone-startup.log" and "keystone.log":

2014-03-06 09:31:29.999 18693 ERROR keystone.common.cms [-] Signing error: 
Unable to load certificate - ensure you've configured PKI with 'keystone-manage 
pki_setup'
2014-03-06 09:31:29.999 18693 ERROR keystone.token.providers.pki [-] Unable to 
sign token
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki Traceback 
(most recent call last):
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/token/providers/pki.py", line 39, in 
_get_token_id
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki 
CONF.signing.keyfile)
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 144, in 
cms_sign_token
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki output = 
cms_sign_text(text, signing_cert_file_name, signing_key_file_name)
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki File 
"/usr/lib/python2.6/site-packages/keystone/common/cms.py", line 139, in 
cms_sign_text
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki raise 
environment.subprocess.CalledProcessError(retcode, "openssl")
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki 
CalledProcessError: Command 'openssl' returned non-zero exit status 3
2014-03-06 09:31:29.999 18693 TRACE keystone.token.providers.pki
2014-03-06 09:31:30.000 18693 WARNING keystone.common.wsgi [-] Unable to sign 
token.
~

Anyone know why this happened ???

Thanks.
-chen



My /etc/keystone/keystone.conf :

[DEFAULT]

[sql]
connection = mysql://keystone:keystone@host-db/keystone

[identity]

[credential]

[trust]

[os_inherit]

[catalog]
driver = keystone.catalog.backends.sql.Catalog

[endpoint_filter]

[token]
driver = keystone.token.backends.memcache.Token

[cache]

[policy]

[ec2]

[assignment]

[oauth1]

[ssl]

[signing]

[ldap]

[auth]
methods = external,password,token,oauth1
password = keystone.auth.plugins.password.Password
token = keystone.auth.plugins.token.Token
oauth1 = keystone.auth.plugins.oauth1.OAuth

[paste_deploy]

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] UX Content in OpenStack Upstream Training?

[Debojyoti Dutta]

I think this is a valid point and we should do something in the UX space.
1.5yrs ago, we wanted to explore UX issues and wrote a tool called
Curvature and did some UX experiments - will dig up our draft paper and
post. For now the demo is at
https://www.openstack.org/summit/portland-2013/session-videos/presentation/interactive-visual-orchestration-with-curvature-and-donabe
we open sourced our "app" written in rails and one of the interns
contributed a bunch of stuff into Horizon.
https://github.com/CiscoSystems/curvature

I am up for a UX working group.

debo



On Thu, Mar 6, 2014 at 7:47 AM, Jacki Bauer wrote:

>  Hello,
> I was looking at the Upstream Training (
> https://wiki.openstack.org/wiki/OpenStack_Upstream_Training/Info) and I'm
> wondering how much of the content is directed at people who want to or are
> currently contributing user experience work - whether that is API design,
> UI design, user research and requirements development? Is it worthwhile for
> these people to attend? And if not, if this content doesn't exist yet, how
> might we get it included in the future?
>
>  Being new to OpenStack, there's an obvious need for UX and design work,
> but the number of contributors is small and it is quite difficult to get
> started because the process isn't well defined.
>
>  Thanks
>  -Jacki
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
-Debo~
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] devstack + ldap

[Craig Jellick]

Hi,

I cannot get devstack + ldap working. I've tried on Ubuntu and CentOS vms and 
in both cases I get a similar error:

In Ubuntu:
+ ldapdelete -x -w test -D cn=Manager,dc=openstack,dc=org -H ldap://localhost 
-r dc=openstack,dc=org
ldap_search: No such object (32)

In CentOS, it's a bit more verbose, but still results in an ldap No such object 
(32) error:
+ local infile=/home/vagrant/devstack/files/ldap/manager.ldif.in
+ sed -e '
s|${LDAP_OLCDB_NUMBER}|2|
s|${SLAPPASS}|{SSHA}ub5DT7KsuOe/t9bZM2R2xcwV3bD9DEnI|
s|${LDAP_ROOTPW_COMMAND}|add|
s|${BASE_DC}|openstack|
s|${BASE_DN}|dc=openstack,dc=org|
s|${MANAGER_DN}|cn=Manager,dc=openstack,dc=org|
' /home/vagrant/devstack/files/ldap/manager.ldif.in
+ sudo ldapmodify -Y EXTERNAL -H ldapi:/// -f 
/tmp/ldap.19515.OLAEpAafC9/manager.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "olcDatabase={2}hdb,cn=config"
ldap_modify: No such object (32)
matched DN: cn=config


My very simple localrc looks like this:
ENABLED_SERVICES=key,n-api,n-crt,n-obj,n-cpu,n-net,n-cond,cinder,c-sch,c-api,c-vol,n-sch,n-novnc,n-xvnc,n-cauth,horizon,mysql,rabbit,ldap
KEYSTONE_IDENTITY_BACKEND=ldap
KEYSTONE_CLEAR_LDAP=yes
DATABASE_PASSWORD=test
RABBIT_PASSWORD=test
SERVICE_TOKEN=test
SERVICE_PASSWORD=test
ADMIN_PASSWORD=test
LDAP_PASSWORD=test

Anyone have any ideas?




/Craig J
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] UX Content in OpenStack Upstream Training?

[Jacki Bauer]

Hello,
I was looking at the Upstream Training 
(https://wiki.openstack.org/wiki/OpenStack_Upstream_Training/Info) and I'm 
wondering how much of the content is directed at people who want to or are 
currently contributing user experience work - whether that is API design, UI 
design, user research and requirements development? Is it worthwhile for these 
people to attend? And if not, if this content doesn't exist yet, how might we 
get it included in the future?

Being new to OpenStack, there's an obvious need for UX and design work, but the 
number of contributors is small and it is quite difficult to get started 
because the process isn't well defined.

Thanks
-Jacki
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] nova-manage network create bug

[Mike Smith]

I have experienced this exact same issue with nova-network on our Havana 
installs with Nova Network.



From: Alexey Wasilyev [awasil...@griddynamics.com]
Sent: Thursday, March 06, 2014 1:28 AM
To: openstack@lists.openstack.org
Subject: [Openstack] nova-manage network create bug

Hello guys

I faced a bug in latest nova network:

[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork 
172.26.0.0/24  --vlan 500
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork 
172.26.1.0/24  --vlan 501
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork 
172.26.2.0/24  --vlan 502
[root@host awasilyev]# nova-manage network list
id   IPv4   IPv6   start address   DNS1   DNS2  
 VlanID project uuid
64   172.26.0.0/24 None   172.26.0.3 
8.8.4.4 None   500 None   
225c8cbf-89bb-4171-b405-0047012a7803
65   172.26.1.0/24 None   172.26.1.3 
8.8.4.4 None   502 None   
d461b285-d9c6-4a8c-ae39-5a657bb5926a
66   172.26.2.0/24 None   172.26.2.3 
8.8.4.4 None   504 None   
4c5a5d5b-24c8-4833-8bd0-6dcca11acb68

I try to create 3 networks, specifying exact vlan number for each network. But 
nova-manage creates networks using wrong vlan id's.

My previous openstack install (it was 3-4 monthes ago) does not have this bug.

--
Alexey Wasilyev
Systems Administrator
Grid Dynamics



CONFIDENTIALITY NOTICE: This message is intended only for the use and review of 
the individual or entity to which it is addressed and may contain information 
that is privileged and confidential. If the reader of this message is not the 
intended recipient, or the employee or agent responsible for delivering the 
message solely to the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify 
sender immediately by telephone or return email. Thank you.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] swift recon query

[Steve Mayer]

The '-a' argument to swift-recon is for looking at the async-pendings, 
which will only be available if you've set up the 
/usr/bin/swift-recon-cron job on the object server nodes.


Try running with the '-d' or '-l' arguments to see some actual 
statistics.


--
Steve Mayer
smaye...@me.com

On 6 Mar 2014, at 2:31, Drudy, Gerry wrote:


Add the verbose option to swift-recon:

swift-recon -av

It will list all the object servers in the ring.  Each server listed 
should have the object-server process running.


Gerry.

From: pragya jain [mailto:prag_2...@yahoo.co.in]
Sent: 06 March 2014 10:25
To: Drudy, Gerry; openstack@lists.openstack.org
Subject: Re: [Openstack] swift recon query

hi Gerry,

I run following commands:
root@swift-VirtualBox:~# curl -i http://127.0.0.1:6000/recon/async
curl: (7) couldn't connect to host
root@swift-VirtualBox:~# swift-recon -a
===
--> Starting reconnaissance on 4 hosts
===
[2014-03-06 15:51:14] Checking async pendings
[async_pending] - No hosts returned valid data.
===
I can't understand where is the problem

Please help.

Thanks
Pragya jain

On Thursday, 6 March 2014 2:38 PM, "Drudy, Gerry"  
wrote:

Try

curl  -i http://127.0.0.1:6000/recon/async

assuming 6000 is the port the object-server binds to.

Gerry,

From: pragya jain [mailto:prag_2...@yahoo.co.in]
Sent: 06 March 2014 06:58
To: openstack@lists.openstack.org
Subject: Re: [Openstack] swift recon query

please somebody answer my questions related to swift recon.

Thanks

Pragya Jain

On Wednesday, 5 March 2014 2:31 PM, pragya jain 
 wrote:

hello all,

I have some basic questions about swift recon. please query them.

Q1: what should be the curl command for recon?

I use the following commands:
1.  root@swift-VirtualBox:~# curl -i http://127.0.0.1:8080/recon/async

HTTP/1.1 401 Unauthorized
Content-Length: 131
Content-Type: text/html; charset=UTF-8
Www-Authenticate: Swift realm="async"
X-Trans-Id: txe8c8850fc0a74ae095faa-005316e3a5
Date: Wed, 05 Mar 2014 08:43:17 GMT

UnauthorizedThis server could not verify that you 
are authorized to access the document you requested.


2.  root@swift-VirtualBox:~# curl -i 
http://127.0.0.1:8080/v1/AUTH_prag2648/recon/async


HTTP/1.1 401 Unauthorized
Content-Length: 131
Content-Type: text/html; charset=UTF-8
Www-Authenticate: Swift realm="AUTH_prag2648"
X-Trans-Id: tx978f787ce01f446a9beeb-005316e424
Date: Wed, 05 Mar 2014 08:45:24 GMT

UnauthorizedThis server could not verify that you 
are authorized to access the document you requested.


Q2. Does 'swift-recon' command not provide the status about
(i)  /proc/meminfo,
(ii) currently mounted file systems
(iii)list of devices
   if 'swift-recon' provides these informations, then what should be 
the command?


Q3. It stands for what?
 low
 high
 avg
 total
 failed
 no_result
 reported

Pragya Jain


___
Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to : openstack@lists.openstack.org
Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] assistcance required on ceilometer alarm-evaluator and ceilometer-alarm-notifier

[m.channappa.negalur]

Hi Glynn,

You can also refer question which I have raised
https://answers.launchpad.net/ubuntu/+source/ceilometer/+question/245076

I have installed Ubuntu and configured with Havana setup

oss@controller:~$ sudo su
root@Tcontroller:/home/oss# cat /etc/issue
Ubuntu 12.04.3 LTS \n \l

root@controller:/home/oss# getconf LONG_BIT
64
root@controller:/home/oss#

-Original Message-
From: Eoghan Glynn [mailto:egl...@redhat.com]
Sent: Thursday, March 06, 2014 4:50 PM
To: Channappa Negalur, M.
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] assistcance required on ceilometer alarm-evaluator and 
ceilometer-alarm-notifier


A quick look at [1] suggests that the Ubuntu packages may not have been updated 
to accommodate the alarm services.

Can you clarify this with the package owner? (also listed on [1])

Cheers,
Eoghan

[1] https://launchpad.net/ubuntu/+source/ceilometer

>
> Hi team ,
>
>
>
> Can any one help in in providing the link to install
> ceilometer-alarm-evaluator and ceil ometer-alarm-notifier and also
> package for ubuntu 12.04 .?
>
>
>
> In install document nothing much mentioned about
> ceilometer-alarm-evaluator and ceil ometer-alarm-notifier . How can I verify 
> this after installation ?
>
>
>
> Regards,
>
> Malleshi C N
>
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you
> have received it in error, please notify the sender immediately and
> delete the original. Any other use of the e-mail by you is prohibited.
> Where allowed by local law, electronic communications with Accenture
> and its affiliates, including e-mail and instant messaging (including
> content), may be scanned by our systems for the purposes of
> information security and assessment of internal compliance with Accenture 
> policy.
> __
> 
>
> www.accenture.com
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>




This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy.
__

www.accenture.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Announcing Dwarf - OpenStack API on top of libvirt/kvm

[Jacob Godin]

Very neat! Could see this as being a nice alternative to a full Devstack
install


On Thu, Mar 6, 2014 at 9:28 AM, Sandy Walsh wrote:

>  Cool idea!
>
>  -S
>
>  --
> *From:* Juerg Haefliger [jue...@gmail.com]
> *Sent:* Thursday, March 06, 2014 7:00 AM
> *To:* openstack@lists.openstack.org Openstack
> *Subject:* [Openstack] Announcing Dwarf - OpenStack API on top of
> libvirt/kvm
>
>Hi all,
>
>  I have this little pet project of mine that reached a state where it
> might be useful to others.
>
>  Dwarf is a simple service, that provides support for a subset of the
> OpenStack API on top of a locally running libvirt daemon (with KVM in the
> back). The main driver for this is to have a somewhat simple and isolated
> environment to test OpenStack guest images and as such, it supports
> importing images and keypairs and booting instances and some more.
>
>  There are lots of restrictions and short-comings and bugs too but if you
> want to check it out, the source is here (along with some more
> information): https://github.com/juergh/dwarf/
>
>  Pre-built packages for Ubuntu Precise and Saucy are available from my
> PPA:
> https://launchpad.net/~juergh/+archive/dwarf
>
>  Comments, feedback, bug reports and suggestions are more than welcome.
>
>  Enjoy
>  ...Juerg
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Announcing Dwarf - OpenStack API on top of libvirt/kvm

[Sandy Walsh]

Cool idea!

-S


From: Juerg Haefliger [jue...@gmail.com]
Sent: Thursday, March 06, 2014 7:00 AM
To: openstack@lists.openstack.org Openstack
Subject: [Openstack] Announcing Dwarf - OpenStack API on top of libvirt/kvm

Hi all,

I have this little pet project of mine that reached a state where it might be 
useful to others.

Dwarf is a simple service, that provides support for a subset of the OpenStack 
API on top of a locally running libvirt daemon (with KVM in the back). The main 
driver for this is to have a somewhat simple and isolated environment to test 
OpenStack guest images and as such, it supports importing images and keypairs 
and booting instances and some more.

There are lots of restrictions and short-comings and bugs too but if you want 
to check it out, the source is here (along with some more information): 
https://github.com/juergh/dwarf/

Pre-built packages for Ubuntu Precise and Saucy are available from my PPA:
https://launchpad.net/~juergh/+archive/dwarf

Comments, feedback, bug reports and suggestions are more than welcome.

Enjoy
...Juerg

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Ceilometer monitoring

[nishant kumar]

Hi,
I  monitored meter disk_write _bytes in table sample for an instance . Its
volume always increasing with timestamp even after deletion of data from
storage alloted to a Vm.
Second thing i noticed after rebooting of virtual machine everytime volume
of disk_write_bytes ,disk_read_bytes, disk_write_request and
disk_read_request  in  table sample increases with timestamp even we dont
send any read and write request to its Vm.so can anyone tell me
1. What exactly volume in sample table store for meter disk_write_bytes and
2.how ceilometer collect the information about of disk usage.
Thanks and regards,
Nishant kumar
Mobile : 9833065902
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] provider network with 3 nics

[Ageeleshwar Kandavelu]

Hi,
I am assuming that eth2 is attached to br-eth2 and eth2 is connected to the 
192.168.1.x network.

1. make sure eth2 has promiscous enabled(ip link show eth2) and the link is 
up(mii-tool eth2)
ip link set eth2 promisc on
ip link set eth2 up

Thank you,
Ageeleshwar K



http://www.csscorp.com/common/email-disclaimer.php
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] assistcance required on ceilometer alarm-evaluator and ceilometer-alarm-notifier

[Eoghan Glynn]

A quick look at [1] suggests that the Ubuntu packages may not
have been updated to accommodate the alarm services.

Can you clarify this with the package owner? (also listed on [1])

Cheers,
Eoghan

[1] https://launchpad.net/ubuntu/+source/ceilometer

> 
> Hi team ,
> 
> 
> 
> Can any one help in in providing the link to install
> ceilometer-alarm-evaluator and ceil ometer-alarm-notifier and also package
> for ubuntu 12.04 .?
> 
> 
> 
> In install document nothing much mentioned about ceilometer-alarm-evaluator
> and ceil ometer-alarm-notifier . How can I verify this after installation ?
> 
> 
> 
> Regards,
> 
> Malleshi C N
> 
> 
> 
> This message is for the designated recipient only and may contain privileged,
> proprietary, or otherwise confidential information. If you have received it
> in error, please notify the sender immediately and delete the original. Any
> other use of the e-mail by you is prohibited. Where allowed by local law,
> electronic communications with Accenture and its affiliates, including
> e-mail and instant messaging (including content), may be scanned by our
> systems for the purposes of information security and assessment of internal
> compliance with Accenture policy.
> __
> 
> www.accenture.com
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Announcing Dwarf - OpenStack API on top of libvirt/kvm

[Juerg Haefliger]

Hi all,

I have this little pet project of mine that reached a state where it might
be useful to others.

Dwarf is a simple service, that provides support for a subset of the
OpenStack API on top of a locally running libvirt daemon (with KVM in the
back). The main driver for this is to have a somewhat simple and isolated
environment to test OpenStack guest images and as such, it supports
importing images and keypairs and booting instances and some more.

There are lots of restrictions and short-comings and bugs too but if you
want to check it out, the source is here (along with some more
information): https://github.com/juergh/dwarf/

Pre-built packages for Ubuntu Precise and Saucy are available from my PPA:
https://launchpad.net/~juergh/+archive/dwarf

Comments, feedback, bug reports and suggestions are more than welcome.

Enjoy
...Juerg
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

[Arindam Choudhury]

Thanks, I used a really bad way of linking qemu-kvm to qemu-system-x86_64, is 
there any better way or I should change nova-compute codes?

From: parthi...@hp.com
To: arin...@live.com; lilinguo8...@gmail.com; openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Thu, 6 Mar 2014 10:19:56 +









Arindam,
 
If you don’t want to see the error in the logs you can configure 
/etc/nova/nova.conf to
 
[libvirt]
inject_partition = -2
 
The guest can then inject files and metadata after it starts up, which is more 
preferable.
 
~parthi
 



From: Arindam Choudhury [mailto:arin...@live.com]


Sent: 06 March 2014 09:48

To: 黎林果; openstack@lists.openstack.org

Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


 

Hi,



It will be very helpful if you can share your procedure. My libguestfs version 
is libguestfs-1.16.34-2.el6.x86_64




Date: Thu, 6 Mar 2014 09:24:51 +0800

Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

From: lilinguo8...@gmail.com

To: arin...@live.com


I've been done. The guestfs's python file has a bug.

Bug I forget what is version of the guestfs. If you can't deal the problem, I 
can find out what I have done.


 

2014-03-05 23:30 GMT+08:00 Arindam Choudhury :




Thanking a lot for helping me. 





From: 
parthi...@hp.com

To: arin...@live.com

CC: 
openstack@lists.openstack.org



Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Date: Wed, 5 Mar 2014 15:16:25 +

The guestfs error is due to a misconfiguration of guestfs and will only result 
in not having files injected before booting. Usually this is harmless as 
cloud-init
 like software will fix it after booting.

 

Glad the VM booted
J

 

 



From: Arindam Choudhury [mailto:arin...@live.com]


Sent: 05 March 2014 15:10



To: Parthipan, Loganathan

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

 


 

changing /etc/libvirt/qemu.conf helped
.
clear_emulator_capabilities=0 was already set.



VM boots up, but it still has the same error in log.



log 



instance-log



ls -alh /var/lib/nova/instances/7d79e021-72a9-4e5c-b2e5-312e16355dcd/

total 52M

drwxr-xr-x 2 nova nova 4.0K Mar  5 15:50 .

drwxr-xr-x 5 nova nova 4.0K Mar  5 15:50 ..

-rw-rw 1 root root  25K Mar  5 15:51 console.log

-rw-r--r-- 1 root root  52M Mar  5 15:51 disk

-rw-r--r-- 1 nova nova 1.6K Mar  5 15:50 libvirt.xml








 

From: 
parthi...@hp.com

To: arin...@live.com; 
openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Date: Wed, 5 Mar 2014 13:53:25 +


If that doesn’t work try setting clear_emulator_capabilities=0

 



From: Parthipan, Loganathan


Sent: 05 March 2014 13:37

To: 'Arindam Choudhury'; 
openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


 

Try setting user and group to root in /etc/libvirt/qemu.conf

 



From: Arindam Choudhury [mailto:arin...@live.com]


Sent: 05 March 2014 13:36

To: Parthipan, Loganathan; 
openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


 



./configure --enable-trace-backend=ftrace --enable-kvm --enable-vhost-net 
--enable-virtfs --target-list=x86_64-linux-user,x86_64-softmmu












...



[邮件部分隐藏]  

___

Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to : openstack@lists.openstack.org

Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

 




  ___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] swift recon query

[Drudy, Gerry]

Add the verbose option to swift-recon:

swift-recon -av

It will list all the object servers in the ring.  Each server listed should 
have the object-server process running.

Gerry.

From: pragya jain [mailto:prag_2...@yahoo.co.in]
Sent: 06 March 2014 10:25
To: Drudy, Gerry; openstack@lists.openstack.org
Subject: Re: [Openstack] swift recon query

hi Gerry,

I run following commands:
root@swift-VirtualBox:~# curl -i http://127.0.0.1:6000/recon/async
curl: (7) couldn't connect to host
root@swift-VirtualBox:~# swift-recon -a
===
--> Starting reconnaissance on 4 hosts
===
[2014-03-06 15:51:14] Checking async pendings
[async_pending] - No hosts returned valid data.
===
I can't understand where is the problem

Please help.

Thanks
Pragya jain

On Thursday, 6 March 2014 2:38 PM, "Drudy, Gerry"  wrote:
Try

curl  -i http://127.0.0.1:6000/recon/async

assuming 6000 is the port the object-server binds to.

Gerry,

From: pragya jain [mailto:prag_2...@yahoo.co.in]
Sent: 06 March 2014 06:58
To: openstack@lists.openstack.org
Subject: Re: [Openstack] swift recon query

please somebody answer my questions related to swift recon.

Thanks

Pragya Jain

On Wednesday, 5 March 2014 2:31 PM, pragya jain  wrote:
hello all,

I have some basic questions about swift recon. please query them.

Q1: what should be the curl command for recon?

I use the following commands:
1.  root@swift-VirtualBox:~# curl -i http://127.0.0.1:8080/recon/async

HTTP/1.1 401 Unauthorized
Content-Length: 131
Content-Type: text/html; charset=UTF-8
Www-Authenticate: Swift realm="async"
X-Trans-Id: txe8c8850fc0a74ae095faa-005316e3a5
Date: Wed, 05 Mar 2014 08:43:17 GMT

UnauthorizedThis server could not verify that you are 
authorized to access the document you requested.

2.  root@swift-VirtualBox:~# curl -i 
http://127.0.0.1:8080/v1/AUTH_prag2648/recon/async

HTTP/1.1 401 Unauthorized
Content-Length: 131
Content-Type: text/html; charset=UTF-8
Www-Authenticate: Swift realm="AUTH_prag2648"
X-Trans-Id: tx978f787ce01f446a9beeb-005316e424
Date: Wed, 05 Mar 2014 08:45:24 GMT

UnauthorizedThis server could not verify that you are 
authorized to access the document you requested.

Q2. Does 'swift-recon' command not provide the status about
   (i)  /proc/meminfo,
   (ii) currently mounted file systems
   (iii)list of devices
  if 'swift-recon' provides these informations, then what should be the 
command?

Q3. It stands for what?
low
high
avg
total
failed
no_result
reported

Pragya Jain


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] query about Statsd

[pragya jain]

hello all,

I have some questions about Statsd server for openstack swift

Q1:  Is swift-informant middleware necessary to be included in 
proxy-server.conf in order to provide metrics to StatsD server?

Q2: what type of metrics does swift-informant middleware provide to StatsD 
server?

Q3:  What is StatsDlog? Is it a middleware or a daemon or something other? And, 
What type of metrics does it provide to StatsD server?

I had searched many documents, but I still have confusion about it.
Please somebody answer my questions.

Thanks 
Pragya jain___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Cinder] Default volume type

[Belmiro Moreira]

Hi,
thanks,
somehow I didn't see it.

regards,
Belmiro


On Thu, Mar 6, 2014 at 12:45 AM, Bill Owen  wrote:

> Hi Belmiro,
> That already exists, see default_volume_type in cinder.conf:
> # default volume type to use (string value)
> #default_volume_type=
>
> Regards,
> Bill Owen
> billo...@us.ibm.com
> GPFS and OpenStack
> 520-799-4829
>
>
> [image: Inactive hide details for Belmiro Moreira ---03/05/2014 01:31:54
> PM---Hi, in our cinder setup we would like to have different v]Belmiro
> Moreira ---03/05/2014 01:31:54 PM---Hi, in our cinder setup we would like
> to have different volume types associated
>
> From: Belmiro Moreira 
> To: "openstack-operat...@lists.openstack.org" <
> openstack-operat...@lists.openstack.org>, "openstack@lists.openstack.org"
> ,
> Date: 03/05/2014 01:31 PM
> Subject: [Openstack] [Cinder] Default volume type
> --
>
>
>
> Hi,
>
> in our cinder setup we would like to have different volume types
> associated to different qos. For example: standard, high_iops.
>
> If the user doesn't specify explicitly the volume type when it creates the
> volume in our use case it should default to one. "standard" for example.
>
> I can't find any option/blueprint related to this.
>
> It's already available? or should I propose a blueprint.
>
> thanks,
> Belmiro___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
<>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] swift recon query

[pragya jain]

hi Gerry,

I run following commands:
root@swift-VirtualBox:~# curl -i http://127.0.0.1:6000/recon/async
curl: (7) couldn't connect to host
root@swift-VirtualBox:~# swift-recon -a
===
--> Starting reconnaissance on 4 hosts
===
[2014-03-06 15:51:14] Checking async pendings
[async_pending] - No hosts returned valid data.
===


I can't understand where is the problem

Please help.

Thanks

Pragya jain




On Thursday, 6 March 2014 2:38 PM, "Drudy, Gerry"  wrote:
 
Try
> 
>curl  -i http://127.0.0.1:6000/recon/async
> 
>assuming 6000 is the port the object-server binds to.
> 
>Gerry,
> 
>From:pragya jain [mailto:prag_2...@yahoo.co.in] 
>Sent: 06 March 2014 06:58
>To: openstack@lists.openstack.org
>Subject: Re: [Openstack] swift recon query
> 
>please somebody answer my questions related to swift recon.
> 
>Thanks 
> 
>Pragya Jain
> 
>On Wednesday, 5 March 2014 2:31 PM, pragya jain  wrote:
>hello all,
>> 
>>I have some basic questions about swift recon. please query them.
>> 
>>Q1: what should be the curl command for recon?
>> 
>>I use the following commands:
>>1.  root@swift-VirtualBox:~# curl -i http://127.0.0.1:8080/recon/async
>> 
>>HTTP/1.1 401 Unauthorized
>>Content-Length: 131
>>Content-Type: text/html; charset=UTF-8
>>Www-Authenticate: Swift realm="async"
>>X-Trans-Id: txe8c8850fc0a74ae095faa-005316e3a5
>>Date: Wed, 05 Mar 2014 08:43:17 GMT
>>
>>UnauthorizedThis server could not verify that you are 
>>authorized to access the document you requested. 
>> 
>>2.  root@swift-VirtualBox:~# curl -i 
>>http://127.0.0.1:8080/v1/AUTH_prag2648/recon/async
>> 
>>HTTP/1.1 401 Unauthorized
>>Content-Length: 131
>>Content-Type: text/html; charset=UTF-8
>>Www-Authenticate: Swift realm="AUTH_prag2648"
>>X-Trans-Id: tx978f787ce01f446a9beeb-005316e424
>>Date: Wed, 05 Mar 2014 08:45:24 GMT
>>
>>UnauthorizedThis server could not verify that you are 
>>authorized to access the document you requested.
>> 
>>Q2. Does 'swift-recon' command not provide the status about 
>>   (i)  /proc/meminfo, 
>>   (ii) currently mounted file systems
>>   (iii)    list of devices
>>  if 'swift-recon' provides these informations, then what should be the 
>>command?
>> 
>>Q3. It stands for what?
>>    low
>>    high
>>    avg
>>    total
>>    failed
>>    no_result
>>    reported
>> 
>>Pragya Jain
>> 
>
>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

[Parthipan, Loganathan]

Arindam,

If you don’t want to see the error in the logs you can configure 
/etc/nova/nova.conf to

[libvirt]
inject_partition = -2

The guest can then inject files and metadata after it starts up, which is more 
preferable.

~parthi

From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 06 March 2014 09:48
To: 黎林果; openstack@lists.openstack.org
Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Hi,

It will be very helpful if you can share your procedure. My libguestfs version 
is libguestfs-1.16.34-2.el6.x86_64

Date: Thu, 6 Mar 2014 09:24:51 +0800
Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
From: lilinguo8...@gmail.com
To: arin...@live.com
I've been done. The guestfs's python file has a bug.
Bug I forget what is version of the guestfs. If you can't deal the problem, I 
can find out what I have done.

2014-03-05 23:30 GMT+08:00 Arindam Choudhury 
mailto:arin...@live.com>>:

Thanking a lot for helping me.

From: parthi...@hp.com
To: arin...@live.com
CC: openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Wed, 5 Mar 2014 15:16:25 +
The guestfs error is due to a misconfiguration of guestfs and will only result 
in not having files injected before booting. Usually this is harmless as 
cloud-init like software will fix it after booting.

Glad the VM booted :)


From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 05 March 2014 15:10

To: Parthipan, Loganathan
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


changing /etc/libvirt/qemu.conf helped [Image removed by sender. Image removed 
by sender. Emoji] . clear_emulator_capabilities=0 was already set.

VM boots up, but it still has the same error in log.

log 

instance-log

ls -alh /var/lib/nova/instances/7d79e021-72a9-4e5c-b2e5-312e16355dcd/
total 52M
drwxr-xr-x 2 nova nova 4.0K Mar  5 15:50 .
drwxr-xr-x 5 nova nova 4.0K Mar  5 15:50 ..
-rw-rw 1 root root  25K Mar  5 15:51 console.log
-rw-r--r-- 1 root root  52M Mar  5 15:51 disk
-rw-r--r-- 1 nova nova 1.6K Mar  5 15:50 libvirt.xml



From: parthi...@hp.com
To: arin...@live.com; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
Date: Wed, 5 Mar 2014 13:53:25 +
If that doesn’t work try setting clear_emulator_capabilities=0

From: Parthipan, Loganathan
Sent: 05 March 2014 13:37
To: 'Arindam Choudhury'; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Try setting user and group to root in /etc/libvirt/qemu.conf

From: Arindam Choudhury [mailto:arin...@live.com]
Sent: 05 March 2014 13:36
To: Parthipan, Loganathan; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)


./configure --enable-trace-backend=ftrace --enable-kvm --enable-vhost-net 
--enable-virtfs --target-list=x86_64-linux-user,x86_64-softmmu
...

[邮件部分隐藏]
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

<>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] assistcance required on ceilometer alarm-evaluator and ceilometer-alarm-notifier

[m.channappa.negalur]

Hi team ,

Can any one help in in providing the link to install 
ceilometer-alarm-evaluator
 and 
ceilometer-alarm-notifier
 and also package for ubuntu 12.04 .?

In install document nothing much mentioned about 
ceilometer-alarm-evaluator
 and 
ceilometer-alarm-notifier.
 How can I verify this after installation ?

Regards,
Malleshi C N



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy.
__

www.accenture.com
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Error mounting disk with libguestfs (child process died unexpectedly)

[Arindam Choudhury]

Hi,

It will be very helpful if you can share your procedure. My libguestfs version 
is libguestfs-1.16.34-2.el6.x86_64

Date: Thu, 6 Mar 2014 09:24:51 +0800
Subject: Re: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)
From: lilinguo8...@gmail.com
To: arin...@live.com

I've been done. The guestfs's python file has a bug.
Bug I forget what is version of the guestfs. If you can't deal the problem, I 
can find out what I have done.



2014-03-05 23:30 GMT+08:00 Arindam Choudhury :





Thanking a lot for helping me. 
From: parthi...@hp.com
To: arin...@live.com

CC: openstack@lists.openstack.org
Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Date: Wed, 5 Mar 2014 15:16:25 +









The guestfs error is due to a misconfiguration of guestfs and will only result 
in not having files injected before booting. Usually this is harmless as 
cloud-init
 like software will fix it after booting.

 

Glad the VM booted
J

 

 




From: Arindam Choudhury [mailto:arin...@live.com]


Sent: 05 March 2014 15:10


To: Parthipan, Loganathan

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)



 


changing /etc/libvirt/qemu.conf helped
.
clear_emulator_capabilities=0 was already set.



VM boots up, but it still has the same error in log.



log 



instance-log



ls -alh /var/lib/nova/instances/7d79e021-72a9-4e5c-b2e5-312e16355dcd/

total 52M

drwxr-xr-x 2 nova nova 4.0K Mar  5 15:50 .

drwxr-xr-x 5 nova nova 4.0K Mar  5 15:50 ..

-rw-rw 1 root root  25K Mar  5 15:51 console.log

-rw-r--r-- 1 root root  52M Mar  5 15:51 disk

-rw-r--r-- 1 nova nova 1.6K Mar  5 15:50 libvirt.xml










From: parthi...@hp.com

To: arin...@live.com; openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)

Date: Wed, 5 Mar 2014 13:53:25 +


If that doesn’t work try setting clear_emulator_capabilities=0


 




From: Parthipan, Loganathan


Sent: 05 March 2014 13:37

To: 'Arindam Choudhury'; openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)



 

Try setting user and group to root in /etc/libvirt/qemu.conf


 




From: Arindam Choudhury [mailto:arin...@live.com]


Sent: 05 March 2014 13:36

To: Parthipan, Loganathan; openstack@lists.openstack.org

Subject: RE: [Openstack] Error mounting disk with libguestfs (child process 
died unexpectedly)



 




./configure --enable-trace-backend=ftrace --enable-kvm --enable-vhost-net 
--enable-virtfs --target-list=x86_64-linux-user,x86_64-softmmu


...

[邮件部分隐藏]  
___

Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to : openstack@lists.openstack.org

Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



  ___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat/Ceilometer/Havana]: Auto scaling no longer occurring after some time

[Eoghan Glynn]

- Original Message -
> On Mon, Feb 24, 2014 at 04:46:17AM -0500, Eoghan Glynn wrote:
> > 
> > Hi Juha,
> > 
> > Are you using Havana?
> > 
> > If so, your alarm resource templates seem to be missing setting the
> > "repeat_actions" attribute to true. Continuous notification was required
> > in order for the Heat autoscaling cooldown logic (and continued scaling
> > actions) to work.
> > 
> > This was a quirk of the Heat implementation in Havan, but TBH from a
> > usability PoV should have always had this set to True by default. This
> > is fixed now on Heat:master:
> > 
> >   https://github.com/openstack/heat/commit/4dc987ef
> > 
> > but hasn't been backported to Heat:stable/stable.
> 
> I just took a look, and I don't think we can backport it, because it's
> changing the resource interface default
> 
> It's possible (although unlikely) that someone could be relying on the
> existing default so I don't think the patch is a valid candidate for a
> stable backport, unfortunately.

Are ceilometer alarms typically used in heat templates for anything other
than autoscaling I wonder?

If not, then I think it would be OK to change the default repeat_actions
on stable, as it would only impact users who are relying on a feature
to *not* work ;)

But if alarms are used in a general purpose sense, then you're probably
correct on the suitability for the stable branch.

Cheers,
Eoghan

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] swift recon query

[Drudy, Gerry]

Try

curl  -i http://127.0.0.1:6000/recon/async

assuming 6000 is the port the object-server binds to.

Gerry,

From: pragya jain [mailto:prag_2...@yahoo.co.in]
Sent: 06 March 2014 06:58
To: openstack@lists.openstack.org
Subject: Re: [Openstack] swift recon query

please somebody answer my questions related to swift recon.

Thanks

Pragya Jain

On Wednesday, 5 March 2014 2:31 PM, pragya jain  wrote:
hello all,

I have some basic questions about swift recon. please query them.

Q1: what should be the curl command for recon?

I use the following commands:
1.  root@swift-VirtualBox:~# curl -i http://127.0.0.1:8080/recon/async

HTTP/1.1 401 Unauthorized
Content-Length: 131
Content-Type: text/html; charset=UTF-8
Www-Authenticate: Swift realm="async"
X-Trans-Id: txe8c8850fc0a74ae095faa-005316e3a5
Date: Wed, 05 Mar 2014 08:43:17 GMT

UnauthorizedThis server could not verify that you are 
authorized to access the document you requested.

2.  root@swift-VirtualBox:~# curl -i 
http://127.0.0.1:8080/v1/AUTH_prag2648/recon/async

HTTP/1.1 401 Unauthorized
Content-Length: 131
Content-Type: text/html; charset=UTF-8
Www-Authenticate: Swift realm="AUTH_prag2648"
X-Trans-Id: tx978f787ce01f446a9beeb-005316e424
Date: Wed, 05 Mar 2014 08:45:24 GMT

UnauthorizedThis server could not verify that you are 
authorized to access the document you requested.

Q2. Does 'swift-recon' command not provide the status about
   (i)  /proc/meminfo,
   (ii) currently mounted file systems
   (iii)list of devices
  if 'swift-recon' provides these informations, then what should be the 
command?

Q3. It stands for what?
low
high
avg
total
failed
no_result
reported

Pragya Jain

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] nova-manage network create bug

[Alexey Wasilyev]

Hello guys

I faced a bug in latest nova network:

[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork
172.26.0.0/24  --vlan 500
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork
172.26.1.0/24  --vlan 501
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork
172.26.2.0/24  --vlan 502
[root@host awasilyev]# nova-manage network list
id   IPv4   IPv6   start address   DNS1   DNS2
  VlanID project uuid
64   172.26.0.0/24 None   172.26.0.3 8.8.4.4 None
500 None   225c8cbf-89bb-4171-b405-0047012a7803
65   172.26.1.0/24 None   172.26.1.3 8.8.4.4 None
502 None   d461b285-d9c6-4a8c-ae39-5a657bb5926a
66   172.26.2.0/24 None   172.26.2.3 8.8.4.4 None
504 None   4c5a5d5b-24c8-4833-8bd0-6dcca11acb68

I try to create 3 networks, specifying exact vlan number for each network.
But nova-manage creates networks using wrong vlan id's.

My previous openstack install (it was 3-4 monthes ago) does not have this
bug.

-- 
Alexey Wasilyev
Systems Administrator
Grid Dynamics
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack