Jim,
Did you verify with Marvel if it's possible to keep the name and use
his hero. In that way we could be the first OpenStack project to have
one.
Victor Morales
On Fri, 2016-04-01 at 08:46 +0300, Jimmy Akin wrote:
> Dear Neutrinos,
>
> We've been following the project for quite some time.
>
Agree, sometimes is hard to figure out what is the Devstack variable that will
modify the configuration value.
There is an effort to categorize the configuration options[1] of some of the
projects. I’m wondering if it could be possible to create category or field
that specifies the Destack var
On 4/11/16, 5:07 AM, "Jakub Libosvar" wrote:
>Hi,
>
>recently we hit an issue in Neutron with tests getting stuck [1]. As a
>side effect we discovered logs are not collected properly which makes it
>hard to find the root cause. The reason of missing logs is that we send
>SIGKILL to whatever
Thanks everyone for voting, I started recently and I’m sure that I’ve many
things to learn but something that I discover since the beginning was the
enthusiasm and welcoming aptitudes of this community. I’m going to do my best
for keeping high standards of the code
Thanks
Victor Morales
irc: e
I got this link[11] from Ankur, apparently Nova and Neutron has already started
a common effort
[11] https://review.openstack.org/#/c/330027/
Regards,
Victor Morales
irc: electrocucaracha
On 3/1/17, 5:53 PM, "Mike Perez" wrote:
>Hey all,
>
>I kicked off a thread [1] to start talking about
On 3/6/17, 8:28 AM, "Ihar Hrachyshka" wrote:
>Hi all,
>
>This is a report on upgrades related topics discussed during PTG in
>Atlanta. A general PTG report from PTL can be found at:
>
>http://lists.openstack.org/pipermail/openstack-dev/2017-February/113032.html
>
>Topics discussed:
>1. O
Well my crazy idea was the addition[10] of an extra argument(—men-trace) on the
pbr binary creation. The idea is to be able to use it from any openstack
binary and print those methods that are differences in the memory
consumption[11].
Regards/Saludos
Victor Morales
irc: electrocucaracha
[10]
+1
From: Zhipeng Huang
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, April 24, 2017 at 3:06 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [tricircle]mascot for the Tricircle project
perfect XD
On M
Armando,
I noticed that Tricircle is mentioned there. Shouldn’t be better to extend its
current functionality or what are the things that are missing there?
Regards,
Victor Morales
From: "Armando M."
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, May
Hi Emilien,
I noticed that the configuration file was created using puppet. I submitted a
patch[1] that was targeting to include the changes in Devstack. My major
concern is with the value of WSGIScriptAlias which should be pointing to WSGI
script.
Regards/Saludos
Victor Morales
[1] https:/
Hi Meher,
I don’t think that you need to create those folders or at least that it’s shown
in the devstack functions[1].
Regards/Saludos
Victor Morales
[1] https://github.com/openstack-dev/devstack/blob/master/lib/apache#L178-L192
From: "meher.h...@orange.com"
Reply-To: "OpenStack Development
Hi Meher,
Can you include the paste for this? Can you also verify that your
global-requirements file contains the tricircleclient module[1]?. It seems
like the pip_install_gr function [2][3] is not resolving [4] the
tricircleclient module[5]
Regards,
Victor Morales
[1]
https://github.com/op
As far as I remember the reason to have everything on a single file is because
we’re trying to make Apache to load the configuration values during the startup.
On 9/6/17, 9:19 PM, "Thomas Bechtold" wrote:
Hi Kevin,
On 04.09.2017 15:01, Kevin Benton wrote:
> Yes, unfortunately I
/blob/master/neutron/common/config.py#L76-L78
On 9/15/17, 3:23 AM, "Thomas Bechtold" wrote:
Hi Victor,
On 13.09.2017 17:37, Morales, Victor wrote:
> As far as I remember the reason to have everything on a single file is
because we’re trying to make Apach
Manjeet,
Tony has some issues moving model classes to other location. Given that some
class models are used by other neutron services, Ihar suggest to use
debtcollector to make this transition smoothly. Can we include that solution
as part of this movement?
Thanks
Victor Morales
On 7/28/1
Hey neutrinos,
First of all, the high priority for OVO implementation in newton release are
the implementation and integration of port, subnet and network objects, but
given that more people is joining to this initiative and also many patches are
related directly and indirectly to this, results
+1, even if my vote doesn’t count.
From: Miguel Lavalle
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, February 5, 2018 at 11:21 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [neutron] PTL candidacy for Rocky
Hello OpenStack Communi
It’s sad to read this, I’m still digesting some of your articles of your blog.
Thanks for all of those years of making OpenStack Quantum/Neutron better.
Regards,
Victor Morales
On 11/28/16, 12:58 PM, "Assaf Muller" wrote:
>Hi all,
>
>For the past few months I've been gaining more responsibi
Henry, it has been a pleasure to have been working with you and thanks for
supporting this community and helping us to get involved quickly. Best wishes
for your new adventure.
Thanks
Victor Morales
PS: Hopefully your Linkedin photo was not taken couple days before you started
working in Neu
Hey there,
There is a mismatch of namespaces in neutron which uses AGENT and agent which
is addressed by Ihar in the patch[1]. That raised the question is
olo-config-generator should be normalize this namespaces, maybe(with my limited
knowledge of oslo.conf) this change can be placed in _clea
More likely, my vote doesn’t count but I’ve seen them very actively
contributing, so +1
From: "Armando M." mailto:arma...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, December 15, 2016 at 5:14 PM
T
Those are sad news for starting this year. First of all, grazie for being the
PTL of Neutron during these last releases. When I started contributing to
neutron, I noticed that this community is so vibrant and passioned, that this
energy needs to be properly addressed and you have demonstrated
My two cents on this
Agree with Kevin, IaaS solutions(like CloudStack, OpenNebula, OpenStack, etc.)
offer a deep level of customization for those apps which requires fine-grained
control of Cloud resources with the disadvantage of increasing the time
required for developing them. By other hand,
Just a FYI, Ankur have been working on have a Feature Classification Matrix in
Neutron[1] which collects some of this information
[1] https://review.openstack.org/#/c/318192/
Regards/Saludos
Victor Morales
Irc: electrocucaracha
On 1/13/17, 10:29 PM, "Mike Perez" wrote:
>Hello all,
>
>In t
Definitely, both are great candidates and my best wishes to both during this
process.
Given the latest issues related with the memory consumption[1] in CI jobs, I’m
just wondering if you have a plan to deal and/or improve it in Neutron.
Regards,
Victor Morales
irc: electrocucaracha
[1] htt
Howdy,
First of all, thanks for the creation of this space to discuss about shouldn’t
be something common(in an utopia) but it’s part of our daily duties. I’m not
sure if this is the right venue but I discovered today that the current
implementation of the job for coverage[1] only valides the
One of my favorites is the usage of #undo command during the meetings for
fixing a quick copy & paste link. Should be necessary to include more
information in this wiki entry[1]
Victor Morales
irc: electrocucaracha
[1] https://wiki.openstack.org/wiki/UsingIRC
From: Rob C mailto:hyaku...@gmai
On 2/9/17, 10:59 PM, "Ihar Hrachyshka" wrote:
>Hi all,
>
>I noticed lately a number of job failures in neutron gate that all
>result in job timeouts. I describe
>gate-tempest-dsvm-neutron-dvr-ubuntu-xenial job below, though I see
>timeouts happening in other jobs too.
>
>The failure mode is all
Hey Lubosz,
First of all, good job responding to the concerns of users and keeping a
healthy OpenStack ecosystem. I’ve one comment about this email, maybe it was
a cultural thing but I found it a little aggressive, specially the use of some
pronouns and names. I know you and I’m completely s
Howdy,
I’m happy to announce that after OpenStack Governance has approved[1] and infra
them processed the request[2], the python-tricircleclient repository has been
created[3]. This client pretends to make things simpler for users who require
multi region solutions which can be addressed by
This achievement reflects the constant effort you makes in OpenStack, kudos Ihar
From: "Armando M."
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Saturday, September 17, 2016 at 11:40 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [o
Hi neutrinos,
The idea of this email is to summarize the effort that we're making during the
implemetation of Rolling upgrades in Neutron, as well as
sharing the upcoming changes.
Announcements
Neutron Newton RC1 has been created and this contains the following changes
related to
+1
From: Miguel Lavalle
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, October 14, 2016 at 1:30 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron] Neutron team social event in Barcelona
Dear Neutrinos,
I am organizing a social eve
I just want to add my two cents on this. Several months ago I asked to nova
community about a bug that they decided to don’t implement, this bug was
suggesting to add a validation to String OVO field[1] to check if the length of
the columns has been changed, the answer was that they considered
My two cents on this.
OVO is going to be the new layer to access to DB model classes, therefore all
the calls to the database(ensuring that there is an opened session) and the
process to receive(validating fields) and/or return data(determining if a
specific column exists) should be managed
Hey Carl,
These are sad news, thanks for those years helping to make OpenStack better,
best of the wishes for your future assignments.
Thanks,
Victor Morales
From: Carl Baldwin mailto:c...@ecbaldwin.net>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack
Thant’s remind me when we tried to improve cloud-init. Basically, the
discovery process checks sequentially where the instance is being landed(EC2,
GoogleCompute, OpenStack). This process could be done in parallel and reduce
the time to boot.
Regards,
Victor Morales
On 11/16/16, 11:31 AM
37 matches
Mail list logo