[Openstack-doc-core] doc bugs - triaging
Hi all - How would you like to work together on doc bug triaging? I am fine with the doc-core team's judgement on any incoming bugs - the main goal is to try to keep the number of new bugs down. I also want to ensure that we have guidelines for Importance and Status. Posting to http://wiki.openstack.org/Documentation/HowTo#Doc_Bug_Triaging_Guidelinesalso so you can edit as you see fit. Status: New - Recently logged by a non-triaging person Incomplete - Needs additional information before it can be triaged Opinion - (not sure what to do with this one) Invalid - Not an issue for docs Won't Fix - Doc fixes won't fix the issue Confirmed - Acknowledged that it's a doc bug Triaged - Comments in the bug indicate its scope and amount of work to be done In Progress - Someone is working on it Fix Committed - A fix is in the repository; Gerrit sets this automatically Fix Released - A fix is published to the site; would like the CI team to set this automatically, bug filed: Importance: Critical - data will be lost if this bug stays in; or it's so bad that we're better off fixing it than dealing with all the incoming questions about it. Also items on the website itself that prevent access are Critical doc bugs. High - Definitely need docs about this or a fix to current docs; docs are incomplete without this. Work on these first if possible. Medium - Need docs about this within a six-month release timeframe. Low - Docs are fine without this but could be enhanced by fixing this bug. Wishlist - Would like this doc task done some day - would prefer to use this for tasks instead of bugs - mark a bug as low rather than putting it on the wishlist. When something is wrong with the doc, mark it as Low rather than Wishlist. Undecided - Recently logged by a non-triaging person or requires more research before deciding its importance. Please triage as you see fit with these guidelines - and please discuss the guidelines to keep us all consistent. Thanks, Anne -- Mailing list: https://launchpad.net/~openstack-doc-core Post to : openstack-doc-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-doc-core More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift][Keystone] Swift Quotas
Should you mix this into Keystone ? Seems kind of wrong to mix identity
manager with Quotas?
2012/5/4 Everett Toews everett.to...@cybera.ca
Since storing the quota data in Keystone is a prereq for do the quotas in
Swift, I'm starting there. After digging through the Keystone code a bit
I've identified at least one issue with storing the quota data per tenant
for the SQL backend.
In the metadata table both tenant_id and user_id are primary keys. So the
question is, *within the current design* how do you store some piece of
metadata per tenant only?
Storing the same quota data per user for a tenant doesn't work because of
the many-to-many relationship between users and tenants.
Another option is to use a static user_id for rows where you want to store
metadata per tenant.
e.g. user_id='per_tenant_metadata',
tenant_id='55b6d515e00e48c38e2c92d27dc5c03e', data='{quota: ...}' (I'll
figure out what the JSON looks like later)
If you retrieved the quotas via SQL it would look something like,
select data from metadata where user_id='per_tenant_metadata' and
tenant_id='55b6d515e00e48c38e2c92d27dc5c03e';
This works but doesn't feel like the cleanest solution. Any thoughts on
this approach?
Of course, stepping outside the current design would yield more options
but I wanted to look for a solution within the current design first.
Everett
On Tue, May 1, 2012 at 2:04 PM, Everett Toews everett.to...@cybera.cawrote:
Hi All,
I led the session [1] on Swift Quotas at the Summit and I'd appreciate
some feedback on the updated spec [2] and blueprint [3]. I also have a
couple of design level questions.
1. Should we store the Swift quota data in Keystone?
One of the ideas that came out of the session was that we could store the
Swift quota data in Keystone. I took a look at Keystone and it appears the
best place for this would be in the metada table but it appears to me that
it's only accessible via the User Metadata Extension API in Keystone. Is it
feasible to store the Swift quota data in Keystone this way? Should we?
On a related note, during the Pluggable Tenant Data session [4] led by
Phil Day something similar was being discussed for moving Nova quotas to
Keystone.
2. Where should the code for Swift quotas live?
It was suggested during the session that this code could live in a
middleware for Swift. Seems like a reasonable approach to me. I've taken a
look at some of the code in /swift/common/middleware and it looks
relatively straight-forward. Any thoughts or suggestions on implementing
this as middleware?
Regards,
Everett
[1] http://etherpad.openstack.org/SwiftQuotas
[2] http://wiki.openstack.org/SwiftQuotas
[3] https://blueprints.launchpad.net/swift/+spec/storage-quotas
[4] http://etherpad.openstack.org/FolsomPluggableTenantData
___
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] [Openstack-operators] Missing linuxbridge_conf.ini
Can you try downloading the package specified in the below url . http://pkgs.org/debian-wheezy/debian-main-i386/quantum-plugin-linuxbridge_2012.1-1_all.deb.html Send Install them . root@openstack:/etc/apt# find / -iname *conf.ini /etc/quantum/plugins/linuxbridge/linuxbridge_conf.ini Meena Raja Consultant __ WIPRO TECHNOLOGIES No 53/1 Ganapa Towers ,Near Madivala Police Station , Hosur Main Road ,Bangalore-560068 Hand Phone : +91-9880549725 | Desk : +91-80-39912554 |Fax No: +91-80-25502160 Email : raja.me...@wipro.com | Website : www.wipro.com From: Igor Laskovy [igor.lask...@gmail.com] Sent: Thursday, May 03, 2012 12:43 PM To: Raja Meena (WT01 - Innovation Group) Cc: openstack@lists.launchpad.net; openstack-operat...@lists.openstack.org; dun...@dreamhost.com Subject: RE: [Openstack] [Openstack-operators] Missing linuxbridge_conf.ini Nope, these packages already installed. Look like that package with Linux Bridge plugin is missing in repository or merged with another. On May 3, 2012 9:53 AM, raja.me...@wipro.commailto:raja.me...@wipro.com wrote: Hi , Make sure you have the following package(s) installed on quantum server host as well as any hosts which run the agent (-- Python library dependencies). 1. python-configobj 2. bridge-utils 3. python-mysqldb 4. sqlite3 This should solve the issue. Meena Raja Consultant __ WIPRO TECHNOLOGIES No 53/1 Ganapa Towers ,Near Madivala Police Station , Hosur Main Road ,Bangalore-560068 Hand Phone : +91-9880549725tel:%2B91-9880549725 | Desk : +91-80-39912554tel:%2B91-80-39912554 |Fax No: +91-80-25502160tel:%2B91-80-25502160 Email : raja.me...@wipro.commailto:raja.me...@wipro.com | Website : www.wipro.comhttp://www.wipro.com From: openstack-bounces+raja.meena=wipro@lists.launchpad.netmailto:wipro@lists.launchpad.net [openstack-bounces+raja.meena=wipro@lists.launchpad.netmailto:wipro@lists.launchpad.net] on behalf of Duncan McGreggor [dun...@dreamhost.commailto:dun...@dreamhost.com] Sent: Thursday, May 03, 2012 2:19 AM To: Igor Laskovy Cc: openstack-operat...@lists.openstack.orgmailto:openstack-operat...@lists.openstack.org; openstack Subject: Re: [Openstack] [Openstack-operators] Missing linuxbridge_conf.ini cc'ing openstack list On Wed, May 2, 2012 at 3:33 PM, Igor Laskovy igor.lask...@gmail.commailto:igor.lask...@gmail.com wrote: Privet all from sunny Kiev! I have playing with Quantum with Quantum Linux Bridge plugin on Ubuntu 12.04 and have installed these packages: i quantum-server i quantum-plugin-linuxbridge-agent i A quantum-common i A python-quantumclient i A python-quantum I can't find plugin configuration file linuxbridge_conf.ini . Which package provide installation of the plugin and this file? -- Igor Laskovy ___ Openstack-operators mailing list openstack-operat...@lists.openstack.orgmailto:openstack-operat...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.comhttp://www.wipro.com Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: [Openstack] Instance IP assignment problem
I think this documentation explains better like me : http://docs.openstack.org/trunk/openstack-network/admin/content/Using-dle455.html Quantum is in incubation with Essex, so it's use Nova as a client of Quantum. In the future, Quantum could be able to manage floating / fixed ips by itself. Regards Le jeudi 03 mai 2012 à 17:06 -0500, Salman Malik a écrit : Hmm... I didn't know the difference. So does it works like this: one can use the floating_range flag/fixed_range in nova. conf for putting instances in this global network by default ? and then one could create quantum network for each project and may use fixed/floating flags with this network to define private and public networks ? __ Date: Thu, 3 May 2012 23:36:36 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: soh...@cs.toronto.edu; ahal...@griddynamics.com; openstack@lists.launchpad.net With Quantum ! Le jeudi 3 mai 2012, Salman Malik salma...@live.com a écrit : I see. So where do you use private IP's in your setup ? Thanks, Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: soh...@cs.toronto.edu; ahal...@griddynamics.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 17:02:23 +0200 Hi Salman, Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit : Hi Emilien, In your configuration you have the following flags: --flat_network_bridge=br100 I'm going to try to change it in both servers. --floating_range=10.68.5.0/24 That's actually my public pool, sot it's not my fixed pool (privates IPs). After my tests, I will let you know of course. Thanks, Regards Can you please tell me why you need br100 when you are using br-int with OVS ? Secondly, you seem to use floating_range flag as the second flag. I assume that it is the pool of addresses that your instances will get IP from, right? It may be worthwhile to modify it to fixed_range because Bilal suggested here that this config worked for him. Let us know. Thanks, Salman Date: Thu, 3 May 2012 08:29:42 -0400 Subject: Re: [Openstack] Instance IP assignment problem From: soh...@cs.toronto.edu To: emilien.openst...@gmail.com CC: ahal...@griddynamics.com; openstack@lists.launchpad.net; salma...@live.com Oops accidently hit send on my phone. I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn't delivering packets. You can check it using tcpdump -e -vvv. BTW, if you are using virtualbox to run openstack, make sure you are not using vbox intel drivers. Use pcnet fast instead. OVS splinter may also be useful. Hope that helps. Cheers Soheil On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote: I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn can you find dhcp requests by using tcpdump for example ? sorry for off-topic but there may be many reasons of such issue with dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum error. I have essex on centos and was trying ubuntu vm. On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi emilien.openst...@gmail.com wrote: All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How t ___ 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] Replication implementations
On 04/05/12 04:07, Brian Waldon wrote: I think the path forward is first to gather information on what people are already doing w.r.t. replication, which you have helped trigger with this email. I'm definitely interested in seeing your solution. Once we get this information out in the open, we need to explore these existing solutions can be included with Glance. I'd prefer to go with an external tool that handles replication rather than baking it directly into the code right now, but if the work has already been done, I'm more than happy to consider it. My code is a separate tool, and I agree that's the way to go. It makes it much easier for systems integrators to tweak how it works to meet their needs, and if we find something that you can't do via the API that probably indicates a gap in the API more than anything else. I will try and make some time early next week to clean up the code enough to show it to you without you laughing at me. Mikal ___ 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] unsubscribe
unsubscribe ___ 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] BadCleaning after deleting a VM instance
Hi i have installed OS Essex and everything is working well so far, yet i have noticed a bad clean up after deleting VMs 1- My Tap interface ( vNIC comming from OpenVSwitch) is still on my bridge and it doesn't go away2- Floating IP doesn't get dissociated resulting in 500 error when i try to fetch all floating IPs I have seen a bug reported about that and fixed but the problem still persist for me and for other peoples tooCan anyone help me out here ? I am using quantum and OpenVSwitch as a pluging on ubuntu 11.04 ( It's an All in one install mode) P.S : Still trying to get a my VNC to work, i have a bad configuration ___ 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] [Metering] schema and counter definitions
Robert Collins wrote: On Fri, May 4, 2012 at 5:27 AM, Turner, Whit (Cloud Services) whit.tur...@hp.com wrote: Hi - I think a flexible aggregation scheme is needed; the levels of aggregation available should be definable in the meter independent of the sources of usage data themselves. If invoices need to be very granular down to the lowest possible level, then this drives higher data requirements all through the processing chain, including the rating engine. Traditional systems tend to pass less granular (more highly aggregated) data into the rating engine so that bill runs and invoices can be generated efficiently. At cloud-scale, this can be problematic. Given some “big data” approaches, though, this could be handled in a more granular and real-time fashion. Has anyone looked at what statsd does? It has very similar requirements (simple to use, no hard a-priori definition of things to count, a few base types to track), and needs to be horizontally scalable. Also Swift has plans to use statsd for instrumentation/monitoring, so it's definitely worth a look to see if it could be used here as well. http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3 http://etherpad.openstack.org/FolsomSwiftStatsd -- 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] [Glance] Replication implementations
Current warts: ... - maintaining amazon ec2 ids across regions requires twiddling the nova database where this mapping is stored Hi Mikal, We discussed that nova s3_images table earlier in the week on IRC. Now at the time, I wasn't fully clear on the mechanics of the glance UUID - EC2-style image ID mapping. I've had a dig into the code since then and it turns out that the EC2 image ID is effectively determined by an auto_increment column in the s3_images table. So there is nothing globally significant about that ID, in fact it's completely determined by the insertion order into the nova s3_images table, which occurs *on demand* the first time the image is being referenced in an EC2-related context (for example the first call to DescribeImages after the image has been uploaded to glance). For example in a fresh openstack deployment, if three images are uploaded with types aki, ari aki respectively, the first EC2-related reference to the images will result in the following EC2 IDs always being generated: aki-0001 ari-0002 ami-0003 Now, if the underlying glance images are migrated to another long-standing openstack deployment, it's likely that there are already multiple images referenced in the local s3_images table, so that the identifiers a[krm]i-000[1-3] are already taken. So the way things currently stand, the EC2 image ID isn't really capable of migration. I was thinking however that we should change the EC2 image generation logic, so that there is a reproducible glance UUID - EC2 mapping (with a small chance of collision). This change would allow the same EC2 ID to be generated in multiple regions for a given glance UUID (modulo collisions). Would that be helpful in your migration use-case? Cheers, Eoghan ___ 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] [QA] Aligning smoke / acceptance / promotion test efforts
+1 to this plan From the above, I would surmise that smoke tests should have all three of the following characteristics: * Test basic operations of an API, usually in a specific order that makes sense as a bare-bones use case of the API * Test only the correct action paths -- in other words, smoke tests do not throw random or invalid input at an API * Use the default client tools to complete the actions * Take a short amount of time to complete [JG] That sounds good. I wonder if we should also restrict them to be user actions only? Maybe we should also try to concentrate on actions that are likely to be available on all OpenStack installations? I am thinking things like resize are less important than VM start. However, I like the idea of testing every user facing compute CLI call using Tempest, but that scope would seem too large for a smoke test. It would be super-awesome if Tempest could be used to remove some of this duplication of efforts. [JG] +1 * Create a base test class that uses the default CLI tools instead of raw HTTP calls [JG] we need to test the default tools, so this sounds like a good plan * Create a set of Manager classes that would provide a config object and one or more client objects to test cases -- this is similar to the tempest.openstack.Manager class currently in the source code, but would allow using the default project client libraries instead of the raw HTTP client currently in Tempest * Allow test cases that derive from the base SmokeTest class to use an ordered test method system -- e.g. test_001_foo, test_002_bar [JG] I don't like order dependent tests, but I think it makes sense in this case * Have the base smoke test case class automatically annotate all of its test methods with type=smoke so that we can run all smoke tests with: nosetests --attr=type=smoke tempest I have put together some code that shows the general idea as a draft patchset [5] [JG] I would like to take this and get it running on several XenServer setups. ___ 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] Energy efficiency
Sorry, my bad.
The more free RAM is better (cost is smaller) thanks to this -1.0. So
the default behavior is spread-first indeed. To make it fill-first,
you can add flag --compute_fill_first_cost_fn_weight=1.0 to scheduler
node.
Kind regards, Yuriy.
On Thu, May 3, 2012 at 8:15 PM, Yuriy Taraday yorik@gmail.com wrote:
Fill-first cost function returns the amount of free RAM. By default it
is negated (multiplied by -1.0), so the less free RAM is better.
I think, this is a bit misguiding, but was changed right before Essex
(see https://bugs.launchpad.net/nova/+bug/965732 ).
Kind regards, Yuriy.
On Thu, May 3, 2012 at 8:05 PM, Lorin Hochstein
lo...@nimbisservices.com wrote:
Yuriy:
On May 3, 2012, at 4:46 AM, Yuriy Taraday wrote:
Just note that since Essex release Nova by default use fill-first cost
function, meaning that nodes with less free RAM will be preferred for
new instances.
Kind regards, Yuriy.
I thought the default behavior in essex was spread-first:
From:
https://github.com/openstack/nova/blob/stable/essex/nova/scheduler/least_cost.py#L41
cfg.FloatOpt('compute_fill_first_cost_fn_weight',
default=-1.0,
help='How much weight to give the fill-first cost function. '
'A negative value will reverse behavior: '
'e.g. spread-first'),
]
Take care,
Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.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
[Openstack] Openstack graphical ressources
Hello all,do you guys know who manage the graphical aspect of OPS : icons, resources, templates, etc...I'd love to have it more developed. It would be cool to provide users some resources : icons for their desktops, wallpapers, maybe skins, application icons,etc...I just wanted to have a sexy OPS wallpaper this morning, but this ain't a cool onehttp://goo.gl/nlWKqThanks,Razique Nuage Co - Razique Mahrouarazique.mahr...@gmail.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
Re: [Openstack] [Glance] Replication implementations
Current warts: ... - maintaining amazon ec2 ids across regions requires twiddling the nova database where this mapping is stored Hi Mikal, We discussed that nova s3_images table earlier in the week on IRC. Now at the time, I wasn't fully clear on the mechanics of the glance UUID - EC2-style image ID mapping. I've had a dig into the code since then and it turns out that the EC2 image ID is effectively determined by an auto_increment column in the s3_images table. So there is nothing globally significant about that ID, in fact it's completely determined by the insertion order into the nova s3_images table, which occurs *on demand* the first time the image is being referenced in an EC2-related context (for example the first call to DescribeImages after the image has been uploaded to glance). For example in a fresh openstack deployment, if three images are uploaded with types aki, ari aki respectively, the first EC2-related reference to the images will result in the following EC2 IDs always being generated: aki-0001 ari-0002 ami-0003 Now, if the underlying glance images are migrated to another long-standing openstack deployment, it's likely that there are already multiple images referenced in the local s3_images table, so that the identifiers a[krm]i-000[1-3] are already taken. So the way things currently stand, the EC2 image ID isn't really capable of migration. I was thinking however that we should change the EC2 image generation logic, so that there is a reproducible glance UUID - EC2 mapping (with a small chance of collision). This change would allow the same EC2 ID to be generated in multiple regions for a given glance UUID (modulo collisions). Would that be helpful in your migration use-case? Of course, the other way of looking at this would be to just follow the lead of EC2 itself and not provide an image ID portability across regions. Though I think we can do better than that by compressing the UUID in a predictable way. Cheers, Eoghan ___ 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] [QA] Aligning smoke / acceptance / promotion test efforts
If the approach would be to use the client tools to only smoke test the Openstack API, I would somewhat agree. I think the smoke tests should be shallow but wide, covering every API in OpenStack but not ever 'scenario'. So to me a subset of test cases would be a subset of test cases from every OpenStack API that would make a smoke suite. If the default client tools are ahead of the Tempest Rest client library with regard to API coverage, then it would make sense to use them to quickly build a smoke test suite, IMHO. The client managers should be used only to contribute to smoke tests, and not used randomly for more detailed scenario tests. I'd agree with Daryl in saying that we should avoid Tempest to smoke test or any test the client tools, rather use them to smoke test the API. The client tools should have their own tests. -Rohit From: openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net [mailto:openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net] On Behalf Of Daryl Walleck Sent: Friday, May 04, 2012 1:24 AM To: Jay Pipes Cc: openstack-qa-t...@lists.launchpad.net; openstack@lists.launchpad.net Subject: Re: [Openstack] [QA] Aligning smoke / acceptance / promotion test efforts So my first question is around this. So is the claim is that the client tools are the default interface for the applications? While that works for coders in python, what about people using other languages? Even then, there's no guarantee that the clients in different languages are implemented in the same way. Tempest was designed originally because while it does use an abstraction between the API and the tests, there is nothing to assist the user by retrying and the like. While I think there's a place for writing tests using the command line clients, to me that would be a smoke test of a client and not as much a smoke test of the API. Daryl On May 3, 2012, at 12:01 PM, Jay Pipes wrote: However, before this can happen, a number of improvements need to be made to Tempest. The issue with the smoke tests in Tempest is that they aren't really smoke tests. They do not use the default client tools (like novaclient, keystoneclient, etc) and are not annotated consistently. __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ 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] Ubuntu packaging team
Hi Paul, We are in the middle of opening quantal for openstack and still working on getting the packages building, however I will have a look at them today and will be integrating them into the packaging branches. Thanks for being patient. Regards chuck On Thu, 03 May 2012 17:15:47 -0400 Paul Belanger paul.belan...@polybeacon.com wrote: List, I'm looking for pointers on how I can get some packaging bugs closed out. I have 5 open issue[1][2][3], with 2 being new features[4][5] (dbconfig-common support for nova / glance). All have patches attached, ready for review and merging however they don't seem to be getting any traction. I'd like to offer up my packaging services to the Ubuntu packaging team, however I've not had much success or feedback. I know everybody was busy with the Essex release, but now that we are starting a new development cycle for Folsom I'd like to before more involved. Any pointers or ProTips? [1] https://bugs.launchpad.net/ubuntu/+source/glance/+bug/989205 [2] https://bugs.launchpad.net/ubuntu/+source/nova/+bug/989241 [3] https://bugs.launchpad.net/ubuntu/+source/nova/+bug/989242 [4] https://bugs.launchpad.net/ubuntu/+source/glance/+bug/953093 [5] https://bugs.launchpad.net/ubuntu/+source/nova/+bug/954915 ___ 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] Openstack graphical ressources
Hi, From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Razique Mahroua [razique.mahr...@gmail.com] Sent: Friday, May 04, 2012 4:20 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: [Openstack] Openstack graphical ressources Hello all, do you guys know who manage the graphical aspect of OPS : icons, resources, templates, etc... +1 I'd love to have it more developed. It would be cool to provide users some resources : icons for their desktops, wallpapers, maybe skins, application icons,etc... I just wanted to have a sexy OPS wallpaper this morning, but this ain't a cool one http://goo.gl/nlWKq Thanks, Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique] Even i would love to see a space on openstack.org with say (branding), which has icons, wallpapers, posters, T-Shirt designs. This will help in say am organizing an Openstack based i will go there and use the source to get stuff printed. I am making a presentation slide and i have all the icons already available, i can simply use them. Atul http://www.csscorp.com/common/email-disclaimer.php attachment: NUAGECO-LOGO-Fblan_petit.jpg___ 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] [Metering] how should it be done ? ( Was: schema and counter definitions)
On Thu, May 3, 2012 at 11:59 AM, Loic Dachary l...@enovance.com wrote: On 05/03/2012 09:58 AM, Robert Collins wrote: On Wed, May 2, 2012 at 10:28 AM, Loic Dachary l...@enovance.com wrote: As I wrote in a previous mail, once we manage to provide an implementation that proves useful, we will be in a position to approach the core OpenStack components. Integrating the metering agents as part of the core component, much in the same way it's currently done in nova. That will reduce the overall complexity of deploying OpenStack with metering (which must not be mandatory). However, there is very little chance that all components developed around OpenStack are convinced and there will always be a need for a metering that is external to the component. Therefore, even if metering eventually manages to become a first class concern for the core OpenStack components, the proposed architecture of the metering project ( per node agents when necessary and a collector harvesting them into a storage ) will keep being used for other components. Do you think I'm wrong ? We're at a very early stage and now is the time to question everything :-) I would avoid node agents as a primary interface: they can always be written to workaround components that don't provide metering themselves - like the nagios plugins example given by Andrew. node agents are more complex than implementing metering in each component because they require a handoff, parsing of local logs (or whatever relevant store the component uses), and they are another process to keep running; they probably devolve to polling, and polling is a good way to use a lot of resources up :(. The key thing I see is having a clear contract for how metering is done, so that anyone writing a new component can add metering easily. This is easier for the component author than having to write their component *and* write a metering node agent for that component. E.g. - define the signals, extension points, and python API for implementing metering in a component. - implement a no-op implementation of that metering API which discards all data. - implement a AMQP based implementation which shoves all the data out to some queue somewhere. Do you envision that writing to AMQP directly, or using the existing notification API (which seems to be a wrapper over the RPC layer, which is in turn a wrapper for AMQP)? - submit patches to existing components to add metering - and if a component owner rejects metering altogether, you can still implement a node agent to gather the data and push it out via the metering API - that will always be an option. Then we will have a situation where: - new components can meter easily - folk with different delivery constraints can change the network layer easily (drop in a different implementation of the Python API) [e.g. to log directly to a NoSQL store] I could not agree more. This way we have the best of both worlds : integration in components when possible and standalone agents when it can't be done for whatever reason. Cheers -- Loïc Dachary Chief Research Officer // eNovance labs http://labs.enovance.com // ✉ l...@enovance.com ☎ +33 1 49 70 99 82 ___ 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] [nova-scheduler] Question
Hello, I have a question about nova-scheduler. I believe that, in order to have viable values supplied to the scheduler filters, it gathers the most recent state from each of the compute host. However, i've read through the documentation and haven't found any explicit statement which confirm my suspicious. Long story short, is this the behavior of nova-scheduler? Regards, Leander ___ 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] Instance IP assignment problem
Emilien, Please see https://answers.launchpad.net/quantum/+question/194111 Nova-compute and nova-network on two different machines seems to be the key here. Solution is proposed in the above thread. Hope that helps. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Thursday, May 03, 2012 1:26 PM To: Salman Malik Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details herehttps://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf. My configurations files are herehttps://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log filehttp://paste.openstack.org/show/14775/) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). Any ideas? Thanks, Salman Date: Tue, 1 May 2012 20:43:44 +0200 Subject: Re: [Openstack] Instance IP assignment problem From: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com To: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com CC: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net; salma...@live.commailto:salma...@live.com Hi Emilien and Salman, Please, could you upload all the files, errors and conf in pastebin or something like that? I have troubles to open in phone :) Thank you El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.commailto:emilien.openst...@gmail.com escribió: Hi, I have a similar problem when I create a network per project_id
Re: [Openstack] Instance IP assignment problem
Please also see this : https://review.openstack.org/#/c/6829/ When nova-network is on remote host, dhcp requests need to go to remote server. I’ve proposed a fix above. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Thursday, May 03, 2012 2:19 PM To: Bilel Msekni Cc: salma...@live.com; openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: ski...@hotmail.frmailto:ski...@hotmail.fr CC: salma...@live.commailto:salma...@live.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details herehttps://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf. My configurations files are herehttps://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log filehttp://paste.openstack.org/show/14775/) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.commailto:emilien.openst...@gmail.com To: salma...@live.commailto:salma...@live.com CC: jorge.delac...@stackops.commailto:jorge.delac...@stackops.com; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs
Re: [Openstack] Keystone API question
Replied inline.
On Thu, May 3, 2012 at 3:23 PM, Luis Gervaso l...@woorea.es wrote:
Yes, this is the real issue.
Since /tenants is only valid for the current user (that's X-Auth-Token
dependant)
Correct.
How can an administrator user list all the tenants a user belongs to?
In the current API, I'm only aware of the opposite call:
GET /tenants/{tenant_id}/users
Another issue i've detected is that endpoints are always dependant on a
service,
may be i'm wrong but for me:
/service/{service_id}/endpoints
is more appropiate than
/endpoints
We had a brief discussion on this topic at the summit in the v.NEXT API
talk, and Joseph Heck followed up with an email on the list regarding use
cases of the service catalog:
http://www.mail-archive.com/openstack@lists.launchpad.net/msg10194.html
I think the direction of that discussion should answer your question :)
Dolph, please correct me
Luis
On Thu, May 3, 2012 at 10:12 PM, Everett Toews everett.to...@cybera.cawrote:
I get the same as Luis when trying GET /users/{user_id}/roles on
stable/essex (using devstack). Keystone spits back an
AttributeError: 'UserController' object has no attribute 'get_user_roles'
message instead of a nice 501.
GET /tenants/{tenant_id}/users/{user_id}/roles works fine. For a bit more
detail have a look at
http://docs.openstack.org/api/openstack-identity-service/2.0/content/GET_listRolesForUserOnTenant_v2.0_tenants__tenantId__users__user_id__roles_Admin_API_Service_Developer_Operations-d1e1356.html
Everett
On Thu, May 3, 2012 at 9:34 AM, Dolph Mathews dolph.math...@gmail.comwrote:
The philosophy in essex is that it's meaningless for a user to have a
role without that role being applied to a tenant, so the call that's
implemented is:
GET /tenants/{tenant_id}/users/{user_id}/roles
Calling this instead should get you an HTTP 501 stating User roles not
supported: tenant ID required.
GET /users/{user_id}/roles
Also, the term roleRefs was deprecated late in the diablo cycle
(AFAIK) in favor of roles.
-Dolph
On Wed, May 2, 2012 at 3:44 PM, Luis Gervaso l...@woorea.es wrote:
Hi,
In Diablo was:
GET /users/{user_id}/roleRefs
In Essex it is maintained for compatibility reasons. I understand that
this is the obsolete now.
I can find:
PUT DELETE /users/{user_id}/roles/OS-KSADM/{role_id}
How can get all the roles having a user_id?
GET /users/{user_id}/roles (i can't find this on stable/essex)
Returning role list with tenant associated
Another option that would work for me is:
GET /users/{user_id}/tenants
Returning tenant list with role list associated per tenant
When i GET /user/{user_id} i obtain only this info
{user: {name: admin, enabled: true, email: ad...@example.com,
id: ef1e63df85b641d7bf3c575bb8670cef, tenantId: null}}
Regards
--
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO CTO
mobile: (+34) 627983344
luis@ luis.gerv...@gmail.comwoorea.es
___
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
--
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO CTO
mobile: (+34) 627983344
luis@ luis.gerv...@gmail.comwoorea.es
___
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] Instance IP assignment problem
Thank's for your link, but I'm not sure to have to use it now. I have one server with all nova services and another with nova-compute only. Anyway, I'm going to post a new e-mail about my problem. Regards Le vendredi 04 mai 2012 à 13:14 +, Vaze, Mandar a écrit : Please also see this : https://review.openstack.org/#/c/6829/ When nova-network is on remote host, dhcp requests need to go to remote server. I’ve proposed a fix above. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Thursday, May 03, 2012 2:19 PM To: Bilel Msekni Cc: salma...@live.com; openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem All seems alright but not working yet. http://paste.openstack.org/show/14791/ I have executed on both servers : ovs-vsctl add-port br-int eth1 Need I do something else ? How the DHCP is working in this case ? Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : Then the problem isn't in the instance but in the nova-network service , please check if it is working well as well as give us the output log when you attempt to create a new instance. __ Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: ski...@hotmail.fr CC: salma...@live.com; openstack@lists.launchpad.net Date: Thu, 3 May 2012 10:21:37 +0200 Fixed IP Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : Fixed IP or Floating IP ? __ From: emilien.openst...@gmail.com To: salma...@live.com Date: Thu, 3 May 2012 09:55:31 +0200 CC: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman __ Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to
Re: [Openstack] Instance IP assignment problem
With this article, I understand I'm not alone to have this problem. I'm going to try the solution, and If it's working, I will update my documentation on Essex. Regards Le vendredi 04 mai 2012 à 13:10 +, Vaze, Mandar a écrit : Emilien, Please see https://answers.launchpad.net/quantum/+question/194111 Nova-compute and nova-network on two different machines seems to be the key here. Solution is proposed in the above thread. Hope that helps. -Mandar From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of Emilien Macchi Sent: Thursday, May 03, 2012 1:26 PM To: Salman Malik Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Instance IP assignment problem Hi, As I told you, I have also a problem for instance IP assignement. My architecture : I use Quantum with OVS plugin on 2 servers Essex-1 Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent nova-compute only. You can see more details here. My configurations files are here and in my documentation. Problem Description : When an instance is created in ESSEX-1, all is working (network). But when the VM is started on ESSEX-2, it does not get an IP address. (log file) I'm sure the problem comes from OVS connection with ESSEX-1. Do I need to configure something like a trunk or a tunnel between Essex-1 Essex-2 ? I miss something in my configuration, if you have any idea... Regards Emilien Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance. Salman __ Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:26:26 +0200 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure. Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. Here my nova.conf and I don't have any interfering DHCP server : https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf Thanks Salman __ Subject: RE: [Openstack] Instance IP assignment problem From: emilien.openst...@gmail.com To: salma...@live.com CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net Date: Tue, 1 May 2012 21:06:01 +0200 Hi Salman, I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ? What do you think about my problem (follow up to my last e-mail) ? Thanks Emilien Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : Hi, Here is the error log: http://pastebin.com/KrNZDrvD and nova.conf: http://pastebin.com/Fvd6dSZs Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches. The problem I am faced with is (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running).
[Openstack] [QA] Tempest Devstack/Jenkins gate job now passing
All, A momentous event has occurred. We now have all Tempest integration tests passing against the devstack-deployed test environment spun up in the dev-gate-tempest-devstack-vm: https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/test/?width=800height=600 Tempest is executing 157 integration tests in about 7-8 minutes on most of the service providers. We're running the job for every commit into all core projects (except Swift right now, until we add the Swift integration tests into Tempest). We're going to observe the job for stability today and tomorrow and then hopefully by next week the QA team can recommend the job to be a full merge gate on the OpenStack core projects. 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] Missing(?) keystone service catalog
Replied inline.
On Thu, May 3, 2012 at 6:08 PM, Nick Lothian nick.loth...@gmail.com wrote:
(Replying to list this time... Is there a reason why the reply-to isn't
set to the list?!)
Is this really the case? Why does service-list require the admin port?
GET /services requires admin privileges because it's really a CRUD
operation on a small portion of the service catalog equation. End users can
simply auth and get endpoints for the services they have access to.
Running against TryStack (note that I don't supply a tenant):
I'm assuming your user account has a default tenant defined in keystone...
because you don't explicitly provide a tenant, keystone can assume you want
to use your default tenant, and provide the corresponding service catalog.
Alternatively, you can call GET /tenants, select an alternative (if any),
and explicitly auth for another tenant.
$ curl -k -X 'POST' -v https://nova-api.trystack.org:5443/v2.0/tokens -d
'{aut
h:{passwordCredentials:{username: username,
password:password}}}' -H 'Content-type: application/json'
{access: {token: {expires: 2012-05-04T23:01:56.797115, id:
token, tenant: {id: tenant, name: username
}}, serviceCatalog: [{endpoints: [{adminURL:
https://nova-api.trystack.or
g:9774/v1.1/929, region: RegionOne, internalURL:
https://nova-api.trysta
ck.org:9774/v1.1/tenent, publicURL:
https://nova-api.trystack.org:9774/v1.1/929
}], type: compute, name: nova}, {endpoints: [{adminURL:
https://GL https://gl/
ANCE_API_IS_NOT_DISCLOSED/v1.1/ tenent , region: RegionOne,
internalURL: http
s://GLANCE_API_IS_NOT_DISCLOSED/v1.1/ tenent , publicURL:
https://GLANCE_API_IS_N https://glance_api_is_n/
OT_DISCLOSED/v1.1/ tenent }], type: image, name: glance},
{endpoints: [{a
dminURL: https://nova-api.trystack.org:5443/v2.0;, region:
RegionOne, int
ernalURL: https://keystone.thefreecloud.org:5000/v2.0;, publicURL:
https://
keystone.thefreecloud.org:5000/v2.0}], type: identity, name:
keystone}]
, user: {id: userid, roles: [{tenantId: tenent , id: 2,
name: Member
}], name: username}}}
On Fri, May 4, 2012 at 1:08 AM, Dolph Mathews dolph.math...@gmail.comwrote:
service-list calls the admin API (port 35357), but the auth_url you
provided was port 5000. I don't think the current keystoneclient is smart
enough to try and switch to the correct endpoint. If you have an admin
role, switching to port 35357 should work for you.
Additionally, you won't get a service catalog without also providing a
tenant, so that behavior is by design as well. Try --os_tenant_name or
--os_tenant_id if using the client, or providing tenantName or tenantId
in your auth object for curl.
-Dolph
On Wed, May 2, 2012 at 11:38 PM, Nick Lothian nick.loth...@gmail.comwrote:
I'm having some trouble using the Keystone API.
When I run
keystone --os_username=admin --os_password=password --os_auth_url=
http://192.168.1.50:5000/v2.0/ service-list
I get the following:
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)
The keystone log shows the following:
(eventlet.wsgi.server): 2012-05-03 14:03:12,840 DEBUG wsgi write
192.168.1.50 - - [03/May/2012 14:03:12] GET /v2.0/OS-KSADM/services
HTTP/1.1 404 176 0.008028
Additionally, if I use curl to call the keystone API directly (as
documented at http://keystone.openstack.org/api_curl_examples.html#id4)
my whole serviceCatalog section is empty (serviceCatalog: {})
I am using a default devstack installation.
What am I missing?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Openstack graphical ressources
Hi all - Yep, we've had that request before. Problem is, the icons are in an ai file and we haven't had the bandwidth to put them in something open and post them somewhere. Plus they need to be sliced out one-by-one from the .ai file. Anyone have Illustrator experience who wants to take on this task? They're CC licensed, we just need to get them into a better format and in separate files. Thanks, Anne On Fri, May 4, 2012 at 6:40 AM, Atul Jha atul@csscorp.com wrote: Hi, From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha= csscorp@lists.launchpad.net] on behalf of Razique Mahroua [ razique.mahr...@gmail.com] Sent: Friday, May 04, 2012 4:20 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: [Openstack] Openstack graphical ressources Hello all, do you guys know who manage the graphical aspect of OPS : icons, resources, templates, etc... +1 I'd love to have it more developed. It would be cool to provide users some resources : icons for their desktops, wallpapers, maybe skins, application icons,etc... I just wanted to have a sexy OPS wallpaper this morning, but this ain't a cool one http://goo.gl/nlWKq Thanks, Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique] Even i would love to see a space on openstack.org with say (branding), which has icons, wallpapers, posters, T-Shirt designs. This will help in say am organizing an Openstack based i will go there and use the source to get stuff printed. I am making a presentation slide and i have all the icons already available, i can simply use them. Atul http://www.csscorp.com/common/email-disclaimer.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 ___ 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] Openstack graphical ressources
Yup,I can totally do it, I used to do webdesign before being a lazy sysadmin. I still have all the resources here.How do you want me to work on that ? and where could we host the resources afterwards ?Razique Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 4 mai 2012 à 15:52, Anne Gentle a écrit :Hi all - Yep, we've had that request before. Problem is, the icons are in an ai file and we haven't had the bandwidth to put them in something open and post them somewhere. Plus they need to be sliced out one-by-one from the .ai file. Anyone have Illustrator experience who wants to take on this task? They're CC licensed, we just need to get them into a better format and in separate files. Thanks,AnneOn Fri, May 4, 2012 at 6:40 AM, Atul Jha atul@csscorp.com wrote: Hi, From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Razique Mahroua [razique.mahr...@gmail.com] Sent: Friday, May 04, 2012 4:20 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: [Openstack] Openstack graphical ressources Hello all, do you guys know who manage the graphical aspect of OPS : icons, resources, templates, etc... +1 I'd love to have it more developed. It would be cool to provide users some resources : icons for their desktops, wallpapers, maybe skins, application icons,etc... I just wanted to have a sexy OPS wallpaper this morning, but this ain't a cool one http://goo.gl/nlWKq Thanks, Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique] Even i would love to see a space on openstack.org with say (branding), which has icons, wallpapers, posters, T-Shirt designs. This will help in say am organizing an Openstack based i will go there and use the source to get stuff printed. I am making a presentation slide and i have all the icons already available, i can simply use them. Atul http://www.csscorp.com/common/email-disclaimer.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 ___ 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] [Glance][Nova] Can't list images
Hello,
I seem to be unable to list the images available in glance. I'm not sure
why this is happening. I've check the logs for nova-api, glance-api and
glance-registry and am unable to found anything out of the ordinary.
Below is an output from the command 'nova image-list'
REQ: curl -i http://192.168.164.128:5000/v2.0/tokens -X POST -H
Content-Type: application/json -H Accept: application/json -H
User-Agent: python-novaclient
REQ BODY: {auth: {tenantName: admin, passwordCredentials:
{username: admin, password: nova}}}
RESP:{'date': 'Fri, 04 May 2012 14:08:53 GMT', 'transfer-encoding':
'chunked', 'status': '200', 'vary': 'X-Auth-Token', 'content-type':
'application/json'} {access: {token: {expires:
2012-05-05T14:08:53Z, id: c6d3145f1e924982982b54e52b97bec9, tenant:
{description: null, enabled: true, id:
765a2012198f4751b8457c49932ec80d, name: admin}}, serviceCatalog:
[{endpoints: [{adminURL:
http://192.168.164.128:8776/v2/765a2012198f4751b8457c49932ec80d;,
region: nova, internalURL:
http://192.168.164.128:8776/v2/765a2012198f4751b8457c49932ec80d;,
publicURL:
http://192.168.164.128:8776/v2/765a2012198f4751b8457c49932ec80d}],
endpoints_links: [], type: volume, name: volume}, {endpoints:
[{adminURL:
http://${SWIFT_HOST}:8080/v1/AUTH_765a2012198f4751b8457c49932ec80d;,
region: nova, internalURL: http://127.0.0.1:8080;, publicURL:
http://${SWIFT_HOST}:8080/v1/AUTH_765a2012198f4751b8457c49932ec80d}],
endpoints_links: [], type: storage, name: swift}, {endpoints:
[{adminURL: http://192.168.164.128:9292/v1;, region: nova,
internalURL: http://192.168.164.128:9292/v1;, publicURL:
http://192.168.164.128:9292/v1}], endpoints_links: [], type:
image, name: glance}, {endpoints: [{adminURL:
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d;,
region: nova, internalURL:
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d;,
publicURL:
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d}],
endpoints_links: [], type: compute, name: nova}, {endpoints:
[{adminURL: http://192.168.164.128:5000/v2.0;, region: nova,
internalURL: http://192.168.164.128:5000/v2.0;, publicURL:
http://192.168.164.128:35357/v2.0}], endpoints_links: [], type:
identity, name: keystone}], user: {username: admin,
roles_links: [], id: 842c74e5daa246239426f92b6f5c5dba, roles:
[{id: d6d2f681acbf4f91a3bd3522e1c006ae, name: admin}, {id:
e1428c3c9403494494b53393660a930a, name: KeystoneServiceAdmin}, {id:
f2a9436d68974a049547c08324a37aed, name: KeystoneAdmin}], name:
admin}}}
REQ: curl -i
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d/images/detail-X
GET -H X-Auth-Project-Id: admin -H User-Agent: python-novaclient -H
Accept: application/json -H X-Auth-Token:
c6d3145f1e924982982b54e52b97bec9
REQ: curl -i
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d/images/detail-X
GET -H X-Auth-Project-Id: admin -H User-Agent: python-novaclient -H
Accept: application/json -H X-Auth-Token:
c6d3145f1e924982982b54e52b97bec9
RESP:{'date': 'Fri, 04 May 2012 14:08:53 GMT', 'status': '500',
'content-length': '128', 'content-type': 'application/json; charset=UTF-8',
'x-compute-request-id': 'req-3e953b5d-5953-438f-bd9b-20f52f2f4bf2'}
{computeFault: {message: The server has either erred or is incapable
of performing the requested operation., code: 500}}
RESP:{'date': 'Fri, 04 May 2012 14:08:53 GMT', 'status': '500',
'content-length': '128', 'content-type': 'application/json; charset=UTF-8',
'x-compute-request-id': 'req-3e953b5d-5953-438f-bd9b-20f52f2f4bf2'}
{computeFault: {message: The server has either erred or is incapable
of performing the requested operation., code: 500}}
I'm using ubuntu 12.04 with the default repository packages. All the
services are running.
Regards,
Leander
___
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] [Swift][Keystone] Swift Quotas
IMHO, if it is a quota related to a tenant or user, then managing it in Keystone makes sense. Jason -Original Message- From: openstack-bounces+jason.rouault=hp@lists.launchpad.net [mailto:openstack-bounces+jason.rouault=hp@lists.launchpad.net] On Behalf Of Eoghan Glynn Sent: Friday, May 04, 2012 3:11 AM To: Endre Karlson Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [Swift][Keystone] Swift Quotas Should you mix this into Keystone ? Seems kind of wrong to mix identity manager with Quotas? This was discussed at several sessions the design summit, so I brought it up at the keystone 'state of the nation' session to get a feel for the keystone community's disposition to the idea. There was in-principle agreement that storing such data in the keystone backend is a reasonable approach (well, no strong objections in any case). The idea is that the determining if a user is over-quota is related to authorization in the sense that it determines whether a user normally authorized to consume a resource is allowed to do so in this particular case. From an implementation point, it would also aid greatly in allowing the nova quotas infrastructure to be promoted to openstack-common and hence be reused by other projects such as glance. Cheers, Eoghan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Openstack graphical ressources
Awesome! Here's the file. I think we can just post the separate files as an attachment to a wiki page, nothing fancy needed. :) I can also post to openstack.org (I think). Let me know if you have any difficulty with the file. Anne On Fri, May 4, 2012 at 9:12 AM, Razique Mahroua razique.mahr...@gmail.comwrote: Yup, I can totally do it, I used to do webdesign before being a lazy sysadmin. I still have all the resources here. How do you want me to work on that ? and where could we host the resources afterwards ? Razique *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 4 mai 2012 à 15:52, Anne Gentle a écrit : Hi all - Yep, we've had that request before. Problem is, the icons are in an ai file and we haven't had the bandwidth to put them in something open and post them somewhere. Plus they need to be sliced out one-by-one from the .ai file. Anyone have Illustrator experience who wants to take on this task? They're CC licensed, we just need to get them into a better format and in separate files. Thanks, Anne On Fri, May 4, 2012 at 6:40 AM, Atul Jha atul@csscorp.com wrote: Hi, From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net[openstack-bounces+atul.jha= csscorp@lists.launchpad.net] on behalf of Razique Mahroua [ razique.mahr...@gmail.com] Sent: Friday, May 04, 2012 4:20 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: [Openstack] Openstack graphical ressources Hello all, do you guys know who manage the graphical aspect of OPS : icons, resources, templates, etc... +1 I'd love to have it more developed. It would be cool to provide users some resources : icons for their desktops, wallpapers, maybe skins, application icons,etc... I just wanted to have a sexy OPS wallpaper this morning, but this ain't a cool one http://goo.gl/nlWKq Thanks, Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique] Even i would love to see a space on openstack.org with say (branding), which has icons, wallpapers, posters, T-Shirt designs. This will help in say am organizing an Openstack based i will go there and use the source to get stuff printed. I am making a presentation slide and i have all the icons already available, i can simply use them. Atul http://www.csscorp.com/common/email-disclaimer.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 ___ 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] Openstack graphical ressources
Thanks I received the file, works wellI'll export the several ressources (main logo + projects icons) in several formats and sizes.Do you have any temporary server I could upload the resources to ?If not,I'll host them here on our servers and give you the URL's :) Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 4 mai 2012 à 16:20, Anne Gentle a écrit :Awesome! Here's the file. I think we can just post the separate files as an attachment to a wiki page, nothing fancy needed. :) I can also post to openstack.org (I think).Let me know if you have any difficulty with the file. AnneOn Fri, May 4, 2012 at 9:12 AM, Razique Mahroua razique.mahr...@gmail.com wrote: Yup,I can totally do it, I used to do webdesign before being a lazy sysadmin. I still have all the resources here.How do you want me to work on that ? and where could we host the resources afterwards ? Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.comNUAGECO-LOGO-Fblan_petit.jpg Le 4 mai 2012 à 15:52, Anne Gentle a écrit :Hi all - Yep, we've had that request before. Problem is, the icons are in an ai file and we haven't had the bandwidth to put them in something open and post them somewhere. Plus they need to be sliced out one-by-one from the .ai file. Anyone have Illustrator experience who wants to take on this task? They're CC licensed, we just need to get them into a better format and in separate files. Thanks,AnneOn Fri, May 4, 2012 at 6:40 AM, Atul Jha atul@csscorp.com wrote: Hi, From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Razique Mahroua [razique.mahr...@gmail.com] Sent: Friday, May 04, 2012 4:20 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: [Openstack] Openstack graphical ressources Hello all, do you guys know who manage the graphical aspect of OPS : icons, resources, templates, etc... +1 I'd love to have it more developed. It would be cool to provide users some resources : icons for their desktops, wallpapers, maybe skins, application icons,etc... I just wanted to have a sexy OPS wallpaper this morning, but this ain't a cool one http://goo.gl/nlWKq Thanks, Razique Nuage Co - Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com [cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique] Even i would love to see a space on openstack.org with say (branding), which has icons, wallpapers, posters, T-Shirt designs. This will help in say am organizing an Openstack based i will go there and use the source to get stuff printed. I am making a presentation slide and i have all the icons already available, i can simply use them. Atul http://www.csscorp.com/common/email-disclaimer.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 openstack-overview-datasheet.ai___ 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] [QA] Tempest Devstack/Jenkins gate job now passing
This is great news! Thanks Jay for all the hard work you've put into getting this up and running. Daryl On May 4, 2012, at 8:34 AM, Jay Pipes wrote: All, A momentous event has occurred. We now have all Tempest integration tests passing against the devstack-deployed test environment spun up in the dev-gate-tempest-devstack-vm: https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/test/?width=800height=600 Tempest is executing 157 integration tests in about 7-8 minutes on most of the service providers. We're running the job for every commit into all core projects (except Swift right now, until we add the Swift integration tests into Tempest). We're going to observe the job for stability today and tomorrow and then hopefully by next week the QA team can recommend the job to be a full merge gate on the OpenStack core projects. 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
[Openstack] Listing roles for a user
Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? I see this teasing option - but I can only list all roles unless I auth with the user's details... role-list List all roles, or only those granted to a user. Cheers, Kev -- Kevin Jackson @itarchitectkev ___ 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] BadCleaning after deleting a VM instance
Hi Bilel, Can you file bugs on these at https://bugs.launchpad.net/quantum and include the appropriate log files so we can see what is going on? For #1 below the nova-compute log is most valuable (do you see references to Failed while unplugging vif?). For #2, a nova-network log that includes the exception you seem to have triggered would be useful. Thanks, Dan On Fri, May 4, 2012 at 2:32 AM, Bilel Msekni ski...@hotmail.fr wrote: Hi i have installed OS Essex and everything is working well so far, yet i have noticed a bad clean up after deleting VMs 1- My Tap interface ( vNIC comming from OpenVSwitch) is still on my bridge and it doesn't go away 2- Floating IP doesn't get dissociated resulting in 500 error when i try to fetch all floating IPs I have seen a bug reported about that and fixed but the problem still persist for me and for other peoples too Can anyone help me out here ? I am using quantum and OpenVSwitch as a pluging on ubuntu 11.04 ( It's an All in one install mode) P.S : Still trying to get a my VNC to work, i have a bad configuration ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack 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
[Openstack] fake_flags + common breakout
Russell, FYI, with the flags patch, it is no longer possible to set rpc-implementation dependent flags in fake_flags. Even Rabbit has a flag in there (fake_rabbit), but Rabbit flags are currently global, so it works. That won't be true for long… We're going to have to fix this. One option is to initialize the RPC layer from fake_flags.py and then set the options. Another option, for now, might just be to push this problem into the implementations and have a global testing flag that is implementation/backend independent. This is uglier on the implementation/driver side, but cleaner on the unit tests. This is basically what 'fake_rabbit' is now, anyway. Thoughts? -- 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] fake_flags + common breakout
I added a flag in my branch which uses a flag defined in the ZeroMQ driver. This was fine before, but is a problem now, because tests/__init__.py doesn't do rpc.register_opts. Instead, it does FLAGS.register_opts(rpc.rpc_opts), which only loads the common RPC flags. Of course, the flags file *defines* the RPC driver to be used, so there would be no benefit of running rpc.register_opts until after fake_flags is loaded. The easiest solutions I see are: A. load fake_flags.py, then rpc.register_opts, then run a fake_rpc_flags.py. B. import rpc, add rpc.register_opts to fake_flags.py, then add any flags we want. C. not support testing flags on RPC drivers, have a common testing flag. -- Eric Windisch On Friday, May 4, 2012 at 6:08 PM, Russell Bryant wrote: On 05/04/2012 11:53 AM, Eric Windisch wrote: Russell, FYI, with the flags patch, it is no longer possible to set rpc-implementation dependent flags in fake_flags. Even Rabbit has a flag in there (fake_rabbit), but Rabbit flags are currently global, so it works. That won't be true for long… We're going to have to fix this. One option is to initialize the RPC layer from fake_flags.py and then set the options. Each place that fake_flags is imported, rpc gets initialized first. See these lines of code, and the fake_flags import shortly after: https://github.com/openstack/nova/blob/master/nova/tests/__init__.py#L63 https://github.com/openstack/nova/blob/master/bin/nova-dhcpbridge#L103 Another option, for now, might just be to push this problem into the implementations and have a global testing flag that is implementation/backend independent. This is uglier on the implementation/driver side, but cleaner on the unit tests. This is basically what 'fake_rabbit' is now, anyway. As far as I can tell, this isn't actually a problem with the uses of fake_flags right now. What problem did you hit? -- Russell Bryant ___ 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] fake_flags + common breakout
On 05/04/2012 12:08 PM, Russell Bryant wrote: On 05/04/2012 11:53 AM, Eric Windisch wrote: Russell, FYI, with the flags patch, it is no longer possible to set rpc-implementation dependent flags in fake_flags. Even Rabbit has a flag in there (fake_rabbit), but Rabbit flags are currently global, so it works. That won't be true for long… We're going to have to fix this. One option is to initialize the RPC layer from fake_flags.py and then set the options. Each place that fake_flags is imported, rpc gets initialized first. See these lines of code, and the fake_flags import shortly after: https://github.com/openstack/nova/blob/master/nova/tests/__init__.py#L63 https://github.com/openstack/nova/blob/master/bin/nova-dhcpbridge#L103 One other related note ... I heard some rumblings from markmc about getting all projects to standardize on a global config object from openstack.common.cfg. If that happens in nova, then we can get rid of this nova.rpc.register_opts() business completely. Another option, for now, might just be to push this problem into the implementations and have a global testing flag that is implementation/backend independent. This is uglier on the implementation/driver side, but cleaner on the unit tests. This is basically what 'fake_rabbit' is now, anyway. As far as I can tell, this isn't actually a problem with the uses of fake_flags right now. What problem did you hit? -- Russell Bryant ___ 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] [QA] Tempest Devstack/Jenkins gate job now passing
Great news indeed :) Cheers, Rohit -Original Message- From: openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net [mailto:openstack-bounces+rohit.karajgi=nttdata@lists.launchpad.net] On Behalf Of Daryl Walleck Sent: Friday, May 04, 2012 9:01 PM To: Jay Pipes Cc: openstack-qa-t...@lists.launchpad.net; openstack@lists.launchpad.net Subject: Re: [Openstack] [QA] Tempest Devstack/Jenkins gate job now passing This is great news! Thanks Jay for all the hard work you've put into getting this up and running. Daryl On May 4, 2012, at 8:34 AM, Jay Pipes wrote: All, A momentous event has occurred. We now have all Tempest integration tests passing against the devstack-deployed test environment spun up in the dev-gate-tempest-devstack-vm: https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/test/?width=800height=600 Tempest is executing 157 integration tests in about 7-8 minutes on most of the service providers. We're running the job for every commit into all core projects (except Swift right now, until we add the Swift integration tests into Tempest). We're going to observe the job for stability today and tomorrow and then hopefully by next week the QA team can recommend the job to be a full merge gate on the OpenStack core projects. 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 __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ 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] fake_flags + common breakout
On 05/04/2012 12:16 PM, Eric Windisch wrote: I added a flag in my branch which uses a flag defined in the ZeroMQ driver. This was fine before, but is a problem now, because tests/__init__.py doesn't do rpc.register_opts. Instead, it does FLAGS.register_opts(rpc.rpc_opts), which only loads the common RPC flags. Of course, the flags file *defines* the RPC driver to be used, so there would be no benefit of running rpc.register_opts until after fake_flags is loaded. The easiest solutions I see are: A. load fake_flags.py, then rpc.register_opts, then run a fake_rpc_flags.py. B. import rpc, add rpc.register_opts to fake_flags.py, then add any flags we want. C. not support testing flags on RPC drivers, have a common testing flag. I guess another question is, why do you need to set ZeroMQ related flags in fake_flags? I think those should only be settings that apply for *all* unit tests. I would just register your flags in your unit tests. https://github.com/openstack/nova/blob/master/nova/tests/rpc/test_qpid.py#L69 It's kind of a hack, but hopefully we can kill this whole register_opts() thing eventually anyway, as I mentioned in another message. -- Russell Bryant ___ 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] [QA] Tempest Devstack/Jenkins gate job now passing
++1 Wow !. yes. It is fantastic. Regards, Ravi -Original Message- From: openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net [mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net] On Behalf Of Daryl Walleck Sent: Friday, May 04, 2012 8:31 AM To: Jay Pipes Cc: openstack-qa-t...@lists.launchpad.net; openstack@lists.launchpad.net Subject: Re: [Openstack] [QA] Tempest Devstack/Jenkins gate job now passing This is great news! Thanks Jay for all the hard work you've put into getting this up and running. Daryl On May 4, 2012, at 8:34 AM, Jay Pipes wrote: All, A momentous event has occurred. We now have all Tempest integration tests passing against the devstack-deployed test environment spun up in the dev-gate-tempest-devstack-vm: https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/test/?width=800height=600 Tempest is executing 157 integration tests in about 7-8 minutes on most of the service providers. We're running the job for every commit into all core projects (except Swift right now, until we add the Swift integration tests into Tempest). We're going to observe the job for stability today and tomorrow and then hopefully by next week the QA team can recommend the job to be a full merge gate on the OpenStack core projects. 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 ___ 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] [Metering] Adding a source notion to the schema
Following up on the discussion on IRC yesterday during the metering meeting, I'd like to explain my proposal to add the notion of source to the schema of our event. The current goal we have for ceilometer is to provide a common way to accumulate counters/meters from various openstack component in a central repository that can be then used by other tools to produce bills in fine. One thing we can currently assume in Essex is that all components share a common repository for identity management: Keystone. This is the assumption we made when defining the existing schema. However, I think we need to plan a little further ahead here, and allow for this not to necessarily remain the same in some complex deployment cases. For example, it could be envisioned that some software, outside of the OpenStack project, maybe deployed and used on top of an OpenStack deployment. This software may need to be billed to customers, and collecting meters for it maybe as important for the provider than doing it for OpenStack components. It cannot be assumed that the identity management used by the software will be keystone. The software may not provide a metering interface built in, and it would make sense for the provider to be able to implement this using existing tool present in the underlying OpenStack deployment: ceilometer. In order to allow for this I think it would make sense to: * extend the current schema to allow for an additional source field in the event record. This should be a short identifier. * add another record definition that maps source to identity managment URL location * Collecting agent would be in charge to specify the source they map to (keystone by default). I think this would allow for easy extension of ceilometer to support other software, but I'd like to know if you share the usefulness of this extension from your experiences. Thanks, Nick ___ 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] [QA] Tempest Devstack/Jenkins gate job now passing
Awesome news, Jay! Big congrats to the entire QA team and others that have dedicated so much time and effort to this milestone! Cheers, Wayne Sent from my iPhone On May 4, 2012, at 8:34 AM, Jay Pipes jaypi...@gmail.com wrote: All, A momentous event has occurred. We now have all Tempest integration tests passing against the devstack-deployed test environment spun up in the dev-gate-tempest-devstack-vm: https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/test/?width=800height=600 Tempest is executing 157 integration tests in about 7-8 minutes on most of the service providers. We're running the job for every commit into all core projects (except Swift right now, until we add the Swift integration tests into Tempest). We're going to observe the job for stability today and tomorrow and then hopefully by next week the QA team can recommend the job to be a full merge gate on the OpenStack core projects. 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
[Openstack] heads up regarding keystone dev venv on an Ubuntu VM (VirtualBox)
Hey folks, We're really pressed for time right now, so there are certain rabbit holes we can't dive down, but I wanted to bring this up in case it hasn't been seen yet. On Mac OS X 10.6 and 10.7, when running a 12.04 Ubuntu VM and setting up the dev env for Keystone, we get some madness. 10.6: VirtualBox instance aborts, leaving no traces of issue in system logs (that I could see) 10.7: VB dies, OS X kernel panics The second time, I watched carefully, and it happened as python-memcached was getting installed via pip in the .venv. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up after I removed .venv and changed tools/install_venv.py to enable system site-package use. d ___ 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] Launching vpn image issue
Hello, I built cloudpipe image using base oneiric ubuntu iso and uploaded it to glance as a raw image. (glance add is_public=true disk_format=raw container_format=ovf name=cloudpipe image cloudpipeimage.img) I am trying to launch it using nova api(cloudpipe-create). It does not launch correctly. Though euca-describe-instances status says running, I cannot vnc into that vm. I see the following errors in nova-compute.log guestmount command not found error and other erros following it. (Detailed log below) I am running essex released version on oneiric. I could not find any package that has guestmount. Is there any package that I am missing? Thanks, -Vijay 2012-05-03 15:05:40 DEBUG nova.utils [req-7ae87f58-34e4-4800-b2c0-bbac606602d9 project-vpn 54dcafb79fcf4438a849bde92a432363] Unexpected error while running command. Command: sudo guestmount --rw -a /var/lib/nova/instances/instance-0004/disk -m /dev/sda1 /tmp/tmpX46A8y Exit code: 1 Stdout: '' Stderr: 'sudo: guestmount: command not found\n' from (pid=1617) trycmd /usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/utils.py:277 2012-05-03 15:05:40 DEBUG nova.utils [req-7ae87f58-34e4-4800-b2c0-bbac606602d9 project-vpn 54dcafb79fcf4438a849bde92a432363] Running cmd (subprocess): sudo fusermount -u /tmp/tmpX46A8y from (pid=1617) execute /usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/utils.py:219 2012-05-03 15:05:40 DEBUG nova.utils [req-7ae87f58-34e4-4800-b2c0-bbac606602d9 project-vpn 54dcafb79fcf4438a849bde92a432363] Result was 1 from (pid=1617) execute /usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/utils.py:235 2012-05-03 15:05:40 DEBUG nova.utils [req-7ae87f58-34e4-4800-b2c0-bbac606602d9 project-vpn 54dcafb79fcf4438a849bde92a432363] Unexpected error while running command. Command: sudo fusermount -u /tmp/tmpX46A8y Exit code: 1 Stdout: '' Stderr: 'fusermount: failed to unmount /tmp/tmpX46A8y: Invalid argument\n' from (pid=1617) trycmd /usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/utils.py:277 2012-05-03 15:05:40 DEBUG nova.virt.disk.api [req-7ae87f58-34e4-4800-b2c0-bbac606602d9 project-vpn 54dcafb79fcf4438a849bde92a432363] Failed to mount filesystem: Unexpected error while running command. Command: sudo guestmount --rw -a /var/lib/nova/instances/instance-0004/disk -m /dev/sda1 /tmp/tmpX46A8y Exit code: 1 Stdout: '' Stderr: 'sudo: guestmount: command not found\n' from (pid=1617) mount /usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/virt/disk/api.py:205 2012-05-03 15:05:40 WARNING nova.virt.libvirt.connection [req-7ae87f58-34e4-4800-b2c0-bbac606602d9 project-vpn 54dcafb79fcf4438a849bde92a432363] [instance: 242a54e8-b7b0-4517-8582-b1321376aa0a] Ignoring error injecting data into image 705ba7d3-945a-4b32-b103-8f958fc72a7a ( -- Failed to map partitions: no partitions found -- Failed to mount filesystem: Unexpected error while running command. Command: sudo guestmount --rw -a /var/lib/nova/instances/instance-0004/disk -m /dev/sda1 /tmp/tmpX46A8y Exit code: 1 Stdout: '' Stderr: 'sudo: guestmount: command not found\n') ___ 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] [QA] Tempest Devstack/Jenkins gate job now passing
+1000 On Fri, May 4, 2012 at 11:30 AM, Daryl Walleck daryl.wall...@rackspace.comwrote: This is great news! Thanks Jay for all the hard work you've put into getting this up and running. Daryl On May 4, 2012, at 8:34 AM, Jay Pipes wrote: All, A momentous event has occurred. We now have all Tempest integration tests passing against the devstack-deployed test environment spun up in the dev-gate-tempest-devstack-vm: https://jenkins.openstack.org/job/dev-gate-tempest-devstack-vm/test/?width=800height=600 Tempest is executing 157 integration tests in about 7-8 minutes on most of the service providers. We're running the job for every commit into all core projects (except Swift right now, until we add the Swift integration tests into Tempest). We're going to observe the job for stability today and tomorrow and then hopefully by next week the QA team can recommend the job to be a full merge gate on the OpenStack core projects. 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 ___ 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] fake_flags + common breakout
I guess another question is, why do you need to set ZeroMQ related flags in fake_flags? I think those should only be settings that apply for *all* unit tests. I would just register your flags in your unit tests. https://github.com/openstack/nova/blob/master/nova/tests/rpc/test_qpid.py#L69 The fake_rabbit flag doesn't, but this is otherwise a good point. For now, I've just hard-coded the flag into the test. The specific flag was to set the MatchMaker. I was forcing messages to use a Localhost matchmaker. I could override the flag from the test itself, but there might be reasons why someone would want to override this. In fact, I have overridden this to test the various matchmakers. It is also more transparent. To be honest, this specific requirement will be much lessened once I write independent tests for the matchmaker classes. However, it would also be *nice* to be able to override various settings to test them without modifying the modules or tests themselves. I'd like if I could bump up/down the number of ZeroMQ IO threads to use during tests (it defaults to 1). While modifying the test/module isn't much worse than modifying fake_flags, I find it cleaner. -- 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] Keystone API question
Hi Luis,
I'm digging around in the Keystone code right now and helping answer your
questions is helping me learn the code base. Keep 'em coming!
Anyway, from what I can tell, you're correct that there's no general way to
get all of the tenants that a user belongs to in the current high level
API. However, there is already support for exactly this feature in the
lower level API. In [1] you'll see that the Driver object has the
method get_tenants_for_user. This method is implemented in all of the
backends in [2] so there's support for it everywhere, it just hasn't been
exposed in the high level API. Looking closer at [1] we see the comment,
# NOTE(termie): seven calls below should probably be exposed by the api
# more clearly when the api redesign happens
which includes the method get_tenants_for_user. Looks like it's just a
matter of adding this method to one of the Routers to make it available in
the REST API.
My advice to you is to track down termie and find out what the story is
with the API redesign he mentions. Of course, you could always propose a
blueprint to [3] and make the method available yourself ;)
Hope this helps,
Everett
[1]
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py
[2]
https://github.com/openstack/keystone/tree/master/keystone/identity/backends
[3] https://blueprints.launchpad.net/keystone
On Thu, May 3, 2012 at 5:27 PM, Luis Gervaso l...@woorea.es wrote:
From admin port I want to list the tenants a user (different from the
current user) belongs to.
On Fri, May 4, 2012 at 1:24 AM, Gabriel Hurley
gabriel.hur...@nebula.comwrote:
On the keystone admin port the tenants call will list all tenants
(provided the token corresponds to a user who has admin privileges).
** **
**- **Gabriel
** **
*From:*
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
Behalf Of *Luis Gervaso
*Sent:* Thursday, May 03, 2012 1:24 PM
*To:* Everett Toews
*Cc:* openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Keystone API question
** **
Yes, this is the real issue.
** **
Since /tenants is only valid for the current user (that's X-Auth-Token
dependant)
** **
How can an administrator user list all the tenants a user belongs to?
** **
Another issue i've detected is that endpoints are always dependant on a
service,
may be i'm wrong but for me:
** **
/service/{service_id}/endpoints
** **
is more appropiate than
** **
/endpoints
** **
Dolph, please correct me
** **
Luis
** **
** **
On Thu, May 3, 2012 at 10:12 PM, Everett Toews everett.to...@cybera.ca
wrote:
I get the same as Luis when trying GET /users/{user_id}/roles on
stable/essex (using devstack). Keystone spits back an
** **
AttributeError: 'UserController' object has no attribute 'get_user_roles'
** **
message instead of a nice 501.
** **
GET /tenants/{tenant_id}/users/{user_id}/roles works fine. For a bit more
detail have a look at
** **
http://docs.openstack.org/api/openstack-identity-service/2.0/content/GET_listRolesForUserOnTenant_v2.0_tenants__tenantId__users__user_id__roles_Admin_API_Service_Developer_Operations-d1e1356.html
** **
Everett
** **
On Thu, May 3, 2012 at 9:34 AM, Dolph Mathews dolph.math...@gmail.com
wrote:
The philosophy in essex is that it's meaningless for a user to have a
role without that role being applied to a tenant, so the call that's
implemented is:
** **
GET /tenants/{tenant_id}/users/{user_id}/roles
** **
Calling this instead should get you an HTTP 501 stating User roles not
supported: tenant ID required.
** **
GET /users/{user_id}/roles
** **
Also, the term roleRefs was deprecated late in the diablo cycle (AFAIK)
in favor of roles.
** **
-Dolph
** **
On Wed, May 2, 2012 at 3:44 PM, Luis Gervaso l...@woorea.es wrote:
Hi,
** **
In Diablo was:
** **
GET /users/{user_id}/roleRefs
** **
In Essex it is maintained for compatibility reasons. I understand that
this is the obsolete now.
** **
I can find:
** **
PUT DELETE /users/{user_id}/roles/OS-KSADM/{role_id}
** **
How can get all the roles having a user_id?
** **
GET /users/{user_id}/roles (i can't find this on stable/essex)
** **
Returning role list with tenant associated
** **
Another option that would work for me is:
** **
GET /users/{user_id}/tenants
** **
Returning tenant list with role list associated per tenant
** **
** **
When i GET /user/{user_id} i obtain only this info
** **
{user: {name: admin, enabled: true, email: ad...@example.com,
id: ef1e63df85b641d7bf3c575bb8670cef, tenantId: null}}
** **
Regards
** **
--
Re: [Openstack] Listing roles for a user
Hi, On Fri, May 4, 2012 at 4:36 PM, Kevin Jackson ke...@linuxservices.co.uk wrote: Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? This should show up in the reply from the rest query after you auth, not sure about keystoneclient 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] heads up regarding keystone dev venv on an Ubuntu VM (VirtualBox)
Updates: * Doug Hellmann narrowed this down to the network access that was happening with pip * Mark McClain further narrowed it down to VirtualBox's networking: with a NATed interface, big probs -- with a bridged interface, things go well. I haven't taken the time to check this on my own system, since I've got a working solution right now, but when I need to rebuild, I will check. Mark also mentioned that VBox networking sometimes does some weird stuff (rewriting headers or something) and that might be contributing to the problem. Hope this helps, d On Fri, May 4, 2012 at 12:40 PM, Duncan McGreggor dun...@dreamhost.com wrote: Hey folks, We're really pressed for time right now, so there are certain rabbit holes we can't dive down, but I wanted to bring this up in case it hasn't been seen yet. On Mac OS X 10.6 and 10.7, when running a 12.04 Ubuntu VM and setting up the dev env for Keystone, we get some madness. 10.6: VirtualBox instance aborts, leaving no traces of issue in system logs (that I could see) 10.7: VB dies, OS X kernel panics The second time, I watched carefully, and it happened as python-memcached was getting installed via pip in the .venv. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up after I removed .venv and changed tools/install_venv.py to enable system site-package use. d ___ 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] fake_flags + common breakout
On 05/04/2012 12:45 PM, Eric Windisch wrote: I guess another question is, why do you need to set ZeroMQ related flags in fake_flags? I think those should only be settings that apply for *all* unit tests. I would just register your flags in your unit tests. https://github.com/openstack/nova/blob/master/nova/tests/rpc/test_qpid.py#L69 The fake_rabbit flag doesn't, but this is otherwise a good point. For now, I've just hard-coded the flag into the test. Yeah, the fake_rabbit flag used to apply to a lot more than it does now. It was applicable to all tests before nova.rpc.impl_fake was added during Essex development. -- Russell Bryant ___ 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] [Nova] EC2 api testing
At the Folsom Design Summit we discussed[1] trying to collaborate on a test suite for EC2 api support. Currently nova supports the common stuff pretty well has differing behaviour in a lot of edge cases. Having a separate suite, along the lines of tempest, that could be run against other existing clouds as well as OpenStack would let us test the tests as well, and would be useful for other projects. Various parties have done work in this direction in the past, the trick is going to be combining it into something we can all use. The existing code I know about includes aws-compat[2], Openstack-EC2[3], the tests in nova itself, some experimental code in awsome, and an Enstratus test suite. I'm hoping to find out more about the Enstratus code, James Urquhart suggested opening the remaining parts would be a reasonable step. Is there anything else out there we should look at as well? Are there any strong opinions over the right way of getting started on this? Martin [1] Nova EC2 compatibility sesson etherpad http://etherpad.openstack.org/FolsomEC2Compatibility [2] https://github.com/cloudscaling/aws-compat [3] https://github.com/yahoo/Openstack-EC2 ___ 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] [Swift][Keystone] Swift Quotas
On Fri, May 4, 2012 at 12:02 PM, Jay Pipes jaypi...@gmail.com wrote: On 05/04/2012 10:14 AM, Rouault, Jason (Cloud Services) wrote: IMHO, if it is a quota related to a tenant or user, then managing it in Keystone makes sense. I think, as Eoghan mentioned, there was pretty broad agreement that *storing* quota information and even the CRUD operations on it were appropriate for Keystone to do, but the actual enforcement of quotas should be left in individual projects. That's how I remember it, too. Doug ___ 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] questions about IP addressing and network config
I find the way to change the nova-base rule,
use the command virsh nwfilter-edit nova-base will allow to edit the xml
file,
and will take effect immediately. : )
Thanks guys for your help.
-Jimmy
2012/5/4 Jimmy Tsai cmi...@gmail.com
I tried with following tests:
1)
add firewall_driver = nova.virt.firewall.IptablesFirewallDriver to
nova.conf
restart nova-compute
Change the following lines in
/usr/share/pyshared/nova/virt/libvirt/firewall.py
self._define_filter(self._filter_container('nova-base',
['no-mac-spoofing',
'no-ip-spoofing',
'no-arp-spoofing',
'allow-dhcp-server']))
to
self._define_filter(self._filter_container('nova-base',
['allow-dhcp-server']))
then flush ebtables ruleset : ebtables -t nat -F
stop libvirt-bin start libvirt-bin
Still generate the anti-spoofing rules
2)
change the action='drop' with 'accept' to following XML files
sed -i s/action='drop'/ action='accept'/g
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml
sed -i s/action='drop'/ action='accept'/g /etc/libvirt/nwfilter/
no-arp-mac-spoofing.xml
sed -i s/action='drop'/ action='accept'/g /etc/libvirt/nwfilter/
no-ip-spoofing.xml
sed -i s/action='drop'/ action='accept'/g /etc/libvirt/nwfilter/
no-mac-broadcast.xml
sed -i s/action='drop'/ action='accept'/g /etc/libvirt/nwfilter/
no-mac-spoofing.xml
sed -i s/action='drop'/ action='accept'/g /etc/libvirt/nwfilter/
no-other-l2-traffic.xml
sed -i s/action='drop'/ action='accept'/g /etc/libvirt/nwfilter/
no-other-rarp-traffic.xml
then flush ebtables ruleset : ebtables -t nat -F
stop libvirt-bin start libvirt-bin
Okay, I can see accept rules, but the kvm processes is also gone at the
same time.
Don't know why.
still waiting for some help!!
-Jimmy
2012/5/3 Yong Sheng Gong gong...@cn.ibm.com
It seems change https://review.openstack.org/#/c/6569/ can help. Please
see how it add a new configuration item to remove some filters.
-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote:
-
To: Mike Scherbakov mih...@gmail.com mih...@gmail.com
From: Jimmy Tsai cmi...@gmail.com cmi...@gmail.com
Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
Date: 05/03/2012 01:45AM
Cc: openstack@lists.launchpad.net, jimmy.t...@104.com.tw
Subject: Re: [Openstack] questions about IP addressing and network config
Hi Mike,
I really need to bind loopback IP on my environment, I use the command
ebtables -t nat -F will flush the ebtables rule, so I can bind any IP I
wish,
but if I do stop libvirt-bin and start libvir-bin, the security rules
will be applied again,
if I remark no-ip-spoofing no-arp-spoofing on file
/etc/libvirt/nwfilter/nova-base.xml, after launching a instance, the file
will reset to default,
I think I use the wrong way, Is there any way to ignore the nova-base
rule on /usr/lib/python2.7/dist-packages/nova/virt/libvirt/firewall.py ?
Thanks for you help.
-Jimmy
2012/4/27 Mike Scherbakov mih...@gmail.com
Jimmy,
Nova is designed to manage IP addresses.
That means that even with Flat manager it will be allocating IP
addresses for you,
storing them in DB. The difference btw FlatDHCP is Flat injects
/etc/network/interfaces to the instance,
not providing IP by DHCP. So, anti-spoofing rules should be the same (I
never checked though for Flat).
If you want to provide your own addresses to instances, I believe you
will need to extend nova code
to provide your custom IP address in API request, and then if it's not
already allocated, it should get allocated.
Regards,
On Fri, Apr 27, 2012 at 3:27 PM, Jimmy Tsai cmi...@gmail.com wrote:
Thanks Vish Mike.
It works very well after flush the anti-spoofing rules , I change the
IP address and bind alias IP to an interface,
but when I restart nova-network and nova-compute , I can't ping neither
the IP I changed nor the instances I haven't changed.
I'll try to figure out what happened with that !!
Even I change the IP address, I can't not see the correct address on
Dashboard, because the record of nova.fixed_ips not changed.
I should try with FlatManager to allocate static IP.
Thanks,
-Jimmy
2012/4/27 Mike Scherbakov mih...@gmail.com
On Thu, Apr 26, 2012 at 10:31 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
On Apr 25, 2012, at 7:31 PM, Jimmy Tsai wrote:
Hi everyone,
I'm running with Essex 2012.1,
and have some questions about the nova network operation,
1. Is it possible manually assigned IP address to a launched
instance, my situation is :
after instance boot up (OS: CentOS 6.2), I changed the
/etc/sysconfig/network-scripts/ifcfg-eth0 setting
from dhcp to static (the same subnet as created by command :
nova-manage create network), and restart the network service,
And then I couldn't ssh or ping the instance
Re: [Openstack] Listing roles for a user
This actually just changed yesterday in https://github.com/openstack/python-keystoneclient/commit/e9ba370434537bcf1e53266e24397311d595b71e PRIOR to that commit: $ keystone help role-list usage: keystone role-list [--user user-id] [--tenant_id tenant-id] List all roles, or only those granted to a user. Optional arguments: --user user-id List roles granted to a user --tenant_id tenant-id List roles granted on a tenant AFTER that commit (role-list has been simplified by introducing a new command): $ keystone help user-role-list usage: keystone user-role-list [--user user-id] [--tenant_id tenant-id] List roles granted to a user Optional arguments: --user user-id List roles granted to a user --tenant_id tenant-id List roles granted on a tenant -Dolph On Fri, May 4, 2012 at 10:36 AM, Kevin Jackson ke...@linuxservices.co.ukwrote: Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? I see this teasing option - but I can only list all roles unless I auth with the user's details... role-list List all roles, or only those granted to a user. Cheers, Kev -- Kevin Jackson @itarchitectkev ___ 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 API question
Hi Everett,
I just uploaded a video showing all the issues i found:
http://youtu.be/TXw7h9Kl-Ow
As you can show, I can't drill down to roles related info from user if i
haven't selected a tenant or the user does
not have a default tenantId
From administrative tasks should be useful list tenants from userId (not
only from X-AuthToken), so I hope this to
be included in the ws api sooner or later ;)
Note : This is using OpenStack Java SDK
On Fri, May 4, 2012 at 6:51 PM, Everett Toews everett.to...@cybera.cawrote:
Hi Luis,
I'm digging around in the Keystone code right now and helping answer your
questions is helping me learn the code base. Keep 'em coming!
Anyway, from what I can tell, you're correct that there's no general way
to get all of the tenants that a user belongs to in the current high level
API. However, there is already support for exactly this feature in the
lower level API. In [1] you'll see that the Driver object has the
method get_tenants_for_user. This method is implemented in all of the
backends in [2] so there's support for it everywhere, it just hasn't been
exposed in the high level API. Looking closer at [1] we see the comment,
# NOTE(termie): seven calls below should probably be exposed by the api
# more clearly when the api redesign happens
which includes the method get_tenants_for_user. Looks like it's just a
matter of adding this method to one of the Routers to make it available in
the REST API.
My advice to you is to track down termie and find out what the story is
with the API redesign he mentions. Of course, you could always propose a
blueprint to [3] and make the method available yourself ;)
Hope this helps,
Everett
[1]
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py
[2]
https://github.com/openstack/keystone/tree/master/keystone/identity/backends
[3] https://blueprints.launchpad.net/keystone
On Thu, May 3, 2012 at 5:27 PM, Luis Gervaso l...@woorea.es wrote:
From admin port I want to list the tenants a user (different from the
current user) belongs to.
On Fri, May 4, 2012 at 1:24 AM, Gabriel Hurley gabriel.hur...@nebula.com
wrote:
On the keystone admin port the tenants call will list all tenants
(provided the token corresponds to a user who has admin privileges).
** **
**- **Gabriel
** **
*From:*
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
Behalf Of *Luis Gervaso
*Sent:* Thursday, May 03, 2012 1:24 PM
*To:* Everett Toews
*Cc:* openstack@lists.launchpad.net
*Subject:* Re: [Openstack] Keystone API question
** **
Yes, this is the real issue.
** **
Since /tenants is only valid for the current user (that's X-Auth-Token
dependant)
** **
How can an administrator user list all the tenants a user belongs to?***
*
** **
Another issue i've detected is that endpoints are always dependant on a
service,
may be i'm wrong but for me:
** **
/service/{service_id}/endpoints
** **
is more appropiate than
** **
/endpoints
** **
Dolph, please correct me
** **
Luis
** **
** **
On Thu, May 3, 2012 at 10:12 PM, Everett Toews everett.to...@cybera.ca
wrote:
I get the same as Luis when trying GET /users/{user_id}/roles on
stable/essex (using devstack). Keystone spits back an
** **
AttributeError: 'UserController' object has no attribute 'get_user_roles'
** **
message instead of a nice 501.
** **
GET /tenants/{tenant_id}/users/{user_id}/roles works fine. For a bit
more detail have a look at
** **
http://docs.openstack.org/api/openstack-identity-service/2.0/content/GET_listRolesForUserOnTenant_v2.0_tenants__tenantId__users__user_id__roles_Admin_API_Service_Developer_Operations-d1e1356.html
** **
Everett
** **
On Thu, May 3, 2012 at 9:34 AM, Dolph Mathews dolph.math...@gmail.com
wrote:
The philosophy in essex is that it's meaningless for a user to have a
role without that role being applied to a tenant, so the call that's
implemented is:
** **
GET /tenants/{tenant_id}/users/{user_id}/roles
** **
Calling this instead should get you an HTTP 501 stating User roles not
supported: tenant ID required.
** **
GET /users/{user_id}/roles
** **
Also, the term roleRefs was deprecated late in the diablo cycle
(AFAIK) in favor of roles.
** **
-Dolph
** **
On Wed, May 2, 2012 at 3:44 PM, Luis Gervaso l...@woorea.es wrote:
Hi,
** **
In Diablo was:
** **
GET /users/{user_id}/roleRefs
** **
In Essex it is maintained for compatibility reasons. I understand that
this is the obsolete now.
** **
I can find:
** **
PUT DELETE /users/{user_id}/roles/OS-KSADM/{role_id}
** **
How can get all the roles having a user_id?
** **
GET
Re: [Openstack] Listing roles for a user
keystone help role-list usage: keystone role-list [--user user-id] [--tenant_id tenant-id] List all roles, or only those granted to a user. Optional arguments: --user user-id List roles granted to a user --tenant_id tenant-id List roles granted on a tenant $ keystone tenant-list ... | bebf7c9c4d1f41d6ba6fb3ba10855b5e | demo | True| ... ubuntu@i-04b4:~$ keystone user-list ... | 906b0dc3d4464f2b88b47643f1c27297 | True| d...@example.com | demo | ... $ keystone role-list --user=906b0dc3d4464f2b88b47643f1c27297 --tenant_id=bebf7c9c4d1f41d6ba6fb3ba10855b5e ... | bbef7b9c03e84507904b352e876f28d4 | Member | | cad6d3b00ce344fbad9857a413c1f3de | anotherrole | ... The parameter --user in role-list should really be --user_id. Everett On Fri, May 4, 2012 at 9:36 AM, Kevin Jackson ke...@linuxservices.co.ukwrote: Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? I see this teasing option - but I can only list all roles unless I auth with the user's details... role-list List all roles, or only those granted to a user. Cheers, Kev -- Kevin Jackson @itarchitectkev ___ 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] [Metering] schema and counter definitions
-Original Message- From: Thierry Carrez thie...@openstack.org To: openstack@lists.launchpad.net Sent: Fri, 04 May 2012 2:50 Subject: Re: [Openstack] [Metering] schema and counter definitions Robert Collins wrote: On Fri, May 4, 2012 at 5:27 AM, Turner, Whit (Cloud Services) whit.tur...@hp.com wrote: Hi - I think a flexible aggregation scheme is needed; the levels of aggregation available should be definable in the meter independent of the sources of usage data themselves. If invoices need to be very granular down to the lowest possible level, then this drives higher data requirements all through the processing chain, including the rating engine. Traditional systems tend to pass less granular (more highly aggregated) data into the rating engine so that bill runs and invoices can be generated efficiently. At cloud-scale, this can be problematic. Given some “big data” approaches, though, this could be handled in a more granular and real-time fashion. Has anyone looked at what statsd does? It has very similar requirements (simple to use, no hard a-priori definition of things to count, a few base types to track), and needs to be horizontally scalable. Also Swift has plans to use statsd for instrumentation/monitoring, so it's definitely worth a look to see if it could be used here as well. http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3 http://etherpad.openstack.org/FolsomSwiftStatsd -- 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 ___ 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] Ubuntu packaging team
On 12-05-04 07:34 AM, Chuck Short wrote: Hi Paul, We are in the middle of opening quantal for openstack and still working on getting the packages building, however I will have a look at them today and will be integrating them into the packaging branches. Thanks for being patient. What is the best way to join the openstack packaging team? And what is the preferred method of submitting patches? Using bzr directly or creating issues in launchpad and submitting debdiffs? -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) | Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger ___ 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] Openstack graphical ressources
On 05/04/2012 07:50 AM, Razique Mahroua wrote: Thanks I received the file, works well I'll export the several ressources (main logo + projects icons) in several formats and sizes. Do you have any temporary server I could upload the resources to ? If not,I'll host them here on our servers and give you the URL's :) I think it would be better if they're on the wiki. You should able to create one and attach them there. Let me or Anne know if you need help with that. Thanks, /stef ___ 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] [Swift] swift news and plans
TL;DR: removing code from swift, associated projects doc, swift 1.5.0 I want to let the openstack community know of some recent changes within swift and how those changes will affect the next version of swift. Swift has a growing developer community and a rapidly expanding deployed base. While this growth is fantastic, it does come with new challenges, especially for the swift core developers. As more and varied use cases are presented to swift, patches are submitted that enhance swift's functionality either by offering optional features or alternative APIs. The challenge with this growth is that the core developers become responsible for understanding and maintaining an ever-increasing codebase. This responsibility becomes a timesink, both for reviews and for fixing regression bugs as new core features are added. For non-core developers, the review process for new code becomes slower, and changes that don't affect swift's core functionality often fall to the bottom of the pile--sometimes even to the point of expiring due to inactivity. Our solution for these problems is to limit the scope of swift. Swift's core functionality is to provide cheap, durable, and scalable object storage exposed through its own API. Other functionality and alternative APIs should be maintained separately from the swift codebase. As a result of this focus in scope, we have begun removing some of the optional parts of swift. Initially, this will include the tempurl, formpost, staticweb, rate limiting, swift3, domain remap, and cname lookup middleware modules. Proposed patches that offer alternative APIs (like CDMI) or include optional functionality that can be implemented external to swift will be encouraged to be developed separately from swift. We have already begun the process of removing many of these pieces of middleware from swift and moving them into their own respective repos. However, all of this functionality is quite valuable and beneficial to swift. There is a real need for most of these modules. Separating them from swift introduces the problem of discoverability. As a result, we have added a new page to our swift docs that lists associated projects and added links to that page on swift.openstack.org. http://swift.openstack.org/associated_projects.html This page is fairly limited right now, but the basic structure is there. As things are removed from swift and as new associated projects are created, they will be added to the list. This doc page is maintained in the swift codebase, so updating it is subject to the same requirements of any other patch to swift. An important note is that this list offers no distinction or references to official or approved associated projects. This list is independent of any openstack CI integration that may or may not happen in the future. Once we finish the process of migrating the optional pieces of swift away from the swift codebase, we will cut our next release: swift 1.5.0. There is no date set for this yet, but I hope the migration process can be finished in the next several weeks. Swift 1.5.0, therefore, will be somewhat larger than most of our other swift releases. Existing deployers will need to be careful about upgrading to ensure that new dependencies are met. If you have any questions, please feel free to email me. This whole effort is a work-in-progress. I know that there are several similar discussions going on within the openstack community, and swift's solution is not necessarily intended to replace any more general solution that may eventually arise. If there is a better solution at some point, we will do what we can to integrate with it. --John smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Metering] schema and counter definitions
On 05/04/2012 02:50 AM, Thierry Carrez wrote: Robert Collins wrote: On Fri, May 4, 2012 at 5:27 AM, Turner, Whit (Cloud Services) whit.tur...@hp.com wrote: Hi - I think a flexible aggregation scheme is needed; the levels of aggregation available should be definable in the meter independent of the sources of usage data themselves. If invoices need to be very granular down to the lowest possible level, then this drives higher data requirements all through the processing chain, including the rating engine. Traditional systems tend to pass less granular (more highly aggregated) data into the rating engine so that bill runs and invoices can be generated efficiently. At cloud-scale, this can be problematic. Given some “big data” approaches, though, this could be handled in a more granular and real-time fashion. Has anyone looked at what statsd does? It has very similar requirements (simple to use, no hard a-priori definition of things to count, a few base types to track), and needs to be horizontally scalable. Also Swift has plans to use statsd for instrumentation/monitoring, so it's definitely worth a look to see if it could be used here as well. http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3 http://etherpad.openstack.org/FolsomSwiftStatsd I am no Stastd expert, but a quick look at the project shows that it is aimed add data collection for the requirements of monitoring, and uses UDP as a way to aggregate vast quantity of data at short interval. The use of UDP implies that delivery is not guaranteed, which is fines for the objectives of monitoring, but is conflicting with the requirements of metering (as a sub component of a billing system). Stastd does not seem either to allow for message signature and authentication of collectors. Here are the requirements I think we have: * The data is sent from agents to the storage daemon via a trusted messaging system * The messages in queue are signed and non repudiable * The agents collecting data are authenticated to avoid pollution of the metering service Nick signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Listing roles for a user
Thanks all - that did the trick. Kev On 4 May 2012 18:39, Everett Toews everett.to...@cybera.ca wrote: keystone help role-list usage: keystone role-list [--user user-id] [--tenant_id tenant-id] List all roles, or only those granted to a user. Optional arguments: --user user-id List roles granted to a user --tenant_id tenant-id List roles granted on a tenant $ keystone tenant-list ... | bebf7c9c4d1f41d6ba6fb3ba10855b5e | demo | True| ... ubuntu@i-04b4:~$ keystone user-list ... | 906b0dc3d4464f2b88b47643f1c27297 | True| d...@example.com | demo | ... $ keystone role-list --user=906b0dc3d4464f2b88b47643f1c27297 --tenant_id=bebf7c9c4d1f41d6ba6fb3ba10855b5e ... | bbef7b9c03e84507904b352e876f28d4 | Member | | cad6d3b00ce344fbad9857a413c1f3de | anotherrole | ... The parameter --user in role-list should really be --user_id. Everett On Fri, May 4, 2012 at 9:36 AM, Kevin Jackson ke...@linuxservices.co.ukwrote: Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? I see this teasing option - but I can only list all roles unless I auth with the user's details... role-list List all roles, or only those granted to a user. Cheers, Kev -- Kevin Jackson @itarchitectkev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Kevin Jackson @itarchitectkev ___ 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] Nova subsystem branches and feature branches
Apologies for top posting. Just wanted to say +1 This all makes sense to me. Vish On May 3, 2012, at 4:08 AM, Mark McLoughlin wrote: Hey, We discussed this during the baking area for features design summit session. I found that discussion fairly frustrating because there were so many of us involved and we all were either wanting to discuss slightly different things or had a slightly different understanding of what we were discussing. So, here's my attempt to put some more structure on the discussion. tl;dr - subsystem branches are managed by trusted domain experts and feature branches are just temporary rebasing branches on personal github forks. We've got a tonne of work to do figuring out how this would all work. We should probably pick a single subsystem and start with that. ... Firstly, problem definition: - Nova is big, complex and has a fairly massive rate of churn. While the nova-core team is big, there isn't enough careful review going on by experts in particular areas and there's a consistently large backlog of reviews. - Developers working on features are very keen to have their work land somewhere and this leads to half-finished features being merged onto master rather than developers collaborating to get a feature to a level of completeness and polish before merging into master. Some assumptions about the solution: - There should be a small number of domain experts who can approve changes to each of major subsystems. This will encourage specialization and give more clear lines of responsibility. - There should be a small number of project dictators who have final approval on merge proposals, but who are not expected to review every patch in great detail. This is good because we need someone with an overall view of the project who can make sure efforts in the various subsystems are coordinated, without that someone being massively overloaded. - New features should be developed on a branch and brought to a level of completeness before being merged into master. This is good because we don't want half-baked stuff in master but also because it encourages developers to break their features into stages where each stage of the work can be brought to completion and merged before moving on to the next stage. - In essence, we're assuming some variation of the kernel distributed development model. (FWIW, my instinct is to avoid the kernel model on projects. Mostly because it's extremely complex and massive overkill for most projects. Looking at the kernel history with gitk is enough to send anyone screaming for the hills. However, Nova seems to be big enough that we're experiencing the same pressures that drove the kernel to adopt their model) Ok, what are subsystem branches and how would they work? - Subsystem branches would have a small number of maintainers who can approve a change. These would be domain experts providing strong oversight over a particular area. (In gerrit, this is a branch with a small team or single person who can +1 approve a review) - Project dictators don't need to do detailed reviews of merge proposals from subsystem maintainers. The dictator's role is mostly just to sign off on the merge proposal. However, the dictator can comment in the proposal on things which could have been done better and the subsystem maintainer should take note of these comments and perhaps retroactively fix them up. Ultimately, though, the dictator can have exercise a veto if the merge proposal is unacceptable or if the subsystem maintainer is consistently making the same mistakes. - It would be up to the project dictators to help drive patches through the right subsystem branches - e.g. they might object if one subsystem maintainer merged a patch that inappropriately cut into another subsystem or they might refuse to merge a given patch into the main branch unless it went through the appropriate subsystem branch. (In gerrit, this would mean a small team or single person who can +1 approve merge proposals on master. They would -1 proposals submitted against master which should have been submitted against a subsystem branch.) - Subsystem branches might not necessarily be blessed centrally. It might be a case that anyone can create such a branch and, over time, establish trust with the project dictators. Subsystem branches would come and go. This is the mechanism by which subsystem maintainership is transferred between people over time. (In gerrit, this means people need to easily be able to create their own branches) (What's more difficult to imagine in gerrit is how a new, potential subsystem maintainer comes along, starts hoovering up patches into her
Re: [Openstack] Listing roles for a user
On 05/04/2012 05:36 PM, Kevin Jackson wrote: Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? I see this teasing option - but I can only list all roles unless I auth with the user's details... role-list List all roles, or only those granted to a user. What about keystone role-list --user userid --tenant_id tenantid ? Here, if i launch this using the SERVICE_TOKEN environment variable to be authenticated as the admin, i see an other user's role. ___ 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] Any issue with pycurl?
unknown, but your httplib issues might be solved with from eventlet.green import httplib Vish On May 3, 2012, at 3:55 PM, Ken Thomas wrote: Hi all, We're working on a custom plugin where we make a web service call. We're having some issues with urllib2 and httplib that we're trying to track down. In the meantime, we've discovered that it all works fine if we use pycurl. If we don't suss out the problem, does anybody know if there are any interaction issues with pycurl being used in a nova plugin? Thanks! Ken ___ 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] heads up regarding keystone dev venv on an Ubuntu VM (VirtualBox)
Duncan: Are you using Vagrant? I saw a recent Vagrant update (1.0.3) that dealt with a networking issue with Ubuntu 12.04, but it was DNS-related: https://github.com/mitchellh/vagrant/commit/6f5a9d13f3afb64c3efacb7a0873226d68bba10a https://github.com/mitchellh/vagrant/commit/93d0821220dbe483bd1d129969ac18d914901bb4 Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com On May 4, 2012, at 12:59 PM, Duncan McGreggor wrote: Updates: * Doug Hellmann narrowed this down to the network access that was happening with pip * Mark McClain further narrowed it down to VirtualBox's networking: with a NATed interface, big probs -- with a bridged interface, things go well. I haven't taken the time to check this on my own system, since I've got a working solution right now, but when I need to rebuild, I will check. Mark also mentioned that VBox networking sometimes does some weird stuff (rewriting headers or something) and that might be contributing to the problem. Hope this helps, d On Fri, May 4, 2012 at 12:40 PM, Duncan McGreggor dun...@dreamhost.com wrote: Hey folks, We're really pressed for time right now, so there are certain rabbit holes we can't dive down, but I wanted to bring this up in case it hasn't been seen yet. On Mac OS X 10.6 and 10.7, when running a 12.04 Ubuntu VM and setting up the dev env for Keystone, we get some madness. 10.6: VirtualBox instance aborts, leaving no traces of issue in system logs (that I could see) 10.7: VB dies, OS X kernel panics The second time, I watched carefully, and it happened as python-memcached was getting installed via pip in the .venv. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up after I removed .venv and changed tools/install_venv.py to enable system site-package use. d ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Questions on VM Lifecycle
On May 3, 2012, at 4:50 PM, Mark Moseley wrote: * What is the right way to stop/start a persistent instance? So far I've been using 'nova boot' to start and 'nova delete' to stop. E.g.: nova boot --flavor=1 --image c5cecc17-295c-4ebc-9019-2ccc222d3f52 --key_name=key3 --nic net-id=63743ee0-f8a1-45f8-888a-cce38d09cca2,v4-fixed-ip=192.168.1.2 --block_device_mapping vda=11 --block_device_mapping vdb=12 --nic=net-id=63743ee0-f8a1-45f8-888a-cce38d09cca2 myvm1 You might try nova suspend/resume (does a hypervisor-level suspend where all memory is written to disk and the vm is stopped) or nova pause/unpause (stops emulation of the vm or api.openstack.org -- stop/start (this one is not exposed to novaclient, but it will shutdown the instance but not delete any files) * Not really a question, but if I'm using persistent storage, it'd be nice if I didn't have to specify --image, since I'm not actually using the image. the image should only be necessary for the initial boot * Is there a way to add an interface, but without Nova trying to configure it? That is, add an eth1 to the vm but do nothing else (yes, I realize I'll have to muck with ebtables/iptables on the compute node). Our imaging process will take care of the network configuration, so it'd be one less thing to add to Nova's management overhead. I can probably accomplish the same thing with a dummy network on the VM's eth1, since it's not actually being injected. not now * Any plans to add a mac= subarg to the --nic option in 'nova boot'? this was discussed at some point, but no active development that i know of ___ 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] heads up regarding keystone dev venv on an Ubuntu VM (VirtualBox)
Nope, sadly :-( Straight-up VirtualBox is where we were having troubles. (Although Mark is using Vagrant for some other stuff). d On Fri, May 4, 2012 at 4:24 PM, Lorin Hochstein lo...@nimbisservices.com wrote: Duncan: Are you using Vagrant? I saw a recent Vagrant update (1.0.3) that dealt with a networking issue with Ubuntu 12.04, but it was DNS-related: https://github.com/mitchellh/vagrant/commit/6f5a9d13f3afb64c3efacb7a0873226d68bba10a https://github.com/mitchellh/vagrant/commit/93d0821220dbe483bd1d129969ac18d914901bb4 Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com On May 4, 2012, at 12:59 PM, Duncan McGreggor wrote: Updates: * Doug Hellmann narrowed this down to the network access that was happening with pip * Mark McClain further narrowed it down to VirtualBox's networking: with a NATed interface, big probs -- with a bridged interface, things go well. I haven't taken the time to check this on my own system, since I've got a working solution right now, but when I need to rebuild, I will check. Mark also mentioned that VBox networking sometimes does some weird stuff (rewriting headers or something) and that might be contributing to the problem. Hope this helps, d On Fri, May 4, 2012 at 12:40 PM, Duncan McGreggor dun...@dreamhost.com wrote: Hey folks, We're really pressed for time right now, so there are certain rabbit holes we can't dive down, but I wanted to bring this up in case it hasn't been seen yet. On Mac OS X 10.6 and 10.7, when running a 12.04 Ubuntu VM and setting up the dev env for Keystone, we get some madness. 10.6: VirtualBox instance aborts, leaving no traces of issue in system logs (that I could see) 10.7: VB dies, OS X kernel panics The second time, I watched carefully, and it happened as python-memcached was getting installed via pip in the .venv. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up after I removed .venv and changed tools/install_venv.py to enable system site-package use. d ___ 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] Questions on VM Lifecycle
On Fri, May 4, 2012 at 1:34 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: On May 3, 2012, at 4:50 PM, Mark Moseley wrote: * What is the right way to stop/start a persistent instance? So far I've been using 'nova boot' to start and 'nova delete' to stop. E.g.: nova boot --flavor=1 --image c5cecc17-295c-4ebc-9019-2ccc222d3f52 --key_name=key3 --nic net-id=63743ee0-f8a1-45f8-888a-cce38d09cca2,v4-fixed-ip=192.168.1.2 --block_device_mapping vda=11 --block_device_mapping vdb=12 --nic=net-id=63743ee0-f8a1-45f8-888a-cce38d09cca2 myvm1 You might try nova suspend/resume (does a hypervisor-level suspend where all memory is written to disk and the vm is stopped) or nova pause/unpause (stops emulation of the vm or api.openstack.org -- stop/start (this one is not exposed to novaclient, but it will shutdown the instance but not delete any files) Yup, suspend/resume are exactly what I was looking for. I would've put money down that I'd tried suspend and it'd left the kvm running. I must've been trying pause/unpause (or just confusing it with virsh suspend, which basically pauses the vm but leaves the process running). * Not really a question, but if I'm using persistent storage, it'd be nice if I didn't have to specify --image, since I'm not actually using the image. the image should only be necessary for the initial boot Hmm, I forget if it was saying this before, but when I try to boot without --image (using the same nova boot invocation as above, but without the --image image uuid part), I get: ERROR: 'NoneType' object has no attribute 'isdigit' I can dig into it more if it'd be helpful (opengrok has been amazingly useful for working with nova source code). Though in light of your and Mandar's suggestion to use 'nova suspend/resume', I shouldn't be reusing 'nova boot' anyway, so I guess it's moot. * Is there a way to add an interface, but without Nova trying to configure it? That is, add an eth1 to the vm but do nothing else (yes, I realize I'll have to muck with ebtables/iptables on the compute node). Our imaging process will take care of the network configuration, so it'd be one less thing to add to Nova's management overhead. I can probably accomplish the same thing with a dummy network on the VM's eth1, since it's not actually being injected. not now Ok, good to know I'm not just overlooking something. Having the ability to attach unconfigured-but-present devices, even beyond NICs, might be useful. * Any plans to add a mac= subarg to the --nic option in 'nova boot'? this was discussed at some point, but no active development that i know of Ok, also good to know. Maybe I'll muck with it -- though my python is just barely passable, so it'd be a rough first cut at best. I also figured out my IP reuse issue: I added to /etc/nova/nova.conf --fixed_ip_disassociate_timeout=1. Any nasty side effects of setting that? ___ 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] [Metering] how should it be done ? ( Was: schema and counter definitions)
On Fri, May 4, 2012 at 4:51 PM, Christopher MacGown ch...@pistoncloud.comwrote: Do you envision that writing to AMQP directly, or using the existing notification API (which seems to be a wrapper over the RPC layer, which is in turn a wrapper for AMQP)? The RPC layer is not merely a wrapper for AMQP, in addition to Kombu and QPid it also supports brokered 0mq. Sorry, I didn't mean to imply that it was only for AMQP. I just meant that instead of talking directly to AMQP, it would probably be better to use one of those wrapper layers that handles the other messaging systems so that deployers have as much flexibility as possible. -- Christopher MacGown, CTO Piston Cloud Computing, Inc. w: (650) 24-CLOUD m: (415) 300-0944 http://www.pistoncloud.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
Re: [Openstack] [Metering] Adding a source notion to the schema
On Fri, May 4, 2012 at 12:29 PM, Nick Barcet nick.bar...@canonical.comwrote: Following up on the discussion on IRC yesterday during the metering meeting, I'd like to explain my proposal to add the notion of source to the schema of our event. The current goal we have for ceilometer is to provide a common way to accumulate counters/meters from various openstack component in a central repository that can be then used by other tools to produce bills in fine. One thing we can currently assume in Essex is that all components share a common repository for identity management: Keystone. This is the assumption we made when defining the existing schema. However, I think we need to plan a little further ahead here, and allow for this not to necessarily remain the same in some complex deployment cases. For example, it could be envisioned that some software, outside of the OpenStack project, maybe deployed and used on top of an OpenStack deployment. This software may need to be billed to customers, and collecting meters for it maybe as important for the provider than doing it for OpenStack components. It cannot be assumed that the identity management used by the software will be keystone. The software may not provide a metering interface built in, and it would make sense for the provider to be able to implement this using existing tool present in the underlying OpenStack deployment: ceilometer. In order to allow for this I think it would make sense to: * extend the current schema to allow for an additional source field in the event record. This should be a short identifier. That makes sense. It seems like the identifier(s) used are meant to be defined by the deployer. Is that your intent? * add another record definition that maps source to identity managment URL location * Collecting agent would be in charge to specify the source they map to (keystone by default). It is not clear why the identity management location needs to be recorded in ceilometer. If the deployer controls the source strings, they know what each value means. The only thing that needs to translate the (source, project, user) values to a billing identity is the end-consumer of all of this data, which is also under the control of the deployer. Couldn't the mapping of the source token to the identity location be handled in that layer? I think this would allow for easy extension of ceilometer to support other software, but I'd like to know if you share the usefulness of this extension from your experiences. Thanks, Nick ___ 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] Listing roles for a user
Hi Dolph, Just out of curiosity, why is the argument --user instead of --user-id? Seems like it would be more informative and consistent if it was --user_id. I actually wound up filing a bug for this at https://bugs.launchpad.net/keystone/+bug/994744 Everett On Fri, May 4, 2012 at 11:36 AM, Dolph Mathews dolph.math...@gmail.comwrote: This actually just changed yesterday in https://github.com/openstack/python-keystoneclient/commit/e9ba370434537bcf1e53266e24397311d595b71e PRIOR to that commit: $ keystone help role-list usage: keystone role-list [--user user-id] [--tenant_id tenant-id] List all roles, or only those granted to a user. Optional arguments: --user user-id List roles granted to a user --tenant_id tenant-id List roles granted on a tenant AFTER that commit (role-list has been simplified by introducing a new command): $ keystone help user-role-list usage: keystone user-role-list [--user user-id] [--tenant_id tenant-id] List roles granted to a user Optional arguments: --user user-id List roles granted to a user --tenant_id tenant-id List roles granted on a tenant -Dolph On Fri, May 4, 2012 at 10:36 AM, Kevin Jackson ke...@linuxservices.co.ukwrote: Hello everyone, Quick Q: As an administrator how can I list the roles for a given user with the keystone client? I see this teasing option - but I can only list all roles unless I auth with the user's details... role-list List all roles, or only those granted to a user. Cheers, Kev -- Kevin Jackson @itarchitectkev ___ 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] [Doc] Folsom blueprints for openstack-manuals
Hi all - I'm working on blueprints for openstack-manuals for the Folsom release. Here's what I'm going to register: 1. Operations manual - outline at http://etherpad.openstack.org/EssexOperationsGuide 2. Template for detailed configuration info for known deployments such as TryStack and Mediawiki, others who are interested like MercadoLibre (if you're interested, let me know) 3. Enable quicker edits - this is related to a CI team blueprint, https://blueprints.launchpad.net/openstack-ci/+spec/ci-doc-automation 4. Try-it-out on http://api.openstack.org 5. Content sharing for API guides ( https://blueprints.launchpad.net/openstack-manuals/+spec/design-content-sharing ) If you have other blueprints you'd like to get in to the Folsom release, let me know, or register them at http://blueprints.launchpad.net/openstack-manuals. I'll get more details into these next week, but wanted to get the ball rolling for thoughts on the top doc goals for this release. We'll also discuss at the next Doc Team meeting May 14th. Thanks, Anne ___ 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] [Metering] Adding a source notion to the schema
On 05/04/2012 02:25 PM, Doug Hellmann wrote: On Fri, May 4, 2012 at 12:29 PM, Nick Barcet nick.bar...@canonical.com mailto:nick.bar...@canonical.com wrote: Following up on the discussion on IRC yesterday during the metering meeting, I'd like to explain my proposal to add the notion of source to the schema of our event. The current goal we have for ceilometer is to provide a common way to accumulate counters/meters from various openstack component in a central repository that can be then used by other tools to produce bills in fine. One thing we can currently assume in Essex is that all components share a common repository for identity management: Keystone. This is the assumption we made when defining the existing schema. However, I think we need to plan a little further ahead here, and allow for this not to necessarily remain the same in some complex deployment cases. For example, it could be envisioned that some software, outside of the OpenStack project, maybe deployed and used on top of an OpenStack deployment. This software may need to be billed to customers, and collecting meters for it maybe as important for the provider than doing it for OpenStack components. It cannot be assumed that the identity management used by the software will be keystone. The software may not provide a metering interface built in, and it would make sense for the provider to be able to implement this using existing tool present in the underlying OpenStack deployment: ceilometer. In order to allow for this I think it would make sense to: * extend the current schema to allow for an additional source field in the event record. This should be a short identifier. That makes sense. It seems like the identifier(s) used are meant to be defined by the deployer. Is that your intent? Correct. We'll just need a sane default for Keystone. * add another record definition that maps source to identity managment URL location * Collecting agent would be in charge to specify the source they map to (keystone by default). It is not clear why the identity management location needs to be recorded in ceilometer. If the deployer controls the source strings, they know what each value means. The only thing that needs to translate the (source, project, user) values to a billing identity is the end-consumer of all of this data, which is also under the control of the deployer. Couldn't the mapping of the source token to the identity location be handled in that layer? True. It might be over-engineering to try to keep the info in the same place as well, but the impact on the system would be negligible. I'd be happy either ways :) Nick signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Nova] EC2 api testing
On Fri, May 4, 2012 at 1:09 PM, Martin Packman martin.pack...@canonical.com wrote: At the Folsom Design Summit we discussed[1] trying to collaborate on a test suite for EC2 api support. Currently nova supports the common stuff pretty well has differing behaviour in a lot of edge cases. Having a separate suite, along the lines of tempest, that could be run against other existing clouds as well as OpenStack would let us test the tests as well, and would be useful for other projects. Various parties have done work in this direction in the past, the trick is going to be combining it into something we can all use. The existing code I know about includes aws-compat[2], Openstack-EC2[3], the tests in nova itself, some experimental code in awsome, and an Enstratus test suite. I'm hoping to find out more about the Enstratus code, James Urquhart suggested opening the remaining parts would be a reasonable step. Is there anything else out there we should look at as well? Are there any strong opinions over the right way of getting started on this? Are you going to try to get all of the code for those projects into one package, or build a meta-tool that downloads the others and uses them? I don't have an opinion one way or the other, I'm just curious. Doug Martin [1] Nova EC2 compatibility sesson etherpad http://etherpad.openstack.org/FolsomEC2Compatibility [2] https://github.com/cloudscaling/aws-compat [3] https://github.com/yahoo/Openstack-EC2 ___ 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] [Metering] Adding a source notion to the schema
On Fri, May 4, 2012 at 6:03 PM, Nick Barcet nick.bar...@canonical.comwrote: On 05/04/2012 02:25 PM, Doug Hellmann wrote: On Fri, May 4, 2012 at 12:29 PM, Nick Barcet nick.bar...@canonical.com mailto:nick.bar...@canonical.com wrote: Following up on the discussion on IRC yesterday during the metering meeting, I'd like to explain my proposal to add the notion of source to the schema of our event. The current goal we have for ceilometer is to provide a common way to accumulate counters/meters from various openstack component in a central repository that can be then used by other tools to produce bills in fine. One thing we can currently assume in Essex is that all components share a common repository for identity management: Keystone. This is the assumption we made when defining the existing schema. However, I think we need to plan a little further ahead here, and allow for this not to necessarily remain the same in some complex deployment cases. For example, it could be envisioned that some software, outside of the OpenStack project, maybe deployed and used on top of an OpenStack deployment. This software may need to be billed to customers, and collecting meters for it maybe as important for the provider than doing it for OpenStack components. It cannot be assumed that the identity management used by the software will be keystone. The software may not provide a metering interface built in, and it would make sense for the provider to be able to implement this using existing tool present in the underlying OpenStack deployment: ceilometer. In order to allow for this I think it would make sense to: * extend the current schema to allow for an additional source field in the event record. This should be a short identifier. That makes sense. It seems like the identifier(s) used are meant to be defined by the deployer. Is that your intent? Correct. We'll just need a sane default for Keystone. You're focusing on source as the origin for the identity information, but it seems like a layer sitting on top of OpenStack may well use Keystone for identity but generate different billable events. Should source be the origin of the metric data being sent to ceilometer? * add another record definition that maps source to identity managment URL location * Collecting agent would be in charge to specify the source they map to (keystone by default). It is not clear why the identity management location needs to be recorded in ceilometer. If the deployer controls the source strings, they know what each value means. The only thing that needs to translate the (source, project, user) values to a billing identity is the end-consumer of all of this data, which is also under the control of the deployer. Couldn't the mapping of the source token to the identity location be handled in that layer? True. It might be over-engineering to try to keep the info in the same place as well, but the impact on the system would be negligible. I'd be happy either ways :) It will be easier to add it later if we really need it than to take it out if we decide we don't. Doug ___ 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] [Metering] schema and counter definitions
On 05/04/2012 11:50 AM, Thierry Carrez wrote: Robert Collins wrote: On Fri, May 4, 2012 at 5:27 AM, Turner, Whit (Cloud Services) whit.tur...@hp.com wrote: Hi - I think a flexible aggregation scheme is needed; the levels of aggregation available should be definable in the meter independent of the sources of usage data themselves. If invoices need to be very granular down to the lowest possible level, then this drives higher data requirements all through the processing chain, including the rating engine. Traditional systems tend to pass less granular (more highly aggregated) data into the rating engine so that bill runs and invoices can be generated efficiently. At cloud-scale, this can be problematic. Given some “big data” approaches, though, this could be handled in a more granular and real-time fashion. Has anyone looked at what statsd does? It has very similar requirements (simple to use, no hard a-priori definition of things to count, a few base types to track), and needs to be horizontally scalable. Also Swift has plans to use statsd for instrumentation/monitoring, so it's definitely worth a look to see if it could be used here as well. http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3 http://etherpad.openstack.org/FolsomSwiftStatsd Thanks :-) Just saved the etherpad as http://etherpad.openstack.org/ep/pad/view/FolsomSwiftStatsd/9cy8Uxtp2U in case it is vandalized. Cheers -- Loïc Dachary Chief Research Officer // eNovance labs http://labs.enovance.com // ✉ l...@enovance.com ☎ +33 1 49 70 99 82 ___ 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] [nova-scheduler] Question
Yes. By default, once in two minutes host's capabilities are refreshed in nova-scheduler. These capabilities are then used along with data from DB to form current host capabilities. After that, resources used by each instance on the host are subtracted from it. The result containing the actual amounts for free resources is then passed to filters and cost functions. Kind regards, Yuriy. On Fri, May 4, 2012 at 5:01 PM, Leander Bessa leande...@gmail.com wrote: Hello, I have a question about nova-scheduler. I believe that, in order to have viable values supplied to the scheduler filters, it gathers the most recent state from each of the compute host. However, i've read through the documentation and haven't found any explicit statement which confirm my suspicious. Long story short, is this the behavior of nova-scheduler? Regards, Leander ___ 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] [Glance][Nova] Can't list images
Please post to http://paste.openstack.org error text and backtrace
from nova-api.log.
Kind regards, Yuriy.
On Fri, May 4, 2012 at 6:13 PM, Leander Bessa leande...@gmail.com wrote:
Hello,
I seem to be unable to list the images available in glance. I'm not sure why
this is happening. I've check the logs for nova-api, glance-api and
glance-registry and am unable to found anything out of the ordinary.
Below is an output from the command 'nova image-list'
REQ: curl -i http://192.168.164.128:5000/v2.0/tokens -X POST -H
Content-Type: application/json -H Accept: application/json -H
User-Agent: python-novaclient
REQ BODY: {auth: {tenantName: admin, passwordCredentials:
{username: admin, password: nova}}}
RESP:{'date': 'Fri, 04 May 2012 14:08:53 GMT', 'transfer-encoding':
'chunked', 'status': '200', 'vary': 'X-Auth-Token', 'content-type':
'application/json'} {access: {token: {expires: 2012-05-05T14:08:53Z,
id: c6d3145f1e924982982b54e52b97bec9, tenant: {description: null,
enabled: true, id: 765a2012198f4751b8457c49932ec80d, name:
admin}}, serviceCatalog: [{endpoints: [{adminURL:
http://192.168.164.128:8776/v2/765a2012198f4751b8457c49932ec80d;, region:
nova, internalURL:
http://192.168.164.128:8776/v2/765a2012198f4751b8457c49932ec80d;,
publicURL:
http://192.168.164.128:8776/v2/765a2012198f4751b8457c49932ec80d}],
endpoints_links: [], type: volume, name: volume}, {endpoints:
[{adminURL:
http://${SWIFT_HOST}:8080/v1/AUTH_765a2012198f4751b8457c49932ec80d;,
region: nova, internalURL: http://127.0.0.1:8080;, publicURL:
http://${SWIFT_HOST}:8080/v1/AUTH_765a2012198f4751b8457c49932ec80d}],
endpoints_links: [], type: storage, name: swift}, {endpoints:
[{adminURL: http://192.168.164.128:9292/v1;, region: nova,
internalURL: http://192.168.164.128:9292/v1;, publicURL:
http://192.168.164.128:9292/v1}], endpoints_links: [], type: image,
name: glance}, {endpoints: [{adminURL:
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d;, region:
nova, internalURL:
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d;,
publicURL:
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d}],
endpoints_links: [], type: compute, name: nova}, {endpoints:
[{adminURL: http://192.168.164.128:5000/v2.0;, region: nova,
internalURL: http://192.168.164.128:5000/v2.0;, publicURL:
http://192.168.164.128:35357/v2.0}], endpoints_links: [], type:
identity, name: keystone}], user: {username: admin,
roles_links: [], id: 842c74e5daa246239426f92b6f5c5dba, roles:
[{id: d6d2f681acbf4f91a3bd3522e1c006ae, name: admin}, {id:
e1428c3c9403494494b53393660a930a, name: KeystoneServiceAdmin}, {id:
f2a9436d68974a049547c08324a37aed, name: KeystoneAdmin}], name:
admin}}}
REQ: curl -i
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d/images/detail
-X GET -H X-Auth-Project-Id: admin -H User-Agent: python-novaclient -H
Accept: application/json -H X-Auth-Token:
c6d3145f1e924982982b54e52b97bec9
REQ: curl -i
http://192.168.164.128:8774/v2/765a2012198f4751b8457c49932ec80d/images/detail
-X GET -H X-Auth-Project-Id: admin -H User-Agent: python-novaclient -H
Accept: application/json -H X-Auth-Token:
c6d3145f1e924982982b54e52b97bec9
RESP:{'date': 'Fri, 04 May 2012 14:08:53 GMT', 'status': '500',
'content-length': '128', 'content-type': 'application/json; charset=UTF-8',
'x-compute-request-id': 'req-3e953b5d-5953-438f-bd9b-20f52f2f4bf2'}
{computeFault: {message: The server has either erred or is incapable of
performing the requested operation., code: 500}}
RESP:{'date': 'Fri, 04 May 2012 14:08:53 GMT', 'status': '500',
'content-length': '128', 'content-type': 'application/json; charset=UTF-8',
'x-compute-request-id': 'req-3e953b5d-5953-438f-bd9b-20f52f2f4bf2'}
{computeFault: {message: The server has either erred or is incapable of
performing the requested operation., code: 500}}
I'm using ubuntu 12.04 with the default repository packages. All the
services are running.
Regards,
Leander
___
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] Glance store question??
Opened this blueprint, I've started doing part of it, with the simple way of doing it (add a new config list that specifies the stores and import them at startup...) Something like: --- a/etc/glance-api.conf +++ b/etc/glance-api.conf @@ -5,10 +5,17 @@ verbose = True # Show debugging output in logs (sets DEBUG log level output) debug = False -# Which backend store should Glance use by default is not specified +# Which backend scheme should Glance use by default is not specified # in a request to add a new image to Glance? Default: 'file' -# Available choices are 'file', 'swift', and 's3' -default_store = file +default_scheme = file + +# List of which stores (and schemes) are currently known to glance at +# startup and the module+class used to construct that store. +# Default: glance.store.filesystem.Store(filesystem; file) +known_stores = glance.store.filesystem.Store(filesystem; file) + glance.store.http.Store(http; https), + glance.store.rbd.Store(rbd), + glance.store.s3.Store(s3; s3+http; s3+https) And then the necessary changes in glance to read those and import those. https://blueprints.launchpad.net/glance/+spec/import-dynamic-stores On 5/3/12 11:06 AM, Joshua Harlow harlo...@yahoo-inc.com wrote: Ok, although I wonder if a plug-in framework could benefit from just being generic enough to be used in either place? I think he's focusing on the notification system right now (being more pluggable) there, so that be his scope for now. I'm willing to work together to make that more generic so that it isn't limited to just that though, this seems like one place that could be fixed easily either way (either via simple fix or via plugins). On 5/3/12 11:02 AM, Brian Waldon brian.wal...@rackspace.com wrote: He definitely is, but its scope is limited to Nova (for now?). The idea discussed below is something we could use without having to worry about a Glance plugin implementation. We can talk about plugins for Glance later. Brian On May 3, 2012, at 10:58 AM, Doug Hellmann wrote: Andrew is doing some work on a plugin architecture. This sounds like another good application of that. On Wed, May 2, 2012 at 7:01 PM, Joshua Harlow harlo...@yahoo-inc.com wrote: Right, if there isn't that existing, then I think I might just make a blueprint out of that. I just wanted to check beforehand that I am doing this right, or if it already exists and I did it wrong... Thx :-) On 5/2/12 3:57 PM, Brian Waldon brian.wal...@rackspace.com http://brian.wal...@rackspace.com/ wrote: Jay might have a better answer, but as far as I know, yes. You could probably make the images stores truly pluggable (i.e. not needing to explicitly list them out) without much work. Brian On May 2, 2012, at 12:23 PM, Joshua Harlow wrote: Glance store question?? Hi all, I am making a y! specific backing store for glance and I was wondering if its really necessary to modify the following file to ensure that the code for that new store gets pulled in (or maybe I'm just doing it wrong). diff --git a/glance/api/v1/images.py b/glance/api/v1/images.py index 9839d2e..7c4f565 100644 --- a/glance/api/v1/images.py +++ b/glance/api/v1/images.py @@ -47,6 +47,7 @@ import glance.store.http import glance.store.rbd import glance.store.s3 import glance.store.swift +import glance.store.SUPERAWESOMEYSTORE from glance.store import (get_from_backend, get_size_from_backend, schedule_delete_from_backend, Is there another way to make that happen so that it gets registered with glance besides either modifying that file or having a patch which will modify it upon installation (ie an RPM patch)? Thx! -Josh ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net http://openstack@lists.launchpad.net/ Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Metering] Adding a source notion to the schema
On 05/04/2012 03:11 PM, Doug Hellmann wrote: On Fri, May 4, 2012 at 6:03 PM, Nick Barcet nick.bar...@canonical.com mailto:nick.bar...@canonical.com wrote: On 05/04/2012 02:25 PM, Doug Hellmann wrote: On Fri, May 4, 2012 at 12:29 PM, Nick Barcet nick.bar...@canonical.com mailto:nick.bar...@canonical.com [...] In order to allow for this I think it would make sense to: * extend the current schema to allow for an additional source field in the event record. This should be a short identifier. That makes sense. It seems like the identifier(s) used are meant to be defined by the deployer. Is that your intent? Correct. We'll just need a sane default for Keystone. You're focusing on source as the origin for the identity information, but it seems like a layer sitting on top of OpenStack may well use Keystone for identity but generate different billable events. Should source be the origin of the metric data being sent to ceilometer? As I see it, source should remain the same as long as you can correlate project_id and user_id from the same source. * add another record definition that maps source to identity managment URL location * Collecting agent would be in charge to specify the source they map to (keystone by default). It is not clear why the identity management location needs to be recorded in ceilometer. If the deployer controls the source strings, they know what each value means. The only thing that needs to translate the (source, project, user) values to a billing identity is the end-consumer of all of this data, which is also under the control of the deployer. Couldn't the mapping of the source token to the identity location be handled in that layer? True. It might be over-engineering to try to keep the info in the same place as well, but the impact on the system would be negligible. I'd be happy either ways :) It will be easier to add it later if we really need it than to take it out if we decide we don't. Agreed. Nick signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Swift's proxy_logging vs. swift3
Hi, Mike: I applied the proxy_logging patch (change 5284) to another Swift, which happens to have the swift3 loaded, and S3 accesses started to fail. Since swift3 is an existing part of Swift, I put a -1 on the review for now, and I hope we can resolve this somehow and re-spin a patch #7. The pipeline looks like this: [zaitcev@kvm-san ~]$ grep pipeline /etc/swift/proxy-server.conf [pipeline:main] pipeline = healthcheck cache swift3 swauth proxy-logging proxy-server [zaitcev@kvm-san ~]$ As much as I can tell, the scenario is this: - swift3's app.__call__ identifies the request as S3. If it's native Swift, it is passed along unmolested and works fine. - __call__ find the controller, say ServiceController - controller defines an intercept start_response(), do_start_response, invokes the downstream app with it - proxy_logger's app.__call__, however, is a generator (has yield). As I guess, a generator is used as a tool to postpone logging like a hook was before - as downstream app returns to swift3, it assumes that start_response was called by the app, but in fact, only the generator prologue was called and returned an iterable. The fields that do_start_response fills are not filled, and swift3 tracebacks with IndexError. I threw together a patch like this (against proxy log patch #6): commit 66b08d63c41c8aeebe745b00ba942dc564595e58 Author: Pete Zaitcev zait...@kotori.zaitcev.us Date: Fri May 4 17:34:32 2012 -0600 Fixed swift3 but now proxy_logging does not log anything for PUT. diff --git a/swift/common/middleware/proxy_logging.py b/swift/common/middleware/proxy_logging.py index b5f25df..c3f4467 100644 --- a/swift/common/middleware/proxy_logging.py +++ b/swift/common/middleware/proxy_logging.py @@ -101,6 +101,10 @@ class ProxyLoggingMiddleware(object): self.access_logger = get_logger(access_log_conf, log_route='proxy-access') +self.client_disconnect = False +self.input_proxy = None +self.start_time = None + def log_request(self, env, status_int, bytes_received, bytes_sent, request_time, client_disconnect): @@ -144,31 +148,34 @@ class ProxyLoggingMiddleware(object): ))) self.access_logger.txn_id = None -def __call__(self, env, start_response): -status_int = [500] +def log_generator(self, env, status_int, body_resp): bytes_sent = 0 -client_disconnect = False -input_proxy = InputProxy(env['wsgi.input']) -env['wsgi.input'] = input_proxy -start_time = time.time() - -def my_start_response(status, headers, exc_info=None): -status_int[0] = int(status.split()[0]) -return start_response(status, headers, exc_info) - try: -for chunk in self.app(env, my_start_response): +for chunk in body_resp: bytes_sent += len(chunk) yield chunk except GeneratorExit: # generator was closed before we finished -client_disconnect = True +self.client_disconnect = True raise finally: -request_time = time.time() - start_time -self.log_request(env, status_int[0], input_proxy.bytes_received, -bytes_sent, request_time, -client_disconnect or input_proxy.client_disconnect) +request_time = time.time() - sef.start_time +self.log_request(env, status_int[0], +self.input_proxy.bytes_received, bytes_sent, request_time, +self.client_disconnect or self.input_proxy.client_disconnect) + +def __call__(self, env, start_response): +status_int = [500] +self.client_disconnect = False +self.input_proxy = InputProxy(env['wsgi.input']) +env['wsgi.input'] = self.input_proxy +self.start_time = time.time() + +def my_start_response(status, headers, exc_info=None): +status_int[0] = int(status.split()[0]) +return start_response(status, headers, exc_info) +body_resp = self.app(env, my_start_response) +return self.log_generator(env, status_int, body_resp) def filter_factory(global_conf, **local_conf): conf = global_conf.copy() With the above, the server works once again, but I did something wrong and PUT requests are not logged by the proxy_logging anymore. It seems like generator's finally clause is not invoked somehow. I thought it was supposed to be invoked when the iterator is deleted, but most likely I'm confused. I need you to take over and apply your Python-fu, because mine is lacking. Cheers, -- Pete ___ 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] Nova subsystem branches and feature branches
Overall, I think you've described problem and solutions well. A few thoughts below. * Mark McLoughlin (mar...@redhat.com) wrote: Firstly, problem definition: - Nova is big, complex and has a fairly massive rate of churn. While the nova-core team is big, there isn't enough careful review going on by experts in particular areas and there's a consistently large backlog of reviews. - Developers working on features are very keen to have their work land somewhere and this leads to half-finished features being merged onto master rather than developers collaborating to get a feature to a level of completeness and polish before merging into master. I'm not sure having subsystem trees and feature branches (as defined below) actually address the desire to land somewhere anymore than developers' github forks do. A feature needs to be just as complete when it lands in a subsystem tree as it does when it lands in master. I don't think it's a shortcoming to the model here, but should be made nice and clear. Some assumptions about the solution: - There should be a small number of domain experts who can approve changes to each of major subsystems. This will encourage specialization and give more clear lines of responsibility. - There should be a small number of project dictators who have final approval on merge proposals, but who are not expected to review every patch in great detail. This is good because we need someone with an overall view of the project who can make sure efforts in the various subsystems are coordinated, without that someone being massively overloaded. - New features should be developed on a branch and brought to a level of completeness before being merged into master. This is good because we don't want half-baked stuff in master but also because it encourages developers to break their features into stages where each stage of the work can be brought to completion and merged before moving on to the next stage. - In essence, we're assuming some variation of the kernel distributed development model. (FWIW, my instinct is to avoid the kernel model on projects. Mostly because it's extremely complex and massive overkill for most projects. Looking at the kernel history with gitk is enough to send anyone screaming for the hills. However, Nova seems to be big enough that we're experiencing the same pressures that drove the kernel to adopt their model) I'm certainly biased, but I think this is a great model ;) Ok, what are subsystem branches and how would they work? - Subsystem branches would have a small number of maintainers who can approve a change. These would be domain experts providing strong oversight over a particular area. (In gerrit, this is a branch with a small team or single person who can +1 approve a review) - Project dictators don't need to do detailed reviews of merge proposals from subsystem maintainers. The dictator's role is mostly just to sign off on the merge proposal. However, the dictator can comment in the proposal on things which could have been done better and the subsystem maintainer should take note of these comments and perhaps retroactively fix them up. Ultimately, though, the dictator can have exercise a veto if the merge proposal is unacceptable or if the subsystem maintainer is consistently making the same mistakes. - It would be up to the project dictators to help drive patches through the right subsystem branches - e.g. they might object if one subsystem maintainer merged a patch that inappropriately cut into another subsystem or they might refuse to merge a given patch into the main branch unless it went through the appropriate subsystem branch. (In gerrit, this would mean a small team or single person who can +1 approve merge proposals on master. They would -1 proposals submitted against master which should have been submitted against a subsystem branch.) - Subsystem branches might not necessarily be blessed centrally. It might be a case that anyone can create such a branch and, over time, establish trust with the project dictators. Subsystem branches would come and go. This is the mechanism by which subsystem maintainership is transferred between people over time. (In gerrit, this means people need to easily be able to create their own branches) (What's more difficult to imagine in gerrit is how a new, potential subsystem maintainer comes along, starts hoovering up patches into her branch and submitting them in batches. Where does she hoover them up from and how does she say I've merged this into my branch, don't merge it via another branch) - Bisectability remains
[Openstack] [OSSA 2012-006] Horizon session fixation and reuse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenStack Security Advisory: 2012-006 CVE: 2012-05-04 Date: Friday, May 4 Title: Horizon session fixation and reuse Impact: Critical Reporter: Thomas Biege, SUSE Products: Horizon Affects: All versions Description: Thomas Biege from SUSE reported a vulnerability in OpenStack Dashboard (Horizon). Under specific circumstances it is possible to reuse session cookies from another user, potentially allowing access to unauthorized information and capabilities. Fixes: Folsom: https://github.com/openstack/horizon/commit/041b1c44c7d6cf5429505067c32f8f35166a8bab 2012.1: https://github.com/openstack/horizon/commit/abc532fa90eac1cc970423339347e318aa8d1b1a References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-2144 https://bugs.launchpad.net/horizon/+bug/978896 Notes: This fix will be included in the folsom-1 development milestone and in a future 2012.1 (essex) release. - -- Russell Bryant OpenStack Vulnerability Management Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+kdO0ACgkQFg9ft4s9SAYLsgCgptN3zZrEpOCPsbbSfPiPz7J5 BegAoK2D0D1YHP08xt3iSdGQ7OKXuyLT =CYxN -END PGP SIGNATURE- ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] heads up regarding keystone dev venv on an Ubuntu VM (VirtualBox)
(Adding Sean at tummy, in case this is useful info for him.) Nice detective work, Jeremy! d On Fri, May 4, 2012 at 8:27 PM, Jeremy Hanmer jeremy.han...@dreamhost.com wrote: After quite a bit of experimentation, I've noticed that the crash is triggered by pip when accessing ftp://tummy.com specifically. After doing some network dumps, it's apparent that after the connection is initiated we receive an ICMP Host Administratively Prohibited message. My assumption is that this message is seen by VirtualBox, who then tears down the NAT session but fails to pass the ICMP message along to the guest (hard to verify because of how quickly the guest gets killed off). When the guest tries to transfer the first bit of data over the NAT link, I'm guessing it causes something along the lines of a null pointer deref. I'll throw in some of the debug info I've got but the problem is trivial to reproduce: simply run pftp tummy.com, log in anonymously, and try an ls. Process: VirtualBoxVM [16548] Path: /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM Identifier: VirtualBoxVM Version: ??? (???) Code Type: X86-64 (Native) Parent Process: VBoxSVC [16535] Date/Time: 2012-05-04 17:14:19.640 -0700 OS Version: Mac OS X 10.7.3 (11D50b) Report Version: 9 Crashed Thread: 22 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0010 On May 4, 2012, at 2:31 PM, Duncan McGreggor wrote: Update: Jeremy Hanmer said that it looks like it's a port lookup that's failing and taking cfprefsd with it. He's gone over my head, but I'm sure that's meaningful to someone out there ;-) d On Fri, May 4, 2012 at 12:59 PM, Duncan McGreggor dun...@dreamhost.com wrote: Updates: * Doug Hellmann narrowed this down to the network access that was happening with pip * Mark McClain further narrowed it down to VirtualBox's networking: with a NATed interface, big probs -- with a bridged interface, things go well. I haven't taken the time to check this on my own system, since I've got a working solution right now, but when I need to rebuild, I will check. Mark also mentioned that VBox networking sometimes does some weird stuff (rewriting headers or something) and that might be contributing to the problem. Hope this helps, d On Fri, May 4, 2012 at 12:40 PM, Duncan McGreggor dun...@dreamhost.com wrote: Hey folks, We're really pressed for time right now, so there are certain rabbit holes we can't dive down, but I wanted to bring this up in case it hasn't been seen yet. On Mac OS X 10.6 and 10.7, when running a 12.04 Ubuntu VM and setting up the dev env for Keystone, we get some madness. 10.6: VirtualBox instance aborts, leaving no traces of issue in system logs (that I could see) 10.7: VB dies, OS X kernel panics The second time, I watched carefully, and it happened as python-memcached was getting installed via pip in the .venv. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up after I removed .venv and changed tools/install_venv.py to enable system site-package use. d ___ 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-poc] Fwd: 3rd Party APIs
FYI. Here is a message that was sent to the list but was refused as non-member post. I think it brings some perspective on how the ecosystem is organizing about 3rd party APIs support, so I forward it on this thread. Message original Sujet: 3rd Party APIs Date : Thu, 3 May 2012 15:57:50 +0200 De :jean-pierre.lai...@bull.net Pour : openstack-poc@lists.launchpad.net Copie à : ijm...@hotmail.com Dear all, We would like to present some insight that we have gained, through work that performed in our project, for discusion on the table of this highly interesting thread. In CompatibleOne, we took the decision to interoperate with OpenStack through a proxy and more precisely, in our case, an OCCI component that we call a PROCCI. We are using the Nova API, and only that API. We remap it for use through this OCCI component to satisfy the provisioning needs of our open source cloud broker. This technique allows us to interoperate with any other platform in much the same way. And we could easily encapsulate, and consequently be compatible with standards such as OCCI Infrastructure. Others such as CIMI or CDMI could easily be adopted as and when they become publicly available. Whilst contributing to OCCI and more than happy to be working with OpenStack, we are looking for the assurance that it is possible to be able to perform complete and fully automated provisioning through the native NOVA APIs. We are looking for well documented and stable API on which our system can be built. For the rest we can easily manage as we have already done with Cactus, Diablo and now Essex. If the transition from release to release could be less painful it would really save valuable time ;) We would also appreciate the idea to have simple test kit to self assess that our OpenStack PROCCI works properly and we would be willing to consacrate time to participate in such an effort. HTH Jean-Pierre Laisne and Jamie Marshall CompatibleOne coordinator and CTO www.compatibleone.org http://www.compatibleone.org ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 946573] Re: 404 handler for doc sites
** Project changed: openstack-common = openstack-ci -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/946573 Title: 404 handler for doc sites Status in OpenStack Core Infrastructure: New Bug description: Since our pages will evolve, it would be good to have a catch-all (perhaps per project) 404 handler on pages like: http://keystone.openstack.org/page_not_found or http://nova.openstack.org/secret_stuff To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ci/+bug/946573/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 927650] Re: cfg: unneeded multiple inheritance
** Changed in: openstack-common Milestone: None = 2012.1 ** Changed in: openstack-common Importance: Undecided = Low ** Changed in: openstack-common Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/927650 Title: cfg: unneeded multiple inheritance Status in openstack-common: Fix Released Bug description: From Monsyne Dragon in https://review.openstack.org/3729 File nova/openstack/common/cfg.py Line 696: class ConfigOpts(collections.Mapping, object): I don't think we really need to multiply inherit from 'object' here. esp. since collections.Mapping already inherits from object. While this doesn't affect anything atm, this kind of diamond inheritance may lead to some rather non-intuitive behavior if someone subclasses ConfigOpts in the future To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/927650/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 925775] Re: utils.import_object sometimes masks the failed import
Think this is fixed by: https://review.openstack.org/#/c/6906/
** Changed in: openstack-common
Milestone: None = folsom-1
** Changed in: openstack-common
Assignee: (unassigned) = Russell Bryant (russellb)
** Changed in: openstack-common
Importance: Undecided = Medium
** Changed in: openstack-common
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/925775
Title:
utils.import_object sometimes masks the failed import
Status in openstack-common:
Fix Committed
Bug description:
146 def import_class(import_str):
147 Returns a class from a string including module and class
148 mod_str, _sep, class_str = import_str.rpartition('.')
149 try:
150 __import__(mod_str)
151 return getattr(sys.modules[mod_str], class_str)
152 except (ImportError, ValueError, AttributeError):
153 raise exception.NotFound('Class %s cannot be found' % class_str)
From time to time we are seeing the exception raised without the
class_str being filled in making it fun to track down what is not
installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-common/+bug/925775/+subscriptions
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 915039] Re: flags.FLAGS( crashes bpython
** Changed in: openstack-common
Status: Fix Committed = Fix Released
** Changed in: openstack-common
Milestone: None = 2012.1
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/915039
Title:
flags.FLAGS( crashes bpython
Status in OpenStack Compute (Nova):
Fix Released
Status in openstack-common:
Fix Released
Bug description:
Bpython tries to do some fancy stuff like lookup obj.__name__ and
check for AttributeError. The code in common/cfg.py has a special
getattr that raises a non AttributeError exception so it leads to a
crash and stack trace in bpython:
Traceback (most recent call last):
File /usr/local/share/python/bpython, line 9, in module
load_entry_point('bpython==0.10.1', 'console_scripts', 'bpython')()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1756, in main
banner=banner)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1658, in curses_wrapper
return func(stdscr, *args, **kwargs)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1727, in main_curses
clirepl.repl()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1015, in repl
inp = self.get_line()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 600, in get_line
if self.p_key(key) is None:
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 911, in p_key
self.addstr(key)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 290, in addstr
self.complete()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 383, in complete
self.list_win_visible = repl.Repl.complete(self, tab)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/repl.py,
line 540, in complete
if not self.get_args():
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/repl.py,
line 511, in get_args
self.argspec = inspection.getargspec(func, f)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/inspection.py,
line 229, in getargspec
func_name = getattr(f, '__name__', None)
File nova/flags.py, line 114, in __getattr__
return getattr(self._conf, name)
File nova/common/cfg.py, line 777, in __getattr__
return self._substitute(self._get(name))
File nova/common/cfg.py, line 930, in _get
info = self._get_opt_info(name, group)
File nova/common/cfg.py, line 1010, in _get_opt_info
raise NoSuchOptError(opt_name, group)
nova.common.cfg.NoSuchOptError: no such option: __name__
To test, you do:
bpython
then at prompt:
from nova import flags
flags.FLAGS(
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/915039/+subscriptions
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 627792] Re: Support getting a logger
Moving to Opinion, no progress in 18+ months and a blueprint would be
better
** Changed in: openstack-common
Status: New = Opinion
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/627792
Title:
Support getting a logger
Status in openstack-common:
Opinion
Bug description:
swift.common.utils.get_logger is a good jumping off point.
Pass in parameters such as
* log name ('openstack-foo')
* method (syslog, rotating file, stderr, etc)
* log level (DEBUG)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-common/+bug/627792/+subscriptions
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 930625] Re: PEP8 cleanup (openstack-common)
** Changed in: openstack-common Milestone: None = 2012.1 ** Changed in: openstack-common Status: Fix Committed = Fix Released ** Changed in: openstack-common Importance: Undecided = Low -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/930625 Title: PEP8 cleanup (openstack-common) Status in openstack-common: Fix Released Bug description: Remove backslash continuations in openstack-common. Fix type checking taboos. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/930625/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 930270] Re: flagfile interpolation breaks instance_name_template
** Changed in: openstack-common
Status: Fix Committed = Fix Released
** Changed in: openstack-common
Milestone: None = 2012.1
** Changed in: openstack-common
Importance: Undecided = High
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/930270
Title:
flagfile interpolation breaks instance_name_template
Status in OpenStack Compute (Nova):
Fix Released
Status in openstack-common:
Fix Released
Bug description:
When --volume_name_template=volume-%08x and
--instance_name_template=instance-%08x are present in nova.conf,
ConfigParser attempts to interpolate the '%' strings. There are meant
for nova to interpolate.
2012-02-10 10:54:49,089 DEBUG nova.service [-] osapi_compute_link_prefix :
None from (pid=22867) wait /opt/stack/nova/nova/service.py:409
2012-02-10 10:54:49,089 CRITICAL nova [-] '%' must be followed by '%' or '(',
found: '%08x'
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File /opt/stack/nova/bin/nova-api, line 53, in module
(nova): TRACE: service.wait()
(nova): TRACE: File /opt/stack/nova/nova/service.py, line 402, in wait
(nova): TRACE: flag_get = FLAGS.get(flag, None)
(nova): TRACE: File /opt/stack/nova/nova/flags.py, line 73, in get
(nova): TRACE: value = getattr(self, name)
(nova): TRACE: File /opt/stack/nova/nova/flags.py, line 70, in __getattr__
(nova): TRACE: return getattr(self._conf, name)
(nova): TRACE: File /opt/stack/nova/nova/openstack/common/cfg.py, line
784, in __getattr__
(nova): TRACE: return self._substitute(self._get(name))
(nova): TRACE: File /opt/stack/nova/nova/openstack/common/cfg.py, line
985, in _get
(nova): TRACE: return opt._get_from_config_parser(self._cparser, section)
(nova): TRACE: File /opt/stack/nova/nova/openstack/common/cfg.py, line
433, in _get_from_config_parser
(nova): TRACE: return cparser.get(section, self.dest)
(nova): TRACE: File /usr/lib/python2.7/ConfigParser.py, line 615, in get
(nova): TRACE: return self._interpolate(section, option, value, d)
(nova): TRACE: File /usr/lib/python2.7/ConfigParser.py, line 683, in
_interpolate
(nova): TRACE: self._interpolate_some(option, L, rawval, section, vars, 1)
(nova): TRACE: File /usr/lib/python2.7/ConfigParser.py, line 724, in
_interpolate_some
(nova): TRACE: '%%' must be followed by '%%' or '(', found: %r %
(rest,))
(nova): TRACE: InterpolationSyntaxError: '%' must be followed by '%' or '(',
found: '%08x'
(nova): TRACE:
stack@356591-essex-k1:/opt/stack/nova$
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/930270/+subscriptions
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 963509] Re: update.py doesn't handle dependencies of configured modules
** Changed in: openstack-common Status: New = Confirmed ** Changed in: openstack-common Importance: Undecided = Wishlist -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/963509 Title: update.py doesn't handle dependencies of configured modules Status in openstack-common: Confirmed Bug description: cfg.py now depends on iniparser.py, but update.py didn't automatically copy it. The dependencies can be figured out automatically and update.py could be friendlier and help out us poor developers. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/963509/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 960487] Re: Request deserializer does not pass an empty body
Ok, based on Brian Waldon's comment in the review I'm going to close this ** Changed in: openstack-common Status: In Progress = Invalid ** Changed in: openstack-common Importance: Undecided = Wishlist -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/960487 Title: Request deserializer does not pass an empty body Status in openstack-common: Invalid Bug description: When a POST is sent via an API call and the body is empty the body is lost and not sent along and sending back a general 400 error. This should send a body even if it is empty to the method in the route specified. The common/wsgi.py Request deserializer for the body needs an update so that this is possible. This will allow the API developer to create a validation message to the client with what is invalid in the body of the action. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/960487/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 976267] Re: auto generate AUTHORS for packaging
** Changed in: openstack-common Status: New = Fix Committed ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in: openstack-common Milestone: None = folsom-1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/976267 Title: auto generate AUTHORS for packaging Status in openstack-common: Fix Committed Bug description: As discussed in bug 920757, the check-ins for all projects are gated using CLA sign. It's not necessary to enforce an entry in AUTHORS file. The file should be auto-generated when we package using python setup.py sdist command. The .mailmap file, if exists, should be honored. This is applicable for all projects, swift, keystone, nova and glance. Once this is resolved, we could remove the test, test_authors.py that check for an entry in AUTHORS file. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/976267/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 967400] Re: iniparser needs absolute import
** Changed in: openstack-common Status: Fix Committed = Fix Released ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in: openstack-common Milestone: None = 2012.1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/967400 Title: iniparser needs absolute import Status in openstack-common: Fix Released Bug description: The use of a relative import for 'iniparser' is causing: http://paste.openstack.org/show/12224/ Changing this to: from openstack.common import iniparser fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/967400/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 965563] Re: Usability issue: is_public=yes sets Public: No
openstack-common fix: https://review.openstack.org/#/c/5712/ ** Changed in: openstack-common Status: New = Fix Released ** Changed in: openstack-common Importance: Undecided = Medium ** Changed in: openstack-common Assignee: (unassigned) = Sean Dague (sdague-b) ** Changed in: openstack-common Milestone: None = 2012.1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/965563 Title: Usability issue: is_public=yes sets Public: No Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in openstack-common: Fix Released Bug description: There is a usability with Glance around the use of booleans. The is_public metadata for an image is displayed via glance show in Yes/No terms. i.e. Id: 7b1ee878-131b-4c1e-bd14-dc8cb0e48ace Public: Yes Protected: No Name: oneiric-11.10-2 Status: active Size: 10486808576 However the bool_from_string function (common/utils.py) doesn't define 'yes' as true. This results in the flag is_public=yes actually setting Public: No in the image. I suggest that 'yes' is added to the list of values considered true. There is a proposed change for it here - https://review.openstack.org/#change,5712 that would go into common, then we could propogate it out to glance proper. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/965563/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 976267] Re: auto generate AUTHORS for packaging
** Changed in: openstack-common Status: In Progress = Fix Committed ** Also affects: nova Importance: Undecided Status: New ** Also affects: swift Importance: Undecided Status: New ** Also affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/976267 Title: auto generate AUTHORS for packaging Status in OpenStack Dashboard (Horizon): New Status in OpenStack Compute (Nova): New Status in openstack-common: Fix Committed Status in OpenStack Object Storage (Swift): New Bug description: As discussed in bug 920757, the check-ins for all projects are gated using CLA sign. It's not necessary to enforce an entry in AUTHORS file. The file should be auto-generated when we package using python setup.py sdist command. The .mailmap file, if exists, should be honored. This is applicable for all projects, swift, keystone, nova and glance. Once this is resolved, we could remove the test, test_authors.py that check for an entry in AUTHORS file. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/976267/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 943336] Re: New requirements never get written out
Could do with more details here, I'm not sure I follow what the issue is ** Changed in: openstack-common Assignee: (unassigned) = Jason Kölker (jason-koelker) ** Changed in: openstack-common Importance: Undecided = Low ** Changed in: openstack-common Milestone: None = folsom-1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/943336 Title: New requirements never get written out Status in openstack-common: Confirmed Bug description: write_requirements is failing to write out requirements.txt on a new virtualenv/checkout. Need to figure out what's going on. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/943336/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
