Re: [openstack-dev] [qa] Tempest Bug triage

2014-09-12 Thread Mauro S M Rodrigues
On 09/11/2014 04:52 PM, David Kranz wrote: So we had a Bug Day this week and the results were a bit disappointing due to lack of participation. We went from 124 New bugs to 75. There were also many cases where bugs referred to logs that no longer existed. This suggests that we really need to ke

Re: [openstack-dev] heads up, set -o errexit on devstack - things will fail earlier now

2014-02-28 Thread Mauro S M Rodrigues
Awesome! thanks for it! Btw I guess this will automatically works for grenade, since we use devstack to setup X-1 release, am I right? (and it's not a concern for the upgrade part since the upgrade- scripts already contain errexit trap on the cleanup functions right?) -- mauro(sr) On 02/27

[openstack-dev] [QA][Tempest] Bug Day - Wed, 19th

2014-03-12 Thread Mauro S M Rodrigues
Hello everybody! In the last QA meeting I stepped ahead and volunteered to organize another QA Bug Day. This week wasn't a good one, so I thought to schedule it to the next Wednesday (March, 19th). If you think we need more time or something, please let me know. == Actions == Basically I'm

Re: [openstack-dev] [QA][Tempest] Reminder: Bug Day - Wed, 19th

2014-03-18 Thread Mauro S M Rodrigues
Hey! I Just want to reminder everybody about the bug day tomorrow. Thanks On 03/12/2014 09:31 PM, Mauro S M Rodrigues wrote: Hello everybody! In the last QA meeting I stepped ahead and volunteered to organize another QA Bug Day. This week wasn't a good one, so I thought to schedule

[openstack-dev] [QA] Bug Day kickoff

2014-03-19 Thread Mauro S M Rodrigues
ent status (and maybe assign someone else to take care of it). - 4 are incomplete without answer and we may try to reach the reporter to get an update. Some actions, from the first email: On 03/12/2014 09:31 PM, Mauro S M Rodrigues wrote: == Actions == Basically I'm proposing the follow ac

Re: [openstack-dev] [nova] Nova API extensions NOT to be ported to v3

2013-07-01 Thread Mauro S M Rodrigues
Correct if I'm wrong but what value ips core api bring to us currently? It offers you two calls: GET on http://localhost:8774/v3/servers//ips => returns instance ips GET on http://localhost:8774/v3/servers//ips/{network-id} => returns instance ips that are member of the specified networl. both

Re: [openstack-dev] [nova] Nova API extensions NOT to be ported to v3

2013-07-01 Thread Mauro S M Rodrigues
One more though, about os-multiple-create: I was also thinking to remove it, I don't see any real advantage to use it since it doesn't offer any kind of flexibility like chose different flavors, images and other attributes. So anyone creating multiple servers would probably prefer an external a

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

2013-07-01 Thread Mauro S M Rodrigues
+1.. make sense to me, I always thought that was weird hehe Say the word and we will remove it from v3. On 07/01/2013 01:02 PM, Russell Bryant wrote: On 07/01/2013 11:47 AM, Jay Pipes wrote: Recently a colleague asked me whether their key pair from one of our deployment zones would be usable in

Re: [openstack-dev] Move keypair management out of Nova and into Keystone?

2013-07-01 Thread Mauro S M Rodrigues
yes, of course... On 07/01/2013 02:07 PM, Joe Gordon wrote: We should not remove it from the v3 API until we know this will be supported by keystone in Havana. best, Joe sent on the go On Jul 1, 2013 6:25 PM, "Mauro S M Rodrigues" mailto:maur...@linux.vnet.ibm.com>>