Tom,
No flame, just observation about the reality of these changes.
I think we missed this communication on the mailing list or in the FAQs or
somewhere else. I think most engineering-focused organizations are looking at
the PTGs only and not really considering the summit for budget planning.
Thomas,
Kolla does not use systemd fies (bifrost may be different here – I am not
certain). Kolla also does not use default configuration files that are shipped
with distros. We find this model to be disruptive to reliable development. I
get distros want to ship them and that’s fine by us.
On Tue, Oct 11, 2016 at 11:32 AM, Alex Schultz wrote:
> On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold wrote:
>> Hi,
>>
>> On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote:
>>> On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold wrote:
>>> > Hi,
>>> >
>>> > in the rpm-packaging projec
Haikel,
We attempted removing EPEL from our repo lists. We got build errors on
cinder-volume. We have iscsi integration because vendors require it to work
with their third party plugins. The package iscsi-target-utils is not in the
newton repos for RDO.
The package that fails can be seen he
We are excited to announce the release of:
ironic-python-agent 1.0.5: Ironic Python Agent Ramdisk
This release is part of the liberty stable release series.
Download the package from:
https://tarballs.openstack.org/ironic-python-agent/
For more details, please see below.
Changes in ironic
Hello,
Thanks to community's support, this is the first time for Tricircle to have
room for design summit sessions.
The design summit schedule for Tricircle is prepared at [1][2].
If you have any question or suggestion, please feel free to reply in the thread.
[1]https://www.openstack.org/summ
Hello Tom,
I must say I think this is bad news - especially for projects like
Kolla - ops centric.
One of reasons we created PTG in the first place is that Summit became
big and expensive, and project developers had harder and harder time
attending it due to budget issues. PTG would offer many of
Neutrinos,
The design summit schedule for Neutron is getting live and into shape at
[1][2].
For questions/suggestions please feel free to reach out.
Cheers,
Armando
[1]
https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Neutron%3A
[2] https://wiki.openstack.org/wiki
On Mon, Oct 10, 2016 at 05:11:28PM +0200, Spyros Trigazis wrote:
> Hi heat and magnum.
>
> Apart from the scalability issues that have been observed, I'd like to
> add few more subjects to discuss during the summit.
>
> 1. One nested stack per node and linear scale of cluster creation
> time.
>
Hello all,
It's fantastic to see all of the PTG planning that has been going on in
recent threads. It's clear there's a bit of confusion too, and as
mriedem notes - us "mere mortals" are probably going to take some time
to figure it out. Nothing's final of course, and we're going to take a
wh
On 11 October 2016 at 18:20, Sean M. Collins wrote:
> Armando M. wrote:
> > At this point I feel that changing the pool range is even less justified.
> > If I had seen bug [4], I would have been against its fix, because you're
> > absolutely right as the change being not backward compatible.
>
>
Hello, Team,
Understand this period is keeping us quite busy, for the Tricircle cleaning is
in parallel with newton release period. Fortunately we have made great progress
for the Tricircle cleaning and Newton release is approaching completeness.
(https://etherpad.openstack.org/p/TricircleSplit
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, team,
Two patches for the stable/newton branch of Tricircle were prepared.
Update the dependency: https://review.openstack.org/#/c/379966/
Release notes: https://review.openstack.org/#/c/384055/
Let's review and get these two patches merged before Oct.15, so that we can
have Newton rele
Armando M. wrote:
> At this point I feel that changing the pool range is even less justified.
> If I had seen bug [4], I would have been against its fix, because you're
> absolutely right as the change being not backward compatible.
https://review.openstack.org/#/c/356026 was written by someone on
On Tue, Oct 11, 2016, at 05:58 PM, Carl Baldwin wrote:
> On Tue, Oct 11, 2016 at 6:26 PM, Clark Boylan
> wrote:
>
> > On Tue, Oct 11, 2016, at 05:14 PM, Carl Baldwin wrote:
> > > I found this [1] added here [2]. Since the provider is using 10.0.0.0/8
> > > on
> > > the public interface, and the s
While reviewing specs I've come across several related to adding more or
exposing existing metrics monitors from nova-compute. At the Newton
midcycle we discussed how we were going to freeze feature requests like
this and start deprecating this capability, at least open-ended until
there is a c
On Tue, Oct 11, 2016 at 6:26 PM, Clark Boylan wrote:
> On Tue, Oct 11, 2016, at 05:14 PM, Carl Baldwin wrote:
> > I found this [1] added here [2]. Since the provider is using 10.0.0.0/8
> > on
> > the public interface, and the subnet pool is also 10.0.0.0/8 the call to
> > ip
> > route replace el
Thanks Cathy, My typo, not sfc. The question was for networking-ovn without
port-security. Anyways, I sent another query with proper title and content,
please ignore this email.
On Tue, Oct 11, 2016 at 12:07 PM, Cathy Zhang
wrote:
> The guide is the networking-ovn guide. Not sure what is meant b
On 11 October 2016 at 17:05, Clark Boylan wrote:
> On Tue, Oct 11, 2016, at 05:01 PM, Armando M. wrote:
> > On 11 October 2016 at 16:54, Clark Boylan wrote:
> >
> > > On Tue, Oct 11, 2016, at 04:51 PM, Armando M. wrote:
> > > > On 11 October 2016 at 16:43, Clark Boylan
> wrote:
> > > >
> > > >
On Tue, Oct 11, 2016, at 05:14 PM, Carl Baldwin wrote:
> I found this [1] added here [2]. Since the provider is using 10.0.0.0/8
> on
> the public interface, and the subnet pool is also 10.0.0.0/8 the call to
> ip
> route replace eliminates the route through the public interface.
It is also an iss
I found this [1] added here [2]. Since the provider is using 10.0.0.0/8 on
the public interface, and the subnet pool is also 10.0.0.0/8 the call to ip
route replace eliminates the route through the public interface.
Carl
[1] https://github.com/openstack-dev/devstack/blob/
6c55227595228bc37b91a1db
On Tue, Oct 11, 2016, at 05:01 PM, Armando M. wrote:
> On 11 October 2016 at 16:54, Clark Boylan wrote:
>
> > On Tue, Oct 11, 2016, at 04:51 PM, Armando M. wrote:
> > > On 11 October 2016 at 16:43, Clark Boylan wrote:
> > >
> > > > On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote:
> > > > > O
On 10/11/2016 9:05 AM, Clint Byrum wrote:
Since there seems to be broad based resistance to time boxing anything
project specific, I'd like to propose a compromise: I'd like to ask that
teams allow people to add their IRC nick to the agenda items they'd like
to be included in, and at the beginni
On 11 October 2016 at 16:54, Clark Boylan wrote:
> On Tue, Oct 11, 2016, at 04:51 PM, Armando M. wrote:
> > On 11 October 2016 at 16:43, Clark Boylan wrote:
> >
> > > On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote:
> > > > On 11 October 2016 at 14:09, Clark Boylan
> wrote:
> > > >
> > > >
On Tue, 2016-10-11 at 18:08 -0500, Ben Nemec wrote:
>
> On 10/11/2016 02:42 PM, Dan Prince wrote:
> >
> > A quick update on the tripleo.org website outage today. We are in
> > the
> > process of moving the server to a new host location. Until DNS
> > updates
> > please use the following URL if yo
gordon chung wrote:
On 11/10/16 05:38 PM, Joshua Harlow wrote:
Yes yes, normalization would be nice to, though a little beyond what I
am (or was) thinking of currently. Going back to how
event_definitions.yaml is the best 'source' we have currently, is it
possible to rip out (for now) event_def
On Tue, Oct 11, 2016, at 04:51 PM, Armando M. wrote:
> On 11 October 2016 at 16:43, Clark Boylan wrote:
>
> > On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote:
> > > On 11 October 2016 at 14:09, Clark Boylan wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > Currently multinode testing + ne
On 11 October 2016 at 16:43, Clark Boylan wrote:
> On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote:
> > On 11 October 2016 at 14:09, Clark Boylan wrote:
> >
> > > Hello everyone,
> > >
> > > Currently multinode testing + neutron is broken in clouds that use
> > > portions of 10.0.0.0/8 for t
I've dropped the vmware CI from the nova-ci group in Gerrit. The CI is
failing all over everything today and -1ing changes, e.g.:
http://208.91.1.172/logs/ext-nova-dsvm/385202/1/439/
So until it's fixed it's now non-voting.
--
Thanks,
Matt Riedemann
It has been some weeks I have been thinking how TripleO project could
scale-up the way we work together.
Over the cycles, we have more contributors, more projects, I think
it's time to revisit our organization.
Here's the proposal: https://review.openstack.org/385201
Feel free to review it prior
On Tue, Oct 11, 2016 at 4:24 PM, Jamie Lennox wrote:
>
> So I'm not going to comment too much on the quality of the library as i
> obviously think it's good
>
acahcpahch, no worries.
Your insights are invaluable - thanks for taking the time to connect some
dots for me - i'm starting to get up t
On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote:
> On 11 October 2016 at 14:09, Clark Boylan wrote:
>
> > Hello everyone,
> >
> > Currently multinode testing + neutron is broken in clouds that use
> > portions of 10.0.0.0/8 for their networking due to route conflicts with
> > devstack + neutr
On 11 October 2016 at 14:09, Clark Boylan wrote:
> Hello everyone,
>
> Currently multinode testing + neutron is broken in clouds that use
> portions of 10.0.0.0/8 for their networking due to route conflicts with
> devstack + neutron deployments. https://bugs.launchpad.net/bugs/1629133
> is tracki
On 11 October 2016 at 23:40, Ian Cordasco wrote:
> -Original Message-
> From: Clay Gerrard
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: October 11, 2016 at 00:25:10
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] requests-mock
>
>
On 11 October 2016 at 16:23, Clay Gerrard wrote:
> Greetings!
>
> Anyone have any experience to share positive or negative using
> requests-mock? I see it's been used to replace another dependency that had
> some problems in many of the OpenStack python client libraries:
>
> Added to global requ
Hello Everyone!
We have a few slots still available on Monday's Command Presence workshop and
are opening out to a broader audience. Please register if interested. Past
attendees, despite their many skills and experience, vouched that they had
learned a trick or two.
https://www.openstack.org/
On 10/11/2016 02:42 PM, Dan Prince wrote:
A quick update on the tripleo.org website outage today. We are in the
process of moving the server to a new host location. Until DNS updates
please use the following URL if you want to access the CI status
report:
http://66.187.229.219/cistatus.html
Hi Jay,
I think that's a perfectly reasonable solution for the moment, and hopefully
we'll have the new solution up and running as soon as possible.
Please let us know if there's anything you could use a hand with.
Lana
On 12/10/16 09:00, Jay Faulkner wrote:
> We are eager to improve our docum
We are eager to improve our documentation, but I think quite a few of us who
work on Ironic documentation have a strong preference to keeping those
documents in-tree. This allows us to enforce contributors having documentation
changes or additions merge at the same time or in close proximity to
On 11/10/16 05:38 PM, Joshua Harlow wrote:
> Yes yes, normalization would be nice to, though a little beyond what I
> am (or was) thinking of currently. Going back to how
> event_definitions.yaml is the best 'source' we have currently, is it
> possible to rip out (for now) event_definitions.yaml
On Tue, Oct 11, 2016 at 10:44 AM, Clay Gerrard
wrote:
> I'm not really sure what a fixture is this context?
>
Answered my own question in this case!
http://requests-mock.readthedocs.io/en/latest/fixture.html
It's one of *these* of course:
https://pypi.python.org/pypi/fixtures
___
gordon chung wrote:
On 11/10/16 04:18 PM, Joshua Harlow wrote:
To be productive here, would there be any problem if I (or someone I
know) just split that yaml off into a new git repository, and started
iterating on figuring out how to turn the yaml into something that can
generate code for [pyt
Thanks, Steve, this will be a valuable session!
On 12 October 2016 at 08:14, Steve Martinelli
wrote:
> The keystone team had a spare fishbowl session, and we decided to use it
> to collaborate with the horizon team on a few long standing issues we've
> had between the two projects.
>
> You can v
The keystone team had a spare fishbowl session, and we decided to use it to
collaborate with the horizon team on a few long standing issues we've had
between the two projects.
You can view the session online:
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16907
Details her
On 11/10/16 04:18 PM, Joshua Harlow wrote:
>
> To be productive here, would there be any problem if I (or someone I
> know) just split that yaml off into a new git repository, and started
> iterating on figuring out how to turn the yaml into something that can
> generate code for [python, java, g
Hello everyone,
Currently multinode testing + neutron is broken in clouds that use
portions of 10.0.0.0/8 for their networking due to route conflicts with
devstack + neutron deployments. https://bugs.launchpad.net/bugs/1629133
is tracking the issue for us. I would like to see this get resolved
pro
Chris Dent wrote:
On Tue, 11 Oct 2016, Joshua Harlow wrote:
Damn, that's crazy that the projects emitting events don't want to own
the formats and versions (and schemas) that they emit. That is ummm,
like ummm, what the, ha, words can't describe... And the fact that
nothing much has changed s
On Tue, 11 Oct 2016, Joshua Harlow wrote:
Damn, that's crazy that the projects emitting events don't want to own the
formats and versions (and schemas) that they emit. That is ummm, like ummm,
what the, ha, words can't describe... And the fact that nothing much has
changed since kilo, ya, also
gordon chung wrote:
On 11/10/16 01:14 PM, Joshua Harlow wrote:
Ah, right, nearly forgot about that yaml. Thanks gordon!
Has there been any ideas from folks to split those
'event_definitions.yaml' into something else (a notifications schema
repo?)? I'd be up for helping do that (nice to have wo
Hi,
Based on team’s decision in tacker weekly meeting [1], Tacker team has decided
to have a virtual developer meetup and not have PTG presence in Atlanta. Given,
most of our contributors are geographically spread out, it was decided that the
virtual midcycle format would be more appropriate in
A quick update on the tripleo.org website outage today. We are in the
process of moving the server to a new host location. Until DNS updates
please use the following URL if you want to access the CI status
report:
http://66.187.229.219/cistatus.html
Dan
__
On 11/10/16 01:14 PM, Joshua Harlow wrote:
>
> Ah, right, nearly forgot about that yaml. Thanks gordon!
>
> Has there been any ideas from folks to split those
> 'event_definitions.yaml' into something else (a notifications schema
> repo?)? I'd be up for helping do that (nice to have would be an i
On Tue, Oct 11, 2016 at 08:34:12AM +1100, Tony Breeds wrote:
> On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote:
>
> > I think it would also make sense to *release* on the boundary of the switch;
> > so that it’s clear which phase a release followed.
>
> I agree, I don't really hav
My personal opinion, speaking as a non-candidate, is that it's very likely
true name recognition plays a role. In fact if I was to vote I would do so
and probably vote for Monty or Doug cause I like how they operate and I'm
familiar with them. And if I don't like someone, I won't vote for them.
Sel
Thank you Craig for your leadership and hard work in helping shape and
guide the Trove community. Wish you good luck and success in everything you
do.
Regards,
Mariam.
From: Craig Vyvial
To: OpenStack Development Mailing List
Date: 10/07/2016 10:25 PM
Subject:[op
The guide is the networking-ovn guide. Not sure what is meant by
“port-security”. From networking-sfc point of view, security group is not
needed.
Thanks,
Cathy
From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of Murali R
Sent: Monday, October 10, 2016 2:47 PM
To: discuss; OpenS
Greetings,
I would like to request for some space dedicated to TripleO project
for the first OpenStack PTG.
https://www.openstack.org/ptg/
The event will happen in February 2017 during the next PTG in Atlanta.
Any feedback is welcome,
--
Emilien Macchi
On 2016-10-11 02:07 PM, Clay Gerrard wrote:
On Tue, Oct 11, 2016 at 10:52 AM, Anita Kuno wrote:
On 2016-10-11 01:40 PM, Ed Leafe wrote:
On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote:
There really needs to be a period when a) we know who all the candidates
are, and b) voting has not yet b
Hi,
Please clarify if port security is required to be enabled with newton
release when installing OVN. The install.rst says it must be. In many of my
use cases I want to disable port security which is how I do currently with
devstack. I would like to know if either ovn or neutron will have
content
On 2016-10-11 02:35 PM, Thiago da Silva wrote:
On 10/11/2016 01:21 PM, Anita Kuno wrote:
On 2016-10-11 12:57 PM, Thiago da Silva wrote:
On 10/11/2016 12:00 PM, Ed Leafe wrote:
On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote:
Just in case folks care, now is the best time to discuss our
el
On 10/11/2016 01:21 PM, Anita Kuno wrote:
On 2016-10-11 12:57 PM, Thiago da Silva wrote:
On 10/11/2016 12:00 PM, Ed Leafe wrote:
On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote:
Just in case folks care, now is the best time to discuss our
election process and suggest options or changes fo
On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold wrote:
> Hi,
>
> On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote:
>> On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold wrote:
>> > Hi,
>> >
>> > in the rpm-packaging project we started to package the services and are
>> > currently disc
Hi,
Approach I am following is not cleaning blindly, there is utility in cleanup
which I’ll use
To get eligible namespace candidates for cleanup (need to deep dive this logic
how effective is that)
Then will extract id from namespace either using namespace manager or l3 agent
code,
And call on
On Tue, Oct 11, 2016 at 12:40 AM Thomas Bechtold wrote:
> Hi,
>
>
>
> On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote:
>
> > On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold
> wrote:
>
> > > Hi,
>
> > >
>
> > > in the rpm-packaging project we started to package the services and are
On Tue, Oct 11, 2016 at 10:52 AM, Anita Kuno wrote:
> On 2016-10-11 01:40 PM, Ed Leafe wrote:
>
>> On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote:
>>
>> There really needs to be a period when a) we know who all the candidates
are, and b) voting has not yet begun.
>>> Why?
>>>
>>> The v
On 2016-10-11 01:43 PM, Ed Leafe wrote:
On Oct 11, 2016, at 12:26 PM, Anita Kuno wrote:
Instead of two week process, make it three:
Again as I replied to Ed's post, I think we can find options that fit in the
current timeframe.
Why do we need a week to nominate? Open it up a month before the
On Tue, Oct 11, 2016 at 9:57 AM, Thiago da Silva wrote:
>
> it would also be nice to have a better place for the questions/answers to
> be stored. During last week there was a ton of great discussion, but when
> it came to voting time (towards end of the week) it was difficult/time
> consuming to
On 2016-10-11 01:42 PM, Chris Dent wrote:
On Tue, 11 Oct 2016, Anita Kuno wrote:
* Getting rid of self nomination. Nominations come from the
electorate at large. They can be refused of course.
What is the current problem with self nomination?
(I almost missed this since it was after your
On 2016-10-11 01:40 PM, Ed Leafe wrote:
On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote:
There really needs to be a period when a) we know who all the candidates are,
and b) voting has not yet begun.
Why?
The voting period is open for a period of several days, voters have the ability
to vot
Hi Navdeep,
Please see inline.
Cathy
From: Navdeep Uniyal [mailto:navdeep.uni...@neclab.eu]
Sent: Tuesday, October 11, 2016 5:42 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [networking-sfc][devstack][mitaka]
Hi all,
I have been trying out networking-sfc to create service
On Oct 11, 2016, at 12:31 PM, Anita Kuno wrote:
> I think one would get a much better sense asking people if they voted when
> they see them at summit or other live events and ask them why not if they say
> no.
As I said in an earlier email, I have done such unscientific polling at recent
sum
On Tue, Oct 11, 2016 at 5:40 AM, Ian Cordasco
wrote:
> So, as a core developer
> of Requests, I would endorse requests-mock for this category of
> dependency.
>
Excellent; exactly the kind of feedback I was hoping to solicit. If you're
looking to add this catagory of dependency - requests-mock
On Oct 11, 2016, at 12:26 PM, Anita Kuno wrote:
>
>> Instead of two week process, make it three:
>
> Again as I replied to Ed's post, I think we can find options that fit in the
> current timeframe.
Why do we need a week to nominate? Open it up a month before the election, and
close it a week
On Tue, 11 Oct 2016, Anita Kuno wrote:
* Getting rid of self nomination. Nominations come from the
electorate at large. They can be refused of course.
What is the current problem with self nomination?
(I almost missed this since it was after your valediction)
I guess the least roundabout
On Oct 11, 2016, at 12:17 PM, Anita Kuno wrote:
>> There really needs to be a period when a) we know who all the candidates
>> are, and b) voting has not yet begun.
>
> Why?
>
> The voting period is open for a period of several days, voters have the
> ability to vote at any time during that v
We are glowing to announce the release of:
oslo.policy 1.15.0: Oslo Policy library
This release is part of the ocata release series.
The source is available from:
http://git.openstack.org/cgit/openstack/oslo.policy
Download the package from:
https://pypi.python.org/pypi/oslo.policy
P
On 2016-10-11 12:55 PM, Ruby Loo wrote:
On Tue, Oct 11, 2016 at 12:08 PM, Chris Dent wrote:
Based on the turnout numbers and a bit of unscientific number
crunching on the voting results it seems that the electorate was
rather more engaged this time around. That's _great_.
As others have said
Hi everyone,
We are interested in improving user trust in the cloud and are
currently working on certificate validation for image signatures in
Nova. Users can upload signed images to Glance and then boot them via
Nova, with Nova validating the image signature when it downloads the
image. Adding c
On 2016-10-11 12:08 PM, Chris Dent wrote:
Based on the turnout numbers and a bit of unscientific number
crunching on the voting results it seems that the electorate was
rather more engaged this time around. That's _great_.
As others have said I imagine some significant part of that was
because
Hi,
Here is this week's subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff between 03 Oct 2016 and 10 Oct 2016)
- Ironic: 216 bugs (+11) + 212 wishlist items. 15 new (+9), 173 in progress
(+4),
On 2016-10-11 12:57 PM, Thiago da Silva wrote:
On 10/11/2016 12:00 PM, Ed Leafe wrote:
On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote:
Just in case folks care, now is the best time to discuss our
election process and suggest options or changes for the next round
of elections. I'm not adver
We are delighted to announce the release of:
osc-lib 1.2.0: OpenStackClient Library
This release is part of the ocata release series.
The source is available from:
https://git.openstack.org/cgit/openstack/osc-lib
Download the package from:
https://pypi.python.org/pypi/osc-lib
Please
We are amped to announce the release of:
senlin-dashboard 0.5.0: Senlin Dashboard
This release is part of the newton release series.
Download the package from:
https://tarballs.openstack.org/senlin-dashboard/
Please report issues through launchpad:
https://bugs.launchpad.net/senlin-da
On 2016-10-11 12:00 PM, Ed Leafe wrote:
On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote:
Just in case folks care, now is the best time to discuss our election process
and suggest options or changes for the next round of elections. I'm not adverse
to discussing it I just think the best time fo
On Tue, Oct 11, 2016 at 4:02 AM, Davanum Srinivas wrote:
> Clay,
>
> Apologies for the top post.
Oh goodness, none needed my friend!
> https://github.com/openstack/requirements#global-
> requirements-for-openstack-projects
>
>
Eternal wells of gratitude for that read! There was so many good
gordon chung wrote:
On 10/10/16 04:48 PM, Joshua Harlow wrote:
So the question started to be raised of is there a documented
format/schema for the events that are being emitted from (there seems to be some at
http://docs.openstack.org/developer/nova/notifications.html)?
we have something to
On 10/11/2016 12:00 PM, Ed Leafe wrote:
On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote:
Just in case folks care, now is the best time to discuss our election process
and suggest options or changes for the next round of elections. I'm not adverse
to discussing it I just think the best time
On Tue, Oct 11, 2016 at 12:08 PM, Chris Dent wrote:
>
> Based on the turnout numbers and a bit of unscientific number
> crunching on the voting results it seems that the electorate was
> rather more engaged this time around. That's _great_.
>
> As others have said I imagine some significant part
Hi team,
I'd like to share a link [1] to Nova Bug Triage wiki page. This page
contains a tag owner list and instructions that allow subscribing not for
all nova bugs, but for a certain tag. It would be great if all tags in a
table have an owner, so if you are interested in some of them, and could
>From my point of view, the rush is so that we can be more efficient with
all of our time/efforts. In ironic, we have a bit of a mess. We now have
duplicated (and perhaps out-of-sync) admin-related information in our
developer docs [1] as well as in the official admin guide [2] -- the latter
conten
On 7 October 2016 at 14:03, Paul Belanger wrote:
> Greetings,
>
> I wanted to propose a work item, that I am happy to spearhead, about setting
> up
> a 3rd party CI system for tripleo project. The work I am proposing, wouldn't
> actually affect anything today about tripleo-ci but provider a worki
On 10/10/16 04:48 PM, Joshua Harlow wrote:
>
> So the question started to be raised of is there a documented
> format/schema for the events that are being emitted from various services> (there seems to be some at
> http://docs.openstack.org/developer/nova/notifications.html)?
we have something
Based on the turnout numbers and a bit of unscientific number
crunching on the voting results it seems that the electorate was
rather more engaged this time around. That's _great_.
As others have said I imagine some significant part of that was
because of more than one mailing of the ballots to
We will pick back up on 11/1.
Doug__
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/
Reminder that the meeting is in 1 hour,
Best regards,
Igor.
From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com]
Sent: Monday, October 10, 2016 5:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron] [classifier] Common Classifier
On Oct 11, 2016, at 10:37 AM, Anita Kuno wrote:
> Just in case folks care, now is the best time to discuss our election process
> and suggest options or changes for the next round of elections. I'm not
> adverse to discussing it I just think the best time for doing so is from the
> time the la
On 10/11/2016 02:09 PM, Markus Zoeller wrote:
> * How to create a "*.deb" package out of the source code of
> libvirt/qemu? (surprisingly enough, I'm still struggling with this)
What version of libvirt / qemu are you trying to build? libvirt 2.3.0
was released 6 days ago, and uploaded to Debian un
Just a quick reminder that the first networking-cisco IRC meeting will be
happening on #openstack-meeting-3 at 16:00 UTC.
See you there,
Sam
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opens
On 2016-10-04 04:53 PM, Anita Kuno wrote:
On 16-10-04 12:54 PM, Thierry Carrez wrote:
Doug Hellmann wrote:
John Davidge wrote:
Thierry, I'm surprised by your open hostility towards candidates.
Accusing
people of 'pretending' to care about things that they've taken the
time to
This is an excel
1 - 100 of 130 matches
Mail list logo
