more documentation in the next days and
I like to have it hierarchically sorted...
Just let me know if something is not clear enough.
Regards,
jaume
[1]:
https://wiki.openstack.org/wiki/Neutron/DynamicRouting/TestingDynamicRouting
--
Jaume Devesa
Software Engineer at Mid
;t overload our server.
Cheers,
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing l
ld
be happy to collaborate in anything to include it there as first
experimental extension.
Cheers,
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/lis
Sorry, I forgot to tag the subject.
On 28 August 2014 16:24, Jaume Devesa wrote:
> I would like to ask you consider to raise priority from low to medium (I
> completely
> understand this is not a high priority feature) the BGP Dynamic Routing
> feature
> (https://blueprint
enced neutron developer confirm me that is the path to follow or
propose another one, please?
Thanks!
--
Jaume Devesa
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to include also resource sync
>> > state. I've put some rumblings on the subjects in the etherpad [3].
>> > Still, it has been correctly pointed out that it might not be enough to
>> know
>> > that a resource is out of
your thoughts in the document.
> >
> > Thank you.
> >
> > Sincerely,
> > Artem Dmytrenko
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>> ___
> >> OpenStack-dev mailing list
> >> OpenStack-dev@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > __
nd maybe they can be more reactive in
the 'good' patches.
[1]: https://review.openstack.org/#/c/99679/2
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstac
. Just want to avoid the first run.
> Thanks,
> Anita.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Regards,
--
Jaume Devesa
Software Engineer at Midokura
Hi Sean,
for what I understood, we will need a new feature flag for each new
feature, and a feature flag (default to false) for each deprecated one. My
concern is: since the goal is make tempest a confident tool to test any
installation and not and 'tempest.conf' will not be auto-generated from an
Kranz wrote:
> On 04/16/2014 11:48 AM, Jaume Devesa wrote:
>
> Hi Sean,
>
> for what I understood, we will need a new feature flag for each new
> feature, and a feature flag (default to false) for each deprecated one. My
> concern is: since the goal is make tempest a confi
Another question about this, Kyle:
once merged, will there be a place where to read these approved specs, or
should we run it locally? I tried to find the approved *nova-specs *in
docs.openstack.org, but I couldn't find them.
Regards,
jaume
On 21 April 2014 09:02, Mandeep Dhami wrote:
>
> Got
Great! Thanks Anne!
On 22 April 2014 16:44, Anne Gentle wrote:
>
>
>
> On Tue, Apr 22, 2014 at 4:42 AM, Jaume Devesa wrote:
>
>> Another question about this, Kyle:
>>
>> once merged, will there be a place where to read these approved specs, or
>> should
of today's L3 subteam meeting.
[1]: https://review.openstack.org/#/c/125401/
[
2]: https://review.openstack.org/#/c/125401/
[3]: https://etherpad.openstack.org/p/bgp-vpn-dynamic-routing
Cheers,
--
Jaume Devesa
Software Engineer at Midokura
__
ent/d/1fUPhpBWpiUvBe_c55lkokDIls--4dKVSFmGVtjxjg0w/edit#
[3]: https://etherpad.openstack.org/p/kilo-l3-refactoring
[4]: https://blueprints.launchpad.net/neutron/+spec/neutron-provider-router
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing
meeting on Thursday.
>
> Carl
> On Oct 29, 2014 5:27 AM, "Jaume Devesa" wrote:
>
>> Hello,
>>
>> it seems like the BGP dynamic routing it is in a good shape to be
>> included in Neutron during Kilo[1]. There is quite interest in offer
>> BGP
penStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
t seems
> it is not the one under the 'edge router' name [2]
I changed the blueprint URL and I forgot to update this spec. I'll
update it in a few days.
>
> Salvatore
>
> [1] https://review.openstack.org/#/c/131535/
> [2] https://review.openstack.org/128272
>
>
om the cloud under that
> respective VRF (VPN).*
>
>
>
> Thanks ®ards,
>
> Keshava
>
>
>
> -Original Message-
> From: Jaume Devesa (Code Review) [mailto:rev...@openstack.org]
> Sent: Wednesday, June 25, 2014 3:06 PM
> To: Artem Dmytrenko
> Cc: Baldwin, Carl (OpenSt
___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Jaume Devesa
Software Engineer at Midokura
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ful to provide URLs that are accessible for
> much longer times, so that anyone who refers to this email months later
> will still be able to access the code in question.
>
> --
> /kashyap
>
> ___
> OpenStack-dev mailing list
>
Hi all,
I see it has been passed two weeks since first mail in this thread and that
blueprint still without assignee. I also think this is a good option for my
first blueprint. However, I can not assign blueprints to myself, only bugs.
Can anybody assign to me?
Steven: if you still interested in
Hi Sam,
that's a great work and it will be for sure my default driver for my
development environment.
I have a question: once the review will be approved and the code merged
into master, do you plan to create a driver nova subteam as Xen, HyperV and
others do? I would be glad to cooperate on it.
2:48 PM
> Subject: Re: [openstack-dev] [midonet] Split up python-midonetclient
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Cc: Jaume Devesa
>
>
> >> Ditto. We already have a mirror re
eople much more experienced than me in Kuryr. I hope I
haven't said anything stupid.
Best regards,
[1]: http://github.com/openstack/kuryr
--
Jaume Devesa
Software Engineer at Midokura
PGP key: 35C2D6B2 @ keyserver.ubuntu.com
signature.asc
Description: PGP signature
://github.com/openstack/diskimage-builder/tree/master/elements/source-repositories
[4]:
https://github.com/openstack/tripleo-puppet-elements/blob/master/elements/puppet-modules/source-repository-puppet-modules
--
Jaume Devesa
Software Engineer at Midokura
_
> 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
>
--
Jaume Devesa
Software
No. I'm saying that I prefer python-os-midonetclient to be a project by its
own
instead of being merged inside the neutron plugin repo.
On 14 December 2015 at 18:43, Antoni Segura Puimedon <
toni+openstac...@midokura.com> wrote:
>
>
> On Mon, Dec 14, 2015 at 6:07 PM, Jaume De
interested to support that in TripleO Puppet
> elements, I can help with that.
>
> On 12/14/2015 02:25 PM, Dan Prince wrote:
> > On Fri, 2015-12-11 at 21:50 +0100, Jaume Devesa wrote:
> >> Hi all,
> >>
> >> Today TripleO CI jobs failed because a new commit introd
(specifically the Puppetfile
> from puppet-openstack-integration) and produce the DIB_REPOREF variables
> (perhaps ignoring all :ref => 'master' ones), so that we don't have to
> track and update them by hand.
>
> I'm not sure if we absolutely need a Puppetfile
__
> 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
>
>
--
Jaume Devesa
Software Engineer at Midokura
__
ect:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Jaume Devesa
Software Engineer at Midokura
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
tuskar as well?
Am I right?
Cheers,
--
Jaume Devesa
Software Engineer at Midokura
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
Hi Steven/Emilien,
Thanks for the quick responses.
On Tue, 18 Aug 2015 16:10, Steven Hardy wrote:
> On Tue, Aug 18, 2015 at 04:19:08PM +0200, Jaume Devesa wrote:
>
> I think the pattern for the templates will be similar to the Cisco ML2
> plugins which are currently bein
ss it next Thursday on the IRC meeting?
On 18 August 2015 at 18:14, Steven Hardy wrote:
> On Tue, Aug 18, 2015 at 05:59:44PM +0200, Jaume Devesa wrote:
> > Hi Steven/Emilien,
> >
> > Thanks for the quick responses.
> >
> > On Tue, 18 Aug 2015 16:10, Steven Hardy wrot
Sorry, I meant "Tuesday".
On 19 August 2015 at 10:51, Jaume Devesa wrote:
> Thanks Steven.
>
> I've registered the blueprint:
>
> https://blueprints.launchpad.net/tripleo/+spec/midonet-deployment-support
>
> We'll start preparing the pseudo-thirdparty
sage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Jaume Devesa
Software Engineer at Midokura
__
OpenStack Developm
>
>>> __
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> > http://lists.openstack.or
ors by this result.
>
> Any feedback is welcome here.
> --
> Emilien Macchi
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.
> -Sean
>>
>> -- Sean Dague http://dague.net
>>
>> __
>>
>>
>>
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/
t about this on next Monday's third party meeting?
Regards,
[1]: https://review.openstack.org/#/c/152876
El 06/02/15 a las 22:54, Kyle Mestery escribió:
,
OpenStack Development Mailing List (not for usage questions)
OpenStack Development Mailing List (not for usage questions)
- --
Jaume
i
[3]: https://github.com/midonet/python-neutron-plugin-midonet
El 11/02/15 a las 17:43, Jaume Devesa escribió:
> Hello,
>
> I'm working in the same job as Kyle for the midonet plugin, but
> first I need to do some changes in devstack. (Sean's review on my
> patch[1]
r the weekend.
>
> Artem Dmytrenko and Jaume Devesa have done great work [1] with me over
> the last year figuring out how to integrate routing protocols with
> Neutron. We have had to exhibit some patience as this work has not
> yet bubbled to the top of the team's overall priority l
_
> 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
--
Jaume Devesa
Software Engineer at Mido
li R. Taleghani
> @linkedIn <http://ir.linkedin.com/in/taleghani>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.opensta
the core part of the project when we'll move to
python3.
Is there a policy that prevents to run some services on python2 and some on
python3 in distros? What's the reason behind?
Regards,
Jaume Devesa
Software Engineer @ Midokura
