+2
From: Amit Gandhi >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Monday, September 21, 2015 at 5:22 PM
To: "OpenStack
+2
From: Amit Gandhi >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Monday, September 21, 2015 at 5:20 PM
To: "OpenStack
Thank You Alej – not just for the tons of code you wrote for Zaqar, but also in
making Zaqar a fun, open and welcoming part of the community!
Good Luck for everything ahead!
From: Victoria Martínez de la Cruz
victo...@vmartinezdelacruz.commailto:victo...@vmartinezdelacruz.com
Reply-To:
A HUGE +1 !
On 8/1/14 10:11 AM, Flavio Percoco fla...@redhat.com wrote:
Greetings,
I'd like to propose adding Victoria Martínez de la Cruz (vkmc) to
zaqar's core team. Victoria has been part of the community for several
months now. During this time, she's been contributing to many different
There is another thread going on for the same
http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg30897.html
We sure need vkmc in the core :)
From: Kurt Griffiths
kurt.griffi...@rackspace.commailto:kurt.griffi...@rackspace.com
Reply-To: OpenStack Development Mailing List (not for
On 7/16/14 4:43 AM, Flavio Percoco fla...@redhat.com wrote:
On 07/15/2014 06:20 PM, Kurt Griffiths wrote:
Hi folks, we¹ve been talking about this in IRC, but I wanted to bring it
to the ML to get broader feedback and make sure everyone is aware. We¹d
like to change our meeting time to better
Oops- My bad!
I just started it.
Thanks for the reminder David.
On 6/23/14 4:31 PM, David Kranz dkr...@redhat.com wrote:
Please remember to do 'check experimental' after uploading new marconi
patches in tempest.
-David
___
OpenStack-dev mailing
Hello,
We went through a similar exercise for Marconi.
At that point of time, there was not any documentation on the series of steps
to go through.
Below are some of the high level steps we went through.
1. Complete devstack integration (Make sure you run devstack with same
local.conf as in
Hello,
We went through a similar exercise for Marconi.
At that point of time, there was not any documentation on the series of steps
to go through.
Below are some of the high level steps we went through.
1. Complete devstack integration (Make sure you run devstack with same
local.conf as in
and decided, and calling out specific “promises” for future
conversations where certain design points are TBD.
From: Malini Kamalambal
malini.kamalam...@rackspace.commailto:malini.kamalam...@rackspace.com
Reply-To: OpenStack Dev
openstack-dev@lists.openstack.orgmailto:openstack-dev
Hello all,
Marconi team will have its weekly meeting tomorrow at 1500 UTC in
#openstack-meeting-alt.
The meeting agenda is available at
https://wiki.openstack.org/wiki/Meetings/Marconi#Next_meeting
All are welcome to add agenda items for the meeting.
If you are interested in learning about the
Hello Tomasz,
We have been pulled into some other priorities the past week haven't got a
chance yet to run a new benchmark.
I hope to get to it later this week.
Meanwhile if you are interested in deploying Marconi/running the benchmarks
yourself, please let me know.
We can point you to the
The beginning of this thread largely came from the fact that Marconi
clearly doing most of their QA not in an upstream way. To be integrated,
that needs to change.
Marconi has very good test coverage within the project.
These tests guarantee functionality at a project level (i.e the API works
We are talking about different levels of testing,
1. Unit tests - which everybody agrees should be in the individual project
itself
2. System Tests - 'System' referring to ( limited to), all the components
that make up the project. These are also the functional tests for the
project.
3.
On 3/21/14 3:49 PM, Rochelle.RochelleGrober rochelle.gro...@huawei.com
wrote:
From: Malini Kamalambal [mailto:malini.kamalam...@rackspace.com]
snip
We are talking about different levels of testing,
1. Unit tests - which everybody agrees should be in the individual
project
itself
2
Flavio has very well summarized the Marconi team's thoughts.
We appreciate all the frank opinions in the discussions that are going on.
Keep those thoughts coming!
We look forward to building a better Marconi and a stronger community.
On 3/20/14 7:30 PM, Clint Byrum cl...@fewbar.com wrote:
Jay
integration a top priority for the cycle.
On 03/20/2014 03:13 PM, Malini Kamalambal wrote:
Thanks Matt for your response !! It has clarified some of the 'cloudy
areas' ;)
So having only looked at the Marconi ML thread and not the actual TC
meeting
minutes I might be missing the whole picture
On 3/21/14 12:01 PM, David Kranz dkr...@redhat.com wrote:
On 03/20/2014 04:19 PM, Rochelle.RochelleGrober wrote:
-Original Message-
From: Malini Kamalambal [mailto:malini.kamalam...@rackspace.com]
Sent: Thursday, March 20, 2014 12:13 PM
'project specific functional testing
Hello all,
I have been working on adding tests in Tempest for Marconi, for the last few
months.
While there are many amazing people to work with, the process has been more
difficult than I expected.
Couple of pain-points and suggestions to make the process easier for myself
future
Let me start by saying that I want there to be a constructive discussion around
all this. I've done my best to keep my tone as non-snarky as I could while
still clearly stating my concerns. I've also spent a few hours reviewing the
current code and docs. Hopefully this contribution will be
along with
the tests in Tempest.
On 3/20/14 1:59 PM, Matthew Treinish mtrein...@kortar.org wrote:
On Thu, Mar 20, 2014 at 11:35:15AM +, Malini Kamalambal wrote:
Hello all,
I have been working on adding tests in Tempest for Marconi, for the
last few months.
While there are many amazing
+1
From: Cindy Pallares
cindy.pallar...@gmail.commailto:cindy.pallar...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, March 3, 2014 1:41 PM
To: OpenStack Development
22 matches
Mail list logo