Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

>>1) We already have identity-api, which will need to be updated once the spec is completed anyway. >So my thinking is to merge the content of openstack/identity-api into openstack/keystone-specs. We use identity-api just like we use keystone-specs anyway, but only for a subset of >our work.   I t

Re: [openstack-dev] Server groups specified by name

On 07/07/2014 12:35 PM, Day, Phil wrote: Hi Folks, I noticed a couple of changes that have just merged to allow the server group hints to be specified by name (some legacy behavior around automatically creating groups). https://review.openstack.org/#/c/83589/ https://review.openstack.org/#/c/8

Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

On Mon, Jul 7, 2014 at 2:43 PM, Steve Martinelli wrote: > >>1) We already have identity-api, which will need to be updated once the > spec is completed anyway. > > >So my thinking is to merge the content of openstack/identity-api into > openstack/keystone-specs. We use identity-api just like we u

[openstack-dev] Barbican Meeting CANCELLED

All, This week is Barbican's mid-cycle meet up. As many of our contributors are in San Antonio this week, I'm going to cancel our weekly meeting today. Several of us are still on IRC, so if you need something from us, feel free to pop into #openstack-barbican and ask. The etherpad being used for

Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

On 7/2/2014 8:23 PM, Mike Bayer wrote: I've just added a new section to this wiki, "MySQLdb + eventlet = sad", summarizing some discussions I've had in the past couple of days about the ongoing issue that MySQLdb and eventlet were not meant to be used together. This is a big one to solve as

[openstack-dev] [neutron] Core reviewer assignment to specific BPs for Juno-2

As we quickly approach Juno-2, I'd like to try something out for the next few weeks. The tl;dr is this: What I'm going to propose is assigning core reviewers to specific BPs which are of community importance and are things we're working hard to land in Juno-2. The long form answer is this: I'd lik

Re: [openstack-dev] [Keystone][Horizon] Proposed Changed for Unscoped tokens.

On 07/07/2014 11:11 AM, Dolph Mathews wrote: On Fri, Jul 4, 2014 at 5:13 PM, Adam Young > wrote: Unscoped tokens are really a proxy for the Horizon session, so lets treat them that way. 1. When a user authenticates unscoped, they should get back a l

[openstack-dev] (no subject)

http://bloggsatt.se/wp-admin/css/afternews.php___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status

On Mon, Jul 7, 2014 at 7:53 AM, Sylvain Bauza wrote: > Le 07/07/2014 12:00, Michael Still a écrit : > > I think you'd be better of requesting an exception for your spec than > > splitting the scheduler immediately. These refactorings need to happen > > anyways, and if your scheduler work diverges

Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

On 07/02/2014 09:23 PM, Mike Bayer wrote: I've just added a new section to this wiki, "MySQLdb + eventlet = sad", summarizing some discussions I've had in the past couple of days about the ongoing issue that MySQLdb and eventlet were not meant to be used together. This is a big one to solve as

Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

On 7/7/14, 3:57 PM, Matt Riedemann wrote: > > > > Regarding the eventlet + mysql sadness, I remembered this [1] in the > nova.db.api code. > > I'm not sure if that's just nova-specific right now, I'm a bit too > lazy at the moment to check if it's in other projects, but I'm not > seeing it in neut

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status

On Mon, Jul 7, 2014 at 8:02 AM, Daniel P. Berrange wrote: > On Mon, Jul 07, 2014 at 02:38:57PM +, Dugger, Donald D wrote: > > Well, my main thought is that I would prefer to see the gantt split > > done sooner rather than later. The reality is that we've been trying > > to split out the sche

Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

On 07/07/2014 04:17 PM, Mike Bayer wrote: On 7/7/14, 3:57 PM, Matt Riedemann wrote: Regarding the eventlet + mysql sadness, I remembered this [1] in the nova.db.api code. I'm not sure if that's just nova-specific right now, I'm a bit too lazy at the moment to check if it's in other projec

Re: [openstack-dev] Server groups specified by name

On Jul 7, 2014 3:47 PM, "Chris Friesen" wrote: > > On 07/07/2014 12:35 PM, Day, Phil wrote: >> >> Hi Folks, >> >> I noticed a couple of changes that have just merged to allow the server >> group hints to be specified by name (some legacy behavior around >> automatically creating groups). >> >> htt

Re: [openstack-dev] [keystone][specs] listing the entire API in a new spec

On Mon, Jul 7, 2014 at 2:51 PM, Anne Gentle wrote: > > > > On Mon, Jul 7, 2014 at 2:43 PM, Steve Martinelli > wrote: > >> >>1) We already have identity-api, which will need to be updated once the >> spec is completed anyway. >> >> >So my thinking is to merge the content of openstack/identity-api

Re: [openstack-dev] [trove] Discussion of capabilities feature

On Jul 3, 2014 6:38 PM, "Doug Shelley" wrote: > > Iccha, > > > > Thanks for the feedback. I guess I should have been more specific – my intent here was to layout use cases and requirements and not talk about specific implementations. I believe that if we can get agreement on the requirements, it w

Re: [openstack-dev] [nova] Audit Log

On 07/04/2014 07:56 AM, Noorul Islam K M wrote: Hello all, I was looking for audit logs in nova. I found [1] but could not find the launchpad entry audit-logging as mentioned in the wiki page. Is this yet to be implemented or am I looking at the wrong place? The audit logging functionality i

Re: [openstack-dev] [oslo] Openstack and SQLAlchemy

On 7/7/2014 3:28 PM, Jay Pipes wrote: On 07/07/2014 04:17 PM, Mike Bayer wrote: On 7/7/14, 3:57 PM, Matt Riedemann wrote: Regarding the eventlet + mysql sadness, I remembered this [1] in the nova.db.api code. I'm not sure if that's just nova-specific right now, I'm a bit too lazy at th

[openstack-dev] [Neutron][IPv6] Volunteer to run tomorrow's IRC meeting?

Hi, I am currently at a book sprint and will probably not be able to run the meeting, if someone could volunteer to chair the meeting and run it, that would be great. Any takers? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.op

Re: [openstack-dev] Policy around Requirements Adds (was: New class of requirements for Stackforge projects)

This thread was unfortunately hidden under a project specific tag (I have thus stripped all the tags). The crux of the argument here is the following: Is a stackforge project project able to propose additions to global-requirements.txt that aren't used by any projects in OpenStack. I believe the

Re: [openstack-dev] [Openstack] [Trove] Trove instance got stuck in BUILD state

Denis Makogon writes: > On Mon, Jul 7, 2014 at 3:40 PM, Amrith Kumar wrote: > >> Denis Makogon (dmako...@mirantis.com) writes: >> > [...] >> >> I think it is totally ludicrous (and to all the technical writers who work >> on OpenStack, downright offensive) to say the “docs are useless”. Not only

Re: [openstack-dev] [third-party-ci][neutron] What is "Success" exactly?

On Jul 3, 2014 8:57 AM, "Anita Kuno" wrote: > > On 07/03/2014 06:22 AM, Sullivan, Jon Paul wrote: > >> -Original Message- > >> From: Anita Kuno [mailto:ante...@anteaya.info] > >> Sent: 01 July 2014 14:42 > >> To: openstack-dev@lists.openstack.org > >> Subject: Re: [openstack-dev] [third-pa

Re: [openstack-dev] [heat] Update behavior for CFN compatible resources

On 07/07/14 20:37, Steven Hardy wrote: > Hi all, > > Recently I've been adding review comments, and having IRC discussions about > changes to update behavior for CloudFormation compatible resources. > > In several cases, folks have proposed patches which allow non-destructive > update of properties

Re: [openstack-dev] [Heat] [Marconi] Heat and concurrent signal processing needs some deep thought

Yeah, this is really sticky when it comes to Auto Scaling. Because you probably want a "Oh, we've got more load than expected, scale up a bit" policy and an "OMG! REDDIT FRONT PAGE!" policy. The right thing is probably to be prepared to execute multiple concurrent signals simultaneously. That

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

Excerpts from Joshua Harlow's message of 2014-07-07 10:41:34 -0700: > So I've been thinking how to respond to this email, and here goes (shields > up!), > > First things first; thanks mark and victor for the detailed plan and > making it visible to all. It's very nicely put together and the amount

[openstack-dev] [Heat] Upwards-compatibility for HOT

With the Icehouse release we announced that there would be no further backwards-incompatible changes to HOT without a revision bump. However, I notice that we've already made an upward-incompatible change in Juno: https://review.openstack.org/#/c/102718/ So a user will be able to create a vali

Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do not exist in a driver backend

I'll +1 UNBOUND or DEFERRED status. QUEUED does have a kind of implication that it will be provisioned without any further action whereas UNBOUND or DEFERRED imply that another action must take place for it to actually be provisioned. Thanks, Brandon Fr

Re: [openstack-dev] [Heat] Upwards-compatibility for HOT

Excerpts from Zane Bitter's message of 2014-07-07 14:25:50 -0700: > With the Icehouse release we announced that there would be no further > backwards-incompatible changes to HOT without a revision bump. However, > I notice that we've already made an upward-incompatible change in Juno: > > https:

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On 7 July 2014 12:29, Scott Moser wrote: > > > I'd honestly love to see us just deprecate the metadata server. > > If I had to deprecate one or the other, I'd deprecate config drive. I do > realize that its simplicity is favorable, but not if it is insufficient. > The question of deprecation is

[openstack-dev] Emails sent to publicly archived mailing lists are *NOT* confidential Re: [third-party-ci][neutron] What is "Success" exactly?

> The contents of this message and any attachments to it are > confidential and may be legally privileged. If you have received this > message in error you should delete it from your system immediately > and advise the sender. > > To any recipient of this message within HP, unless otherwise stated

Re: [openstack-dev] [nova][scheduler] Proposal: FairShareScheduler.

On Jul 7, 2014 9:50 AM, "Lisa" wrote: > > Hi all, > > during the last IRC meeting, for better understanding our proposal (i.e the FairShareScheduler), you suggested us to provide (for the tomorrow meeting) a document which fully describes our use cases. Such document is attached to this e-mail. >

Re: [openstack-dev] [Heat] Upwards-compatibility for HOT

On 07/07/14 18:13, Clint Byrum wrote: Excerpts from Zane Bitter's message of 2014-07-07 14:25:50 -0700: >I'd like to propose a policy that we bump the revision of HOT whenever >we make a change from the previous stable version, and that we declare >the new version stable at the end of each rele

Re: [openstack-dev] Policy around Requirements Adds (was: New class of requirements for Stackforge projects)

On Jul 7, 2014 4:48 PM, "Sean Dague" wrote: > > This thread was unfortunately hidden under a project specific tag (I > have thus stripped all the tags). > > The crux of the argument here is the following: > > Is a stackforge project project able to propose additions to > global-requirements.txt th

Re: [openstack-dev] Policy around Requirements Adds (was: New class of requirements for Stackforge projects)

On Mon, Jul 7, 2014 at 3:45 PM, Joe Gordon wrote: > > On Jul 7, 2014 4:48 PM, "Sean Dague" wrote: >> >> This thread was unfortunately hidden under a project specific tag (I >> have thus stripped all the tags). >> >> The crux of the argument here is the following: >> >> Is a stackforge project pro

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Jul 3, 2014 11:43 AM, "Dmitry Guryanov" wrote: > > Hi, All! > > As far as I know, there are some requirements, which virt driver must meet to > use Openstack 'label'. For example, it's not allowed to mount cinder volumes > inside host OS. I am a little unclear on what your question is. If it i

Re: [openstack-dev] [Heat] Upwards-compatibility for HOT

On 08/07/14 09:25, Zane Bitter wrote: > With the Icehouse release we announced that there would be no further > backwards-incompatible changes to HOT without a revision bump. > However, I notice that we've already made an upward-incompatible > change in Juno: > > https://review.openstack.org/#/c/10

Re: [openstack-dev] [Heat] Upwards-compatibility for HOT

On 08/07/14 10:13, Clint Byrum wrote: > Excerpts from Zane Bitter's message of 2014-07-07 14:25:50 -0700: >> With the Icehouse release we announced that there would be no further >> backwards-incompatible changes to HOT without a revision bump. However, >> I notice that we've already made an upwa

[openstack-dev] [Neutron][LBaaS] LBaaS API Version 2 WIP in gerrit

https://review.openstack.org/#/c/105331 It's a WIP and the shim layer still needs to be completed. Its a lot of code, I know. Please review it thoroughly and point out what needs to change. Thanks, Brandon ___ OpenStack-dev mailing list OpenStack-d

[openstack-dev] [nova] new nasty gate bug 1338844 with nova-network races

I noticed the bug [1] today. Given the trend in logstash, it might be related to some fixes proposed to try and resolve the other big nova ssh timeout bug 1298472. It appears to only be in jobs using nova-network. [1] https://bugs.launchpad.net/nova/+bug/1338844 -- Thanks, Matt Riedemann

[openstack-dev] [swift] add checking daemons existence in Healthcheck middleware

Hi, Current Healthcheck middleware provides the functionality of monitoring Servers such as Proxy Server, Object Server, Container Server, Container Server and Account Server. The middleware checks whether each Servers can handle request/response. My idea to enhance this middleware is check

[openstack-dev] [nova] request to tag novaclient 2.18.0

Is it possible to tag a new release containing the fix for https://bugs.launchpad.net/python-novaclient/+bug/1297796 ? The bug can cause correct code to fail ~50% of the time (every connection reuse fails with a BadStatusLine). Thanks! <3 ___ OpenStack-

Re: [openstack-dev] [Openstack] [Trove] Trove instance got stuck in BUILD state

On 08/07/14 00:40, Amrith Kumar wrote: I think it is totally ludicrous (and to all the technical writers who work on OpenStack, downright offensive) to say the “docs are useless”. Not only have I been able to install and successfully operate a OpenStack installation by (largely) following t

Re: [openstack-dev] [swift] add checking daemons existence in Healthcheck middleware

In general, you're right. It's pretty important to know what's going on in the cluster. However, the checks for these background daemons shouldn't be done in the wsgi servers. Generally, we've stayed away from a lot of process monitoring in the Swift core. That it, Swift already works around fai

[openstack-dev] [OpenStack-Dev] Commit messages and lawyer speak

Hey All, Just wondering what's up with the following items showing up in commit messages: "CCLA SCHEDULE B SUBMISSION" Don't know that I care, but it seems completely unnecessary as signing the Corporate CCLA means your submissions are of course covered under this clause (at least I would think)

Re: [openstack-dev] [OpenStack-Dev] Commit messages and lawyer speak

"Oh hell no". -Rob On 8 July 2014 15:13, John Griffith wrote: > Hey All, > > Just wondering what's up with the following items showing up in commit > messages: > > "CCLA SCHEDULE B SUBMISSION" > > Don't know that I care, but it seems completely unnecessary as signing the > Corporate CCLA means y

Re: [openstack-dev] [OpenStack-Dev] Commit messages and lawyer speak

Hi John, There's a thread started on the legal-discuss list: http://lists.openstack.org/pipermail/legal-discuss/2014-July/000304.html Probably want to follow along there. Anne On Mon, Jul 7, 2014 at 10:13 PM, John Griffith wrote: > Hey All, > > Just wondering what's up with the following items

Re: [openstack-dev] [Containers] Nova virt driver requirements

Joe has a good answer, but you should also be aware of the hypervisor support matrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix), which hopefully comes some way to explaining what we expect of a nova driver. Cheers, Michael On Tue, Jul 8, 2014 at 9:11 AM, Joe Gordon wrote: > > On J

Re: [openstack-dev] [swift] add checking daemons existence in Healthcheck middleware

John, Thank you for your response. I checked out the doc of swift-recon and that function is exactly the one what I want to have. # Sorry, my checking is not enough... Thanks again, Hisashi Osanai > -Original Message- > From: John Dickinson [mailto:m...@not.mn] > Sent: Tuesday, July

Re: [openstack-dev] [Containers][Nova] Containers Mid-Cycle Meetup

Adrian, is there any news on this? I want to start booking my ops meetup travel, but I don't know if I should include this meetup or not. Thanks, Michael On Wed, Jul 2, 2014 at 8:12 AM, Russell Bryant wrote: > On 07/01/2014 05:59 PM, Adrian Otto wrote: >> Team, >> >> Please help us select dates

[openstack-dev] [Openstack][Nova] Launch of VM failed after certain count openstack Havana

Hi all, I am facing issue with VM launch. I am using openstack *Havana.* I have one compute node with following specification: root@compute-node:~# lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):8 On-line C

Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

On 07/07/2014 01:16 PM, Victor Lowther wrote: As one of the original authors of dracut, I would love to see it being used to build initramfs images for TripleO. dracut is flexible, works across a wide variety of distros, and removes the need to have special-purpose toolchains and packages for u

Re: [openstack-dev] DVR and FWaaS integration

Vivek, I will try to join the DVR meeting. Since it conflicts with one of my other meeting (from my real job), I may join late or may not be able to join at all. If I missed it, please see if you can join FWaaS meeting at Wed 11:30AM PST on openstack-meeting-3. Otherwise, a separated meeting

[openstack-dev] [gantt] scheduler group meeting agenda 7/8

1) Forklift (tasks & status) 2) Fair Share scheduler 3) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/

[openstack-dev] [nova] [VMware] Can someone help to look at this bug https://bugs.launchpad.net/nova/+bug/1338881

Hi All, Can someone help to look at this bug that is regarding the non-admin user connect to vCenter when run nova compute services? -- Best regard, David Geng --_

Re: [openstack-dev] [Openstack] [Trove] Trove instance got stuck in BUILD state

Mark, there are also no documentation about service tuning(no description of service related options, sample configs in Trove repo is not enough). So, I think we should extend your list of significant things to document. Thanks, Denis M. вторник, 8 июля 2014 г. пользователь Mark Kirkwood написал:

Re: [openstack-dev] [Openstack] [Trove] Trove instance got stuck in BUILD state

On 08/07/14 17:08, Denis Makogon wrote: Mark, there are also no documentation about service tuning(no description of service related options, sample configs in Trove repo is not enough). So, I think we should extend your list of significant things to document. Right - I guess most of the tuning

Re: [openstack-dev] [Openstack] [Trove] Trove instance got stuck in BUILD state

On 08/07/14 17:08, Denis Makogon wrote: Mark, there are also no documentation about service tuning(no description of service related options, sample configs in Trove repo is not enough). So, I think we should extend your list of significant things to document. ...and in case it might be helpful

Re: [openstack-dev] openstack/requirements and tarball subdirs

Hello Doug, thank you for your help. > > I guess the problem is that the subdirectory within that tarball includes > > the version number, as in "dbus-python-0.84.0/". How can I tell the extract > > script that it should look into that one? > > It looks like that package wasn't built correctly

Re: [openstack-dev] [Neutron][IPv6] Volunteer to run tomorrow's IRC meeting?

I can lead it, but I'm not sure if there is anything new to discuss since the QoS spec is still under review. Did you have any specific agenda items that you wanted to cover? On Mon, Jul 7, 2014 at 1:43 PM, Collins, Sean < sean_colli...@cable.comcast.com> wrote: > Hi, > > I am currently at a boo

Re: [openstack-dev] [Neutron][IPv6] Volunteer to run tomorrow's IRC meeting?

On Mon, Jul 07, 2014 at 11:01:52PM PDT, Kevin Benton wrote: > I can lead it, but I'm not sure if there is anything new to discuss since > the QoS spec is still under review. > Did you have any specific agenda items that you wanted to cover? Ah. The QoS IRC meeting will also need to be chaired in m

Re: [openstack-dev] [Neutron][IPv6] Volunteer to run tomorrow's IRC meeting?

I think at this point the discussion is mostly contained in the review for the spec[1] so I don't see a particular need to continue the IRC meeting. 1. https://review.openstack.org/#/c/88599/ On Mon, Jul 7, 2014 at 11:12 PM, Collins, Sean < sean_colli...@cable.comcast.com> wrote: > On Mon, Jul

[openstack-dev] [Horizon] request to review bug 1301359

HI All, Could someone please, review the bug https://bugs.launchpad.net/horizon/+bug/1301359 Made Size parameter optional while creating DB Instance. While creating Database Instance size parameter depends on whether trove_volume_support is set. So size paramater is set to mandatory if trove_vol

Re: [openstack-dev] [OpenStack-Dev] Commit messages and lawyer speak

On 07/07/2014 08:18 PM, Anne Gentle wrote: > Hi John, > There's a thread started on the legal-discuss list: > http://lists.openstack.org/pipermail/legal-discuss/2014-July/000304.html > Probably want to follow along there. Hi! a) I agree with Anne - so I have responded there. b) I agree with Robe

Re: [openstack-dev] [Horizon] request to review bug 1301359

On 08/07/14 08:29, Harshada Kakad wrote:> > HI All, > Could someone please, review the bug [...] Hello Harshada, please don't send such e-mails or ask in the IRC, submitting the patch is enough to get reviewers to read it, eventually. If we sent such an e-mail for every patch, this mailing list

Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

I once used update-initramfs under ubuntu, building ramdisk to boot from remote iscsi disk. - 韦远科 3479 中国科学院 计算机网络信息中心 On Tue, Jul 8, 2014 at 12:15 PM, Adam Young wrote: > On 07/07/2014 01:16 PM, Victor Lowther wrote: > > As on

Re: [openstack-dev] [Heat] Upwards-compatibility for HOT

On 8 July 2014 01:25, Zane Bitter wrote: > With the Icehouse release we announced that there would be no further > backwards-incompatible changes to HOT without a revision bump. However, I > notice that we've already made an upward-incompatible change in Juno: > > https://review.openstack.org/#/c

<    1   2