Re: [Openstack] User Account and Authentication Service (UAA)
still learning , because we use openid here and LDAP. F On Fri, Aug 3, 2012 at 12:37 PM, Endre Karlson endre.karl...@gmail.com wrote: It has keystone. Den 3. aug. 2012 03:05 skrev Frans Thamura fr...@meruvian.org følgende: hi all anyone here have paper related to User Account and Authentication Service (UAA) in is OpenStack using UAA also? thx in advance F ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Ceilometer] Project Technical Leader election result
Hi, The PTL election for Ceilometer¹ is over. The winner is Nick Barcet. Congratulations ! The results are available here: http://www.opavote.org/vote/491028 ¹ http://wiki.openstack.org/EfficientMetering/PTLElectionProcess Cheers, -- Julien Danjou // Free Software hacker freelance // http://julien.danjou.info pgpWkJFf1lvVk.pgp Description: PGP signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] No handlers could be found for logger keystoneclient.v2_0.client (HTTP 404)？？？
Everyone: Hi! When I install keystone alone, find a error, that’s make me crazy !the situation as follow: This is my conf [DEFAULT] bind_host = 0.0.0.0 public_port = 5000 admin_port = 35357 admin_token = admin compute_port = 8774 verbose = True debug = True log_config = /etc/keystone/logging.conf # = Syslog Options # Send logs to syslog (/dev/log) instead of to file specified # by `log-file` use_syslog = False # Facility to use. If unset defaults to LOG_USER. # syslog_log_facility = LOG_LOCAL0 [sql] #connection = sqlite:var/lib/keystone/keystone.db connection = mysql://keystone:***@172.18.32.7/keystone idle_timeout = 200 [ldap] #url = ldap://localhost #tree_dn = dc=example,dc=com #user_tree_dn = ou=Users,dc=example,dc=com #role_tree_dn = ou=Roles,dc=example,dc=com #tenant_tree_dn = ou=Groups,dc=example,dc=com #user = dc=Manager,dc=example,dc=com #password = freeipa4all #suffix = cn=example,cn=com [identity] driver = keystone.identity.backends.sql.Identity [catalog] driver = keystone.catalog.backends.sql.Catalog [token] driver = keystone.token.backends.sql.Token # Amount of time a token should remain valid (in seconds) expiration = 86400 [policy] driver = keystone.policy.backends.rules.Policy [ec2] driver = keystone.contrib.ec2.backends.sql.Ec2 [filter:debug] paste.filter_factory = keystone.common.wsgi:Debug.factory [filter:token_auth] paste.filter_factory = keystone.middleware:TokenAuthMiddleware.factory [filter:admin_token_auth] paste.filter_factory = keystone.middleware:AdminTokenAuthMiddleware.factory [filter:xml_body] paste.filter_factory = keystone.middleware:XmlBodyMiddleware.factory [filter:json_body] paste.filter_factory = keystone.middleware:JsonBodyMiddleware.factory [filter:crud_extension] paste.filter_factory = keystone.contrib.admin_crud:CrudExtension.factory [filter:ec2_extension] paste.filter_factory = keystone.contrib.ec2:Ec2Extension.factory [app:public_service] paste.app_factory = keystone.service:public_app_factory [app:admin_service] paste.app_factory = keystone.service:admin_app_factory [pipeline:public_api] pipeline = token_auth admin_token_auth xml_body json_body debug ec2_extension public_service [pipeline:admin_api] pipeline = token_auth admin_token_auth xml_body json_body debug ec2_extension crud_extension admin_service [app:public_version_service] paste.app_factory = keystone.service:public_version_app_factory [app:admin_version_service] paste.app_factory = keystone.service:admin_version_app_factory [pipeline:public_version_api] pipeline = xml_body public_version_service [pipeline:admin_version_api] pipeline = xml_body admin_version_service [composite:main] use = egg:Paste#urlmap /v2.0 = public_api / = public_version_api [composite:admin] use = egg:Paste#urlmap /v2.0 = admin_api / = admin_version_api When I restart keystone Add tenant and user : root@keystone:~# keystone user-create --tenant_id e87f632d2c4e4f2b8dfe1fd2691d229d --name admin --pass admin --enabled true No handlers could be found for logger keystoneclient.v2_0.client Unable to communicate with identity service: 404 Not Found The resource could not be found. . (HTTP 404) Why? What can I miss? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] best practices for merging common into specific projects
Mark McLoughlin wrote: On Thu, 2012-08-02 at 15:47 -0700, Vishvananda Ishaya wrote: On Aug 2, 2012, at 1:05 PM, Eric Windisch e...@cloudscaling.com wrote: The scope of common is expanding. I believe it is time to seriously consider a proper PTL. Preferably, before the PTL elections. +1 So, I guess I've been doing this unofficially. I'm happy for that to be official until the next round elections. The only difference between a regular team lead and a PTL is the assignment of one seat on the Technical Committee. So the question is not whether openstack-common should have a formal lead, the question is whether the openstack-common lead should have an assigned seat on the future Technical Committee (TC). As you may know, I was advocating for a lean, directly-elected committee of 9 members, with no reserved seats. The current PPB (responsible for bootstrapping the TC) preferred another option: (elected) PTLs + 5 directly-elected members. My main opposition to that latter model was that it was difficult to separate between projects worth an automatic seat and projects not worth an automatic seat, and that it would ultimately result in a bloated board as we continue to add new projects. With the all-directly-elected model we wouldn't even be having this discussion. That said, I certainly think openstack-common is worth an automatic seat, and that with 13 members we'd not yet cross a critical bloat threshold. And Mark (or whoever else would get elected to common PTL) would certainly get elected in a direct election anyway. So I support that move, and will prepare a resolution to adjust the TC charter to accommodate this change and propose it at the next PPB meeting. I just think that at some point in a not-so-distant future we'll have to reconsider the PTLs+5 setup to support further project growth while keeping the TC dedicated and efficient. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qcow2 Details on base images
Hi Jay, Thanks a lot again, trying to get an understanding of the overall process. So the file system for qcow2 is sort of managed by qemu(not by openstack itself) ... create etc is done by qemu but read/write from filesystem is also manged by qemu? Is the filesystem supported by qemu for all cases(hypervisors other than kvm, or different image formats or when COW layer is not implemented) or does openstack have it's own filesystem management as well. And my next question is regarding memory management. In memory blocks are read/write to and from filesystem. So this process is supported by openstack ( if so,where should i look in the code for memory management ) or qemu? Thanks and Regards, Gaurab On Thu, Aug 2, 2012 at 10:53 PM, Jay Pipes jaypi...@gmail.com wrote: On 08/02/2012 07:47 AM, Gaurab Basu wrote: Hi Jay, Thanks for your reply, it helped me get started. I have been going through the code and some of the sparse docs that are available. This is the code file https://github.com/openstack/nova/blob/master/nova/virt/libvirt/utils.py However I am facing a new issue and require some help. I wanted to modify how openstack handles the cow layer as such and also the qcow2 format. It turns out that openstack issues the external command qemu-img. First of all, is qemu-img internal to openstack ( I mean code for how qemu-img is implemented is in openstack or in qemu ) It is in openstack, where is the code located. If it is outside openstack, does that mean i have to change the code in qemu and then link those binaries with openstack. QEMU is a totally separate project from Nova, yes. QEMU is written in C and has a number of executables such as qemu-img and qemu-nbd, etc. Nova calls out to these executables in subprocesses. If you want to make changes to QEMU, yes, you would want to look into the QEMU contribution process and community. Here's where to start: http://wiki.qemu.org/Documentation/GettingStartedDevelopers Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] os-create-server-ext and use
Hi- While going through the source code of Openstack Nova, I have seen this comment, We support two approaches to determining vNICs: - By default, a VM gets a vNIC for any network belonging to the VM's project, and a vNIC for any global network that has a NULL project_id. vNIC order is determined by the network's 'priority' field. - *If the 'os-create-server-ext' was used to create the VM, only the networks in 'requested_networks' are used to create vNICs, and the vNIC order is determiend by the order in the requested_networks array.* Can any one help me understand on how the second case will come in determining the vNICs of VM while creating VM from Horizon. Thanking you... -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] best practices for merging common into specific projects
Thierry Carrez wrote: So I support that move, and will prepare a resolution to adjust the TC charter to accommodate this change and propose it at the next PPB meeting. Pushed to the PPB's next meeting agenda as: http://wiki.openstack.org/Governance/Proposed/OpenStackCommonException Cheers, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] growing fixed-ip network
* Am Thu, Aug 02 2012 at 09:24:55 -0400 , schrieb Ravi Jagannathan: It should hop on to the next subnet block if available Since openstack doesn't do this, its just not possible to grow grow the network ? Christoph Ravi On Thu, Aug 2, 2012 at 5:58 AM, Christoph Kluenter c...@iphh.net wrote: Hi, I don't know how to handle the case when a tenant has used up all IPs. We use FlatNetworking, so no Floating IPs possible. So, when one tenant has used up all the IPs in their net, how can I assign another net to the same tenant ? If I just assign another net, every new instance just gets an IP from both nets. But if the first net doesn't have free IPs, I get the exception.NoMoreFixedIps() even if the second net still has lots of IPs. Can this be solved with quantum ? Cheers, Christoph -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] growing fixed-ip network
clarify more. By growing network do you mean adding more machine machines instances ? On Fri, Aug 3, 2012 at 7:03 AM, Christoph Kluenter c...@iphh.net wrote: * Am Thu, Aug 02 2012 at 09:24:55 -0400 , schrieb Ravi Jagannathan: It should hop on to the next subnet block if available Since openstack doesn't do this, its just not possible to grow grow the network ? Christoph Ravi On Thu, Aug 2, 2012 at 5:58 AM, Christoph Kluenter c...@iphh.net wrote: Hi, I don't know how to handle the case when a tenant has used up all IPs. We use FlatNetworking, so no Floating IPs possible. So, when one tenant has used up all the IPs in their net, how can I assign another net to the same tenant ? If I just assign another net, every new instance just gets an IP from both nets. But if the first net doesn't have free IPs, I get the exception.NoMoreFixedIps() even if the second net still has lots of IPs. Can this be solved with quantum ? Cheers, Christoph -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot pass hint to Nova Scheduler
Thank you guys, my issue is solved for the moment.
Sincerely, Heng
From: openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net
[openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net] on
behalf of Jay Pipes [jaypi...@gmail.com]
Sent: Friday, August 03, 2012 12:08 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Cannot pass hint to Nova Scheduler
Sorry for top-posting, but there's not really a good place to inline
comment.
First, let's tackle logging in devstack...
When using devstack, you noticed that it logs to the screen session by
default. To make devstack ALSO log to a file, put the following in your
localrc:
LOG_COLOR=False
SCREEN_LOGDIR=/opt/stack/logs
And re-run stack.sh. You will now find the various service log files in
/opt/stack/logs.
Second, let's handle the JSON issue...
Nova isn't trying to decode a file. It's trying to JSON-decode the
string you're putting on the command line:
--hint query=['=','$free_ram_mb',1024]
The novaclient is passing the string ['=','$free_ram_mb',1024] to the
jsonutils.loads() function, which is what is failing. You can try
parsing this string yourself and see that the failure is raised the same
as appears in the log:
jpipes@uberbox:~/repos/tempest$ python
Python 2.7.3 (default, Apr 20 2012, 22:39:59)
[GCC 4.6.3] on linux2
Type help, copyright, credits or license for more information.
import json
p = json.loads(['=','$free_ram_mb',1024])
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/json/__init__.py, line 326, in loads
return _default_decoder.decode(s)
File /usr/lib/python2.7/json/decoder.py, line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.7/json/decoder.py, line 384, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
The problem is the string needs to be properly formatted JSON, and
single-quotes are not allowed -- you need to use double-quotes:
p = json.loads('[=,$free_ram_mb,1024]')
print p
[u'=', u'$free_ram_mb', 1024]
Try your command like this instead:
nova --debug boot --image 827d564a-e636-4fc4-a376-d36f7ebe1747 --flavor
1 --hint query='[=,$free_ram_mb,1024]' server1
And I think you should be fine, as the following proof shows:
jpipes@uberbox:~/repos/tempest$ echo '[=,$free_ram_mb,1024]' |
python -mjson.tool
[
=,
$free_ram_mb,
1024
]
Best,
-jay
On 08/02/2012 02:09 PM, Heng Xu wrote:
Hi, attached is the json_filter file I was used, but I it just came with
devstack script installation, I did not even modify it.
Heng
From: Pengjun Pan [panpeng...@gmail.com]
Sent: Thursday, August 02, 2012 6:07 PM
To: Heng Xu
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Cannot pass hint to Nova Scheduler
Post your filter file. Might be a typo.
PJ
On Thu, Aug 2, 2012 at 1:02 PM, Heng Xu
shouhengzhang...@mail.utoronto.ca wrote:
Hi, I recorded the error message, below
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/opt/stack/nova/nova/scheduler/filters/json_filter.py, line 141, in
host_passes
2012-08-02 13:51:02 TRACE nova.rpc.amqp result =
self._process_filter(jsonutils.loads(query), host_state)
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/opt/stack/nova/nova/openstack/common/jsonutils.py, line 123, in loads
2012-08-02 13:51:02 TRACE nova.rpc.amqp return json.loads(s)
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/usr/lib/python2.7/json/__init__.py, line 326, in loads
2012-08-02 13:51:02 TRACE nova.rpc.amqp return _default_decoder.decode(s)
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/usr/lib/python2.7/json/decoder.py, line 366, in decode
2012-08-02 13:51:02 TRACE nova.rpc.amqp obj, end = self.raw_decode(s,
idx=_w(s, 0).end())
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/usr/lib/python2.7/json/decoder.py, line 384, in raw_decode
2012-08-02 13:51:02 TRACE nova.rpc.amqp raise ValueError(No JSON object
could be decoded)
2012-08-02 13:51:02 TRACE nova.rpc.amqp ValueError: No JSON object could be
decoded
2012-08-02 13:51:02 TRACE nova.rpc.amqp
it seems that the filter cannot find my json file, so although I was using
the --hint functionality, whatever typed after the hint did not went to the
filter host_passed function, so it could not locate the json object, any
thoughts?
Thanks. Heng
From:
openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net
[openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net] on
behalf of Heng Xu [shouhengzhang...@mail.utoronto.ca]
Sent: Thursday, August 02, 2012 4:47 PM
To: Pengjun Pan
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Cannot pass hint to Nova Scheduler
Hi PJ
I don't know what happen, I could not find the file in my
Re: [Openstack] EC2 api and tenants
Ryan, This looks like what the problem was. I'm running 2012.1 from the epel packages on centos 6.2. The ec2 layer doesn't look like it follows policy.json by default. It still has roles for netadmin, sysadmin and projectmanager hard coded in nova/api/ec2/__init__.py. Right now, I'm just making use of netadmin and sysadmin rather than creating new rules in policy.json. On Thu, Aug 2, 2012 at 6:51 PM, Ryan Lane rl...@wikimedia.org wrote: On Thu, Aug 2, 2012 at 1:23 PM, Mitchell Broome mitchell.bro...@gmail.com wrote: I'm using essex 2012.1 and I'm running into an issue with tenant separation using the ec2 api. I end up having to give a user the 'admin' role in keytone to create instances within a tenant. I can live with that but the problem is, now that the user has 'admin', they also see all of the instances including ones from other tenants via a describe_instances(). If I only give them the 'Member' role, they can only see the instances within thier default tenant but they can't create instances. Also, if they only have 'Member', I'm able to create instances via horizon manually. I'm assuming I'm missing some combination of roles I need to setup to allow a users to create instances in thier default tenant but not see other instances in other tenants. So far, from what I can tell, you need to add custom roles (or continue using sysadmin and netadmin), and add these roles to the proper actions in policy.json. - Ryan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] growing fixed-ip network
* Am Fri, Aug 03 2012 at 07:57:03 -0400 , schrieb Ravi Jagannathan: clarify more. By growing network do you mean adding more machine machines instances ? More instances. The tenant has used up the first net, has 254 instances running and now wants to add more instances. But since the net is full, it has to be another net. But this does not work. Cheers, Christoph On Fri, Aug 3, 2012 at 7:03 AM, Christoph Kluenter c...@iphh.net wrote: * Am Thu, Aug 02 2012 at 09:24:55 -0400 , schrieb Ravi Jagannathan: It should hop on to the next subnet block if available Since openstack doesn't do this, its just not possible to grow grow the network ? Christoph Ravi On Thu, Aug 2, 2012 at 5:58 AM, Christoph Kluenter c...@iphh.net wrote: Hi, I don't know how to handle the case when a tenant has used up all IPs. We use FlatNetworking, so no Floating IPs possible. So, when one tenant has used up all the IPs in their net, how can I assign another net to the same tenant ? If I just assign another net, every new instance just gets an IP from both nets. But if the first net doesn't have free IPs, I get the exception.NoMoreFixedIps() even if the second net still has lots of IPs. Can this be solved with quantum ? Cheers, Christoph -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Christoph Kluenter E-Mail: supp...@iphh.net Technik Tel: +49 (0)40 374919-10 IPHH Internet Port Hamburg GmbH Fax: +49 (0)40 374919-29 Wendenstrasse 408AG Hamburg, HRB 76071 D-20537 Hamburg Geschaeftsfuehrung: Axel G. Kroeger ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot pass hint to Nova Scheduler
Another questions is, I can get all the status of a computing node in the mysql
nova database, and select * from compute_node, but now I am using json filter,
the only field I have success with now is the free_ram_db, if my hint uses
free_disk_gb, then I always get error, but the database is showing my compute
node has $free_disk_gb equal 17, so I was wondering, where to find exactly what
kind of json field can use in json filter, thanks in advance
Heng
From: openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net
[openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net] on
behalf of Heng Xu [shouhengzhang...@mail.utoronto.ca]
Sent: Friday, August 03, 2012 12:08 PM
To: Jay Pipes; openstack@lists.launchpad.net
Subject: Re: [Openstack] Cannot pass hint to Nova Scheduler
Thank you guys, my issue is solved for the moment.
Sincerely, Heng
From: openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net
[openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net] on
behalf of Jay Pipes [jaypi...@gmail.com]
Sent: Friday, August 03, 2012 12:08 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Cannot pass hint to Nova Scheduler
Sorry for top-posting, but there's not really a good place to inline
comment.
First, let's tackle logging in devstack...
When using devstack, you noticed that it logs to the screen session by
default. To make devstack ALSO log to a file, put the following in your
localrc:
LOG_COLOR=False
SCREEN_LOGDIR=/opt/stack/logs
And re-run stack.sh. You will now find the various service log files in
/opt/stack/logs.
Second, let's handle the JSON issue...
Nova isn't trying to decode a file. It's trying to JSON-decode the
string you're putting on the command line:
--hint query=['=','$free_ram_mb',1024]
The novaclient is passing the string ['=','$free_ram_mb',1024] to the
jsonutils.loads() function, which is what is failing. You can try
parsing this string yourself and see that the failure is raised the same
as appears in the log:
jpipes@uberbox:~/repos/tempest$ python
Python 2.7.3 (default, Apr 20 2012, 22:39:59)
[GCC 4.6.3] on linux2
Type help, copyright, credits or license for more information.
import json
p = json.loads(['=','$free_ram_mb',1024])
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/json/__init__.py, line 326, in loads
return _default_decoder.decode(s)
File /usr/lib/python2.7/json/decoder.py, line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.7/json/decoder.py, line 384, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
The problem is the string needs to be properly formatted JSON, and
single-quotes are not allowed -- you need to use double-quotes:
p = json.loads('[=,$free_ram_mb,1024]')
print p
[u'=', u'$free_ram_mb', 1024]
Try your command like this instead:
nova --debug boot --image 827d564a-e636-4fc4-a376-d36f7ebe1747 --flavor
1 --hint query='[=,$free_ram_mb,1024]' server1
And I think you should be fine, as the following proof shows:
jpipes@uberbox:~/repos/tempest$ echo '[=,$free_ram_mb,1024]' |
python -mjson.tool
[
=,
$free_ram_mb,
1024
]
Best,
-jay
On 08/02/2012 02:09 PM, Heng Xu wrote:
Hi, attached is the json_filter file I was used, but I it just came with
devstack script installation, I did not even modify it.
Heng
From: Pengjun Pan [panpeng...@gmail.com]
Sent: Thursday, August 02, 2012 6:07 PM
To: Heng Xu
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Cannot pass hint to Nova Scheduler
Post your filter file. Might be a typo.
PJ
On Thu, Aug 2, 2012 at 1:02 PM, Heng Xu
shouhengzhang...@mail.utoronto.ca wrote:
Hi, I recorded the error message, below
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/opt/stack/nova/nova/scheduler/filters/json_filter.py, line 141, in
host_passes
2012-08-02 13:51:02 TRACE nova.rpc.amqp result =
self._process_filter(jsonutils.loads(query), host_state)
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/opt/stack/nova/nova/openstack/common/jsonutils.py, line 123, in loads
2012-08-02 13:51:02 TRACE nova.rpc.amqp return json.loads(s)
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/usr/lib/python2.7/json/__init__.py, line 326, in loads
2012-08-02 13:51:02 TRACE nova.rpc.amqp return _default_decoder.decode(s)
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/usr/lib/python2.7/json/decoder.py, line 366, in decode
2012-08-02 13:51:02 TRACE nova.rpc.amqp obj, end = self.raw_decode(s,
idx=_w(s, 0).end())
2012-08-02 13:51:02 TRACE nova.rpc.amqp File
/usr/lib/python2.7/json/decoder.py, line 384, in raw_decode
2012-08-02 13:51:02 TRACE nova.rpc.amqp raise ValueError(No JSON object
could be decoded)
Re: [Openstack] [Ceilometer] Project Technical Leader election result
Congratulations, Nick! On Fri, Aug 3, 2012 at 4:22 AM, Julien Danjou jul...@danjou.info wrote: Hi, The PTL election for Ceilometer¹ is over. The winner is Nick Barcet. Congratulations ! The results are available here: http://www.opavote.org/vote/491028 ¹ http://wiki.openstack.org/EfficientMetering/PTLElectionProcess Cheers, -- Julien Danjou // Free Software hacker freelance // http://julien.danjou.info ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Ceilometer] Project Technical Leader election result
On Fri, Aug 3, 2012 at 10:22 AM, Julien Danjou jul...@danjou.info wrote: The PTL election for Ceilometer¹ is over. The winner is Nick Barcet. congratulation Nick, well deserved. Chmouel. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Keystone: 'PKI Signed Tokens' lack support for revocation
On 08/02/2012 10:54 PM, Nathanael Burton wrote: Adam, I haven't yet had a chance to review how the new PKI signed tokens is implemented, but what you're describing sounds quite similar to online certificate status protocol (OCSP) but for tokens. Yes, I don't really have new idea here, just reimplementaiton of ideas from other projects. Nate On Aug 2, 2012 10:24 PM, Adam Young ayo...@redhat.com mailto:ayo...@redhat.com wrote: On 08/01/2012 11:05 PM, Maru Newby wrote: Hi Adam, I apologize if my questions were answered before. I wasn't aware that what I perceive as a very serious security concern was openly discussed. The arguments against revocation support, as you've described them, seem to be: - it's complicated/messy/expensive to implement and/or execute - Kerberos doesn't need it, so why would we? I'm not sure why either of these arguments would justify the potential security hole that a lack of revocation represents, but I suppose a 'short enough' token lifespan could minimize that hole. But how short a span are you suggesting as being acceptable? The delay between when a user's access permissions change (whether roles, password or even account deactivation) and when the ticket reflects that change is my concern. The default in Keystone has been 24h, which is clearly too long. Something on the order of 5 minutes would be ideal, but then ticket issuance could become the bottleneck. Validity that's much longer could be a real problem, though. Maybe not at the cloud administration level, but for a given project I can imagine someone being fired and their access being revoked. How long is an acceptable period for that ticket to still be valid? How much damage could be done by someone who should no longer have access to an account if their access cannot be revoked, by anyone, at all? I realize that I had been thinking about the revocation list as something that needs to be broadcast. This is certainly not the case. A much better approach would be for the Keystone server to have a list of revoked tokens exposed in an URL. Then, as service like Glance or Nova can query the Revocation list on a simple schedule. The time out would be configurable, of course. There is a question about what to do if the keystone server cannot be reached during that interval. Since the current behavior is for authentication to fail, I suppose we would continue doing that, but also wait a random amount of time and then requery the Keystone server. In the future, I would like to make the set of Keystone servers a configurable list, and the policy for revocation checking should be able to vary per server: some Keystone servers in a federated approach might not be accessible. In those cases, it might be necessary for one Keystone server to proxy the revocation list for another server. Let me know if this scheme makes sense to you. If so, we can write it up as an additional blueprint. It should not be that hard to implement. I'm hearing that you, as the implementer of this feature, don't consider the lack of revocation to be an issue. What am I missing? Is support for revocation so repugnant that the potential security hole is preferable? I can see that from a developer's perspective, but I don't understand why someone deploying Keystone wouldn't avoid PKI tokens until revocation support became available. Thanks, Maru On 2012-08-01, at 9:47 PM, Adam Young wrote: On 08/01/2012 09:19 PM, Maru Newby wrote: I see that support for PKI Signed Tokens has been added to Keystone without support for token revocation. I tried to raise this issue on the bug report: https://bugs.launchpad.net/keystone/+bug/1003962/comments/4 And the review: https://review.openstack.org/#/c/7754/ I'm curious as to whether anybody shares my concern and if there is a specific reason why nobody responded to my question as to why revocation is not required for this new token scheme. Anybody? It was discussed back when I wrote the Blueprint. While it is possible to do revocations with PKI, it is expensive and requires a lot of extra checking. Revocation is a policy decision, and the assumption is that people that are going to use PKI tokens are comfortable with out revocation. Kerberos service tickets have the same limitation, and Kerberos has been in deployment that way for close to 25 years. Assuming that PKI ticket lifespan is short enough, revocation should not be required. What will be tricky is to balance the needs of long lived tokens (delayed operations, long running operations) against the needs for reasonable token timeout. PKI Token revocation would look like CRLs in the
Re: [Openstack] [Netstack] os-create-server-ext and use
On Fri, Aug 3, 2012 at 3:48 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- While going through the source code of Openstack Nova, I have seen this comment, We support two approaches to determining vNICs: - By default, a VM gets a vNIC for any network belonging to the VM's project, and a vNIC for any global network that has a NULL project_id. vNIC order is determined by the network's 'priority' field. - *If the 'os-create-server-ext' was used to create the VM, only the networks in 'requested_networks' are used to create vNICs, and the vNIC order is determiend by the order in the requested_networks array.* Can any one help me understand on how the second case will come in determining the vNICs of VM while creating VM from Horizon. Hi Trinath, I think you're pointing to Quantum integration code in Nova. Horizon support for Quantum is currently in review: https://review.openstack.org/#/c/10116/ Based on plans, this will include the ability to specify the set of networks that a VM will connect to. Dan Thanking you... -- Regards, -- Trinath Somanchi, +91 9866 235 130 -- Mailing list: https://launchpad.net/~netstack Post to : netst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] keystone and ssl ?
On 08/03/2012 05:18 AM, Pierre Amadio wrote: snip https://blueprints.launchpad.net/keystone/+spec/2-way-ssl At the bottom of the blueprint, there are 2 addressed by links with a set of patches: https://review.openstack.org/1038 https://review.openstack.org/7706 But i do not find trace of those patches in the ubuntu package snip I also fail to find trace of those in a git checkout of the refs/heads/stable/essex branch of keystone's git repository. I am confused. The reason is because that code and a bunch of other stuff was ripped out of Keystone late in the Essex release series with the move to Keystone Light, which was essentially a rewrite of Keystone that replaced the Keystone project that had the code in it that you refer to above. I've cc'd Joe Heck to give you some information on when SSL support might be re-added to Keystone. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] best practices for merging common into specific projects
On 08/02/2012 08:52 PM, Eric Windisch wrote: What do you mean by membership services? See the email today from Yun Mao. This is a proposal to have a pluggable framework for integration services that maintain memberships. This was originally desiged to replace the MySQL heartbeats in Nova, although there will be a mysql-heartbeat backend by default as a drop-in replacement. There is a zookeeper backend in the works, and we've discussed the possibility of building a backend that can poll RabbitMQ's list_consumers. Ah, yes. I've urged the team to use the term ServiceGroup instead of the Zookeeper membership terminology -- as membership has other connotations in Glance and Nova -- for instance, membership in a project/tenant really has nothing to do with the concept of service groups that can monitor response/hearbeat of service daemons. Best, -jay This is useful for more than just Nova's heartbeats, however. This will largely supplant the requirement for the matchmaker to build these backends in itself, which had been my original plan (the matchmaker is already in openstack-common). As such, it had already been my intent to have a MySQL-backed matchmaker. The only thing new is that someone has actually written the code. In the first pass, the intention is to leave the matchmaker in and introduce the membership modules. Then, the matchmaker would either use the new membership modules as a backend, or even replaced entirely. Regards, Eric Windisch ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] best practices for merging common into specific projects
Ah, yes. I've urged the team to use the term ServiceGroup instead of the Zookeeper membership terminology -- as membership has other connotations in Glance and Nova -- for instance, membership in a project/tenant really has nothing to do with the concept of service groups that can monitor response/hearbeat of service daemons. I see. For some additional context, I'm looking to use this managing consumers of round-robin and fanout queues with the ZeroMQ driver, instead of the static hashmap that is used currently. Regards, Eric Windisch ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cannot pass hint to Nova Scheduler
On 08/03/2012 09:28 AM, Heng Xu wrote: Another questions is, I can get all the status of a computing node in the mysql nova database, and select * from compute_node, but now I am using json filter, the only field I have success with now is the free_ram_db, if my hint uses free_disk_gb, then I always get error, but the database is showing my compute node has $free_disk_gb equal 17, so I was wondering, where to find exactly what kind of json field can use in json filter, thanks in advance The nova.scheduler.host_manager.HostState class is what is checked for attributes, not the ComputeNode model. So, you need to use $free_disk_mb, not free_disk_gb. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [glance] legacy client removal and python-glanceclient
On Aug 3, 2012, at 6:59 AM, Alan Pevec wrote: So before glance is removed from openstack/glance (in folsom-3 if I understood correctly?) Given the response from the community, I think it would be a bad idea to remove bin/glance in Folsom. My current plan is to leave it in until Grizzly opens up and then drop it.___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qcow2 Details on base images
Hi Gaurab, Openstack is not a hypervisor, it is a management layer that sits on top of a hypervisor. Management of the guest filesystem and memory is all done by an underlying hypervisor, Generally KVM or Xen. KVM is essentially kernel module extensions for QEMU (which is a software emulator). I hope this is helpful. Vish On Aug 3, 2012, at 3:05 AM, Gaurab Basu basugaura...@gmail.com wrote: Hi Jay, Thanks a lot again, trying to get an understanding of the overall process. So the file system for qcow2 is sort of managed by qemu(not by openstack itself) ... create etc is done by qemu but read/write from filesystem is also manged by qemu? Is the filesystem supported by qemu for all cases(hypervisors other than kvm, or different image formats or when COW layer is not implemented) or does openstack have it's own filesystem management as well. And my next question is regarding memory management. In memory blocks are read/write to and from filesystem. So this process is supported by openstack ( if so,where should i look in the code for memory management ) or qemu? Thanks and Regards, Gaurab On Thu, Aug 2, 2012 at 10:53 PM, Jay Pipes jaypi...@gmail.com wrote: On 08/02/2012 07:47 AM, Gaurab Basu wrote: Hi Jay, Thanks for your reply, it helped me get started. I have been going through the code and some of the sparse docs that are available. This is the code file https://github.com/openstack/nova/blob/master/nova/virt/libvirt/utils.py However I am facing a new issue and require some help. I wanted to modify how openstack handles the cow layer as such and also the qcow2 format. It turns out that openstack issues the external command qemu-img. First of all, is qemu-img internal to openstack ( I mean code for how qemu-img is implemented is in openstack or in qemu ) It is in openstack, where is the code located. If it is outside openstack, does that mean i have to change the code in qemu and then link those binaries with openstack. QEMU is a totally separate project from Nova, yes. QEMU is written in C and has a number of executables such as qemu-img and qemu-nbd, etc. Nova calls out to these executables in subprocesses. If you want to make changes to QEMU, yes, you would want to look into the QEMU contribution process and community. Here's where to start: http://wiki.qemu.org/Documentation/GettingStartedDevelopers Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] keystone and ssl ?
The basic support for SSL has been readded to Keystone earlier this release cycle, alough theres still a few pieces trickling through the pipeline (recent updates to keystone client to allow for self-signed certs). It needs testing, and I dont know that we yet have good deployment option docs (there are several options there) on how to deploy keystone with SSL. The option to use a signed SSL cert as an authenticated administrative request itself has not been re-added, instead there was more interest from developers doing the code to focus on getting a base PKI implementation to allow for generically signed tokens in this release. - joe On Aug 3, 2012, at 9:13 AM, Jay Pipes jaypi...@gmail.com wrote: On 08/03/2012 05:18 AM, Pierre Amadio wrote: snip https://blueprints.launchpad.net/keystone/+spec/2-way-ssl At the bottom of the blueprint, there are 2 addressed by links with a set of patches: https://review.openstack.org/1038 https://review.openstack.org/7706 But i do not find trace of those patches in the ubuntu package snip I also fail to find trace of those in a git checkout of the refs/heads/stable/essex branch of keystone's git repository. I am confused. The reason is because that code and a bunch of other stuff was ripped out of Keystone late in the Essex release series with the move to Keystone Light, which was essentially a rewrite of Keystone that replaced the Keystone project that had the code in it that you refer to above. I've cc'd Joe Heck to give you some information on when SSL support might be re-added to Keystone. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [HPC] Reminder monthly telecon Aug. 6
Hi, This is just a reminder that we'll hold the first of the monthly HPC telecons this Monday, August 6 at 12:00 noon EDT. We'll use Webex (details below) due to the number of people who expressed interest earlier (way more than the 9 person Google Meetup max). I'm proposing the following agenda, but I'm open to additions or changes. 1) Update on ISI's HPC extensions 2) Comments from anyone who's stood up an HPC cloud or planning to do so 3) User feedback - what's missing from the current HPC extensions. 4) Opportunity for anyone to share best practices I hope to hear from you on Monday! best, JP -- John Paul Walters invites you to attend this online meeting. Topic: HPC Monthly Telecon Date: Monday, August 6, 2012 Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) Meeting Number: 923 255 478 Meeting Password: hpcmonthly --- To join the online meeting (Now from mobile devices!) --- 1. Go to https://openstack.webex.com/openstack/j.php?ED=200451317UID=0PW=NNDc0NWQwM2Q0RT=MiMxMQ%3D%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: hpcmonthly 4. Click Join. To view in other time zones or languages, please click the link: https://openstack.webex.com/openstack/j.php?ED=200451317UID=0PW=NNDc0NWQwM2Q0ORT=MiMxMQ%3D%3D --- For assistance --- 1. Go to https://openstack.webex.com/openstack/mc 2. On the left navigation bar, click Support. You can contact me at: jwalt...@isi.edu To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://openstack.webex.com/openstack/j.php?ED=200451317UID=0ICS=MILD=1RD=2ST=1SHA2=Rgtldz-Me-bviq4iqjCdUTu5tvTmYbooQApYM5I5a6Y=RT=MiMxMQ%3D%3D The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going tohttps://openstack.webex.com/openstack/systemdiagnosis.php. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] A series of blog posts on OpenStack networking details
Hello, Looks nice but I look forward to read the one about VLAN manager :D Thanks! Cheer! On Fri, Aug 3, 2012 at 8:50 PM, Eugene Kirpichov ekirpic...@gmail.comwrote: Hello community, I'd like to advertise that me and my colleague Piotr Siwczak at Mirantis have started a series of blog posts explaining the gory details of OpenStack networking. http://www.mirantis.com/tag/networking/ So far we have two posts: http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/ - basics of FlatManager and FlatDHCPManager in multi-host mode. http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/ - extremely detailed account of FlatDHCPManager in single-host mode; down to a walkthrough of L2 packet flow for several scenarios. I wrote this post in revenge for my own struggles when I dreamt if only someone had described in extreme detail how it is *supposed* to work but was not able to find anything like that :) A few more will appear soon: two posts from Piotr on VLANManager, eventually also analyzing the packet flow. (me and Peter have slightly different styles: he prefers to cover details across several posts while I prefer to write a huge post with all the details at once) Comments and especially corrections are extremely welcome! [and, well, shares too :) ] -- Eugene Kirpichov http://www.linkedin.com/in/eugenekirpichov ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Quantum] Multi-host implementation
Hi folks Gary Thank you for your comment. I wanna discuss your point on the mailing list. Yusuke pushed Multi-host implementation for review. https://review.openstack.org/#/c/10766/2 This patch changes only quantum-dhcp-agent side. Gary's point is we should have host attribute on the port for scheduling. I agree with Gary. In the nova, vm has available_zone for scheduling. So Instead of using host properties. How about use available_zone for port? Format of availability_zone is something like this available_zone=zone_name:host. We can also add availability_zone attribute for the network as a default value of port. We can write this until next Monday. However I'm not sure quantum community will accept this or not, so I'm asking here. If there are no objections, we will push zone version for review. Thanks Nachi ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Quantum] Update policy of device_id
Hi folks I report this bug recently. device_id should not be updated twice https://bugs.launchpad.net/quantum/+bug/1031473 Now, a user can update device_id which may cause problem. This is related to port id spec for nova boot. https://bugs.launchpad.net/nova/+bug/1031096 My question is how we should deal with port on the failure or deletion. My patch will delete the port on failure or deletion https://review.openstack.org/#/c/10639/ Another spec could be update port device_id for None. But this is depends on how we solve bug 1031473. Any thought? -- Nachi Ueno email:nati.u...@gmail.com twitter:http://twitter.com/nati ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Quantum] Multi-host implementation
Hi folks Sorry. I added openstack-...@lists.openstack.org in this discussion. 2012/8/3 Nati Ueno nati.u...@gmail.com: Hi folks Gary Thank you for your comment. I wanna discuss your point on the mailing list. Yusuke pushed Multi-host implementation for review. https://review.openstack.org/#/c/10766/2 This patch changes only quantum-dhcp-agent side. Gary's point is we should have host attribute on the port for scheduling. I agree with Gary. In the nova, vm has available_zone for scheduling. So Instead of using host properties. How about use available_zone for port? Format of availability_zone is something like this available_zone=zone_name:host. We can also add availability_zone attribute for the network as a default value of port. We can write this until next Monday. However I'm not sure quantum community will accept this or not, so I'm asking here. If there are no objections, we will push zone version for review. Thanks Nachi ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Quantum] Update policy of device_id
Hi folks Sorry. I added openstack-...@lists.openstack.org in this discussion. 2012/8/3 Nati Ueno nati.u...@gmail.com: Hi folks I report this bug recently. device_id should not be updated twice https://bugs.launchpad.net/quantum/+bug/1031473 Now, a user can update device_id which may cause problem. This is related to port id spec for nova boot. https://bugs.launchpad.net/nova/+bug/1031096 My question is how we should deal with port on the failure or deletion. My patch will delete the port on failure or deletion https://review.openstack.org/#/c/10639/ Another spec could be update port device_id for None. But this is depends on how we solve bug 1031473. Any thought? -- Nachi Ueno email:nati.u...@gmail.com twitter:http://twitter.com/nati ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] A series of blog posts on OpenStack networking details
Hi Sean, Yes, I am :) Thanks, I'll follow the necessary procedures. On Fri, Aug 3, 2012 at 12:50 PM, Sean Dague sda...@linux.vnet.ibm.com wrote: On 08/03/2012 02:50 PM, Eugene Kirpichov wrote: Hello community, I'd like to advertise that me and my colleague Piotr Siwczak at Mirantis have started a series of blog posts explaining the gory details of OpenStack networking. http://www.mirantis.com/tag/networking/ So far we have two posts: http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/ - basics of FlatManager and FlatDHCPManager in multi-host mode. http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/ - extremely detailed account of FlatDHCPManager in single-host mode; down to a walkthrough of L2 packet flow for several scenarios. I wrote this post in revenge for my own struggles when I dreamt if only someone had described in extreme detail how it is *supposed* to work but was not able to find anything like that :) A few more will appear soon: two posts from Piotr on VLANManager, eventually also analyzing the packet flow. (me and Peter have slightly different styles: he prefers to cover details across several posts while I prefer to write a huge post with all the details at once) Comments and especially corrections are extremely welcome! [and, well, shares too :) ] Look like a great thing to add to the OpenStack Planet if you are interested. -Sean -- Sean Dague IBM Linux Technology Center email: sda...@linux.vnet.ibm.com alt-email: slda...@us.ibm.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Eugene Kirpichov http://www.linkedin.com/in/eugenekirpichov ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] A series of blog posts on OpenStack networking details
Here's the review item: https://review.openstack.org/#/c/10790/ Know anyone who's authorized to approve items in openstack-planet? On Fri, Aug 3, 2012 at 1:12 PM, Eugene Kirpichov ekirpic...@gmail.com wrote: Hi Sean, Yes, I am :) Thanks, I'll follow the necessary procedures. On Fri, Aug 3, 2012 at 12:50 PM, Sean Dague sda...@linux.vnet.ibm.com wrote: On 08/03/2012 02:50 PM, Eugene Kirpichov wrote: Hello community, I'd like to advertise that me and my colleague Piotr Siwczak at Mirantis have started a series of blog posts explaining the gory details of OpenStack networking. http://www.mirantis.com/tag/networking/ So far we have two posts: http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/ - basics of FlatManager and FlatDHCPManager in multi-host mode. http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/ - extremely detailed account of FlatDHCPManager in single-host mode; down to a walkthrough of L2 packet flow for several scenarios. I wrote this post in revenge for my own struggles when I dreamt if only someone had described in extreme detail how it is *supposed* to work but was not able to find anything like that :) A few more will appear soon: two posts from Piotr on VLANManager, eventually also analyzing the packet flow. (me and Peter have slightly different styles: he prefers to cover details across several posts while I prefer to write a huge post with all the details at once) Comments and especially corrections are extremely welcome! [and, well, shares too :) ] Look like a great thing to add to the OpenStack Planet if you are interested. -Sean -- Sean Dague IBM Linux Technology Center email: sda...@linux.vnet.ibm.com alt-email: slda...@us.ibm.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Eugene Kirpichov http://www.linkedin.com/in/eugenekirpichov -- Eugene Kirpichov http://www.linkedin.com/in/eugenekirpichov ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] keystone and ssl ?
Pierre,
In Diablo and Essex it is a common deployment pattern to serve Keystone via
SSL proxy or run Keystone as a mod_wsgi application directly. Running like
this provides connection security between the clients and the Keystone
server.
Adam Young provided a good example of doing this via Apache httpd on a blog
post of his: http://adam.younglogic.com/2012/04/keystone-httpd/
Best,
Nate
On Aug 3, 2012 5:23 AM, Pierre Amadio pierre.ama...@canonical.com wrote:
Hi there !
I have an essex install that works, and am trying now to do the same
thing but with SSL for keystone communication.
I am using Ubuntu 12.04
I followed http://docs.openstack.org/developer/keystone/configuration.html
On a remote box that will serve as my CA, i generated an auto signed
root certificate:
cd /etc/ssl
sudo /usr/lib/ssl/misc/CA.pl -newca
This generated a /etc/ssl/demoCA/cacert.pem file wich i think is to copy
on my keystone node wherever ca_certs in the config file points to. Right ?
So i have stored this file on /etc/ssl/cacert.pem
On my keystone box, i generate a certificate request:
sudo openssl req -nodes -out keystone-req.pem -new -newkey rsa:2048
-keyout cert.key -days 1095
sudo mv cert.key /etc/ssl/
sudo chmod 0600 /etc/ssl/cert.key
I send a copy of kesytone-req.pem on my CA box and sign it:
cd /etc/ssl
sudo openssl ca -policy policy_anything -out keystone-cert.crt -infiles
keystone-req.pem
I copy back the signed keystone-cert.crt file on my keystone box in
/etc/ssl/keystone-cert.crt
I add the following on /etc/keystone/kesytone.conf :
[ssl]
enable = True
certfile = /etc/ssl/keystone-cert.crt
keyfile = /etc/ssl/cert.key
ca_certs = /etc/ssl/cacert.pem
cert_required = True
From there, i was expecting to just have to restart keystone and start
using the keystone client with a https SERVICE_ENDPOINT environment
variable so i could create services, tenants, users and so on.
However, it looks to me like keystone is not even trying to negociate a
ssl handshake:
$ export SERVICE_ENDPOINT=https://192.168.122.3:35357/v2.0/
$ export SERVICE_TOKEN=whatever
$ keystone user-list
No handlers could be found for logger keystoneclient.client
Unable to communicate with identity service: [Errno 1] _ssl.c:504:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol.
(HTTP 400)
From a tcpdump:
#
...Pe...O..4..6wq}...V...
..!.9.8.5... ...
.3.2.E.D./...A..I.
.4.2... ...
...#...head
titleError response/title
/head
body
h1Error response/h1
pError code 400.
pMessage: Bad request syntax
('\x16\x03\x01\x00\xcd\x01\x00\x00\xc9\x03\x02P\x1b\x86\x7f\xaee\x03\xb9\x88O\x9b\xf9\xa6\xff\x85\xea\xe8\xf7\x9e\xe64\x8f\xc86w\xa1\xd7\xb6\xc3q}\x03\x00\x00V\xc0\x14\xc0').
pError code explanation: 400 = Bad request syntax or unsupported method.
/body
##
I do not understand what i am doing wrong, nor am i 100% sure this is
suppose to work yet.
According to the following blue print, i think it should be available in
essex:
https://blueprints.launchpad.net/keystone/+spec/2-way-ssl
At the bottom of the blueprint, there are 2 addressed by links with a
set of patches:
https://review.openstack.org/1038
https://review.openstack.org/7706
But i do not find trace of those patches in the ubuntu package
ii keystone
2012.1+stable~20120608-aff45d6-0ubuntu1 OpenStack identity service -
Daemons
ii python-keystone
2012.1+stable~20120608-aff45d6-0ubuntu1 OpenStack identity service -
Python library
ii python-keystoneclient 2012.1-0ubuntu1
Client libary for Openstack Keystone API
I also fail to find trace of those in a git checkout of the
refs/heads/stable/essex branch of keystone's git repository.
I am confused.
Any help would be appreciated.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] vlan, public IP, certain vm services ok others not
Hi All, I have an OpenStack install where the cloud controller has a public/routeable interface and a management/vm interface. I am running a single instance in a VLAN with a public/floating IP. This instance is running nginx webserver on port 80 I can ssh and ping the public IP but if I try to telnet to port 80 I get no route to host. Any idea what could be going on? I can not connect to port 80 on the either the fixed IP or floating IP from the node, or the floating IP remotely. Here is some of the information I am sure you will want to see (x.x.x.226 is the cloud controller, x.x.x.230 is the floating up of the instance): trying to connect to the various ports: http://paste2.org/p/2093635 the secgroup I included when booting the image: http://paste2.org/p/2093634 iptables on cloud controller (FILTER table): http://paste2.org/p/2093628 iptables on cloud controller (NAT table): http://paste2.org/p/2093630 listening ports on the instance: http://paste2.org/p/2093629 If you have any ideas it would be greatly appreciated. I can't imagine why ssh and ping would work, but not this. Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] vlan, public IP, certain vm services ok others not
I am so sorry. There are too many (3) firewalls involved here. I didn't realize the fedora instance had it's own firewall running that blocked port 80. Problem solved. Sorry and thanks for reading! Sam On Fri, Aug 3, 2012 at 11:36 PM, Samuel Winchenbach swinc...@gmail.com wrote: Hi All, I have an OpenStack install where the cloud controller has a public/routeable interface and a management/vm interface. I am running a single instance in a VLAN with a public/floating IP. This instance is running nginx webserver on port 80 I can ssh and ping the public IP but if I try to telnet to port 80 I get no route to host. Any idea what could be going on? I can not connect to port 80 on the either the fixed IP or floating IP from the node, or the floating IP remotely. Here is some of the information I am sure you will want to see (x.x.x.226 is the cloud controller, x.x.x.230 is the floating up of the instance): trying to connect to the various ports: http://paste2.org/p/2093635 the secgroup I included when booting the image: http://paste2.org/p/2093634 iptables on cloud controller (FILTER table): http://paste2.org/p/2093628 iptables on cloud controller (NAT table): http://paste2.org/p/2093630 listening ports on the instance: http://paste2.org/p/2093629 If you have any ideas it would be greatly appreciated. I can't imagine why ssh and ping would work, but not this. Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] how to using constraint in nova db?
soft deletes is used in nova db. but how to use uc with soft-deletes? exp: the address field of modes.VIrtualInterface is unique. Using constraints (UC, FK) is impossible. Using a unique constraint (UC) is not really possible, as the RDBMS will take into account the rows which are 'deleted' as well. So a value might be unique for the rows in the working set, but for the total set of rows in the table it doesn't have to be unique and the update or insert fails. In our example above with Customer and Order, we've seen that foreign key constraints are not really working anymore either, as they don't protect us from 'deleting' a PK side while keeping the FK side: for the RDBMS, both rows are still there and everything is fine (which is not the case) http://weblogs.asp.net/fbouma/archive/2009/02/19/soft-deletes-are-bad-m-kay.aspx ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: quantal_folsom_quantum_trunk #67
Title: quantal_folsom_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_quantum_trunk/67/Project:quantal_folsom_quantum_trunkDate of build:Fri, 03 Aug 2012 09:31:55 -0400Build duration:2 min 0 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNotification for network/subnet/port create/delete/update.by gongysheditetc/quantum.confeditquantum/tests/unit/test_api_v2.pyeditquantum/api/v2/base.pyConsole Output[...truncated 1334 lines...]Fail-Stage: apt-get-updateInstall-Time: 0Job: quantum_2012.2+git201208030932~quantal-0ubuntu1.dscPackage: quantumPackage-Time: 0Source-Version: 2012.2+git201208030932~quantal-0ubuntu1Space: 0Status: failedVersion: 2012.2+git201208030932~quantal-0ubuntu1Finished at 20120803-0933Build needed 00:00:00, 0k disc spaceE: apt-get update failedERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'quantum_2012.2+git201208030932~quantal-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.git archive master --format tar --prefix quantum-2012.2-201208030932/git archive master --format tar --prefix quantum-2012.2-201208030932/git log -n1 --no-merges --pretty=format:%Hgit log d4a7eabec0efc22c568d476b2237367d51a5025f..HEAD --no-merges --pretty=format:[%h] %sbzr branch lp:~openstack-ubuntu-testing/quantum/quantal-folsom-proposed quantumbzr merge lp:~openstack-ubuntu-testing/quantum/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208030932~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208030932~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucmk-build-deps -i -r -t apt-get -y /tmp/tmpZ_DNpR/quantum/debian/controlbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2012.2+git201208030932~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A quantum_2012.2+git201208030932~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'quantum_2012.2+git201208030932~quantal-0ubuntu1.dsc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'quantum_2012.2+git201208030932~quantal-0ubuntu1.dsc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_deploy #186
Title: precise_folsom_deploy General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/186/Project:precise_folsom_deployDate of build:Fri, 03 Aug 2012 15:16:44 -0400Build duration:13 minBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 2421 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-10.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.tar: Removing leading `/' from member names+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_nova_trunk #306
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/306/Project:precise_folsom_nova_trunkDate of build:Fri, 03 Aug 2012 21:31:54 -0400Build duration:3 min 55 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesFix broken pep8 exclude processing.by mordrededittox.iniedittools/hacking.pyRemove unused variablesby yunmaoeditnova/compute/manager.pyeditnova/compute/api.pyConsole Output[...truncated 4057 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-dd83b659-ce46-4fe3-80d7-579c30702c10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmph3q96n/novamk-build-deps -i -r -t apt-get -y /tmp/tmph3q96n/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208032133~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208032133~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-dd83b659-ce46-4fe3-80d7-579c30702c10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-dd83b659-ce46-4fe3-80d7-579c30702c10', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #307
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/307/Project:precise_folsom_nova_trunkDate of build:Fri, 03 Aug 2012 22:01:54 -0400Build duration:4 min 0 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesPartially revert Remove unused scheduler functionsby rbryanteditnova/scheduler/manager.pyConsole Output[...truncated 4057 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-12ce3244-0b7d-4af8-831c-d6a2fc1596fa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpYfttjN/novamk-build-deps -i -r -t apt-get -y /tmp/tmpYfttjN/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208032203~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208032203~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-12ce3244-0b7d-4af8-831c-d6a2fc1596fa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-12ce3244-0b7d-4af8-831c-d6a2fc1596fa', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #300
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/300/Project:quantal_folsom_nova_trunkDate of build:Sat, 04 Aug 2012 00:01:54 -0400Build duration:3 min 27 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40Changesfix unmounting of LXC containersby pbradyeditnova/virt/disk/mount.pyeditnova/tests/test_virt.pyeditnova/virt/disk/guestfs.pyeditnova/virt/disk/loop.pyeditnova/virt/libvirt/driver.pyeditnova/virt/disk/nbd.pyeditnova/virt/disk/api.pyConsole Output[...truncated 4826 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-b4d197cc-ef19-4664-b5fe-b03579475133', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpB08mE5/novamk-build-deps -i -r -t apt-get -y /tmp/tmpB08mE5/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208040003~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208040003~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-b4d197cc-ef19-4664-b5fe-b03579475133', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-b4d197cc-ef19-4664-b5fe-b03579475133', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #308
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/308/Project:precise_folsom_nova_trunkDate of build:Sat, 04 Aug 2012 00:01:55 -0400Build duration:4 min 13 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40Changesfix unmounting of LXC containersby pbradyeditnova/virt/disk/mount.pyeditnova/virt/disk/guestfs.pyeditnova/virt/disk/api.pyeditnova/virt/disk/loop.pyeditnova/tests/test_virt.pyeditnova/virt/libvirt/driver.pyeditnova/virt/disk/nbd.pyConsole Output[...truncated 4057 lines...]Applying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pyHunk #1 succeeded at 137 (offset 47 lines).Hunk #2 succeeded at 148 (offset 47 lines).Hunk #3 succeeded at 166 (offset 47 lines).Hunk #4 succeeded at 240 (offset 47 lines).Hunk #5 succeeded at 399 (offset 47 lines).patching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-2ccd92a7-19f6-4e57-96b7-15782d5411e9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpMyuJNT/novamk-build-deps -i -r -t apt-get -y /tmp/tmpMyuJNT/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208040003~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208040003~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-2ccd92a7-19f6-4e57-96b7-15782d5411e9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-2ccd92a7-19f6-4e57-96b7-15782d5411e9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
