Re: [openstack-dev] [qa] Moving the QA meeting time

Hey, guys. We've got a team in China that is focused mainly on Test and at least one or two would like to attend the meetings. 22:00 UTC is a bit early for them so I think it would be better to alternate to get reasonable participation. The team wants to get more involved in the test effort an

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

I think Jesse illustrates *why* we need a program for UX. SW Developers don't think the same way as UX developers. UX is working on stuff most of us have never considered across all sorts of project lines. A warm, understanding home to brainstorm issues before returning to the project trenche

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

Anne Gentle wrote: On Wed, Nov 20, 2013 at 9:09 AM, Thierry Carrez mailto:thie...@openstack.org>> wrote: Hi everyone, How should we proceed to make sure UX (user experience) is properly taken into account into OpenStack development ? Historically it was hard for UX sessions (especially the one

Re: [openstack-dev] Propose "project story wiki" idea

+1 I'd also love to see a tag or keyword associated with items that (affects {project x,y,z}) or (possibly affects {project x,y,z} to highlight areas in need of collaboration between teams. There is so much going on cross-project these days, that if the project team thinks the change has side

Re: [openstack-dev] [Openstack][qa][Tempest][Network] Test for external connectivity

For External connectivity beyond the network gateway, rather than pinging google.com, configuring the vm for an external DNS server and pinging it by IPaddress would be a good initial test of external connectivity. --Rocky From: Tomoe Sugihara [mailto:to...@midokura.com] Sent: Tuesday, Novemb

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

Perhaps all this sound and fury will get a some entity to step up and provide Neutron project t-shirts for the sprint;-) Then maybe the participants will *want* to wear the Neutron Team shirt. And as for errors, Anita, I fully understand, sympathize and have experience in that area. --Rocky

Re: [openstack-dev] Split of the openstack-dev list (summary so far)

Coming from QA/Ops, I agree that there are horizontal teams that need to get info from the mailing list(s) across the spectrum. I also agree with Clint's and Adrian's statements about the synergies and serendipities of all the developers on one list. But I also understand the feeling of drowni

Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest

I agree that parametric testing, with input generators is the way to go for the API testing. Both positive and negative. I've looked at a number of frameworks in the past and the one that until recently was the highest on my list is Robot: http://code.google.com/p/robotframework/ I had looked

Re: [openstack-dev] [qa] Policy on spelling and grammar

From: Christopher Yeoh [mailto:cbky...@gmail.com] Sent: Monday, November 11, 2013 3:06 PM To: openst...@nemebean.com; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [qa] Policy on spelling and grammar On Tue, Nov 12, 2013 at 6:24 AM, Ben Nemec mailto:op

Re: [openstack-dev] [openstack-tc] Proposal to recognize indirect contributions to our code base

I just looked at the Gerrit docs and saw that there is a "your category here" option that would allow adding a category to the already existing ones. It can be set as blocking (not what we would want) or non-blocking. I think this could be used to credit a sponsor ("courtesy of") without mucki

Re: [openstack-dev] L3 advanced features blueprint mapping to IETF and IEEE standards

From: Pedro Roque Marques [mailto:pedro.r.marq...@gmail.com] Colin, "The nice thing about standards is that there are so many of them to choose from." For instance, if you take this Internet Draft: http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-02 which is based on RFC4364. It has alr

Re: [openstack-dev] Fwd: [Openstack-Dev] [Compass] Announcement of the Compass Deployment project

From: Dmitry Mescheryakov [mailto:dmescherya...@mirantis.com] I've noticed you list "Remote install and configure a Hadoop cluster (synergy with Savanna?)" among possible use cases. Recently there was a discussion about Savanna on bare metal provisioning through Nova (see thread [1]). Nobody tes

Re: [openstack-dev] Fwd: [Openstack-Dev][Compass] Announcement of the Compass Deployment project

The demo session is: Wednesday, November 6 * 1:20pm - 1:35pm in the Demo Theatre The presentation is: Thursday, November 7 * 4:30pm - 5:10pm in Sky City Meeting Rm 4 (Marriot) We are also trying for an unconference session to do some brainstorming with interested developers. And, our schedul

Re: [openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

John Griffith wrote: On Wed, Oct 23, 2013 at 8:47 AM, Sean Dague mailto:s...@dague.net>> wrote: On 10/23/2013 10:40 AM, John Griffith wrote: On Sun, Oct 20, 2013 at 7:38 AM, Sean Dague mailto:s...@dague.net> >> wrote: Dave Kranz has been buil

Re: [openstack-dev] Hyper-V meeting Minutes

Monty Taylor wrote: On 10/15/2013 08:36 PM, Sean Dague wrote: > On 10/15/2013 04:54 PM, Vishvananda Ishaya wrote: >> Hi Everyone, >> >> I've been following this conversation and weighing the different >> sides. This is a tricky issue but I think it is important to decouple >> further a

Re: [openstack-dev] Hyper-V meeting Minutes

From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Hi Everyone, I've been following this conversation and weighing the different sides. This is a tricky issue but I think it is important to decouple further and extend our circle of trust. When nova started it was very easy to do

Re: [openstack-dev] [Hyper-V] Havana status

When you do, have a beer for me. I'll be looking for what you guys come up with. And I don't think a separate project would be a second class project. The driver guys could be so successful that all the drivers end up there and the interfaces between Nova and the drivers get *real* clean and

Re: [openstack-dev] [Hyper-V] Havana status

Pardon me for cutting out most of the discussion. I'd like to summarize a bit here and make a proposal. Issues: * Driver and Plugin writers for Nova (and other Core OpenStack projects) have a different development focus than core developers which can create both delays in getting sub

Re: [openstack-dev] Stats on blueprint design info / creation times

+100 If one blueprint points to another, then the pointers should be present and available in both blueprints. Dependency linking, folks. --Rocky From: Mike Spreitzer [mailto:mspre...@us.ibm.com] Sent: Wednesday, August 21, 2013 9:04 AM To: Daniel P. Berrange Cc: OpenStack Development Mailing