On 2017-01-25 08:24, Andreas Jaeger wrote:
> On 2017-01-25 05:03, Matthew Thode wrote:
>> On 01/24/2017 09:57 PM, Matthew Thode wrote:
>>> Basically I'd like to ask the docs people if they are fine with updating
>>> the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to
>>>
I pushed https://review.openstack.org/#/c/425023 as one of approaches.
On Wed, Jan 25, 2017 at 10:29 AM Anna Taraday
wrote:
> Thanks for bringing this up!
>
> I was assuming that from Ocata everyone should switch from usage 'old'
> TunnelTypeDriver to updated one.
>
On 2017-01-25 05:03, Matthew Thode wrote:
> On 01/24/2017 09:57 PM, Matthew Thode wrote:
>> Basically I'd like to ask the docs people if they are fine with updating
>> the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to
>> sphinx>=1.5.1. This change seems fairly major, especially
Hello!
I have 2 similar patches with different change_id. On the first case
Jenkins has failed: https://review.openstack.org/#/c/422481/ , on the
second case Jenkins has successfully passed:https://review.openstack.org/#
/c/424553/ . I can not understand the reason for it. Besides all test that
Thanks for bringing this up!
I was assuming that from Ocata everyone should switch from usage 'old'
TunnelTypeDriver to updated one.
Revering both back to session means reverting all refactor and this is not
in line with enginefacade work and as I remember some of OVO patches we
waiting for this
Hi,
We have weekly Nova API meeting today. The meeting is being held Wednesday
UTC1300 and irc channel is #openstack-meeting-4.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
Thanks
Hello Bernard,
I believe the design docs and API parts are good and once I had the
environment up and running I didn't have any problems following the
examples or running the commands.
My biggest hurdle was around getting the devstack environment functioning,
I was following the steps here:
Thanks for stepping up again, Matt!
You've been an excellent Nova PTL: knowledgeable, diligent, pragmatic,
welcoming, (and fun!).
I look forward to working with you and learning from you in the next release.
Thanks for all you do (and thanks to your family too)!
Enjoy your time in Mexico; you
+1 for both.
-Original Message-
From: Wenzhi Yu [mailto:wenzhi...@163.com]
Sent: Tuesday, January 24, 2017 7:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Zun] Propose a change of the Zun core
On 1/24/2017 2:57 PM, Matt Riedemann wrote:
On 1/24/2017 2:38 PM, Sylvain Bauza wrote:
It's litterally 2 days before FeatureFreeze and we ask operators to
change their cloud right now ? Looks difficult to me and like I said in
multiple places by email, we have a ton of assertions saying it's
On 1/24/2017 2:57 PM, Matt Riedemann wrote:
On 1/24/2017 2:38 PM, Sylvain Bauza wrote:
It's litterally 2 days before FeatureFreeze and we ask operators to
change their cloud right now ? Looks difficult to me and like I said in
multiple places by email, we have a ton of assertions saying it's
On 01/24/2017 09:57 PM, Matthew Thode wrote:
> Basically I'd like to ask the docs people if they are fine with updating
> the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to
> sphinx>=1.5.1. This change seems fairly major, especially given that
> there is no overlay between the
Basically I'd like to ask the docs people if they are fine with updating
the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to
sphinx>=1.5.1. This change seems fairly major, especially given that
there is no overlay between the 'before' and 'after' versions.
I'd appreciate docs team
On 01/23/2017 05:07 AM, Saravanan KR wrote:
Thanks John for the info.
I am going through the spec in detail. And before that, I had few
thoughts about how I wanted to approach this, which I have drafted in
https://etherpad.openstack.org/p/tripleo-derive-params. And it is not
100% ready yet, I
On 01/24/2017 12:45 AM, Saravanan KR wrote:
Thanks Giulio for adding it to PTG discussion pad. I am not yet sure
of my presence in PTG. Hoping that things will fall in place soon.
We have spent a considerable about of time in moving from static roles
to composable roles. If we are planning to
On 1/24/2017 8:16 PM, Alex Xu wrote:
One other thing: we're going to need to also fix this in
python-novaclient, which we might want to do first, or work
concurrently, since that's going to give us the client side
perspective on how gross it will be to deal with this issue.
Cathy,
I believe Mohan Kumar did that work.
- Louis
-Original Message-
From: Cathy Zhang
Sent: Tuesday, January 24, 2017 5:39 PM
To: OpenStack Development Mailing List (not for usage questions); Henry Fourie;
Vikram Choudhary
Cc: Cathy Zhang
Subject: RE: [openstack-dev]
2017-01-25 0:27 GMT+08:00 Matt Riedemann :
> On 1/24/2017 9:18 AM, Matt Riedemann wrote:
>
>>
>> First, thanks to Kevin and Alex for finding this issue and explaining it
>> in detail so we can understand the scope.
>>
>> This is a nasty unfortunate issue which I really wish
+1
On 25/01/17 02:36, Brian Rosmaita wrote:
> I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance
> core. She has been an active reviewer and contributor to the Glance
> project during the Newton and Ocata cycles, has contributed to other
> OpenStack projects, and has
+1
She does good work and I will be happy to see this happen.
I am not so sure about the argument part :) (jk)
On 1/24/17 8:36 AM, Brian Rosmaita wrote:
> I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance
> core. She has been an active reviewer and contributor to the
Hi all,
I've had the pleasure of serving the Zaqar community as PTL for the past
three cycles, and I'd like to continue for Pike cycle, if you'll have me.
For Pike release, things I'd like to do:
1. Scalability
A scalable service should be able to process increases in load
without obvious
Thanks Alex for raising this up widely, as Chinese holiday is comming and
Alex and me might be away for a week, And it will be better to fix this
faster, so thanks Artom taking over to fix it :)
On Wed, Jan 25, 2017 at 7:50 AM, Ghanshyam Mann
wrote:
>
> On Wed, Jan 25,
There is a SFC Horizon code patch available. And our presentation video GUI is
based on that.
Louis/Vikram,
I am on business trip and have difficulty to access some openstack links. Could
you share the link to our SFC Horizon work?
Thanks,
Cathy
-Original Message-
From: Bernard
>I would really like us to discuss this issue head-on and see what is
missing in Neutron APIs and what would take to make them extensible so that
vendors do not run around trying to figure out alternative solutions
The Neutron API is already very extensible and that's problematic. Right
now a
Tackers,
I'd like to propose following changes to the Tacker core team.
Stephen Wong
After being associated with Tacker project from its genesis, Stephen
Wong (irc: s3wong) has decided to step down from the core-team. I
would like to thank Stephen for his contribution to Tacker,
particularly
Another file in our repo is just to provide this review mechanism for
now. All deliverables has to follow governance procedures as well.
On 24 January 2017 at 12:04, Doug Hellmann wrote:
> Excerpts from Ian Cordasco's message of 2017-01-24 14:55:31 -0500:
>> -Original
On 01/24/2017 06:42 PM, Sukhdev Kapur wrote:
Ihar and Kevin,
As our potential future PTLs, I would like to draw your attention to one
of the critical issue regarding Neutron as "the" networking service in
OpenStack.
I keep hearing off and on that Neutron is not flexible to address many
> -Original Message-
> From: Paul Bourke [mailto:paul.bou...@oracle.com]
> Sent: Tuesday, January 24, 2017 11:49 AM
> To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org>
> Subject: Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?
On Tue, Jan 24, 2017 at 3:24 PM, Edgar Magana
wrote:
> You just made me remember my time as police man for Neutron plugins! ☺
>
Now we can have distributed police men :-)
-Sukhdev
>
>
> Edgar
>
>
>
> *From: *Sukhdev Kapur
> *Reply-To:
Sean Dague wrote:
> I'll probably still default this to python3, it is the future direction
> we are headed.
Works for me :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Wed, Jan 25, 2017 at 1:18 AM, Matt Riedemann wrote:
> On 1/24/2017 2:05 AM, Alex Xu wrote:
>
>> Unfortunately the device tag support in the API was broken in the old
>> Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks
>> to Kevin Zheng to find out
I remember good old days when CI was introduced in Neutron (during Icehouse
time frame). There was excellent momentum behind it. We did not know some
of the enforcement details, which created lots of confusion/havoc.
Now that we have a better understanding of the past issues, and lots of
good
Ihar and Kevin,
As our potential future PTLs, I would like to draw your attention to one of
the critical issue regarding Neutron as "the" networking service in
OpenStack.
I keep hearing off and on that Neutron is not flexible to address many
networking use cases and hence a new (or additional)
You just made me remember my time as police man for Neutron plugins! ☺
Edgar
From: Sukhdev Kapur
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, January 24, 2017 at 3:14 PM
To: "OpenStack
In deed, excellent and well qualified candidates.
Best of Luck to both
-Sukhdev
On Tue, Jan 24, 2017 at 7:16 AM, Armando M. wrote:
> Hi neutrinos,
>
> No, it's not what you might be thinking...I am just delighted to see two
> excellent candidates willing to take the
On Mon, Jan 23, 2017 at 2:03 PM, Emilien Macchi wrote:
> Greeting folks,
>
> I would like to propose some changes in our core members:
>
> - Remove Jay Dobies who has not been active in TripleO for a while
> (thanks Jay for your hard work!).
> - Add Flavio Percoco core on
On Tue, Jan 24, 2017 at 11:53 AM, Alexis Monville <
alexis.monvi...@redhat.com> wrote:
>
> >
> > I spent quite a bit of our cross project session at the Ocata Summit
> doing a
> > quick recap of the concept of Servant Leadership and it seemed like
> plenty
> > of attendees appreciated that. Would
Or start writing down (in the BP) what you want to put in the driver.
Network, lbaas, scripts, the order of the scripts and then we can see
if it's possible to adapt to the current coreos driver.
Spyros
On Jan 24, 2017 22:54, "Hongbin Lu" wrote:
> As Spyros mentioned, an
Hi Anna,
I see that as part of [1], we changed the argument type for the $subj
function from session to context. Sadly, it turns out we still call it
with a session from the 'old' TunnelTypeDriver. I suspect the same
issue may affect allocate_fully_specified_segment.
I assume that means all
On 1/24/2017 2:38 PM, Sylvain Bauza wrote:
It's litterally 2 days before FeatureFreeze and we ask operators to
change their cloud right now ? Looks difficult to me and like I said in
multiple places by email, we have a ton of assertions saying it's
acceptable to have not all the filters.
As Spyros mentioned, an option is to start by cloning the existing templates.
However, I have a concern for this approach because it will incur a lot of
duplication. An alternative approach is modifying the existing CoreOS templates
in-place. It might be a little difficult to implement but it
OpenStack community decided to officially support Python 3.5 by the
end of Pike cycle:
https://governance.openstack.org/tc/goals/pike/python35.html
To track this work in TripleO, I created a blueprint:
https://blueprints.launchpad.net/tripleo/+spec/support-python-35
I'm also tracking the work
Le 24/01/2017 22:22, Dan Smith a écrit :
>> No. Have administrators set the allocation ratios for the resources they
>> do not care about exceeding capacity to a very high number.
>>
>> If someone previously removed a filter, that doesn't mean that the
>> resources were not consumed on a host.
On 2017-01-24 13:10:26 -0800 (-0800), Ihar Hrachyshka wrote:
> On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley wrote:
[...]
> > I guess the question I have is who, then, can tell our
> > operators/users what Neutron drivers are reasonably supported? It
> > sounds like you're
This email is directed at anyone who maintains a 3rd-party Template
plugin for Heat. (Do such people exist?)
Good news: you know how it's never been clear what parts of the Stack
and Resource interfaces you could rely on to be stable? I'm proposing to
fix that in Pike.
Bad news: you know
> No. Have administrators set the allocation ratios for the resources they
> do not care about exceeding capacity to a very high number.
>
> If someone previously removed a filter, that doesn't mean that the
> resources were not consumed on a host. It merely means the admin was
> willing to
On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley wrote:
> On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote:
>> On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote:
>> > I'm on board with getting visibility into the drivers with improvements to
>>
On Mon, Jan 23, 2017 at 2:03 PM, Emilien Macchi wrote:
> Greeting folks,
>
> I would like to propose some changes in our core members:
>
> - Remove Jay Dobies who has not been active in TripleO for a while
> (thanks Jay for your hard work!).
> - Add Flavio Percoco core on
On Tue, Jan 24, 2017 at 12:03 PM, Juan Antonio Osorio
wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core
On 24 January 2017 at 12:46, Jeremy Stanley wrote:
> On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote:
> > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote:
> > > I'm on board with getting visibility into the drivers with
> improvements to
> >
On 01/24/2017 02:28 PM, Steve Martinelli wrote:
>
> The OpenStackClient team will be posting patches to bump the minimum
> level of python-openstacksdk to the latest release 0.9.13 (out today).
> We'll also be releasing a new python-openstackclient version (3.8.0),
> which should also be the
Cody,
Thank you for your contributions over the years.
On Fri, Jan 20, 2017 at 12:29 PM, Cody Herriges wrote:
> I attempted to send this out last week but think I messed it up by sending
> from my work email address which isn't the one I am signed up to the lists
> with.
On 24/01/17 03:05 PM, Julien Danjou wrote:
> I think Aodh emits notifications when something happens so it can be in
> Panko indeed. I don't think it'd be fair to force Panko to have (a
> recent) history though. :)
i'm going to add a work item (for anyone): allow multiple notification
topics
Hi.
IMO, you should add a BP and start by adding a v2 driver in /contrib.
Cheers,
Spyros
On Jan 24, 2017 20:44, "Kevin Lefevre" wrote:
> Hi,
>
> The CoreOS template is not really up to date and in sync with upstream
> CoreOS « Best Practice »
On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote:
> On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote:
> > I'm on board with getting visibility into the drivers with improvements to
> > driverlog, etc. What I'm uncertain of is providing much in the lines of
> >
Hey Matthew,
The OpenStackClient team will be posting patches to bump the minimum level
of python-openstacksdk to the latest release 0.9.13 (out today). We'll also
be releasing a new python-openstackclient version (3.8.0), which should
also be the minimum version.
On Tue, Jan 24, 2017 at 3:22
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]
We are going to be freezing Thursday at ~20:00 UTC.
So if you need any changes we'll be needing needing them in soon, with
reasoning. Thanks.
--
Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
On Tue, Jan 24 2017, gordon chung wrote:
> just curious, why doesn't vitrage send an event to aodh (on the error
> topic) in this case rather than get nova to do it? if you created an
> event alarm in aodh to check for vitrage error events could it solve the
> use case? i don't know if we
Excerpts from Ian Cordasco's message of 2017-01-24 14:55:31 -0500:
> -Original Message-
> From: Michał Jastrzębski
> Reply: OpenStack Development Mailing List (not for usage questions)
>
On Tue, Jan 24, 2017 at 12:03 PM, Juan Antonio Osorio
wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core
-Original Message-
From: Michał Jastrzębski
Reply: OpenStack Development Mailing List (not for usage questions)
Date: January 24, 2017 at 11:01:14
To: OpenStack Development Mailing
Hi,
The CoreOS template is not really up to date and in sync with upstream CoreOS «
Best Practice » (https://github.com/coreos/coreos-kubernetes), it is more a
port of th fedora atomic template but CoreOS has its own Kubernetes deployment
method.
I’d like to implement the changes to sync
On 24/01/17 02:05 PM, Emilien Macchi wrote:
> I'm ok if you deprecate it in Ocata, as long:
>
> 1) it's properly document how to make a transition to the new services.
> 2) We don't remove it in Pike, because work to deprecate it would have
> been done end of Ocata.
>
> Deal?
no. period.
On Tue, Jan 24, 2017 at 2:05 PM, Emilien Macchi wrote:
> On Tue, Jan 24, 2017 at 12:52 PM, gordon chung wrote:
> >
> >
> > On 24/01/17 11:53 AM, Emilien Macchi wrote:
> >> Yes, even outside TripleO, it's already hard to follow all changes
> >> made in projects,
+1
On 01/24/2017 11:03 AM, Juan Antonio Osorio wrote:
Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
on the current CI solution and in getting tripleo-quickstart jobs for
it); So I would like to propose him as part of the TripleO CI core team.
I think he'll make a great
+1
On Tue, Jan 24, 2017 at 2:10 PM, Brent Eagles wrote:
>
>
> On Tue, Jan 24, 2017 at 1:33 PM, Juan Antonio Osorio
> wrote:
>
>> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
>> on the current CI solution and in getting
On 24/01/17 03:01 AM, Afek, Ifat (Nokia - IL) wrote:
> We understood that Aodh aims to be OpenStack alarming service, which is much
> more than an ‘engine of alarm evaluation’ (as you wrote in your comment in
> gerrit). If I may describe another use case for generic alarms - of OPNFV
>
On Tue, Jan 24, 2017 at 1:33 PM, Juan Antonio Osorio
wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core
On Tue, Jan 24, 2017 at 07:03:56PM +0200, Juan Antonio Osorio wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core team.
>
> I
On Tue, Jan 24, 2017 at 12:52 PM, gordon chung wrote:
>
>
> On 24/01/17 11:53 AM, Emilien Macchi wrote:
>> Yes, even outside TripleO, it's already hard to follow all changes
>> made in projects, so please do not deprecate things at the end of a
>> cycle.
>> Let's take some time, we
Hi,
My name is Felipe Monteiro. I have decided to run for Murano PTL for the Pike
release cycle. I would like to continue to grow Murano in order to make the
project more stable, mature and performant, while exploring avenues to evolve
the project.
I've been working on the project for the past
On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote:
> I'm on board with getting visibility into the drivers with improvements to
> driverlog, etc. What I'm uncertain of is providing much in the lines of
> 'validation'. Core reviewers don't frequently have access to the
On 01/24/2017 12:03 PM, Juan Antonio Osorio wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core team.
>
> I think he'll make a
Dharini has tackled sticky bugs and complex feature work with good
judgement, patience, and agility. Her work is highly valuable to the
project and community. I'm happy to offer a vote in favor.
On Tue, Jan 24, 2017 at 5:36 AM, Brian Rosmaita
wrote:
> I'd like to
On Tue, Jan 24, 2017 at 12:03 PM, Juan Antonio Osorio
wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core
On 24/01/17 11:53 AM, Emilien Macchi wrote:
> Yes, even outside TripleO, it's already hard to follow all changes
> made in projects, so please do not deprecate things at the end of a
> cycle.
> Let's take some time, we do it in Pike, making good communication, so
> folks like TripleO etc can
On Tue, Jan 24 2017, Thomas Goirand wrote:
> Check this bug entry:
> https://bugs.debian.org/851032
>
> This may have been fixed since Newton though. The FTBFS was reported
> against packages aimed for Debian Stretch.
This is likely a race condition, it has nothing to do with webob IMHO.
We
On Mon, 23 Jan 2017, Sean Dague wrote:
We all inherited a bunch of odd and poorly defined behaviors in the
system we're using. They were made because at the time they seemed like
reasonable tradeoffs, and a couple of years later we learned more, or
needed to address a different use case that
On Mon, Jan 23, 2017 at 3:33 PM, Emilien Macchi wrote:
> Greeting folks,
>
> I would like to propose some changes in our core members:
>
> - Remove Jay Dobies who has not been active in TripleO for a while
> (thanks Jay for your hard work!).
> - Add Flavio Percoco core on
Hello everyone!
I have been involved in OpenStack since late 2013 and now it is time
to put my name forward as a candidate for keystone PTL during the Pike
development cycle. See my openstack/election change in [1].
As your PTL, I would like to see our team's focuses classified into
three
Hi all!
I am announcing my candidacy for PTL for the Ironic team for the Pike release
cycle. In case you don't know me, I'm dtantsur on IRC. I started working on
Ironic around late spring or summer 2014, and I'm probably best known as a
founder of ironic-inspector sub-project. I work for Red
Eran Rom wrote:
>> These submissions will be evaluated next week and grantees will be
>> notified by Friday, January 20th.
> Were people who were not granted also get notifications?
> I am not sure if I was not granted or if I simply did not apply as I
> thought I did.
Yes everyone gets
Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
on the current CI solution and in getting tripleo-quickstart jobs for
it); So I would like to propose him as part of the TripleO CI core team.
I think he'll make a great addition to the team and will help move CI
issues forward
Hello everyone,
We've reached our agreement!
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_28264d5a40d0088c
New deliverable process will be lightweight - just normal +2+2+PTL
vote is needed to add new deliverable. I'm going to create new
deliverables.yaml file in Kolla repository which will
On Fri, Jan 20, 2017 at 2:29 PM, Cody Herriges wrote:
> I attempted to send this out last week but think I messed it up by sending
> from my work email address which isn't the one I am signed up to the lists
> with. Seeing Alex's note in IRC this morning reminded me that I had
>
+1
On 01/23/2017 01:03 PM, Emilien Macchi wrote:
Greeting folks,
I would like to propose some changes in our core members:
- Remove Jay Dobies who has not been active in TripleO for a while
(thanks Jay for your hard work!).
- Add Flavio Percoco core on tripleo-common and
On Mon, Jan 23, 2017 at 2:00 PM, Colette Alexander
wrote:
> Hello Stackers,
>
> As we move into the last four weeks of work before the PTG in Atlanta, I
> wanted to check in to talk about what the Stewardship Working Group has
> planned and what we're looking to
On Tue, Jan 24, 2017 at 10:53 AM, Julien Danjou wrote:
> On Tue, Jan 24 2017, gordon chung wrote:
>
>> ceilometer
>> - polling definition file support [1]
>> - configurable control exchanges [2]
>> - deprecate collector [3]
>
> I've -2ed this for now because it is too late to
I attempted to send this out last week but think I messed it up by sending from
my work email address which isn't the one I am signed up to the lists with.
Seeing Alex's note in IRC this morning reminded me that I had probably screwed
it up...
I just wanted to let everyone know how much I
On 1/24/2017 9:18 AM, Matt Riedemann wrote:
First, thanks to Kevin and Alex for finding this issue and explaining it
in detail so we can understand the scope.
This is a nasty unfortunate issue which I really wish we could just fix
without a microversion bump but we have microversions for a
On 1/24/2017 2:05 AM, Alex Xu wrote:
Unfortunately the device tag support in the API was broken in the old
Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks
to Kevin Zheng to find out that.
Actually there are two bugs, just all of them are about device tag. The
first one
Hey, Flavio :) Thanks for your questions!
As you said currently only Nokia's adopting Glare for its own platform, but
if we talk about OpenStack, that I believe Mistral will start to use it
soon.
In my opinion Glare's adoption is low due to the fact that the project is
not included under Big
On 01/24/2017 04:15 PM, Julien Danjou wrote:
> On Tue, Jan 24 2017, Thomas Goirand wrote:
>
>> FYI, this was a very unfortunate upload of the latest webob version in
>> Sid, which was reverted. IMO though, OpenStack should prepare itself to
>> support the latest version to avoid failures once we
On Tue, Jan 24 2017, gordon chung wrote:
> ceilometer
> - polling definition file support [1]
> - configurable control exchanges [2]
> - deprecate collector [3]
I've -2ed this for now because it is too late to have the TripleO
changes pushed. That's a shame, but we'll do it first week in Pike.
Cool. Then i'd support a backport when the review against master
merges. Thanks Ann and Kirill.
-- Dims
On Tue, Jan 24, 2017 at 10:33 AM, Anna Taraday
wrote:
> Nope, this won't be necessary.
>
> 0.8.10 - allows us to create pk on alembic_version table automatically,
hi,
so i just wanted to create a list of items i'm tracking for ocata that
i'd like to see in:
ceilometer
- polling definition file support [1]
- configurable control exchanges [2]
- deprecate collector [3]
- equivalent publisher/dispatcher support [4]
gnocchi
- creator(user+project) unique
Nope, this won't be necessary.
0.8.10 - allows us to create pk on alembic_version table automatically, but
only for new deployments.
I propose manually add pk on this table if it is not existing.
On Tue, Jan 24, 2017 at 7:25 PM Davanum Srinivas wrote:
> Ann,
>
> Don't you
-Original Message-
From: Brian Rosmaita
Reply: OpenStack Development Mailing List (not for usage questions)
Date: January 24, 2017 at 07:37:24
To: OpenStack Development Mailing List
Gema,
Yes team meeting sounds good.
I am changing my vote from choice 2 to abstain until this is sorted out.
Regards
-steve
-Original Message-
From: Gema Gomez
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
1 - 100 of 146 matches
Mail list logo