Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

On 12/18/2013 10:33 PM, Gabriel Hurley wrote: > > Adding developers to Horizon Core just for the purpose of reviewing > an incubated umbrella project is not the right way to do things at > all. If my proposal of two separate groups having the +2 power in > Gerrit isn't technically feasible th

Re: [openstack-dev] Diversity as a requirement for incubation

Le 18/12/2013 16:37, Steven Dake a écrit : In the early days of incubation requests, I got the distinct impression managers at companies believed that actually getting a project incubated in OpenStack was not possible, even though it was sparsely documented as an option. Maybe things are dif

Re: [openstack-dev] [Neutron][lbaas] plugin driver

Hi Subrahmanyam, The patch was originally implemented by Oleg Bondarev :) > plugin-driver appears to be specific to driver provider That's correct > How does this work with single common agent and many providers? The idea is that the plugin-driver is server-side logic which defines how neutron-ser

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

Hi Guys, I run into this issue trying to incorporate this test into cross_tenant_connectivity scenario: launching 2 VMs in different tenants What I saw, is that in the gate it fails half the time (the original test passes without issues) and ONLY on the 2nd VM (the first FLIP propagates fine).

Re: [openstack-dev] [heat] Nomination for heat-core

> I would like to nominate Bartosz Górski to be a heat-core reviewer. His > reviews to date have been valuable and his other contributions to the > project have shown a sound understanding of how heat works. > > Here is his review history: > https://review.openstack.org/#/q/reviewer:bartosz.gors

Re: [openstack-dev] [neutron][policy] Policy-Rules discussions based on Dec.12 network policy meeting

On Dec 17, 2013 3:22 PM, "Tim Hinrichs" wrote: > > > > - Original Message - > | From: "Prasad Vellanki" > | To: "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org> > | Sent: Monday, December 16, 2013 2:11:37 PM > | Subject: Re: [openstack-de

[openstack-dev] [Ironic] Yuriy Zveryanskyy for ironic-core?

Yuriy seems to have been doing reviews consistently over the last three months, is catching plenty of issues. He isn't catching everything, but I think he catches approximately as much as other cores - none of us catch everything. -Rob -- Robert Collins Distinguished Technologist HP Converged

Re: [openstack-dev] [neutron][policy] Policy-Rules discussions based on Dec.12 network policy meeting

On Tue, Dec 17, 2013 at 7:34 PM, Stephen Wong wrote: > Hi Prasad, > > Thanks for the comments, please see responses inline. > > On Mon, Dec 16, 2013 at 2:11 PM, Prasad Vellanki > wrote: > > Hi > > Please see inline > > > > > > On Sun, Dec 15, 2013 at 8:49 AM, Stephen Wong > wrote: > >>

[openstack-dev] [Neutron][IPv6] Blueprint Bind dnsmasq in qrouter- namespace

I am reading through the blueprint created by Randy to bind dnsmasq into qrouter- namespace: https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace I don't think I can follow the reason that we need to change the namespace which contains dnsmasq process and the device

Re: [openstack-dev] [heat] Nomination for heat-core

On Thu, Dec 19, 2013 at 03:21:46PM +1300, Steve Baker wrote: > I would like to nominate Bartosz Górski to be a heat-core reviewer. His > reviews to date have been valuable and his other contributions to the > project have shown a sound understanding of how heat works. > > Here is his review histor

[openstack-dev] meeting times and rotations etc...

So, I'm a little worried about the complexities of organising free slots given we're basically about to double the # of entrieshave in all our calendars. Maybe we can do something a little simpler: just have the *whole calender* shift phase 180' each week: it won't be perfect, particularly for tho

Re: [openstack-dev] meeting times and rotations etc...

Another option would be to use what we already have to our benefit. Instead of trying to provision two meeting rooms (-meeting and -meeting-alt), use the various other IRC channels that we already have for team meetings. This would allow for meetings to be at the same time, but it would free up

Re: [openstack-dev] [tuskar] How to install tuskar-ui from packaging point of view

On 16/12/13 04:47, Thomas Goirand wrote: [snip] > As for tuskar-ui, the install.rst is quite vague about how to install. I > got the python-tuskar-ui binary package done, with egg-info and all, > that's not the problem. What worries me is this part: [snip] Hello Thomas, sorry for the late repl

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 14/12/13 16:51, Jay Pipes wrote: [snip] > Instead of focusing on locking issues -- which I agree are very > important in the virtualized side of things where resources are > "thinner" -- I believe that in the bare-metal world, a more useful focus > would be to ensure that the Tuskar API servic

[openstack-dev] [Neutron][LBaaS] Weekly subteam meeting at Thursday, 19.12, 14-00 UTC

Hi lbaas folks, Let's meet as usual at #openstack-meeting on Thursday, 19 at 14-00 UTC. The primary discussion points should be: 1) Third party testing, test scenarios 2) L7 rules 3) HA for agents and HA for HAProxy 4) SSL termination Thanks, Eugene ___

Re: [openstack-dev] meeting times and rotations etc...

On 19/12/13 01:28 -0800, John Dickinson wrote: Another option would be to use what we already have to our benefit. Instead of trying to provision two meeting rooms (-meeting and -meeting-alt), use the various other IRC channels that we already have for team meetings. This would allow for meeti

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

On 12/18/2013 10:54 PM, Jay Pipes wrote: > On 12/18/2013 10:21 PM, Brent Eagles wrote: >> Hi, >> >> Yair and I were discussing a change that I initiated and was >> incorporated into the test_network_basic_ops test. It was intended as a >> configuration control point for floating IP address assignme

Re: [openstack-dev] meeting times and rotations etc...

Robert Collins wrote: > So, I'm a little worried about the complexities of organising free > slots given we're basically about to double the # of entrieshave in > all our calendars. I don't think that's what we are about to do, as I don't expect every single meeting to implement a rotation. As I s

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

On 12/19/2013 03:31 AM, Yair Fried wrote: > Hi Guys, > I run into this issue trying to incorporate this test into > cross_tenant_connectivity scenario: > launching 2 VMs in different tenants > What I saw, is that in the gate it fails half the time (the original > test passes without issues) and ONL

Re: [openstack-dev] [Ironic] Yuriy Zveryanskyy for ironic-core?

I up-vote this election. Yuri doing much reviews, moreover he is mostly working on "core" ironic features, so he is more likely will spot architectural problems. Best regards, Max Lobur, Python Developer, Mirantis, Inc. Mobile: +38 (093) 665 14 28 Skype: max_lobur 38, Lenina ave. Kharkov, Ukrain

Re: [openstack-dev] meeting times and rotations etc...

On 12/19/2013 04:28 AM, John Dickinson wrote: > Another option would be to use what we already have to our benefit. Instead > of trying to provision two meeting rooms (-meeting and -meeting-alt), use the > various other IRC channels that we already have for team meetings. This would > allow for

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Apologies for being late onto this thread, and not making the meeting the other day. Also apologies this is almost totally a top post. On 17 December 2013 15:09, Ian Wells wrote: > Firstly, I disagree that > https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support is an accurate > reflection

Re: [openstack-dev] [Nova] Future meeting times

+1 to 14:00 meeting, I can always make those. I can probably make some of the 21:00 meetings But probably only in the summer when its UTC+1 over here. John On 19 December 2013 07:49, Day, Phil wrote: > +1, I would make the 14:00 meeting. I often have good intention of making the > 21:00 meeting

Re: [openstack-dev] Incubation Request for Barbican

On 12/19/2013 12:10 AM, Mike Perez wrote: > On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez > wrote: > I reviewed the TC meeting notes, and my question still stands. > > It seems the committee is touching on the point of there being a worry > because if > it's a single com

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

On 12/19/2013 08:58 AM, Matthias Runge wrote: On 12/18/2013 10:33 PM, Gabriel Hurley wrote: Adding developers to Horizon Core just for the purpose of reviewing an incubated umbrella project is not the right way to do things at all. If my proposal of two separate groups having the +2 power in G

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

John: > At a high level: > > Neutron: > * user wants to connect to a particular neutron network > * user wants a super-fast SRIOV connection Administration: > * needs to map PCI device to what neutron network the connect to > The big question is: > * is this a specific SRIOV only (provider) netwo

[openstack-dev] [savanna] team meeting Dec 19 1800 UTC

Hi folks, We'll be having the Savanna team meeting as usual in #openstack-meeting-alt channel. Additionally, we are canceling our next two weekly meetings - Dec 26 and Jan 2. Agenda: https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_December.2C_19 http://www.timeanddate.com/worl

Re: [openstack-dev] [TripleO][Tuskar] Icehouse Requirements

On 11/12/13 21:42, Robert Collins wrote: > On 12 December 2013 01:17, Jaromir Coufal wrote: >> On 2013/10/12 23:09, Robert Collins wrote: [snip] >>> Thats speculation. We don't know if they will or will not because we >>> haven't given them a working system to test. >> >> Some part of that is sp

[openstack-dev] [Climate] Next two weekly meetings cancelled ?

Hi team, I won't be able to attend the next two weekly meetings (23Dec and 30Dec), I would like to postpone our meetings till 6th January 2014. Any objections to this ? -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http:/

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 19 December 2013 12:21, Ian Wells wrote: > > John: >> >> At a high level: >> >> Neutron: >> * user wants to connect to a particular neutron network >> * user wants a super-fast SRIOV connection >> >> Administration: >> * needs to map PCI device to what neutron network the connect to >> >> The b

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

Howdy, yup, agreed. Additionally, I'd like to start a discussion about new meeting time that'd be more US-folks friendly. Thanks. On Thu, Dec 19, 2013 at 4:49 PM, Sylvain Bauza wrote: > Hi team, > > I won't be able to attend the next two weekly meetings (23Dec and 30Dec), > I would like to pos

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 19 December 2013 12:54, John Garbutt wrote: > On 19 December 2013 12:21, Ian Wells wrote: >> >> John: >>> >>> At a high level: >>> >>> Neutron: >>> * user wants to connect to a particular neutron network >>> * user wants a super-fast SRIOV connection >>> >>> Administration: >>> * needs to map

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

I have Christmas holidays till 12th January... So I don't really know I if I will be available 6th Jan. On Thu, Dec 19, 2013 at 4:49 PM, Sylvain Bauza wrote: > Hi team, > > I won't be able to attend the next two weekly meetings (23Dec and 30Dec), > I would like to postpone our meetings till 6th

Re: [openstack-dev] [Neutron][IPv6] Blueprint Bind dnsmasq in qrouter- namespace

First, dnsmasq is not being "moved". Instead, it's a different instance for the attached subnet in the qrouter namespace. If it's not in the qrouter namespace, the default gateway (the local router interface) will be the interface of qdhcp namespace interface. That will cause blackhole for traff

Re: [openstack-dev] [Neutron][IPv6] Blueprint Bind dnsmasq in qrouter- namespace

Hi, Xuhan: Thanks for reaching out to us for questions! Here are the summary of several key points: 1. Currently dnsmasq is bound to the ns- interface within qdhcp- namespace. If we continue to use this model, then the announced RA has to use the ns- interface’s link-local address as source, b

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Hi John, I totally agree that we should define the use cases both for administration and tenant that powers the VM. Since we are trying to support PCI pass-through network, let's focus on the related use cases. Please see my comments inline. Regards, Irena -Original Message- From: John G

Re: [openstack-dev] [heat] Nomination for heat-core

On 12/19/2013 10:21 AM, Steve Baker wrote: I would like to nominate Bartosz Górski to be a heat-core reviewer. His reviews to date have been valuable and his other contributions to the project have shown a sound understanding of how heat works. Here is his review history: https://review.openst

Re: [openstack-dev] [Heat] [Trove] [Savanna] [Oslo] Unified Agents - what is the actual problem?

I agree that enabling communication between guest and cloud service is a common problem for most agent designs. The only exception is agent based on hypervisor provided transport. But as far as I understand many people are interested in network-based agent, so indeed we can start a thread (or conti

Re: [openstack-dev] [neutron] Re: [Blueprint vlan-aware-vms] VLAN aware VMs

On 19 December 2013 06:35, Isaku Yamahata wrote: > > Hi Ian. > > I can't see your proposal. Can you please make it public viewable? > Crap, sorry - fixed. > > Even before I read the document I could list three use cases. Eric's > > covered some of them himself. > > I'm not against trunking. >

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

Le 19/12/2013 13:54, Sergey Lukjanov a écrit : yup, agreed. Additionally, I'd like to start a discussion about new meeting time that'd be more US-folks friendly. Luckily, we do have Internet now : http://

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

Le 19/12/2013 13:57, Dina Belova a écrit : I have Christmas holidays till 12th January... So I don't really know I if I will be available 6th Jan. Oh ok. Who else are still on vacation these times ? We can do our next meeting on 12th Jan, but I'm concerned with the delivery of Climate 0.1 wh

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

I would also like to point out that, since Brent used compute.build_timeout as the timeout value ***It takes more time to update FLIP in nova DB, than for a VM to build*** Yair - Original Message - From: "Sean Dague" To: "OpenStack Development Mailing List (not for usage questions)" S

[openstack-dev] [climate] PTL elections: nominations

Hey all, It was decided to choose the PTL for Climate project and I've volunteered to handle it. All important questions was discussed on the last IRC team meeting [1]. You can find details on a wiki page [2]. So, we'd like to choose PTL for the rest Icehouse release cycle. To announce your candi

[openstack-dev] [neutron] [ml2] Canceling next two weekly meetings

Since the next two Neutron ML2 meetings fall on Dec. 25 and Jan. 1, we'll cancel both and reconvene on Jan. 8. Thanks! Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de

Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow

Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn wrote: > Wouldn't 2200 UTC be in about 20 mins? > > > On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA wrote: > Hi, > > It seems the meeting was not held on 2200 UTC on Wednesday (t

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Response inline... On 19 December 2013 13:05, Irena Berezovsky wrote: > Hi John, > I totally agree that we should define the use cases both for administration > and tenant that powers the VM. > Since we are trying to support PCI pass-through network, let's focus on the > related use cases. > Pl

Re: [openstack-dev] [heat] Nomination for heat-core

+1 Sent from my Verizon Wireless 4G LTE Smartphone Original message From: Steve Baker Date: 12/18/2013 8:28 PM (GMT-06:00) To: OpenStack Development Mailing List Subject: [openstack-dev] [heat] Nomination for heat-core I would like to nominate Bartosz Górski to be a heat-

Re: [openstack-dev] [Nova][Docker] Environment variables

On 17 December 2013 12:53, Daniel P. Berrange wrote: > On Mon, Dec 16, 2013 at 01:04:33PM -0800, Dan Smith wrote: >> > eg use a 'env_' prefix for glance image attributes >> > >> > We've got a couple of cases now where we want to overrides these >> > same things on a per-instance basis. Kernel comm

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On 16 December 2013 15:50, Daniel P. Berrange wrote: > On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote: >> On 16 December 2013 15:25, Daniel P. Berrange wrote: >> > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote: >> >> I'd like to propose the following for the V3 API (we

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Thu, Dec 19, 2013 at 02:27:40PM +, John Garbutt wrote: > On 16 December 2013 15:50, Daniel P. Berrange wrote: > > On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote: > >> On 16 December 2013 15:25, Daniel P. Berrange wrote: > >> > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Ko

[openstack-dev] [Neutron][IPv6] Agenda for today's meeting

Hi, Agenda for today's meeting is pretty light - if you have something you'd like to discuss please add it to the wiki page https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Dec_19_2013 I would also ask that when we conduct the meeting - we stick to the agenda that has bee

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

I think it was: ceilometer sample-list -m cpu_util -q 'resource_id=vm_uuid' Vladik - Original Message - > From: "Daniel P. Berrange" > To: "John Garbutt" > Cc: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Thursday, 19 December, 2013 9:34:02 AM > Subject: R

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

Or ceilometer meter-list -q resource_id='vm_uuid' - Original Message - > From: "Daniel P. Berrange" > To: "John Garbutt" > Cc: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Thursday, 19 December, 2013 9:34:02 AM > Subject: Re: [openstack-dev] [nova] VM diagn

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

Hi, Yair Fried wrote: I would also like to point out that, since Brent used compute.build_timeout as the timeout value ***It takes more time to update FLIP in nova DB, than for a VM to build*** Yair Agreed. I think that's an extremely important highlight of this discussion. Propagation of t

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

On 4 December 2013 17:10, Russell Bryant wrote: > I think option 3 makes the most sense here (pending anyone saying we > should run away screaming from mox3 for some reason). It's actually > what I had been assuming since this thread a while back. > > This means that we don't need to *require* th

Re: [openstack-dev] [Neutron][IPv6] Three SLAAC and DHCPv6 related blueprints

On Wed, Dec 18, 2013 at 10:29:35PM -0500, Shixiong Shang wrote: > It is up to Sean to make the call, but I would love to see IBM team in the > meeting. Agreed - If we can find a time that works for USA, Europe and China that would be great. How good/bad is 1500 UTC? I don't trust my math :)

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the "FloatingIPChecker" control point

My 2 cents: In the test the floating IP is created via neutron API and later checked via nova API. So the test is relying here (or trying to verify?) the network cache refresh mechanism in nova. This is something that we should test, but in a test dedicated to this. The primary objective of tes

Re: [openstack-dev] [trove] datastore migration issues

We did consider doing that, but decided it wasn't really any different from the other options as it required the deployer to know to alter that data. That would require the fewest code changes, though. It was also my understanding that mysql variants were a possibility as well (percona and mar

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Thu, Dec 19, 2013 at 03:47:30PM +0100, Vladik Romanovsky wrote: > I think it was: > > ceilometer sample-list -m cpu_util -q 'resource_id=vm_uuid' Hmm, a standard devstack deployment of ceilometer doesn't seem to record any performance stats at all - just shows me the static configuration param

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Thursday, December 19, 2013 8:49:13 AM, Vladik Romanovsky wrote: Or ceilometer meter-list -q resource_id='vm_uuid' - Original Message - From: "Daniel P. Berrange" To: "John Garbutt" Cc: "OpenStack Development Mailing List (not for usage questions)" Sent: Thursday, 19 December,

[openstack-dev] [Horizon] Support for Django 1.6

Hi, Sid has Django 1.6. Is it planned to add support for it? I currently don't know what to do with the Horizon package, as it's currently broken... :( Thomas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/c

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote: > Hi, > Following the discussion yesterday I have updated the wiki - please see > https://wiki.openstack.org/wiki/Nova_VM_Diagnostics. The proposal is > backwards compatible and will hopefully provide us with the tools to be > able to tro

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

2013/12/19 Fox, Kevin M > How about a different approach then... OpenStack has thus far been very > successful providing an API and plugins for dealing with things that cloud > providers need to be able to switch out to suit their needs. > > There seems to be two different parts to the unified ag

Re: [openstack-dev] [trove] datastore migration issues

I think that we need to be good citizens and at least add dummy data. Because it is impossible to know who all is using this, the list you have is probably complete. But Trove has been available for quite some time and all these users will not be listening on this thread. Basically anytime you have

Re: [openstack-dev] [Horizon] Support for Django 1.6

On 2013-12-19 23:45:09 +0800 (+0800), Thomas Goirand wrote: > Sid has Django 1.6. Is it planned to add support for it? I currently > don't know what to do with the Horizon package, as it's currently > broken... :( You probably want to follow https://blueprints.launchpad.net/horizon/+spec/django-1p

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On 12/19/13 5:50 PM, "Daniel P. Berrange" wrote: >On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote: >> Hi, >> Following the discussion yesterday I have updated the wiki - please see >> >>https://urldefense.proofpoint.com/v1/url?u=https://wiki.openstack.org/wik >>i/Nova_VM_Diagnostic

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On 12/19/13 6:07 PM, "Daniel P. Berrange" wrote: >On Thu, Dec 19, 2013 at 08:02:16AM -0800, Gary Kotton wrote: >> >> >> On 12/19/13 5:50 PM, "Daniel P. Berrange" wrote: >> >> >On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote: >> >> Hi, >> >> Following the discussion yesterday I h

Re: [openstack-dev] [Heat] [Trove] [Savanna] [Oslo] Unified Agents - what is the actual problem?

>> I agree that enabling communication between guest and cloud service is a >> common problem for most agent designs. The only exception is agent based on >> hypervisor provided transport. But as far as I understand many people are >> interested in network-based agent, so indeed we can start a t

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

On Thu, Dec 19, 2013 at 08:02:16AM -0800, Gary Kotton wrote: > > > On 12/19/13 5:50 PM, "Daniel P. Berrange" wrote: > > >On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote: > >> Hi, > >> Following the discussion yesterday I have updated the wiki - please see > >> > >>https://urldefens

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

Ah, I think I've responded too fast, sorry. meter-list provides a list of various measurements that are being done per resource. sample-list provides a list of samples per every meter: ceilometer sample-list --meter cpu_util -q resource_id=vm_uuid These samples can be aggregated over a period of

Re: [openstack-dev] Incubation Request for Barbican

Excerpts from Sean Dague's message of 2013-12-19 04:14:51 -0800: > On 12/19/2013 12:10 AM, Mike Perez wrote: > > On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez > > wrote: > > > I reviewed the TC meeting notes, and my question still stands. > > > > It seems the committee is

[openstack-dev] [swift] Blocking issue with ring rebalancing

Hi, Our team run into some serious trouble with performance of 'swift-ring-builder rebalance' after some recent changes. On our environment it takes about 8 minutes, and this and it is not the maximum. This is really blocker for us. This issue is reproducible on Ubuntu 12.04 + Python 2.7. The fun

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

So basically this is our first proposal what we send out: http://lists.openstack.org/pipermail/openstack-dev/2013-December/022196.html After Horizon meetings, several e-mails and also couple of other discussions of people who are for/against codebase merge, it looks that in the end upstream le

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

So after a lot of consideration, my opinion is the two code bases should stay in separate repos under the Horizon Program, for a few reasons: -Adding a large chunk of code for an incubated project is likely going to cause the Horizon delivery some grief due to dependencies and packaging issues at

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

- Original Message - > So basically this is our first proposal what we send out: > http://lists.openstack.org/pipermail/openstack-dev/2013-December/022196.html > > After Horizon meetings, several e-mails and also couple of other > discussions of people who are for/against codebase merge,

[openstack-dev] [Climate] PTL Candidacy

Hi, I hereby would like to announce my candidacy for the Climate (Reservations) PTL. A brief history about me : I'm playing with Software Engineering and Operations since more than 10 years, with a special focus on Openstack since the Essex release. I promoted Openstack in my previous compan

Re: [openstack-dev] [Heat] [Trove] [Savanna] [Oslo] Unified Agents - what is the actual problem?

Tim, IMHO network-based and hypervisor-based agents definitely can co-exist. What I wanted to say is that the problem of enabling communication between guest and cloud service is not relevant for hypervisor-based agents. They simply don't need network access into a VM. Dmitry 2013/12/19 Tim Sim

Re: [openstack-dev] [Ceilometer] Nomination of Sandy Walsh to core team

On Mon, Dec 09 2013, Herndon, John Luke wrote: Hi John, > I¹m not 100% sure what the process is around electing an individual to the > core team (i.e., can a non-core person nominate someone?). However, I > believe the ceilometer core team could use a member who is more active in > the developmen

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

+1 to this! - Original Message - > So after a lot of consideration, my opinion is the two code bases should stay > in separate repos under the Horizon Program, for a few reasons: > -Adding a large chunk of code for an incubated project is likely going to > cause the Horizon delivery some g

Re: [openstack-dev] Horizon and Tuskar-UI codebase merge

On 12/19/2013 05:32 PM, Jordan O'Mara wrote: > > - Original Message - >> So basically this is our first proposal what we send out: >> http://lists.openstack.org/pipermail/openstack-dev/2013-December/022196.html >> >> After Horizon meetings, several e-mails and also couple of other >> discus

Re: [openstack-dev] [Neutron][IPv6] Three SLAAC and DHCPv6 related blueprints

Perfect! Will you be at the IRC meeting to discuss these? I've added them to the agenda in the hopes that we can discuss -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listi

Re: [openstack-dev] [Neutron][IPv6] Three SLAAC and DHCPv6 related blueprints

I will surely be there this afternoon, Sean! Look forward to it! On Dec 19, 2013, at 12:22 PM, Collins, Sean wrote: > Perfect! Will you be at the IRC meeting to discuss these? I've added > them to the agenda in the hopes that we can discuss > > -- > Sean M. Collins > _

Re: [openstack-dev] [heat] Nomination for heat-core

On Thu, Dec 19, 2013 at 03:21:46PM +1300, Steve Baker wrote: > I would like to nominate Bartosz Górski to be a heat-core reviewer. His > reviews to date have been valuable and his other contributions to the > project have shown a sound understanding of how heat works. > > Here is his review histor

[openstack-dev] [State-Management] Agenda for today meeting at 2000 UTC

Hi all, The [state-management] project team holds a weekly meeting in #openstack-meeting on thursdays, 2000 UTC. The next meeting is today, 2013-12-19!!! As usual, everyone is welcome :-) Link: https://wiki.openstack.org/wiki/Meetings/StateManagement Taskflow: https://wiki.openstack.org/Ta

Re: [openstack-dev] [Climate] PTL Candidacy

Confirmed. https://wiki.openstack.org/wiki/Climate/PTL_Elections_Icehouse#Candidates On Thu, Dec 19, 2013 at 8:39 PM, Sylvain Bauza wrote: > Hi, > > I hereby would like to announce my candidacy for the Climate > (Reservations) PTL. > > A brief history about me : I'm playing with Software Engin

Re: [openstack-dev] [trove] My thoughts on the Unified Guest Agent

When the OpenStack project was started in 2010, we conceived of two languages that would be considered to have first class status: Python, and C++. The idea is that Python would be used for the API services, and that C++ would be used in special cases where Python was not a good fit, such as for

Re: [openstack-dev] Incubation Request for Barbican

On Thu, Dec 19, 2013 at 4:14 AM, Sean Dague wrote: > On 12/19/2013 12:10 AM, Mike Perez wrote: > > On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez > > wrote: > > > I reviewed the TC meeting notes, and my question still stands. > > > > It seems the committee is touching on

Re: [openstack-dev] Adding DB migration items to the common review checklist

On 2013-12-18 22:08, Jay Pipes wrote: On 12/18/2013 02:14 PM, Brant Knudson wrote: Matt - Could a test be added that goes through the models and checks these things? Other projects could use this too. Here's an example of a test that checks if the tables are all InnoDB: http://git.openstack.or

Re: [openstack-dev] Incubation Request for Barbican

On Thu, Dec 12, 2013 at 4:48 PM, Morgan Fainberg wrote: > On December 12, 2013 at 14:32:36, Dolph Mathews > (dolph.math...@gmail.com) > wrote: > > > On Thu, Dec 12, 2013 at 2:58 PM, Adam Young wrote: > >> On 12/04/2013 08:58 AM, Jarret Raim wrote: >> >> While I am all for adding a new program,

Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

On Wed, Dec 18, 2013 at 7:16 PM, Gao, Fengqian wrote: > Hi, Devananda, > > I agree with you that new features should be towards Ironic. > > As you asked why use Ironic instead of lm-sensors, actually I just want to > use IPMI instead of lm-sensors. I think it is reasonable to put the IPMI > part

[openstack-dev] [Nova] Default ephemeral filesystem

The default ephemeral filesystem in Nova is ext3 (for Linux). However ext3 is IMNSHO a pretty poor choice given ext4's existence. I can totally accept that other fs's like xfs might be contentious - but is there any reason not to make ext4 the default? I'm not aware of any distro that doesn't have

Re: [openstack-dev] [Nova] Default ephemeral filesystem

On 12/19/2013 03:21 PM, Robert Collins wrote: > The default ephemeral filesystem in Nova is ext3 (for Linux). However > ext3 is IMNSHO a pretty poor choice given ext4's existence. I can > totally accept that other fs's like xfs might be contentious - but is > there any reason not to make ext4 the d

Re: [openstack-dev] [bugs] definition of triaged

On 16 December 2013 23:56, Thierry Carrez wrote: > Robert Collins wrote: >> https://wiki.openstack.org/wiki/BugTriage is a 10 step process: thats >> not something we can sensible do over coffee in the morning. > > Totally agree with that. The idea of those 10 steps was not meant as > something you

Re: [openstack-dev] [Neutron][IPv6] Agenda for today's meeting

Minutes from the meeting: http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-19-21.00.html -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listin

[openstack-dev] [Neutron][IPv6] Meeting time - change to 1300 UTC or 1500 UTC?

Thoughts? I know we have people who are not able to attend at our current time. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12/19/2013 04:55 AM, Radomir Dopieralski wrote: On 14/12/13 16:51, Jay Pipes wrote: [snip] Instead of focusing on locking issues -- which I agree are very important in the virtualized side of things where resources are "thinner" -- I believe that in the bare-metal world, a more useful focus

Re: [openstack-dev] [Neutron][IPv6] Meeting time - change to 1300 UTC or 1500 UTC?

I cannot do 13:00UTC, but 14:00 or 15:00 UTC should work for me. > On Dec 19, 2013, at 5:12 PM, "Collins, Sean" > wrote: > > Thoughts? I know we have people who are not able to attend at our > current time. > > -- > Sean M. Collins > ___ > OpenSta

[openstack-dev] [Ceilometer][Oslo] Consuming Notifications in Batches

Hi Folks, The Rackspace-HP team has been putting a lot of effort into performance testing event collection in the ceilometer storage drivers[0]. Based on some results of this testing, we would like to support batch consumption of notifications, as it will greatly improve insertion performance. Bat

Re: [openstack-dev] [Neutron][IPv6] Meeting time - change to 1300 UTC or 1500 UTC?

Any of those times suit me. Sent from my iPhone On Dec 19, 2013, at 5:12 PM, "Collins, Sean" wrote: > Thoughts? I know we have people who are not able to attend at our > current time. > > -- > Sean M. Collins > ___ > OpenStack-dev mailing list > O

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Anita, Fawad and Myself will be also attending. BTW. Fawad will require an invitation letter for visa. He will email you directly with that request. Thanks, Edgar On Wed, Dec 18, 2013 at 1:17 PM, Anita Kuno wrote: > Okay time for a recap. > > What: Neutron Tempest code sprint > Where: Montr

  1   2   >