[openstack-dev] [Nova] Drop the Amazon specific flavor prefix "m1." from OpenStack flavor names

This is regarding the bug https://bugs.launchpad.net/nova/+bug/1161988 I think we should drop the Amazon specific flavor prefix "m1." from OpenStack flavor names because they have no meaning in OpenStack where each deployment uses different hardware. Amazon has the M1 prefix to denote high memo

Re: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

On 25/11/13 16:50 -0600, Dolph Mathews wrote: On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco wrote: On 25/11/13 09:28 +1000, Jamie Lennox wrote: So the way we have this in keystone at least is that querying GET / will return all available API versions and querying /v2

Re: [openstack-dev] [Keystone][Oslo] Future of Key Distribution Server, Trusted Messaging

On Tue, Nov 26, 2013 at 5:25 AM, Adam Young wrote: > Back in the Day, Barbican was just one Service of Cloud Keep. While I > would say that KDS belongs in the Cloud Keep, it is not the same as, and > should not be deployed with Barbican. Is it possible to keep them as > separate services? I th

Re: [openstack-dev] Gate broken right now

On 26/11/13 00:55 -0600, Alex Gaynor wrote: Hi all, Right now there appears to be an issue in the gate whereby all python2.6 jobs break. This is resulting in a massive amount of churn for the gate, which has it basically at a standstill. It's 1AM in the US central time, and I wasn't able to fin

Re: [openstack-dev] [Keystone] Keystone client support for Py3K

On 25/11/13 15:46 -0500, Chuck Short wrote: Hi, There is a gate for python-keystoneclient for py33. I have been trying to port it over to python3 but its blocked on httpretty right now not being pyhon3 compatible. Erm, I checked a patch yday and didn't see the gate, I rechecked today and now t

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On 25/11/13 21:24 -0600, Dolph Mathews wrote: On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins wrote: This has been mentioned in other threads, but I thought I'd call it out and make it an explicit topic. We have over 100 recheck bugs open on http://status.openstack.org/rechecks/ -

Re: [openstack-dev] Gate broken right now

On Tue, Nov 26, 2013 at 9:52 AM, Flavio Percoco wrote: > This seems to be the issue you're talking about, is it? > > http://logs.openstack.org/49/57049/2/gate/gate-swift- > python26/c1aedf1/console.html > Thanks for the heads up indeed, I was wondering if there was somebody on shift/awake from i

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

> -Original Message- > From: Russell Bryant [mailto:rbry...@redhat.com] > Sent: 25 November 2013 22:37 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and > deprecation plan > > On 11/25/2013 05:19 PM, Matt Riedemann wrote: > > I'll p

Re: [openstack-dev] EC2 Filter

Oh hai! That's nice to hear! I would like to help by adapting this patch set to latest and I will try to work out the tempest test cases. Is there any form of documentation for new developers? Thanks in advance Sebastian -- Sebastian Porombka, M.Sc. Zentrum für Informations- und Medientech

Re: [openstack-dev] Fw: [Neutron][IPv6] Meeting logs from the first IRC meeting

Hi ShiXiong, I have reviewed the code you submitted in Community. Some comments, please to fix it. Also I think we need more discuss with Sean about Neutron support DHCPv6, before this, please review Sean and my code change for Neutron support DHCPv6: https://review.openstack.org/#/c/56184/4 a

Re: [openstack-dev] [horizon] JavaScript use policy

On 25/11/13 18:29, Lyle, David wrote: > We have been having this discussion here on the mailing list [1][2] and also > in the Horizon team meetings [3]. > > The overall consensus has been that we are going to move forward with a > JavaScript requirement. [...] > [1] > http://lists.openstack.o

Re: [openstack-dev] Gate broken right now

Indeed, Climate is also impacted. Is there a bug already open or shall I create one ? -Sylvain Le 26/11/2013 10:46, Chmouel Boudjnah a écrit : On Tue, Nov 26, 2013 at 9:52 AM, Flavio Percoco > wrote: This seems to be the issue you're talking about, is it?

Re: [openstack-dev] Gate broken right now

http://zuul.openstack.org/rechecks is not mentioning it by the way. Le 26/11/2013 11:32, Sylvain Bauza a écrit : Indeed, Climate is also impacted. Is there a bug already open or shall I create one ? -Sylvain Le 26/11/2013 10:46, Chmouel Boudjnah a écrit : On Tue, Nov 26, 2013 at 9:52 AM, Fl

Re: [openstack-dev] Gate broken right now

Created https://bugs.launchpad.net/openstack-ci/+bug/1255041 Le 26/11/2013 11:34, Sylvain Bauza a écrit : http://zuul.openstack.org/rechecks is not mentioning it by the way. Le 26/11/2013 11:32, Sylvain Bauza a écrit : Indeed, Climate is also impacted. Is there a bug already open or shall I c

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

Dolph Mathews wrote: > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins > mailto:robe...@robertcollins.net>> wrote: > > So my proposal is that we make it part of the base hygiene for a > project that any recheck bugs being seen (either by elastic-recheck or > manual inspection) be consi

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On Tue, Nov 26, 2013 at 7:37 PM, Flavio Percoco wrote: > On 25/11/13 21:24 -0600, Dolph Mathews wrote: > >> >> On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins < >> robe...@robertcollins.net> >> wrote: >> I agree with the notion here (that fixing transient failures is >> critically high >> priorit

Re: [openstack-dev] tenant or project

On Mon, Nov 25, 2013 at 7:50 PM, Flavio Percoco wrote: > On 24/11/13 12:47 -0500, Doug Hellmann wrote: > >> >> >> >> On Sun, Nov 24, 2013 at 12:08 AM, Morgan Fainberg >> wrote: >> >>In all honesty it doesn't matter which term we go with. As long as we >> are >>consistent and define the

Re: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

Nottingham's RFC is exceptionally well documented. I would be strongly against Marconi moving from that RFC to any other format unless the alternative was equally well documented. If they were equally well documented, then I would be neutral on changing it. More importantly, if a project is pro

Re: [openstack-dev] [horizon] Javascript development improvement

On 11/22/2013 06:13 PM, Julie Pichon wrote: "Imre Farkas" wrote: On 11/22/2013 02:49 PM, Maxime Vidori wrote: It seems a bit crazy to me to introduce NodeJS as a dependency just for the sake of an easy way to run jslint. There are other options available that run without NodeJS as a dependency

Re: [openstack-dev] How to stage client major releases in Gerrit?

Mark Washenberger wrote: > > FWIW, I don't think the changes glanceclient needs in v1 will > break the > > 'B' case above. But it does raise a question--if they did, would it be > > sufficient to backport a change to adapt old supported stable B > versions > > of, say, Nova,

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On 11/25/2013 08:00 PM, Matt Riedemann wrote: > On Monday, November 25, 2013 4:37:29 PM, Russell Bryant wrote: >> I think the short answer is, "whatever we're running against all Nova >> changes in the gate". > > Maybe a silly question, but is what is run against the check queue any > different fr

Re: [openstack-dev] [Nova] Drop the Amazon specific flavor prefix "m1." from OpenStack flavor names

On 11/26/2013 03:06 AM, Rohan Kanade wrote: > This is regarding the bug https://bugs.launchpad.net/nova/+bug/1161988 > > I think we should drop the Amazon specific flavor prefix "m1." from > OpenStack flavor names > because they have no meaning in OpenStack where each deployment uses > different

Re: [openstack-dev] [Nova] Are BIOS strings configured in Hyper-V & ESX similar to KVM instantiated VMs?

It's not certain that this will be implemented for the XenAPI driver. Our view is that the BIOS strings shouldn't be relied upon - the hypervisor can clearly set them to anything so it's not really a reliable way to configure the application. Also note that in some scenarios, such as PV guests

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

I'm sorry to restart this topic. I don't mind if we upgrade to 0.1.8, but then I will need to have patches for Havana to support version 0.1.8. Otherwise, it's going to be very difficult on the packaging side: I will need to upload 0.1.8 for Icehouse, but then it will break everything else (eg: Ha

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On 11/26/2013 04:48 AM, Bob Ball wrote: >> -Original Message- >> From: Russell Bryant [mailto:rbry...@redhat.com] >> Sent: 25 November 2013 22:37 >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and >> deprecation plan >> >> On 11/25/

Re: [openstack-dev] Unwedging the gate

On 11/25/2013 09:14 PM, James E. Blair wrote: > Joe Gordon writes: > >> On Sun, Nov 24, 2013 at 10:48 PM, Robert Collins >> wrote: >> >>> On 25 November 2013 19:25, Joe Gordon wrote: On Sun, Nov 24, 2013 at 9:58 PM, Robert Collins < >>> robe...@robertcollins.net> wrote:

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On 11/25/2013 10:24 PM, Dolph Mathews wrote: > > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins > mailto:robe...@robertcollins.net>> wrote: > > This has been mentioned in other threads, but I thought I'd call it > out and make it an explicit topic. > > We have over 100 recheck bugs

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

Hello, seems too big to do the inline comments, so just a few notes here: If we truly want to have Templates portable, it would mean to have the 'metadata' somehow standardised, right? Otherwise if every UI will add their own metadata, then I hardly see the templates as portable. I think first

Re: [openstack-dev] [Ceilometer][qa] Tenant isolation - IntegrityError exception

Hi Nejc, Apologies for the delay in responding, I'm just getting to grips with Tempest myself. So the problem here is nothing to do with whether the tenant exists in keystone, in fact creating an alarm with a completely fictitious project_id will work just fine in general. Rather it appears to

Re: [openstack-dev] [horizon] Javascript development improvement

I made a little POC about Nodejs integration with its task runner Grunt https://review.openstack.org/58525 It is easy to configure and override, we have more flexibility with this solution. Running Selenium which will run Firefox which will launch an html page with js embedded seems really ove

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

> -Original Message- > From: Russell Bryant [mailto:rbry...@redhat.com] > Sent: 26 November 2013 13:56 > To: openstack-dev@lists.openstack.org > Cc: Sean Dague > Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and > deprecation plan > > On 11/26/2013 04:48 AM, Bob Ball wrote:

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On 11/26/2013 09:38 AM, Bob Ball wrote: >> -Original Message- >> From: Russell Bryant [mailto:rbry...@redhat.com] >> Sent: 26 November 2013 13:56 >> To: openstack-dev@lists.openstack.org >> Cc: Sean Dague >> Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and >> deprecation pl

Re: [openstack-dev] Adding notifications to Horizon

Thanks for your feedback. Sandy, thank you for the link. I agree that the .start/.end notification pattern that you propose seems to be the most appropriate to monitor actions launched through the Horizon dashboard. In the case of .start/.end notifications, the decorator should do the job an

Re: [openstack-dev] [Ironic][Ceilometer] get IPMI data for ceilometer

> 2. Not sure if our Ceilometer only accept the signed-message, if it is case, how Ironic get the message trust for Ceilometer, and send the valid message which can be accepted by Ceilometer Collector? > I'm not sure it's appropriate for ironic to be sending messages using ceilometer's sample f

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On Tue, Nov 26, 2013 at 03:04:12PM +0100, Ladislav Smola wrote: > Hello, > > seems too big to do the inline comments, so just a few notes here: > > If we truly want to have Templates portable, it would mean to have > the 'metadata' somehow standardised, right? > Otherwise if every UI will add the

Re: [openstack-dev] [Nova] Are BIOS strings configured in Hyper-V & ESX similar to KVM instantiated VMs?

It is basically used to tailor the boot sequence if the VM gets booted in OpenStack. For ex. it could do the following 1. Get IP through DHCP if booted in OpenStack 2. Read config drive or contact metadata service and init the system if booted in OpenStack Thanks, Vijay V. From:

Re: [openstack-dev] [Neutron][LBaaS] SSL Termination write-up

Hi, I've updated the wiki page Please see and comment https://wiki.openstack.org/wiki/Neutron/LBaaS/SSL Thanks, Evg -Original Message- From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com] Sent: Wednesday, November 20, 2013 4:17 PM To: Samuel Bercovici; OpenStack Development

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On 11/26/2013 09:56 AM, Russell Bryant wrote: > On 11/26/2013 09:38 AM, Bob Ball wrote: >>> -Original Message- >>> From: Russell Bryant [mailto:rbry...@redhat.com] >>> Sent: 26 November 2013 13:56 >>> To: openstack-dev@lists.openstack.org >>> Cc: Sean Dague >>> Subject: Re: [openstack-dev]

Re: [openstack-dev] [Tempest] Drop python 2.6 support

On 11/25/2013 09:37 PM, Matt Riedemann wrote: On Monday, November 25, 2013 7:35:51 AM, Zhi Kun Liu wrote: Does that mean Tempest could not run on python 2.6 in the future? Well so if you're running a single-node setup of OpenStack on a VM on top of RHEL 6 and running Tempest from there, yeah,

Re: [openstack-dev] [nova] Core pinning

Tuomas, > I haven't but I will write a blueprint for the core pinning part. Can’t wait to see it! > Are you using extra specs for carrying cpuset attributes in your > implementation? Yes, exactly. Although we're using slightly different syntax to update flavor, for example: $ nova flavor-key s

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On Tue, Nov 26, 2013 at 5:23 AM, Thierry Carrez wrote: > Dolph Mathews wrote: > > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins > > mailto:robe...@robertcollins.net>> wrote: > > > > So my proposal is that we make it part of the base hygiene for a > > project that any recheck bugs being s

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

On Tuesday, November 26, 2013 10:07:02 AM, Sean Dague wrote: On 11/26/2013 09:56 AM, Russell Bryant wrote: On 11/26/2013 09:38 AM, Bob Ball wrote: -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: 26 November 2013 13:56 To: openstack-dev@lists.openstack.org Cc:

Re: [openstack-dev] [Keystone][Marconi][Oslo] Discoverable home document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in Nova)

On Tue, Nov 26, 2013 at 2:47 AM, Flavio Percoco wrote: > On 25/11/13 16:50 -0600, Dolph Mathews wrote: > >> >> On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco >> wrote: >> >>On 25/11/13 09:28 +1000, Jamie Lennox wrote: >> >>So the way we have this in keystone at least is that queryin

[openstack-dev] [Neutron] Rename 'tenant' to 'project' as per Keystone?

Keystone is almost finished replacing the term 'tenant' with 'project' (see recent thread https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg09709.html) and we might want to think about how and when Neutron makes a similar transition. It's an unlikely priority in the near term

[openstack-dev] Hyper-V meeting cancelled.

Hi All, Key individuals are out on vacation this week. We will resume next week. p Peter J. Pouliot CISSP Sr. SDET OpenStack Microsoft New England Research & Development Center 1 Memorial Drive Cambridge, MA 02142 P: 1.(857).4536436 E: ppoul...@microsoft.com

Re: [openstack-dev] [Tempest] Drop python 2.6 support

Giulio, are you speaking for Red Hat here, or is this just your opinion? And have you actually tried to doing what you propose? Regards, -peter On Tue, Nov 26, 2013 at 11:18 AM, Giulio Fidente wrote: > On 11/25/2013 09:37 PM, Matt Riedemann wrote: >> >> On Monday, November 25, 2013 7:35:51 AM, Z

Re: [openstack-dev] [Glance] Interested in a mid-Icehouse Glance mini-summit?

On Mon, Nov 25, 2013 at 10:47 PM, Boris Pavlovic wrote: > Mark, > > > Why we are not able to combine this and Nova meetup in the same place in > the same time? > > The two events are being planned and sponsored separately. Maybe in the future it will make sense to merge them to ease travel difficu

[openstack-dev] [Glance] Meeting cancelled this week

Hi folks, Our normally scheduled meeting this week will not be held, since it would coincide with a major U.S. holiday and I'll be busy at that time stuffing my face with turkey and a wide variety of starches. We'll pick up where we left off next week during our normal timeslot (which is at 1400

[openstack-dev] [Neutron][Tempest] Heat template for services

Hi Summit, Eugene We have submitted a Heat template for advanced services. This is combination of LBaaS, FWaaS and VPN. This is a also good demo for how to use neutron services. https://review.openstack.org/#/c/58496/1 It is great if we could get feedback from yours. FYI, here is existing heat

Re: [openstack-dev] Gate broken right now

Chmouel Boudjnah writes: > On Tue, Nov 26, 2013 at 9:52 AM, Flavio Percoco wrote: > >> This seems to be the issue you're talking about, is it? >> >> http://logs.openstack.org/49/57049/2/gate/gate-swift- >> python26/c1aedf1/console.html >> > > Thanks for the heads up indeed, I was wondering if th

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

Excerpts from Thierry Carrez's message of 2013-11-26 03:23:51 -0800: > Dolph Mathews wrote: > > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins > > mailto:robe...@robertcollins.net>> wrote: > > > > So my proposal is that we make it part of the base hygiene for a > > project that any rechec

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 26/11/13 03:26, Keith Bray wrote: On 11/25/13 5:46 PM, "Clint Byrum" wrote: Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800: Hi Steve, As one of the UI developers driving the requirements behind these new blueprints I wanted to take a moment to assure you and the rest o

Re: [openstack-dev] tenant or project

Can we get a TC policy that 'project' is the standard and that all projects using tenant should plan a smooth migration path to project along with the timescales for implementation and retirement of tenant ? Tim From: Christopher Yeoh [mailto:cbky...@gmail.com] Sent: 26 November 2013 12:48 To:

[openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

Greetings, I would like to propose that we re-add Dan Prince to the nova-core review team. Dan Prince has been involved with Nova since early in OpenStack's history (Bexar timeframe). He was a member of the nova-core review team from May 2011 to June 2013. He has since picked back up with nova

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

+1 On Wed, Nov 27, 2013 at 6:32 AM, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review

Re: [openstack-dev] [Glance] Interested in a mid-Icehouse Glance mini-summit?

On 11/26/2013 12:39 PM, Mark Washenberger wrote: > > > > On Mon, Nov 25, 2013 at 10:47 PM, Boris Pavlovic > wrote: > > Mark, > > > Why we are not able to combine this and Nova meetup in the same > place in the same time? > > > The two events are b

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

Hello. On Fri, Nov 22, 2013 at 1:11 PM, Flavio Percoco wrote: >1) Store the commit sha from which the module was copied from. > I would suggest we don't duplicate this in every project's repo. It is possible to find using the contents of the modules currently in project's repo the correspo

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

+1 >-Original Message- >From: Russell Bryant [mailto:rbry...@redhat.com] >Sent: Tuesday, November 26, 2013 11:33 AM >To: OpenStack Development Mailing List >Subject: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova- >core > >Greetings, > >I would like to propose that we re-add

Re: [openstack-dev] [infra] Meeting Tuesday November 26th at 19:00 UTC

On Mon, Nov 25, 2013 at 11:02 AM, Elizabeth Krumbach Joseph wrote: > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting tomorrow, Tuesday November 26th, at 19:00 UTC in > #openstack-meeting Minutes: http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-11-26-19.02.

[openstack-dev] [Solum] Definition feedback

Hi All, Few comments on the Definitions blueprint [1]: 1. I'd propose to alter the term 'Application' to either 'Application Package' or 'Package'. Application isn't very descriptive and can be confusing to some with the actual deployed instance, etc. 2. It should be possible for the package

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On Nov 26, 2013 8:48 AM, "Dolph Mathews" wrote: > > > On Tue, Nov 26, 2013 at 5:23 AM, Thierry Carrez wrote: >> >> Dolph Mathews wrote: >> > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins >> > mailto:robe...@robertcollins.net>> wrote: >> > >> > So my proposal is that we make it part of the b

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

+1 On 26/11/13 20:32, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review team > from M

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

+1 On Nov 26, 2013, at 11:32 AM, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

On Nov 26, 2013 11:37 AM, "Russell Bryant" wrote: > > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review team >

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

> My overall concern, and I think the other guys doing this for virt > drivers will agree, is trying to scope down the exposure to unrelated > failures. But, if it's not related to your driver, then it also failed in the upstream gate, right? If it didn't fail the upstream gate, then it is some we

[openstack-dev] [nova] [QA] Triaging Bugs during Review

Hi Everyone, I tend to follow merges and look for valuable havana backports. A few bug fixes have merged recently where the associated bug is untriaged (i.e. the severity is listed as 'Unknown'). I assume that reviewers of a bugfix patch are viewing the associated bugs. It makes sense for core-rev

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

So the originally question that I attempted to pose was, "Can we add a schema-less metadata section to the template that can be used for a variety of purposes?". It looks like the answer is no, we need to discuss the features that would go in the metadata section and add them to the HOT specificati

Re: [openstack-dev] [Neutron][Tempest] Heat template for services

On 11/27/2013 07:16 AM, Nachi Ueno wrote: > Hi Summit, Eugene > > We have submitted a Heat template for advanced services. > This is combination of LBaaS, FWaaS and VPN. > This is a also good demo for how to use neutron services. > > https://review.openstack.org/#/c/58496/1 > > It is great if we co

Re: [openstack-dev] Fw: [Neutron][IPv6] Meeting logs from the first IRC meeting

On Tue, Nov 26, 2013 at 06:07:07PM +0800, Da Zhao Y Yu wrote: > Sean, what about your progress? I saw your code change jekins still in > failed status. Hi, I've been busy tracking down the IPv6 issue in our lab environment - we were using the Hybrid OVS driver in our Nova.conf and that was break

Re: [openstack-dev] [nova] [QA] Triaging Bugs during Review

I wonder how hard it would be to add bug information to gerrit to make the state of the bug being fixed more obvious? Just a random idea. Michael On Wed, Nov 27, 2013 at 8:06 AM, Vishvananda Ishaya wrote: > Hi Everyone, > > I tend to follow merges and look for valuable havana backports. A few b

Re: [openstack-dev] [Neutron][Tempest] Heat template for services

Hi Steve Thank you for your input. I agree with you. We added "apache, mysql and wordpress" for this review, because heat-template is a show-case for example template. I agree with you, we can start a process of simplehttpserver in meta data script for LBaaS test. Best Nachi 2013/11/26 Steve B

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell wrote: > So the originally question that I attempted to pose was, "Can we add a > schema-less metadata section to the template that can be used for a > variety of purposes?". It looks like the answer is no, we need to discuss > the features that would g

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

On 11/26/2013 02:32 PM, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review team > from

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

On Tue, 2013-11-26 at 14:32 -0500, Russell Bryant wrote: > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review t

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 11/27/2013 10:24 AM, Tim Schnell wrote: > So the originally question that I attempted to pose was, "Can we add a > schema-less metadata section to the template that can be used for a > variety of purposes?". It looks like the answer is no, we need to discuss > the features that would go in the m

Re: [openstack-dev] [nova] [QA] Triaging Bugs during Review

On 11/26/2013 04:06 PM, Vishvananda Ishaya wrote: > Hi Everyone, > > I tend to follow merges and look for valuable havana backports. A > few bug fixes have merged recently where the associated bug is > untriaged (i.e. the severity is listed as 'Unknown'). I assume that > reviewers of a bugfix patc

Re: [openstack-dev] [nova] [QA] Triaging Bugs during Review

On Tue, 2013-11-26 at 13:06 -0800, Vishvananda Ishaya wrote: > Hi Everyone, > > I tend to follow merges and look for valuable havana backports. A few bug > fixes have merged recently where the associated bug is untriaged (i.e. the > severity is listed as 'Unknown'). I assume that reviewers of a bu

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 11/27/2013 11:02 AM, Christopher Armstrong wrote: > On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell > mailto:tim.schn...@rackspace.com>> wrote: > > > > Use Case #3 > Grouping parameters would help the client make smarter decisions > about how > to display the parameters for input

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

From: Christopher Armstrong mailto:chris.armstr...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, November 26, 2013 4:02 PM To: "OpenStack Development Mailing List (not for usage questions)" mail

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

From: Steve Baker mailto:sba...@redhat.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, November 26, 2013 4:29 PM To: "openstack-dev@lists.openstack.org" mailto:open

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On Tue, 2013-11-26 at 12:29 -0800, Joe Gordon wrote: > On Nov 26, 2013 8:48 AM, "Dolph Mathews" wrote: > > > > > > On Tue, Nov 26, 2013 at 5:23 AM, Thierry Carrez > wrote: > >> > >> Dolph Mathews wrote: > >> > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins > >> > mailto:robe...@robertcollins.net

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell wrote: > >From: Christopher Armstrong > > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Tuesday, November 26, 2013 4:02 PM > > To: "OpenStack Development Mailing List (not fo

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 11/26/13 4:16 PM, "Steve Baker" wrote: >On 11/27/2013 10:24 AM, Tim Schnell wrote: >> So the originally question that I attempted to pose was, "Can we add a >> schema-less metadata section to the template that can be used for a >> variety of purposes?". It looks like the answer is no, we need

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell mailto:tim.schn...@rackspace.com>> wrote: From: Christopher Armstrong mailto:chris.armstr...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, November

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

On Fri, 2013-11-22 at 12:39 -0500, Doug Hellmann wrote: > On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco wrote: > > > Greetings, > > > > Based on the recent discussion that came out about not having enough > > information in the commit message when syncing oslo-incubator modules, > > I was think

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

On Fri, 2013-11-22 at 16:24 +, Duncan Thomas wrote: > On 22 November 2013 14:59, Ben Nemec wrote: > > > One other thought I had was to add the ability to split one Oslo sync up > > into multiple commits, either one per module, or even one per Oslo commit > > for some really large module chang

Re: [openstack-dev] [TripleO] Summit session wrapup

On 26 November 2013 07:41, Jaromir Coufal wrote: > Hey Rob, > > can we add 'Slick Overcloud deployment through the UI' to the list? There > was no session about that, but we discussed it afterwords and agreed that it > is high priority for Icehouse as well. > > I just want to keep it on the list,

Re: [openstack-dev] [keystone] Service scoped role definition

Hi David, Thanks for your time and valuable comments. I have replied to your comments and try to explain why I am advocating to this BP. Let me know your thoughts, please feel free to update below etherpad https://etherpad.openstack.org/p/service-scoped-role-definition Thanks again, Arvind

Re: [openstack-dev] [nova] [QA] Triaging Bugs during Review

On Nov 26, 2013, at 2:26 PM, Mark McLoughlin wrote: > On Tue, 2013-11-26 at 13:06 -0800, Vishvananda Ishaya wrote: >> Hi Everyone, >> >> I tend to follow merges and look for valuable havana backports. A few bug >> fixes have merged recently where the associated bug is untriaged (i.e. the >> sev

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 26/11/13 22:55 +, Tim Schnell wrote: On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell mailto:tim.schn...@rackspace.com>> wrote: From: Christopher Armstrong mailto:chris.armstr...@rackspace.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev

Re: [openstack-dev] [Solum] Definition feedback

Tom, On Nov 26, 2013, at 12:09 PM, "Tom Deckers (tdeckers)" wrote: > Hi All, > > Few comments on the Definitions blueprint [1]: > > 1. I'd propose to alter the term 'Application' to either 'Application > Package' or 'Package'. Application isn't very descriptive and can be > confusing to s

Re: [openstack-dev] How to best make User Experience a priority in every project

On Wed, 2013-11-20 at 11:06 -0600, Dean Troyer wrote: > On Wed, Nov 20, 2013 at 9:09 AM, Thierry Carrez wrote: > > > However, as was apparent in the Technical Committee meeting discussion > > > about it yesterday, most of us are not convinced that establishing and > > blessing a separate team is t

Re: [openstack-dev] [heat][horizon]Heat UI related requirements & roadmap

On 11/26/13 5:24 PM, "Angus Salkeld" wrote: >On 26/11/13 22:55 +, Tim Schnell wrote: >> >>On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell >>mailto:tim.schn...@rackspace.com>> wrote: >> >>From: Christopher Armstrong >>mailto:chris.armstr...@rackspace.com>> >> >>Reply-To: "OpenStack Development M

Re: [openstack-dev] [keystone] Service scoped role definition

Hi Adam, Based on our discussion over IRC, I have updated the below etherpad with proposal for nested role definition https://etherpad.openstack.org/p/service-scoped-role-definition Please take a look @ "Proposal (Ayoung) - Nested role definitions", I am sorry if I could not catch your idea.

Re: [openstack-dev] [Solum] Definition feedback

> On Nov 26, 2013, at 6:30 PM, Adrian Otto wrote: > > Tom, > > On Nov 26, 2013, at 12:09 PM, "Tom Deckers (tdeckers)" > wrote: > >> Hi All, >> >> Few comments on the Definitions blueprint [1]: >> >> 1. I'd propose to alter the term 'Application' to either 'Application >> Package' or 'Pac

[openstack-dev] [Nova] Is there a way for the VM to identify that it is getting booted in OpenStack

Hi, Is there a way for the VM to identify that it is getting booted in OpenStack? As said in the below mail, once the VM knows it is booting in OpenStack it will alter the boot sequence. AWS provides signatures in the BIOS strings. PS: Changed the

Re: [openstack-dev] [Nova] [Infra] Support for PCI Passthrough

On 2013年11月23日 03:43, Jeremy Stanley wrote: Hi, Jeremy for currently, we need setup it up asap, so the third party seems the right way. but i have some concern, if you post -1, you should post testing log somewhere for people to debug it, so does third party testing can post testing log to t

[openstack-dev] [neutron] [ml2] Proposing a new time for the ML2 sub-team meeting

Folks: I'd like to propose moving the weekly ML2 meeting [1]. The new proposed time is Wednesdays at 1600 UTC, and will be in the #openstack-meeting-alt channel. Please respond back if this time conflicts for you, otherwise starting next week on 12-4-2013 we'll have the meeting at the new time. W

Re: [openstack-dev] [Solum] Definition feedback

> On Nov 26, 2013, at 4:20 PM, "Clayton Coleman" wrote: > > > >> On Nov 26, 2013, at 6:30 PM, Adrian Otto wrote: >> >> Tom, >> >> On Nov 26, 2013, at 12:09 PM, "Tom Deckers (tdeckers)" >> wrote: >> >>> Hi All, >>> >>> Few comments on the Definitions blueprint [1]: >>> >>> 1. I'd propo

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing "request identification"

Hi all, I'm also interested in this issue. > Create a unified request identifier > https://blueprints.launchpad.net/nova/+spec/cross-service-request-id I checked this BP and the following review. https://review.openstack.org/#/c/29480/ There are many comments. Finally, this review looks rejecte

  1   2   >