Also +1.__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
+2 from me.
Marc Gariépy
On 2018-04-24 11:05 AM, Jean-Philippe Evrard wrote:
Hi everyone,
I’d like to propose Mohammed Naser [1] as a core reviewer for OpenStack-Ansible.
He has been working actively on fixing the telemetry stack, and is now
willing to step up to improve the CentOS platform
Marc
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
discussed about using ML2 GW [2] or trunk port [3].
I consider the design above as simple enough to get merged smoothly
in Newton.
@Ben: Will be back for bug hunting now.
Regards
Marc
[1]:
https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/ironic-ml2-integration.htm
> On 09 Mar 2016, at 08:43, Sukhdev Kapur wrote:
>
> Hi Marc,
>
> I am driving the ironic-ml2 integration and introduced baremetal type for
> vmic_type.
Basically that’s my plan. So in my current implementation
I use the baremetal vnic_type [1] and add a binding profi
was to use the same principle as ironic ml2 intregration is doing [3]
by setting the vnic_type to “baremetal”.
In Manila's current implementation storage drivers are also responsible to
setup the right networking setup. Would you suggest to move this part into the
port binding phase?
Regards
information that is exposed
are all segments of a network. But this is not sufficient to identify which
segments actually used for a port binding.
Regards
Marc
SAP SE
[1]: https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support
<https://wiki.openstack.org/wiki/Manila/design/manila-new
Hi Nidhi,
It’s might also a good idea to have a short discussion during the manila
meeting [1].
You can simply add your topic to the agenda.
Regards
Marc
[1]: https://wiki.openstack.org/wiki/Manila/Meetings
<https://wiki.openstack.org/wiki/Manila/Meetings>
> On 26 Feb 2016,
I know that there are folks around that are using it.
+1 to move it to a separate repo.
Regards
Marc
> On 11 Feb 2016, at 13:59, Daniel Mellado wrote:
>
> +1 to that, it was my 2nd to-be-deprecated after javelin ;)
>
> El 11/02/16 a las 12:47, Sean Dague escribió:
>> In
groups a set of tests?
Please have a look to the qa-spec for more detail [2] and sample
implementation [3].
Regards Marc
SAP SE
[1]: http://ddt.readthedocs.org/en/latest/
[2]: https://review.openstack.org/#/c/259934/
[3]: https://review.openstack.org/#/c/223953
+1 I am also very confused about the new UI.. but maybe it takes time to get
use to it.
Regards
Marc
Am 17.12.2015 um 10:55 schrieb Mohan Kumar :
> Eugene: +1 , Old Gerrit page was better than new one . Please fix
>
> On Thu, Dec 17, 2015 at 2:11 PM, Eugene Nikanorov
> wrote:
Hello TelcoWG,
Due to personal reasons I have to resign my TelcoWG core team membership.
I will remove myself from the core reviewer group.
Thanks for all the support!
Regards
Marc
__
OpenStack Development Mailing List
files in similar cases not the ones in
> the venv.
Idempotent id’s aren’t covered in the first drop of tempest plugin interface.
I am wondering if there is a need from refstack..?
Regards
Marc
> Regards
> Lajos
>
> On 09/11/2015 08:50 AM, Lajos Katona wrote:
>> Hi Matthew,
&g
within the configuration.
I will add this topic to the next Manila meeting to discuss the next steps.
Regards
Marc
[1]: https://review.openstack.org/#/c/201955/
[2]:
http://specs.openstack.org/openstack/qa-specs/specs/tempest/tempest-external-plugin-interface.html
.
I used a script to produce this table [1]. Please let me know if you find a bug
:)
Regards
Marc
[1]: http://paste.openstack.org/show/391303/
Am 15.07.2015 um 22:26 schrieb John Griffith :
>
>
> On Wed, Jul 8, 2015 at 12:48 AM, Marc Koderer wrote:
>
> Am 08.07.2015 um 01:
Am 08.07.2015 um 01:37 schrieb Mike Perez :
> On 18:38 Jun 22, Marc Koderer wrote:
>>
>> Am 20.06.2015 um 01:59 schrieb John Griffith :
>>> * The BaseVD represents the functionality we require from all drivers.
>>> Yep
>>>
>>> * The add
+1
Am 23.06.2015 um 02:06 schrieb GHANSHYAM MANN :
> +1 :)
>
> On Tue, Jun 23, 2015 at 5:23 AM, Matthew Treinish
> wrote:
>
>
> Hi Everyone,
>
> I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team.
> Jordan has been a steady contributor and reviewer on tempest over
ormation, which I dislike the idea of.
>
> Yeah, back to the dreaded "Matrix", I can't imagine anything worse for
> Cinder than a matrix of supported API calls on a driver per driver basis.
I agree that such a matrix tool
vers adapt their interface.
IMHO a runtime exception should be only used as interim solution to get all
drivers ported.
If the driver interfaces changes quite often we need to use versions.
Regards
Marc
>
> --
> Clinton Knight
>
> From: John Griffith
> Reply-To: "OpenSta
]).
I would like to use this Etherpad to coordinate the work:
https://etherpad.openstack.org/p/cinder-abc-driver-update
So, I need an assignee for each driver :)
Regards
Marc
[1]: https://review.openstack.org/#/c/177114/
[2]: https://review.openstack.org/#/c/138661/
—
Deutsche Telekom
[+1, +1]
Am 24.04.2015 um 06:42 schrieb Ramana Raja :
> +1 to both.
>
> - Original Message -
> From: "Ben Swartzlander"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Wednesday, April 22, 2015 11:53:15 PM
> Subject: [openstack-dev] [Manila] Two nominat
.
Regards
Marc
[1]: https://review.openstack.org/#/c/155248/
[2]: https://wiki.openstack.org/wiki/How_To_Contribute
Am 06.02.2015 um 12:11 schrieb Marc Koderer :
> Hello everyone,
>
> we are currently facing the issue that we don’t know how to proceed with
> our telco WG use case
- we link blueprint related to this use case
- we build a core team and approve/prioritize them
Regards
Marc
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
Hi Steve,
I can host it.
Regards
Marc
Am 27.01.2015 um 08:40 schrieb Steve Gordon :
> Hi all,
>
> As mentioned in the notes from last week's meeting I am going to be in
> transit during our 1400 UTC meeting this Wednesday (28th) [1]. Is anyone else
> willing and able
io tests.
Since we are already planning to have a external CI system it would make
sense to keep them somewhere outside and use the tempest lib (when ready).
Regards
Marc
> In addition to the functional tests in Nova, we have also proposed two basic
> scenarios in Tempest [2][3]. One
Hi Valeriy,
thanks for feedback. My answers see below.
Am 02.12.2014 um 16:44 schrieb Valeriy Ponomaryov :
> Hello Marc,
>
> Here, I tried to cover mentioned use cases with "implemented or not" notes:
>
> 1) Implemented, but details of implementation are differe
Share
Resize existing and assigned share on the fly.
8.) Copy existing share
Copy existing share between different storage technologies
Regards
Marc
Deutsche Telekom
[1]: https://wiki.openstack.org/wiki/Manila/usecases
___
OpenStack-dev mailing
+1
Am 22.11.2014 um 15:51 schrieb Andrea Frittoli :
> +1
>
> On 21 Nov 2014 18:25, "Ken1 Ohmichi" wrote:
> +1 :-)
>
> Sent from my iPod
>
> On 2014/11/22, at 7:56, Christopher Yeoh wrote:
>
> > +1
> >
> > Sent from my iPad
> >
> >> On 22 Nov 2014, at 4:56 am, Matthew Treinish wrote:
> >>
>
Hi Angus,
Am 25.11.2014 um 12:48 schrieb Angus Salkeld :
> On Tue, Nov 25, 2014 at 7:27 PM, Marc Koderer wrote:
> Hi all,
>
> as discussed during our summit sessions we would like to expand the scope
> of the Telco WG (aka OpenStack NFV group) and start working
> on the o
document and move it onto the Telco WG wiki [2] when
it becomes stable.
Feedback welcome ;)
Regards
Marc
Deutsche Telekom
[1] https://etherpad.openstack.org/p/telco_orchestration
[2] https://wiki.openstack.org/wiki/TelcoWorkingGroup
___
OpenStack-dev
d
> "openstack-integration-tests" or "os-integration-tests“.
why not keeping it simple:
tempest: importable test library
tempest-tests: all the test cases
Simple, obvious and clear ;)
Regards
Marc
> Best,
> -jay
>
>
>
;) Anyway I do think that moving test
cases closer to the project is a good idea.
Regards
Marc
On Wed, Aug 6, 2014 at 12:25 PM, Duncan Thomas
wrote:
I'm not following here - you complain about rally being monolithic,
then suggest that parts of it should be baked into tempest - a
n't put PaaS in OpenStack core # rally is not PaaS
*) Duplication of functionality (actually dashboard) # Rally doesn't
duplicate anything
IMHO rally duplicates at least some pieces. So you can find parts of
Tempest scenarios tests in the benchmarks area, Tempest stress tests
and Tempe
y to have
a tool set that monitors agreements of a service. I don't see how this fits
into the existing projects you are referring to. IMHO SLA Management would
never consist of debugging or tracing anything. It would be always
focused on a
service and not on a root-cause analysis.
Regard
+1
> -Ursprüngliche Nachricht-
> Von: Matthew Treinish [mailto:mtrein...@kortar.org]
> Gesendet: Dienstag, 22. Juli 2014 00:34
> An: openstack-dev@lists.openstack.org
> Betreff: [openstack-dev] [QA] Proposed Changes to Tempest Core
>
>
> Hi Everyone,
>
> I would like to propose 2 change
send
it around
Regards
Marc
> -Ursprüngliche Nachricht-
> Von: Matthew Treinish [mailto:mtrein...@kortar.org]
> Gesendet: Donnerstag, 29. Mai 2014 18:07
> An: openstack-dev@lists.openstack.org; openstack-in...@lists.openstack.org
> Betreff: [openstack-dev] [QA][Infra] Mid-
Hi,
7:30pm at Ted's Montana Grill. I called them and they put us on the list.
Again the location:
https://plus.google.com/100773563660993493024/posts/P9YSgT8AVXh
It's quite near to all the hotels.
See you there!
Marc
From: Koderer, Ma
nd me your mobile number..
Regards
Marc
From: Koderer, Marc [m.kode...@telekom.de]
Sent: Monday, May 05, 2014 8:41 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta
All right, let
arrive Sunday at 3:30pm. Either Sunday or Monday are fine with me. Lookging
forward to it :-)
On Wed, Apr 30, 2014 at 5:11 AM, Koderer, Marc
mailto:m.kode...@telekom.de>> wrote:
Hi folks,
last time we met one day before the Summit started for a short meet-up.
Should we do the same this time?
Hi folks,
last time we met one day before the Summit started for a short meet-up.
Should we do the same this time?
I will arrive Saturday to recover from the jet lag ;) So Sunday 11th would be
fine for me.
Regards,
Marc
___
OpenStack-dev mailing
> From: Matthew Treinish [mtrein...@kortar.org]
> Sent: Tuesday, March 18, 2014 7:08 PM
> On Tue, Mar 18, 2014 at 12:34:57PM +0100, Koderer, Marc wrote:
> > On Tue, 18 Marc 2014 12:00:00 +0100
> > Christopher Yeoh [mailto:cbky...@gmail.com] wrote:
> > > On T
On Tue, 18 Marc 2014 12:00:00 +0100
Christopher Yeoh [mailto:cbky...@gmail.com] wrote:
> On Tue, 18 Mar 2014 10:39:19 +0100
> "Koderer, Marc" wrote:
> >
> > I just recognized that we have very similar interface definitions in
> > tempest/api_schema and etc/
location? I'd prefer to use json as
file format instead of .py. As final goal we should find a way how to merge
them competently but I feel like this is something for the design summit ;)
Regards,
Marc
DEUTSCHE TELEKOM AG
Digital Business Unit, Cloud Services (P&I)
Marc Koderer
Cloud T
the usage of "import-time" code and we may think about a better solution in
general.
I'll try to address the missing pieces tomorrow.
Bug: https://bugs.launchpad.net/tempest/+bug/1291826
Regards,
Marc
DEUTSCHE TELEKOM AG
Digital Business Unit, Cloud Services (P&I)
Marc K
> Von: LELOUP Julien [mailto:julien.lel...@3ds.com]
> Gesendet: Montag, 3. März 2014 11:21
> An: OpenStack Development Mailing List (not for usage questions); Koderer,
> Marc
> Betreff: [Tempest - Stress Test][qa] : implement a full SSH connection on
> "ssh_floating.py&qu
Hi Forent,
thanks for the link. Our current implementation of for the cleanup is a bit
buggy. I will give your script a try.
Maybe we could use it an replace the existing module.
Regards
Marc
From: Florent Flament [florent.flament-...@cloudwatt.com
could end up in a quite confusing interface.. if you allow kwargs for such a
generic case.
Are you already working on those bugs? If yes, could you assign them to you?
Regards,
Marc
>
> From: LELOUP Julien [julien.lel...@3ds.com]
> Sent: Mond
/tempest/stress/etc/sample-unit-test.json
With that you can launch them with the parameters you already described.
Regards,
Marc
From: LELOUP Julien [julien.lel...@3ds.com]
Sent: Friday, January 17, 2014 3:49 PM
To: Koderer, Marc
Cc: openstack-dev
possible help to understand the state. I didn't managed to work on the action
items that are left.
Your suggestions sound good. So I'd happy so see some patches :)
Regards
Marc
From: LELOUP Julien [julien.lel...@3ds.com]
Sent: Friday, January 17, 201
Hi all,
first part of the negative test framework is ready for review:
https://review.openstack.org/#/c/64733/
Please have a look.
Regards
Marc and David
DEUTSCHE TELEKOM AG
Digital Business Unit, Cloud Services (P&I)
Marc Koderer
Cloud Technology Software Developer
T-Online-Allee 1, 6
If you are planning to work in that
area for more than just a patch, a blueprint would be nice. A good way to
coordinate your efforts is also in the QA meeting
(https://wiki.openstack.org/wiki/Meetings/QATeamMeeting)
Regards
Marc
From: LELOUP Julien [
.
Feedback is welcome!
Regards
Marc
From: Robert Collins [robe...@robertcollins.net]
Sent: Tuesday, January 07, 2014 3:59 AM
To: David Kranz
Cc: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [qa] negative test generation and testscenarios
ion of negative testing, and just fuzz known
> bad against the schema definitions.
> >> Sorry, I'm not sure I understand this question correctly.
> >> We need to define schemas for each API with the separated schema
> patches.
> >> It is impossible to define
s
> > there are plenty of open slots before 1500 UTC which would be early
> > for people in the US and late for people in the Asia Pacific region.
> > There are plenty of slots starting at 2300 UTC which is late for
> people in Europe.
> >
> > Would something like
+1 for both!
From: Sean Dague [s...@dague.net]
Sent: Friday, November 15, 2013 2:38 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [qa] Proposals for Tempest core
It's post summit time, so time to evaluate our c
Hi all,
I think we have quite the same issue with the neutron testing. I already put it
on the agenda for the QA meeting for today.
Let's make it to a general topic.
Regards
Marc
From: Giulio Fidente [gfide...@redhat.com]
Sent: Thursday, Novemb
Hi,
see below.
Regards
Marc
From: Kenichi Oomichi [oomi...@mxs.nes.nec.co.jp]
Sent: Wednesday, November 13, 2013 7:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [qa] moratorium on new negative tests in
oint for a discussion on the summit.
Regards,
Marc
DEUTSCHE TELEKOM AG
Digital Business Unit, Cloud Services (P&I)
Marc Koderer
Cloud Technology Software Developer
T-Online-Allee 1, 64211 Darmstadt
www.telekom.com
LIFE IS FOR SHARING.
DEUTSCHE TELEKOM AG
Supervisory Board: Prof. Dr. Ulrich Le
Hello,
I am Marc Pinhède, working in Netvirt with professor Omar Cherkaoui.
We started working on a Neutron plugin. A first version is now almost ready.
To inform the community, we posted a blueprint:
https://blueprints.launchpad.net/neutron/+spec/modular-adaptative-plugin
We would like to
want to generate load that simulates real life load in a
production-like system
--> Leads to concurrent scenario test
Kind Regards
Marc
DEUTSCHE TELEKOM AG
Digital Business Unit, Cloud Services (P&I)
Marc Koderer
Cloud Technology Software Developer
T-Online-Allee 1, 64211 D
60 matches
Mail list logo
