- Original Message -
> Hi,
>
> Today Puppet OpenStack CI is running unit and functional test jobs
> against puppet 3 and puppet 4.
> Unit jobs for puppet 4 are currently voting and pretty stable.
> Functional jobs for puppet 4 are not voting but also stable.
>
> Even if Puppet4 has not
+1
On Thu, Aug 4, 2016 at 9:29 AM, Vincent FRANÇOISE
wrote:
> Alexander Chadin did prove he knew the various moving parts of Watcher
> by participating the numerous design discussions and blueprints during
> the last months which makes him a precious asset for our team.
>
> So that's a definite +
On 08/09/2016 08:25 PM, Julien Danjou wrote:
> On Tue, Aug 09 2016, John Dickinson wrote:
>
>> I'd like to advocate for *not* raising minimum versions very often. Every
>> time
>> some OpenStack project raises minimum versions, this change is propagated to
>> all projects, and that puts extra bur
On 08/09/2016 08:33 PM, Ian Cordasco wrote:
>
>
> -Original Message-
> From: John Dickinson
> Reply: OpenStack Development Mailing List (not for usage questions)
>
> Date: August 9, 2016 at 13:17:08
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [requirement
On 08/09/2016 08:54 PM, Hayes, Graham wrote:
> But then packagers are going to have to do the work anyway, as it will
> have in effect raised the minimum version of routes for Glance, and thus
> need a new package.
Which isn't a problem. It's perfectly ok to upload a new upstream
release of a pack
On 08/09/2016 09:09 PM, Doug Hellmann wrote:
> We've tried to be consistent in telling packagers to use the
> versions listed in upper-constraints.txt unless there is an absolute
> need to use something else. Those are the versions we test, and
> therefore the versions we claim to support right now
So I tried to get into helping with the cinder stable tree for a while, and
while I wasn't very successful (lack of time and an inability to convince
my employer it should be a priority), one thing I did notice it that much
of the breakage seemed to come from outside cinder - many of the libraries
Jeremy Stanley wrote:
On 2016-08-09 15:56:57 -0700 (-0700), Mike Perez wrote:
As others have said and as being a Cinder stable core myself, the
status-quo
and this proposal itself are terrible practices because there is no
testing
behind it, thereby it not being up to the community QA stan
@moshe, any insight on this?
I guess that'd depend on the nic internal switch implementation and
how the switch ARP tables are handled there (per network, or global
per switch).
If that's the case for some sr-iov vendors (or all), would it make
sense to have a global switch to create globally uni
Duncan Thomas wrote:
So I tried to get into helping with the cinder stable tree for a while,
and while I wasn't very successful (lack of time and an inability to
convince my employer it should be a priority), one thing I did notice it
that much of the breakage seemed to come from outside c
Hello, team,
Cross pod L2 networking(shared VLAN) has made good progress, let's continue the
discussion:
IRC meeting: https://webchat.freenode.net/?channels=openstack-meetingon every
Wednesday starting from UTC 13:00.
The agenda of this weekly meeting is:
# progress review in feature
On Wed, Aug 10, 2016 at 11:33:52AM +0300, Duncan Thomas wrote:
> So I tried to get into helping with the cinder stable tree for a while, and
> while I wasn't very successful (lack of time and an inability to convince
> my employer it should be a priority), one thing I did notice it that much
> of t
On Wed, 3 Aug 2016, Jay Pipes wrote:
Let me know what you think about the structure of the library and whether you
would be interested in owning additions to the library of constants in your
area of expertise.
Seems mostly sane to me. I don't really care for the inspection of
sys.modules (or
On Wed, Aug 10, 2016 at 9:27 AM, Thomas Goirand wrote:
> On 08/09/2016 08:33 PM, Ian Cordasco wrote:
>>
>>
>> -Original Message-
>> From: John Dickinson
>> Reply: OpenStack Development Mailing List (not for usage questions)
>>
>> Date: August 9, 2016 at 13:17:08
>> To: OpenStack Develop
Hello,
I wanted to uset he zmq as message Q for all Openstack components
like, Nova, glance, cinder, Ceilmeter,etc (just replace the default
rabbitmq with zmq).
Is it possible to do this?
Please advise.
Thanks
Swami
__
Open
Hi,
The general answer is: yes! it is possible for all services except Ceilometer
yet.
RPC use case is 100% covered, but Ceilometer uses Notifications which are
partly supported
in zmq backend because they need some persistence when consumer is not present
etc.
For all the other services (Nov
We are overjoyed to announce the release of:
debtcollector 1.8.0: A collection of Python deprecation patterns and
strategies that help you collect your technical debt in a non-
destructive manner.
This release is part of the newton release series.
With source available at:
http://git.openst
We are gleeful to announce the release of:
oslo.context 2.8.0: Oslo Context library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.context
With package available at:
https://pypi.python.org/pypi/oslo.context
P
We are frolicsome to announce the release of:
oslo.db 4.11.0: Oslo Database library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.db
With package available at:
https://pypi.python.org/pypi/oslo.db
Please repo
We are frolicsome to announce the release of:
oslo.config 3.15.0: Oslo Configuration API
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.config
With package available at:
https://pypi.python.org/pypi/oslo.config
We are glowing to announce the release of:
oslo.middleware 3.17.0: Oslo Middleware library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.middleware
With package available at:
https://pypi.python.org/pypi/oslo.
We are gleeful to announce the release of:
oslo.log 3.14.0: oslo.log library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.log
With package available at:
https://pypi.python.org/pypi/oslo.log
Please report is
We are joyful to announce the release of:
oslo.policy 1.14.0: Oslo Policy library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.policy
With package available at:
https://pypi.python.org/pypi/oslo.policy
Pleas
We are tickled pink to announce the release of:
oslo.reports 1.14.0: oslo.reports library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.reports
With package available at:
https://pypi.python.org/pypi/oslo.repo
We are thrilled to announce the release of:
oslo.messaging 5.7.0: Oslo Messaging API
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.messaging
With package available at:
https://pypi.python.org/pypi/oslo.messagi
We are mirthful to announce the release of:
oslo.rootwrap 5.1.0: Oslo Rootwrap
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.rootwrap
With package available at:
https://pypi.python.org/pypi/oslo.rootwrap
Plea
We are pleased to announce the release of:
oslo.vmware 2.13.0: Oslo VMware library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.vmware
With package available at:
https://pypi.python.org/pypi/oslo.vmware
Plea
We are exuberant to announce the release of:
oslo.serialization 2.13.0: Oslo Serialization library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.serialization
With package available at:
https://pypi.python.org
We are delighted to announce the release of:
oslo.service 1.15.0: oslo.service library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.service
With package available at:
https://pypi.python.org/pypi/oslo.service
We are glowing to announce the release of:
oslo.versionedobjects 1.15.0: Oslo Versioned Objects library
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.versionedobjects
With package available at:
https://pypi.py
We are exuberant to announce the release of:
taskflow 2.5.0: Taskflow structured state management library.
This release is part of the newton release series.
With source available at:
http://git.openstack.org/cgit/openstack/taskflow
With package available at:
https://pypi.python.org/p
-Original Message-
From: Erno Kuvaja
Reply: OpenStack Development Mailing List (not for usage questions)
Date: August 10, 2016 at 05:53:14
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [requirements] History lesson please
> On Wed, A
> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll be
> missed. :-)
It also seems from http://www.openstack.org/project-mascots that the majority
of OpenStack projects have selected a mascot. I think it would be a great
shame if the Nova project didn’t have an easily reco
On 08/10/2016 07:30 AM, Ian Cordasco wrote:
> To be clear, I think the requirements work Tony is doing has the potential to
> make things worse for some subset of deployers/operators.
>
> --
> Ian Cordasco
Any change we make has the potential to make things worse for some subset :P
--
-- Mat
We are chuffed to announce the release of:
python-neutronclient 5.1.0: CLI and Client Library for OpenStack
Networking
This release is part of the newton release series.
With source available at:
https://git.openstack.org/cgit/openstack/python-neutronclient
With package available at:
Hi Ironicers,
This email serves as a reminder (and a bit of a call to action) about our
third party CI policy:
http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/third-party-ci.html
1) When I went to find a link to the policy, I realized that it isn't in our
developer docs
Hi,
Does anyone know if the Neutron Juno release logging conf allows options
such as: logging_exception_prefix, logging_debug_format_suffix,
logging_default_format_string, logging_context_format_string like the other
general OS services?
>From the Juno doc (
http://docs.openstack.org/juno/config-
Hi,
> [Mooney, Sean K]
> In ovs 2.5 only linux kernel conntrack was supported assuming you had a 4.x
> kernel that supported it. that means that the feature was not available on
> bsd,windows or with dpdk.
Yup, I also thought about something like that.
I think I was at-least-slightly misguided by
Please join the meeting for Incubation and ptaches decision
Meeting Wednesday 10th (14 Hr-15 Hr UTC ) [7AM-8AM PDT]
irc #openstck-megdwar
Follow up1 The last week agenda and actions taken or pending 2 Meghdwar Gateway
API discussions https://review.openstack.org/#/c/319466/
https://rev
+1 from me also. This will help everyone who is trying to transition to it.
On Wed, Aug 10, 2016 at 1:46 AM, Javier Pena wrote:
>
>
> - Original Message -
> > Hi,
> >
> > Today Puppet OpenStack CI is running unit and functional test jobs
> > against puppet 3 and puppet 4.
> > Unit jobs f
On 08/09/2016 09:21 PM, Adam Young wrote:
On 08/09/2016 06:00 PM, Zane Bitter wrote:
In either case a good mechanism might be to use a Heat Software
Deployment via the Heat API directly (i.e. not as part of a stack) to
push changes to the servers. (I say 'push' but it's more a case of
making
On 08/09/2016 05:11 PM, Adam Young wrote:
The Fernet token format uses a symmetric key to sign tokens. In order
to check the signature, these keys need to be synchronized across all
of the Keystone servers.
I don't want to pass around nake symmetric keys. The right way to do
this is to put
From: Yujun Zhang
Date: Tuesday, 9 August 2016 at 14:48
1. How do I register a new datasource in an existing system?
[yujunz] It seems to be in
https://github.com/openstack/vitrage/blob/master/vitrage/datasources/__init__.py
Not exactly. This file defines the default datasources to be used. You
On 08/10/2016 04:33 AM, Duncan Thomas wrote:
So I tried to get into helping with the cinder stable tree for a while,
and while I wasn't very successful (lack of time and an inability to
convince my employer it should be a priority), one thing I did notice it
that much of the breakage seemed to co
On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote:
> On 08/10/2016 04:33 AM, Duncan Thomas wrote:
> > So I tried to get into helping with the cinder stable tree for a while,
> > and while I wasn't very successful (lack of time and an inability to
> > convince my employer it should b
Miguel,
I talked to our driver architect and according to him this is vendor
implementation (according to him this should work with Mellanox NIC)
I need to verify that this indeed working.
I will update after I will prepare SR-IOV setup and try it myself.
-Original Message-
From: Mi
Luigi Toscano wrote:
On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote:
On 08/10/2016 04:33 AM, Duncan Thomas wrote:
So I tried to get into helping with the cinder stable tree for a while,
and while I wasn't very successful (lack of time and an inability to
convince my employe
On 2016-08-10 10:46:23 +0800 (+0800), 吕冬兵 wrote:
> The issue still exists after the
> https://review.openstack.org/352490 merged, what else should I do?
> http://logs.openstack.org/58/351458/8/check/gate-python-bileanclient-requirements/fa1119c/console.html
That change was for a script which gets
On 10/08/2016 16:04, Ihar Hrachyshka wrote:
> Luigi Toscano wrote:
>
>> On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote:
>>> On 08/10/2016 04:33 AM, Duncan Thomas wrote:
So I tried to get into helping with the cinder stable tree for a while,
and while I wasn't very succ
Hi all,
Both Sudipta and Wenzhi have been actively contributing to the Zun project
for a while. Sudipta provided helpful advice for the project roadmap and
architecture design. Wenzhi consistently contributed high quality patches
and insightful reviews. I think both of them are qualified to join t
While supernova looks super cool on photographs, I frankly have no idea how
this could look like a logo. You know, the cartoonish style. Tried to google
for examples, but they do look terrible…
From: Bob Ball [mailto:[email protected]]
Sent: Wednesday, August 10, 2016 6:37 AM
To: OpenStack Dev
On 09/08/16 18:28, Fox, Kevin M wrote:
It needs to work in a distributed way...
What happens if the one node you have cron running on doesn't work for a while.
Keystone breaks?
IIUC it wouldn't break, but your keys wouldn't get rotated so you'd end
up using the same key until such time as yo
Excerpts from Doug Hellmann's message of 2016-07-29 16:55:22 -0400:
> One of the outcomes of the discussion at the leadership training
> session earlier this year was the idea that the TC should set some
> community-wide goals for accomplishing specific technical tasks to
> get the projects synced
On 08/10/2016 11:19 AM, Szankin, Maciej wrote:
> While supernova looks super cool on photographs, I frankly have no idea
> how this could look like a logo. You know, the cartoonish style. Tried
> to google for examples, but they do look terrible…
That's why you have graphics designers try a thing.
On 09/08/16 21:21, Adam Young wrote:
On 08/09/2016 06:00 PM, Zane Bitter wrote:
In either case a good mechanism might be to use a Heat Software
Deployment via the Heat API directly (i.e. not as part of a stack) to
push changes to the servers. (I say 'push' but it's more a case of
making the dat
On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote:
> Luigi Toscano wrote:
> > On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote:
> >> On 08/10/2016 04:33 AM, Duncan Thomas wrote:
> >>> So I tried to get into helping with the cinder stable tree for a while,
> >>> and
On 08/09/2016 07:30 PM, Heidi Joy Tretheway wrote:
> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll
> be missed. :-)
>
> A few notes following up on Matt Riedemann, Clint Byrum, Daniel
> Berrange’s conversation regarding the Nova mascot…
>
> Nova doesn’t have to have a mas
On Wed, Aug 10, 2016 at 9:21 AM, Jim Rollenhagen
wrote:
> Hi Ironicers,
>
> This email serves as a reminder (and a bit of a call to action) about our
> third party CI policy:
> http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/third-party-ci.html
>
> 1) When I went to find a
On Wed, Aug 10, 2016 at 8:21 AM, Jim Rollenhagen
wrote:
> Hi Ironicers,
>
> This email serves as a reminder (and a bit of a call to action) about our
> third party CI policy:
> http://specs.openstack.org/openstack/ironic-specs/specs/
> not-implemented/third-party-ci.html
>
> 1) When I went to fin
On 08/10/2016 11:36 AM, Sean Dague wrote:
> On 08/09/2016 07:30 PM, Heidi Joy Tretheway wrote:
>> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll
>> be missed. :-)
>>
>> A few notes following up on Matt Riedemann, Clint Byrum, Daniel
>> Berrange’s conversation regarding the N
On 08/08/2016 09:22 PM, Dan Prince wrote:
> On Mon, 2016-08-08 at 15:42 -0500, Ben Nemec wrote:
>> This is something that has existed for a while, but I had been
>> hesitant
>> to evangelize it until it was a little more proven. At this point
>> I've
>> used it to generate templates for a number o
On 08/10/2016 11:33 AM, Luigi Toscano wrote:
On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote:
Luigi Toscano wrote:
On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote:
On 08/10/2016 04:33 AM, Duncan Thomas wrote:
So I tried to get into helping with the cinder s
On Wed, Aug 10, 2016 at 11:52 AM, Ben Nemec wrote:
> On 08/08/2016 09:22 PM, Dan Prince wrote:
> > On Mon, 2016-08-08 at 15:42 -0500, Ben Nemec wrote:
> >> This is something that has existed for a while, but I had been
> >> hesitant
> >> to evangelize it until it was a little more proven. At thi
On 19:42 Aug 09, Ben Swartzlander wrote:
> Mike, you must have left the midcycle by the time this topic came up. On the
> issue of out-of-tree drivers, I specifically offered this proposal (a
> community managed mechanism for distributing driver bugfix backports) as an
> compromise alternative to t
It's time to make sure we have all of our active technical contributors
(ATCs) identified for Newton.
Following the Foundation bylaws [1] and TC Charter [2], Project
teams should identify contributors who have had a significant impact
this cycle but who would not qualify for ATC status using the r
+1
On Tue, Aug 9, 2016 at 9:13 AM, James Page wrote:
> On Mon, 8 Aug 2016 at 18:19 Ryan Beisner wrote:
>>
>> Greetings,
>>
>> I would like to nominate David Ames for addition to the
>> charms-release team, as he has played a valuable role in the charm release
>> processes. This change will gra
On Wednesday, 10 August 2016 12:00:41 CEST Ben Swartzlander wrote:
> On 08/10/2016 11:33 AM, Luigi Toscano wrote:
> > On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote:
> >> Luigi Toscano wrote:
> >>> On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote:
> On 08/10
On 08/10/2016 04:51 AM, Erno Kuvaja wrote:
On Wed, Aug 10, 2016 at 9:27 AM, Thomas Goirand wrote:
Not necessarily. Take for example Swift. It has lower requirements than
other projects in OpenStack. Yet, Swift is fully co-installable with all
other OpenStack projects. They just support lower
On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander
wrote:
>
> A big source of problems IMO is that tempest doesn't have stable branches.
> We use the master branch of tempest to test stable branches of other
> projects, and tempest regularly adds new features.
>
How come not this +1000 just fix t
On Mon, Aug 8, 2016 at 8:31 AM, Matthew Treinish
wrote:
> When we EOL a branch all of the infrastructure for running any ci against
> it goes away.
But... like... version control? I mean I'm sure it's more complicated than
that or you wouldn't have said this - but I don't understand, sorry.
C
Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400:
> 2) A number of drivers do not have third-party CI up, let alone reporting
>on patches. Unless someone moves quickly, I strongly suspect the following
>drivers will be dropped from our tree before the end of Newton. Thes
On Wed, Aug 10, 2016 at 1:05 PM, Clint Byrum wrote:
> Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400:
>> 2) A number of drivers do not have third-party CI up, let alone reporting
>>on patches. Unless someone moves quickly, I strongly suspect the following
>>drivers wi
Hello Neutrinos,
One of the things, that is required to have ease of use, is good documentation.
Similar to what's done for Nova [4], I've decided to prepare Feature
Classification for Neutron.
Work was already approved, and it got greenlit [1], but we still lack of final
approval. In the light
On Wed, Aug 10, 2016 at 09:56:09AM -0700, Clay Gerrard wrote:
> On Mon, Aug 8, 2016 at 8:31 AM, Matthew Treinish
> wrote:
>
> > When we EOL a branch all of the infrastructure for running any ci against
> > it goes away.
>
>
> But... like... version control? I mean I'm sure it's more complicate
Excerpts from Jim Rollenhagen's message of 2016-08-10 13:21:11 -0400:
> On Wed, Aug 10, 2016 at 1:05 PM, Clint Byrum wrote:
> > Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400:
> >> 2) A number of drivers do not have third-party CI up, let alone reporting
> >>on patches. U
On Wed, Aug 10, 2016 at 10:21 AM, Matthew Treinish
wrote:
> But, to keep the gate running
> involves a lot of coordination between multiple projects that are tightly
> coupled. Things like an entire extra set of job definitions in zuul, a
> branch on
> global requirements, a devstack branch, extr
-Original Message-
From: Chris Friesen
Reply: OpenStack Development Mailing List (not for usage questions)
Date: August 10, 2016 at 11:50:48
To: [email protected]
Subject: Re: [openstack-dev] [requirements] History lesson please
> On 08/10/2016 04:51 AM, Erno Kuvaja wr
On Wed, Aug 10, 2016 at 09:52:55AM -0700, Clay Gerrard wrote:
> On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander
> wrote:
>
> >
> > A big source of problems IMO is that tempest doesn't have stable branches.
> > We use the master branch of tempest to test stable branches of other
> > projects, an
On Wed, Aug 10, 2016 at 10:57 AM, Matthew Treinish
wrote:
> We also test every incoming
> tempest change on all the stable branches, and nothing can land unless it
> works
> on all supported branches.
Did not know that, pretty awesome!
>
-Clay
_
On 10 August 2016 at 10:20, Gupta, Ankur wrote:
> Hello Neutrinos,
>
>
>
> One of the things, that is required to have ease of use, is good
> documentation.
>
> Similar to what's done for Nova [4], I've decided to prepare Feature
> Classification for Neutron.
>
> Work was already approved, and it
Join us Thursday for our weekly meeting, scheduled for August 11th at
17:00UTC in #openstack-meeting-3
The agenda can be found here, and please add to if you want to discuss
something with the Community App Catalog team:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Tomorrow we will be tal
https://review.openstack.org/353693
Thanks!
Eran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/
Greetings,
In an effort to make TripleO CI composable and managed and governed by the
TripleO project we have found the need to create additional git repos in
openstack under the TripleO project. This could also be done outside of
the TripleO project, but ideally it's in TripleO.
I'm proposing
On Wed, Aug 10, 2016 at 10:57 AM, Matthew Treinish
wrote:
>
> http://specs.openstack.org/openstack/qa-specs/specs/tempest/implemented/
> branchless-tempest.html
>
>
>
This was actually a *great* read, thanks for that link!
-Clay
___
Hi all,
I wanted to report on status and answer any questions you all have about
the API reference and guide publishing process.
The expectation is that we provide all OpenStack API information on
developer.openstack.org. In order to meet that goal, it's simplest for now
to have all projects use t
Miguel--
There have been a number of tempest patches in the review queue for a long
time now, but I think the reason they're not getting attention is that we
don't want to have to import a massive amount of tempest code into our
repository (which will become stale and need hot-fixing, as has happe
On Tue, Aug 9, 2016 at 11:54 AM, Hayes, Graham wrote:
>
> It might not make a difference to deployers / packagers who only deploy
> one project from OpenStack, but they are in the minority - having a
> known good minimum for requirements helps deployers who have multiple
> services to deploy.
>
On 08/09/2016 01:28 AM, Vasyl Saienko wrote:
> Hello Ironic'ers!
>
> We've recorded a demo that shows how static portgroup works at the moment:
>
> Flat network scenario: https://youtu.be/vBlH0ie6Lm4
> Multitenant network scenario: https://youtu.be/Kk5Cc_K1tV8
Awesome! Thank you for creating & s
On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann
wrote:
> It's time to make sure we have all of our active technical contributors
> (ATCs) identified for Newton.
>
> Following the Foundation bylaws [1] and TC Charter [2], Project
> teams should identify contributors who have had a significant impac
Based on reading some logs, it looks like requirements updates are
getting regenerated on every requirements land for all open patches,
even if they aren't impacted by it -
https://review.openstack.org/#/c/351991/
patch 10,11,12 in that series are just rebases, all happening within a
couple of hou
Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann
> wrote:
>
> > It's time to make sure we have all of our active technical contributors
> > (ATCs) identified for Newton.
> >
> > Following the Foundation bylaws [1] and TC Charter
Sean and team,
On Wed, 2016-08-03 at 08:55 -0300, Erlon Cruz wrote:
> Hi sean, I think it would worth to CC the contact info informed in
> the CI
> Wiki ([email protected]).
>
> On Tue, Aug 2, 2016 at 4:26 PM, Sean McGinnis
> wrote:
>
> >
> > Tomorrow is the one week grace period. I jus
On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann
wrote:
> Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann
> > wrote:
> >
> > > It's time to make sure we have all of our active technical contributors
> > > (ATCs) identified for
Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000:
> On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann
> wrote:
>
> > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> > > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann
> > > wrote:
> > >
> > > > It's time to mak
On 2016-08-11 07:01:37 +1000 (+1000), Michael Still wrote:
> I have a script to generate this that I wrote while Nova PTL.
[...]
Note that, as one requirement for ATC status is being a current
OpenStack Foundation Individual Member, there is still the manual
step of confirming that for each potent
On Thu, Aug 11, 2016 at 7:38 AM, Doug Hellmann
wrote:
> Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000:
> > On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann
> > wrote:
> >
> > > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> > > > On Thu, Aug 11, 2016 at
+1
On Wed, Aug 10, 2016 at 4:13 AM, Antoine Cabot
wrote:
> +1
>
> On Thu, Aug 4, 2016 at 9:29 AM, Vincent FRANÇOISE
> wrote:
> > Alexander Chadin did prove he knew the various moving parts of Watcher
> > by participating the numerous design discussions and blueprints during
> > the last months
On 2016-08-11 08:25:00 +1000 (+1000), Michael Still wrote:
[...]
> At the time I proposed it for the tools directory in the governance repo,
> but it never actually landed.
[...]
For reference: https://review.openstack.org/121730
--
Jeremy Stanley
On Friday, August 12, at approximately 20:00 UTC our Gerrit service
on review.openstack.org will be restarted for some minor patch
updates and addition of a Storyboard integration plug-in. The outage
is anticipated to run less than 5 minutes, though could go slightly
longer if issues are encountere
On Friday, August 12, from approximately 21:00 to 23:00 UTC our
Mediawiki instance on wiki.openstack.org will be upgraded from its
present 1.25 pre-release to the latest 1.27 version. We're allotting
two hours in case issues are encountered with the upgrade requiring
us to roll back to a snapshot,
1 - 100 of 109 matches
Mail list logo
