Hi,
There's a zombie account "dell-afc-ci" which was disabled in April [1]
that has been trying to connect to gerrit every 5 seconds since
...
[2016-12-15 06:27:44,223 +] 946a4473 dell-afc-ci - AUTH FAILURE FROM
143.166.116.138 inactive-account
[2016-12-15 06:27:49,544 +] 9497a4aa del
On Thu, Dec 15, 2016 at 12:48 AM, Ian Cordasco
wrote:
> -Original Message-
> From: Joshua Hesketh
> Reply: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Date: December 14, 2016 at 06:56:22
> To: OpenStack Development Mailing List ,
Hi Sumit,
That's fine. That repo wasn't marked for removal.
Cheers,
Josh
On Thu, Dec 15, 2016 at 3:28 PM, Sumit Naiksatam
wrote:
> On Wed, Dec 14, 2016 at 4:54 AM, Joshua Hesketh
> wrote:
> > The repos listed[0] have had stable/liberty branch removed and replaced
> with
> > a liberty-eol tag.
On Wed, Dec 14, 2016 at 4:54 AM, Joshua Hesketh
wrote:
> The repos listed[0] have had stable/liberty branch removed and replaced with
> a liberty-eol tag. Any open reviews have been abandoned.
>
> Please let me know if there are any mistakes or latecomers to the list.
Hi Joshua, Apologies for chi
duonghq,
Thanks for kicking this process off, it really fits in with the point
was raising about us needing to define the user experience that we are
looking to get with Kolla Kubernetes. However, I think before we jump
straight into composing a document on gerrit it may make morse sense
to have t
Dear Kollish,
As consensus from last weekly meeting [1], we need to define use cases for
kolla-kubernetes,
so we can have more concrete ideas about what we should do next for Ocata cycle
and next cycles.
After discussed on IRC [2], I created a patchset [3] for tracking use cases
evolving. If y
On Wed, Dec 14, 2016 at 4:34 PM, Takashi Yamamoto
wrote:
> hi,
>
> which driver are you using?
>
neutron.services.vpn.device_drivers.ipsec.OpenSwanDriver
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
If we don't update the default quota configuration at the same time for Nova
services in different
physical nodes, then there is a chance for the quota control in dis-order
period: for example,
30 cores qutoa limit in one node, 20 cores quota limit in the other node.
Best Regards
Chaoyi Huang (
On Wed, Dec 14, 2016 at 7:22 PM, Wesley Hayutin wrote:
>
>
> On Fri, Dec 2, 2016 at 12:04 PM, Wesley Hayutin wrote:
>>
>> Greetings,
>>
>> I wanted to send a status update on the quickstart based containerized
>> compute ci.
>>
>> The work is here:
>> https://review.openstack.org/#/c/393348/
>>
>
On 7/18/2016 6:36 PM, Sean Dague wrote:
On 07/14/2016 08:07 AM, Kevin L. Mitchell wrote:
The original concept of quota classes was to allow the default quotas
applied to a tenant to be a function of the type of tenant. That is,
say you have a tiered setup, where you have gold-, silver-, and
bro
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, Dec 15th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_December_15th_2016_.280900_UTC.2
On 12/14/2016 8:54 AM, Sean Dague wrote:
We spent most of the Nova API meeting today to try to get to a concensus
space on https://review.openstack.org/#/c/393205/ which is about
validating the parameters passed for sorting / filtering on the servers
resource. Today, we pretty much take whatever
Hello,
As we discussed yesterday in the weekly meeting, we'd like to have one online
etherpad discussion on VxLAN L2 networking across Neutron.
The etherpad link is :
https://etherpad.openstack.org/p/TricircleVxLANL2Networking
Time: start from UTC2:00am(China 10:00am, Korea/Japan 11:00am), 1 ho
On Fri, Dec 2, 2016 at 12:04 PM, Wesley Hayutin wrote:
> Greetings,
>
> I wanted to send a status update on the quickstart based containerized
> compute ci.
>
> The work is here:
> https://review.openstack.org/#/c/393348/
>
> I had two passes on the morning of Nov 30 in a row, then later that day
Hi all,
Given the upcoming holidays, there will not be any requirements meetings for
the remainder of the year. That puts the next one at January 4, 2017.
Thanks for a great year.
Yours Tony.
signature.asc
Description: PGP signature
_
On 12/14/2016 09:56 AM, Doug Hellmann wrote:
> Excerpts from Dean Troyer's message of 2016-12-14 08:15:08 -0600:
>> On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann wrote:
>>> FWIW, some of the deployment tool communities (ansible and puppet,
>>> I think) rely on git repos without external artifacts
On Wed, Dec 14, 2016 at 08:51:29AM -0500, Ian Cordasco wrote:
> I do have one question, will creating the branch's end-of-life
> eventually work the same way? For example, Glance's projects were
> missed in the recent liberty end of life work. Could we submit a
For the record glance repos were de
On 12/13/2016 04:45 PM, Dean Troyer wrote:
> On Tue, Dec 13, 2016 at 4:26 PM, Jay Pipes wrote:
>> Not sure if it's already been brought up, but I really like govendor:
>
> Govendor and glide are the two most promising candidates at this
> point. I just read today's summary of the Package Managem
On 12/14/2016 3:53 PM, Shane Peters wrote:
Hello all,
Per https://review.openstack.org/#/c/283695/ multi-attach was disabled
for rbd volumes.
Does anyone know what features are missing or aren't compatible in rbd
for it to support multi-attach?
Thanks
Shane
__
Hello,
I used posted this on the openstack user list but it might be a better
question for this group.
Does anyone know if neutron-sfc is working in devstack?
I started to follow the instructions here:
https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining#
Single_Host_networkin
I agree that meeting notes are crucial to this type of meeting.I just say
that gerrit PoC/demo is valid form of 'notes' if meeting was about some
implementional detail, which I assume is the case for this type of meetings.
Do we agree that as hoc hangout meetings are acceptable form of cooperation
On 12/14/2016 03:21 PM, Emilien Macchi wrote:
> On Tue, Dec 13, 2016 at 5:02 PM, Emilien Macchi wrote:
> > I thought it would be useful to share our roadmap for TripleO releases.
> > As a reminder, this is the official source of trust for OpenStack
> > releases schedule:
> > https://releases.opens
On Tue, Dec 13, 2016 at 5:02 PM, Emilien Macchi wrote:
> I thought it would be useful to share our roadmap for TripleO releases.
> As a reminder, this is the official source of trust for OpenStack
> releases schedule:
> https://releases.openstack.org/ocata/schedule.html
>
> Over the last weeks, we
On Wed, Dec 14, 2016 at 5:11 PM, Jeremy Stanley wrote:
> On 2016-12-14 16:42:05 -0500 (-0500), David Moreau Simard wrote:
> [...]
>> This would lead upstream OpenStack (and downstream distros) to
>> support 3 stable releases for a good while.
> [...]
>
> We (upstream) supported stable/newton, stab
On 2016-12-14 16:42:05 -0500 (-0500), David Moreau Simard wrote:
[...]
> This would lead upstream OpenStack (and downstream distros) to
> support 3 stable releases for a good while.
[...]
We (upstream) supported stable/newton, stable/mitaka and
stable/liberty branches concurrently for a span of ro
Excerpts from Emilien Macchi's message of 2016-12-14 15:34:27 -0500:
> On Wed, Dec 14, 2016 at 8:45 AM, Doug Hellmann wrote:
> > [Sending again due to mail delivery issues.]
> >
> > The release team is pleased to announce that the branch automation
> > work is now complete, and that teams can now
Hello all,
Per https://review.openstack.org/#/c/283695/ multi-attach was disabled for
rbd volumes.
Does anyone know what features are missing or aren't compatible in rbd for
it to support multi-attach?
Thanks
Shane
__
OpenSt
Hi all,
Given the upcoming holidays, there will not be nova cells meetings for
the remainder of the year. That puts the next one at January 4, 2017.
--Dan
__
OpenStack Development Mailing List (not for usage questions)
Unsub
Hello,
Typically, OpenStack releases have EOL'd approximately one year after
being released [1].
Another way to look at it is that OpenStack has usually kept no more
than 2 stable releases going at a time, deprecating the oldest one
once the newest release was shipped.
With the Ocata short cycle
Hello Octavia folks!
I wanted to remind folks to enter their timezone information in the
etherpad to help us come up with a meeting time that works for
everyone. Please do so here:
https://etherpad.openstack.org/p/octavia-weekly-meeting-time
At the octavia IRC meeting today we agreed to take a b
I have talked with Izik on IRC and have started work to get this fixed.
I will be setting up the octavia-ci group and fixing the permissions.
Michael
On Wed, Dec 14, 2016 at 12:49 AM, Ihar Hrachyshka wrote:
> Izik Penso wrote:
>
>> Hi Neutron, Infra Cores,
>>
>> Radware CI would like to acqui
Hi all,
I wrote this email to introduce Fuxi [1], a Kuryr sub-project for providing
container persistency by leveraging existing OpenStack infrastructure (i.e.
Cinder, Manila, etc.). As a brief introduction, Fuxi is for bridging container
storage models to existing OpenStack storage abstraction
On 2016-12-14 14:37:26 -0600 (-0600), Ian Cordasco wrote:
> From: Michał Jastrzębski
[...]
> > Ian, you mentioned that gerrit as outcome of hangout violates 4
> > opens...how?
>
> The artifacts of any meeting should include meeting notes. IRC
> meetings have this autogenerated for us.
[...]
Anot
-Original Message-
From: Michał Jastrzębski
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 14, 2016 at 09:58:33
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla][tc] Video Meetings - input reque
On Wed, Dec 14, 2016 at 8:45 AM, Doug Hellmann wrote:
> [Sending again due to mail delivery issues.]
>
> The release team is pleased to announce that the branch automation
> work is now complete, and that teams can now manage feature and
> stable branch creation through the openstack/releases repo
-Original Message-
From: Brian Rosmaita
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 14, 2016 at 14:18:23
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [glance] respecting glance priorities
> Hello Glancers,
>
> I realize
+1 Steve has done a great job, nice to have him in the team.
On 14/12/16 11:05, Brian Rosmaita wrote:
> I'd like to propose Steve Lewis (stevelle on IRC) for Glance core. Take
> a look at any of his reviews, and you can see that he's thorough and
> comprehensive in his reviewing. He's knowledge
Hello Glancers,
I realize that the weekly priority mailing is a new thing for us, so
here's a quick reminder of how it works/what it's for.
Priorities are discussed and set at the weekly meeting and that gives us
all some focus for what to do in the coming week.
If you're a glance core: please a
+2 for Steve!
On Wed, Dec 14, 2016 at 3:36 AM, Ian Cordasco
wrote:
> +2 from me as well
>
> On Dec 14, 2016 3:16 AM, "Erno Kuvaja" wrote:
>
>> On Tue, Dec 13, 2016 at 10:05 PM, Brian Rosmaita
>> wrote:
>> > I'd like to propose Steve Lewis (stevelle on IRC) for Glance core. Take
>> > a look at
+1 to portdirect and srwilkers. both are doing a great job!
Thanks,
Kevin
From: Steven Dake (stdake) [std...@cisco.com]
Sent: Wednesday, December 14, 2016 10:45 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
Excerpts from Michał Jastrzębski's message of 2016-12-14 11:14:01 -0600:
> So if one of potential attendees cannot join for that reason, again I
> would consider this to be reason enough to move meeting back to irc.
> IRC is and keep being our default communication channel. Hangouts
> would only be
portdirect +1
srwilkers +1
Doing a fantastic job reviewing and writing code and participating in team
meetings/irc conversations.
Regards
-steve
-Original Message-
From: Michał Jastrzębski
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, Dece
Hi,
I also feel that quota as a service is the best approach.It is justified as
well, since we have multiple projects(Nova,Cinder,Neutron) now ,having the
concept of quotas.Keeping it under a single umbrella, paves the way for lesser
code duplication and easier feature enhancement like adopt
This is just a reminder that we'll be tagging the o-2 tag for nova
tomorrow (Thursday Dec 15th). There is generally no science to this,
it's just the HEAD of the nova master branch whenever I decide to create
the release request (probably end of day today for me).
If there are critical bugs/up
On 12/2/2016 7:52 AM, Doug Hellmann wrote:
Excerpts from Steve Martinelli's message of 2016-12-02 08:04:51 -0500:
A bit of colour should will go a long way here, black and brown would help
make it more obvious (IMO).
Yes, Heidi's email does say this is the version without color. There are
some
So if one of potential attendees cannot join for that reason, again I
would consider this to be reason enough to move meeting back to irc.
IRC is and keep being our default communication channel. Hangouts
would only be mitigation of "typing is too slow for this flame"
problem. With constant brainst
I'm happy to start nomination process for our 2 colleagues:
srwilkers and portdirect
to kolla-k8s core team!
This nomination will is open for 1 week. Kolla-k8s core team, please vote:)
Consider this email as vote +1 from me.
Regards,
Michal
__
Excerpts from Michał Jastrzębski's message of 2016-12-14 09:56:46 -0600:
> OK, I think we had some grave misunderstandings here.
>
> 1. ad-hoc meetings *are not* and *were never meant to be* replacement
> for weekly meetings. Kolla community is single community across all
> its deliverables and we
On 12/13/2016 8:43 PM, int32bit wrote:
Hi, all. As we know, the "index()" method usually return object list and
the "show()" method return an object for detail in api's controller. But
I found in our InstanceUsageAuditLogController[1], the 'index' method
return an object, I'm really not sure that
Hi Anirudh,
Yes, SFC flow_rules are not downloaded. Could you check q-agt timeout
errors? My suggestion is to recheck flow_classifer fields like protocol
ports. If possible please find me over IRC #openstack-neutron in IST.
Thanks.,
Mohankumar.N
On Wed, Dec 14, 2016 at 5:14 PM, Anirudh Gupta
Hi Conrad,
You are correct in your reading of the Neutron DNS integration
documentation. Ports 'inherit' their dns_domain from their network. I
encourage you to submit a RFE (Request for Enhacement) here:
https://bugs.launchpad.net/neutron. Once you file it, I'll track it down
and will make sure i
Excerpts from Vladyslav Drok's message of 2016-12-14 17:11:56 +0200:
> On Wed, Dec 14, 2016 at 3:48 PM, Ian Cordasco
> wrote:
>
> > -Original Message-
> > From: Joshua Hesketh
> > Reply: OpenStack Development Mailing List (not for usage questions) <
> > openstack-dev@lists.openstack.org>
On Dec 14, 2016 7:03 PM, "Steven Dake (stdake)" wrote:
Swapnil,
If you want to do that, please add it to the meeting agenda here:
https://wiki.openstack.org/wiki/Meetings/Kolla
Regards
-steve
Done
-Original Message-
From: Swapnil Kulkarni
Reply-To: "OpenStack Development Mailing L
Excerpts from Dean Troyer's message of 2016-12-14 08:15:08 -0600:
> On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann wrote:
> > FWIW, some of the deployment tool communities (ansible and puppet,
> > I think) rely on git repos without external artifacts, and we're
> > supporting them in our release t
OK, I think we had some grave misunderstandings here.
1. ad-hoc meetings *are not* and *were never meant to be* replacement
for weekly meetings. Kolla community is single community across all
its deliverables and we hold common meetings, chats and mailing list.
Also, as long as I'm PTL, I'm unwill
Excerpts from Jeremy Stanley's message of 2016-12-14 14:28:30 +:
> On 2016-12-14 08:51:29 -0500 (-0500), Ian Cordasco wrote:
> [...]
> > I do have one question, will creating the branch's end-of-life
> > eventually work the same way? For example, Glance's projects were
> > missed in the recent
1. That is correct.
2. That is not quite correct.
In static we only define the main properties of each entity, meaning type, id,
category and thus it is ok that for each main entity we will create its
neighbors and connect between them. There is no need for any distinguish due to
that.
From:
+1
From: Kevin Benton
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, December 14, 2016 at 4:56 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [neutron] Proposing Abhishek Raut as neutronclient
core
On Wed, Dec 14, 2016 at 3:48 PM, Ian Cordasco
wrote:
> -Original Message-
> From: Joshua Hesketh
> Reply: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Date: December 14, 2016 at 06:56:22
> To: OpenStack Development Mailing List ,
>
-Original Message-
From: Ed Leafe
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 14, 2016 at 08:08:33
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla][tc] Video Meetings - input requested
> On
Hi, Alexey,
Thanks for the detail example. It explains the existing mechanism of vertex
creation well.
So it looks like each resource type will have a primary datasource, e.g.
nova.host for nova.host, nova.intance for nova.instance, that holds full
details. Is that correct?
Not sure that you rem
-Original Message-
From: Jeremy Stanley
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 14, 2016 at 08:30:22
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [release][ptl][all] self-service branch mana
We spent most of the Nova API meeting today to try to get to a concensus
space on https://review.openstack.org/#/c/393205/ which is about
validating the parameters passed for sorting / filtering on the servers
resource. Today, we pretty much take whatever you throw in there and jam
it in the sql fi
On 2016-12-14 08:51:29 -0500 (-0500), Ian Cordasco wrote:
[...]
> I do have one question, will creating the branch's end-of-life
> eventually work the same way? For example, Glance's projects were
> missed in the recent liberty end of life work. Could we submit a
> review to do that work so Josh &
On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann wrote:
> FWIW, some of the deployment tool communities (ansible and puppet,
> I think) rely on git repos without external artifacts, and we're
> supporting them in our release tools today. I'm not sure how
> downstream packagers feel about the lack of
On Wed, Dec 14, 2016 at 4:25 AM, Thierry Carrez wrote:
> I don't think we need to stop producing and publishing source code
> tarballs in the Go case, just because it's not the primary way people
> consume the code. Publication of the source code is something we need to
> do as part of the open so
On Dec 14, 2016, at 7:45 AM, Ian Cordasco wrote:
>
> Taking you to the extreme of your statement, it seems there are several of
> these "ad hoc" meetings a week (by inc0's admission). The video meetings seem
> to replace the time that sub-team is missing in the weekly IRC meeting, which
> Jeff
On Dec 14, 2016, at 4:03 AM, Thierry Carrez wrote:
>
> Jeffrey took the hard step of raising
> the issue, I don't think ignoring his point and pretending Hangout
> meetings are just fine will get you anywhere.
That is why I suggested a balanced approach. If the current practice is
impacting the
Excerpts from Morales, Victor's message of 2016-12-02 19:07:25 +:
> 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, m
Excerpts from Dean Troyer's message of 2016-12-13 12:45:07 -0600:
> Release Deliverables
>
> OpenStack still officially considers the tarballs generated during the
> release rpocess to be our official deliverable. Many downstream
> consumers, however, bypass those and go directly to the tagged
>
Focus
-
Feature work and major refactoring for bug fixes should be well
under way as we reach the second milestone deadline of
Thursday 15 Dec.
Release Actions
---
Submit the tag request for the Ocata 2 milestone by 15 Dec. Several
projects missed the Ocata-1 deadline. Keep in mi
The release team is pleased to announce that the branch automation
work is now complete, and that teams can now manage feature and
stable branch creation through the openstack/releases repository.
Creating a branch is very similar to creating a release: Edit the
appropriate file in the releases re
Focus
-
We've passed the first milestone, so teams should be focused on
feature development.
The second milestone deadline is Thursday 15 Dec.
General Notes
-
All release announcements are now being sent to the new openstack-releases
mailing list instead of openstack-dev or open
Excerpts from Rob C's message of 2016-11-30 18:38:53 +:
> [Resending without the PTLs in CC because it got my mail stuck in the spam
> filters]
>
> I'm struggling to find good info on when the adjusted PTL nomination cycle
> starts.
>
> I've checked here: https://releases.openstack.org/ocata/
Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500:
> A few months ago, our community started to find and work on
> OpenStack-wide goals to "achieve visible common changes, push for
> basic levels of consistency and user experience, and efficiently
> improve certain areas where tec
Excerpts from Thierry Carrez's message of 2016-12-02 11:35:05 +0100:
> So I'm now wondering how much that artificial scarcity policy is hurting
> us more than it helps us. I'm still convinced it's very valuable to have
> a number of "meetings rooms" that you can lurk in and be available for
> ping
Excerpts from Clint Byrum's message of 2016-12-02 09:44:40 -0800:
> Excerpts from Tony Breeds's message of 2016-12-02 15:26:40 +1100:
> > On Thu, Dec 01, 2016 at 08:41:54AM -0800, Joshua Harlow wrote:
> > > Keen, Joe wrote:
> > > > I¹ll look into testing the newest version of kafka-python and see i
Excerpts from Steve Martinelli's message of 2016-12-02 08:04:51 -0500:
> A bit of colour should will go a long way here, black and brown would help
> make it more obvious (IMO).
Yes, Heidi's email does say this is the version without color. There are
some very subtle grey patches that line up with
Excerpts from Kevin Benton's message of 2016-11-30 03:23:04 -0700:
> >I'll let someone from the Neutron team fill in the details behind their
> >decision,
> because I don't want to misrepresent them.
>
> I can shed a bit of light on this since I'm a core and had been working for
> a driver vendor
-Original Message-
From: Doug Hellmann
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 14, 2016 at 07:47:58
To: openstack-dev
Subject: [openstack-dev] [release][ptl][all] self-service branch management
> [Sending again due to mail delivery issues.]
>
-Original Message-
From: Joshua Hesketh
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 14, 2016 at 06:56:22
To: OpenStack Development Mailing List ,
openstack-infra
Subject: Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging
liberty
[Sending again due to mail delivery issues.]
Excerpts from Dean Troyer's message of 2016-12-13 12:45:07 -0600:
> Release Deliverables
>
> OpenStack still officially considers the tarballs generated during the
> release rpocess to be our official deliverable. Many downstream
> consumers, however,
[Sending again due to mail delivery issues.]
Focus
-
Feature work and major refactoring for bug fixes should be well
under way as we reach the second milestone deadline of
Thursday 15 Dec.
Release Actions
---
Submit the tag request for the Ocata 2 milestone by 15 Dec. Several
pr
-Original Message-
From: Ed Leafe
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 13, 2016 at 21:45:39
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla][tc] Video Meetings - input requested
> On De
[Sending again due to mail delivery issues.]
The release team is pleased to announce that the branch automation
work is now complete, and that teams can now manage feature and
stable branch creation through the openstack/releases repository.
Creating a branch is very similar to creating a release
Swapnil,
If you want to do that, please add it to the meeting agenda here:
https://wiki.openstack.org/wiki/Meetings/Kolla
Regards
-steve
-Original Message-
From: Swapnil Kulkarni
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, December 14, 20
+1
On 12/13/16 8:22 PM, Armando M. wrote:
Hi folks,
Abhishek Raut's recent involvement in OSC and python-neutronclient has
helped moving a few efforts along in the right direction. I would like
to suggest we double down on core firepower for the neutronclient repo
alongside Akihiro [1].
This n
Part of the issue here is that the CentOS team told us yesterday they were
having technical difficulties signing and releasing the new 2.6.0 packages
to the public mirrors.
Yesterday around 6:30PM UTC they gave us an approximate ETA of 5 hours. I
see this morning that it still seems problematic an
The repos listed[0] have had stable/liberty branch removed and replaced
with a liberty-eol tag. Any open reviews have been abandoned.
Please let me know if there are any mistakes or latecomers to the list.
Cheers,
Josh
[0]
https://gist.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4
On 12/14/2016 10:17 AM, Julie Pichon wrote:
> On 14 December 2016 at 08:56, Dougal Matthews wrote:
>> On 13 December 2016 at 16:12, Emilien Macchi wrote:
>>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou
>>> wrote:
Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
>>
Doug Hellmann wrote:
> [...]
> 5. Consider driver teams to be a completely different animal, defined
>in drivers.yaml instead of projects.yaml (grey option) [6]
>
>This establishes drivers as second-order objects that are necessary
>for the success of the main projects, and for which r
+2 from me as well
On Dec 14, 2016 3:16 AM, "Erno Kuvaja" wrote:
> On Tue, Dec 13, 2016 at 10:05 PM, Brian Rosmaita
> wrote:
> > I'd like to propose Steve Lewis (stevelle on IRC) for Glance core. Take
> > a look at any of his reviews, and you can see that he's thorough and
> > comprehensive in
Hi,
I think one of the issues we're trying to solve here is duplication
reducing. Quotas in OpenStack commonly contain two parts: limits
management and limits enforcement.
If we're talking about library (delimiter) vs service (keystone or quota
service) for a duplication reducing in a limits man
On 14/12/16 11:17, Julie Pichon wrote:
> On 14 December 2016 at 08:56, Dougal Matthews wrote:
>> On 13 December 2016 at 16:12, Emilien Macchi wrote:
>>>
>>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou
>>> wrote:
Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
>>>
Monty Taylor wrote:
> On 12/13/2016 12:45 PM, Dean Troyer wrote:
>> Release Deliverables
>>
>> OpenStack still officially considers the tarballs generated during the
>> release rpocess to be our official deliverable. Many downstream
>> consumers, however, bypass those and go directly to the tagged
On Wed, Dec 14, 2016 at 3:33 PM, Thierry Carrez wrote:
> Ed Leafe wrote:
>> On Dec 12, 2016, at 10:30 PM, Steven Dake (stdake) wrote:
>>
>>> The issue raised is they violate the 4 opens.
>>
>> Not necessarily. If you have regular planning meetings and discussions in an
>> open manner as prescrib
Ed Leafe wrote:
> On Dec 12, 2016, at 10:30 PM, Steven Dake (stdake) wrote:
>
>> The issue raised is they violate the 4 opens.
>
> Not necessarily. If you have regular planning meetings and discussions in an
> open manner as prescribed, an occasional conference to discuss a particular
> matter
Hi Yujun,
This is a good question, and let me explain for you how it works.
Lets say we are supposed to get 2 entities from nova, nova.host called host1
and nova.instance called vm1 and vm1 is supposed to be connected to host1.
The nova.host driver and nova.instance driver are working simultaneou
On 14 December 2016 at 08:56, Dougal Matthews wrote:
> On 13 December 2016 at 16:12, Emilien Macchi wrote:
>>
>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou
>> wrote:
>> > Hi OOOs o/ as discussed on this week's upstream weekly irc meeting [1]
>> > lets schedule a syncup on the Ocata composa
On Tue, Dec 13, 2016 at 10:05 PM, Brian Rosmaita
wrote:
> I'd like to propose Steve Lewis (stevelle on IRC) for Glance core. Take
> a look at any of his reviews, and you can see that he's thorough and
> comprehensive in his reviewing. He's knowledgeable about Python,
> Glance, and software engin
1 - 100 of 105 matches
Mail list logo