Thanks for the reminder, I saw related patches showed up in the Gerrit,
will ensure them pass validation jobs.
2017-07-29 5:13 GMT+08:00 Doug Hellmann :
> As Thierry mentioned in his countdown email today, the release team has
> now created the stable branches for most deliverables with type
> "l
Hello,
The patch [1] is to add a tag for python-tricircleclient after new features
were added to it since last release. But unfortunately, a branch called
"stable/pike" was there in Apr., and lead to the patch can not pass the gate
test.
"deliverables/pike/python-tricircleclient.yaml:
opensta
Hi.
I'm working through the process of converting the libvirt driver in Nova to
privsep with the assistance of Tony Breeds. For various reasons, I started
with removing all the calls to the chown binary and am replacing them with
privsep equivalents. You can see this work at:
https://review.o
On Fri, Jul 28, 2017 at 07:39:25PM +, Jeremy Stanley wrote:
> On 2017-07-28 15:32:01 -0400 (-0400), David Desrosiers wrote:
> [...]
> > I am very opposed to removing subsets of docs, including the install guide,
> > after the release goes eol upstream from consumers for exactly that reason.
> >
On 03:07 Jul 25, Sean McGinnis wrote:
> I am proposing we add TommyLike as a Cinder core.
>
> DISCLAIMER: We work for the same company.
>
> I have held back on proposing him for some time because of this conflict. But
> I think from his number of reviews [1] and code contributions [2] it's
> hope
On 2017-07-28 15:37:07 -0400 (-0400), David Desrosiers wrote:
[...]
> You could compress the individual files, configure the webserver to send
> the correct encoding (Content-Encoding: gzip or deflate) to the client
> (assuming their browser sends the correct Accept-Encoding header) which can
> the
Maybe we could just ban search engines from indexing the releases using
robots.txt once they go EOL. That would solve the problem of losing old
information for people that still need it while preventing people stumbling
onto old docs when they search for something.
On Fri, Jul 28, 2017 at 12:39 PM
As Thierry mentioned in his countdown email today, the release team has
now created the stable branches for most deliverables with type
"library".
We have 3 exceptions:
1. python-neutronclient had a late release, so I will be branching it
shortly.
2. python-barbicanclient was skipped until the
On 2017-07-28 15:32:01 -0400 (-0400), David Desrosiers wrote:
[...]
> I am very opposed to removing subsets of docs, including the install guide,
> after the release goes eol upstream from consumers for exactly that reason.
>
> Watermarking the upstream docs with series and version should reduce o
On Thu, Jul 27, 2017 at 8:16 PM, Sean McGinnis
wrote:
> I like this approach. With the size being manageable (large, but
> manageable), I would prefer we leave it until we need to free up
> some of the space
You could compress the individual files, configure the webserver to send
the correct en
On Thu, Jul 27, 2017 at 6:07 PM, Jeremy Stanley wrote:
> The current solution of not publishing installation guides for EOL
> releases seems like a
> good enough compromise there to me.
>
This then breaks fidelity for those operators who need to either reinstall
their existing environment, which
Hi PTL/all,
I would like to request an exception for inclusion of net-mtu-enh API
extension (with ML2 implementation) for Pike.
The patch is ready for review, it includes tempest tests and docs
update. There are several things in the patch that we will need to
follow up in the next release (hence
A change to remove these channels is now up at
https://review.openstack.org/488544
I'll put this for one week in WIP to give teams the chance to -1 - and
will pop in their channels to tell them about this as well,
Andreas
On 2017-07-19 21:24, Jeremy Stanley wrote:
> For those who are unaware, F
Thanks for the suggestion, Jeremy.
I¹ll look into that. Two key pieces will be needed:
1. Know ahead of time what user tempest tests would be run from (should be
determined by job setup?)
2. Have a way to specify in job/devstack to start congress using that user.
On 7/28/17, 6:30 AM, "Jeremy Stan
Thanks for your help and sketch of solution, Andrea! -Eric
From: Andrea Frittoli
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, July 28, 2017 at 9:03 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev]
On 07/28/2017 09:47 AM, Chris Dent wrote:
On Fri, 28 Jul 2017, Chris Dent wrote:
I thought there were going to be some changes to the resource tracker
made overnight, related to ensuring allocations on the source and
destination of a move are managed correctly, but I don't see them yet.
If they
On Fri, Jul 28, 2017 at 4:38 AM Eric K wrote:
> A tempest test [1] launches additional instances of Congress using
> subprocess.popen and tests the coordination between them and the original
> instance launched by devstack. The problem is, the new instances are
> launched from the tempest test us
Welcome to our regular release countdown email!
Development Focus
-
Focus should be on fixing release-critical bugs in order to produce the
first release candidates (for deliverables following the with-milestones
model) or final Pike releases (for deliverables following the
with-i
If the topics below interest you and you want to contribute to the
discussion, feel free to join the next meeting:
Time: Thursdays, 14:30-15:30 UTC
Place: https://bluejeans.com/4113567798/
Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
= Discussion topics =
Wes sugges
Hello,
When we build the kolla images using the command [1], it builds
neutron-server-ovn and neutron-server-odl which are not in tripleoupstream
docker hub.
Is it possible to upload them ? I am not sure if it is done manually or a
script does it.
neutron-server-ovn image is required to have a C
Excerpts from Jeremy Stanley's message of 2017-07-28 13:23:32 +:
> On 2017-07-28 08:34:18 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > I wasn't able to come up with a way to disable the link without
> > triggering a new build. I didn't want us to have to land a patch in each
> > repo as part
On 7/26/2017 4:16 PM, Eric Harney wrote:
From a technical point of view there are not a lot of steps involved
here, we can restore the previous gate jobs and driver code and I expect
things would still be in working order.
I can help coordinate these things with the new owner.
Note that the l
On Fri, 28 Jul 2017, Chris Dent wrote:
I thought there were going to be some changes to the resource tracker
made overnight, related to ensuring allocations on the source and
destination of a move are managed correctly, but I don't see them yet.
If they get pushed up today can someone followup h
On 2017-07-27 20:37:49 -0700 (-0700), Eric K wrote:
> A tempest test [1] launches additional instances of Congress using
> subprocess.popen and tests the coordination between them and the original
> instance launched by devstack. The problem is, the new instances are
> launched from the tempest tes
On 2017-07-28 08:34:18 -0400 (-0400), Doug Hellmann wrote:
[...]
> I wasn't able to come up with a way to disable the link without
> triggering a new build. I didn't want us to have to land a patch in each
> repo as part of marking it EOL, but if we're going to do that to remove
> the installation
Hello,
I will try to check QoS tests in this job.
—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl
> Wiadomość napisana przez Jakub Libosvar w dniu
> 28.07.2017, o godz. 14:49:
>
> Hi all,
>
> as sending out a call for help with our precious jobs was very
> successful last time and we
On Wed, Jul 26, 2017 at 7:39 AM, Jiří Stránský wrote:
> On 21.7.2017 16:55, Emilien Macchi wrote:
>
>> Hi,
>>
>> Bogdan (bogdando on IRC) has been very active in Containerization of
>> TripleO and his quality of review has increased over time.
>> I would like to give him core permissions on conta
Hi all,
as sending out a call for help with our precious jobs was very
successful last time and we swept all Python 3 functional from Neutron
pretty fast (kudos the the team!), here comes a new round of failures.
This time I'm asking for your help with gate-tempest-dsvm-neutron-dvr-multinode-sce
Excerpts from Dmitry Tantsur's message of 2017-07-28 12:29:29 +0200:
> On 07/28/2017 09:12 AM, Andreas Jaeger wrote:
> > On 2017-07-27 21:40, Doug Hellmann wrote:
> >> [...]
> >> Please encourage everyone there to explore options that require the
> >> least amount of effort. An ideal solution is on
Excerpts from Andreas Jaeger's message of 2017-07-28 09:12:59 +0200:
> On 2017-07-27 21:40, Doug Hellmann wrote:
> > [...]
> > Please encourage everyone there to explore options that require the
> > least amount of effort. An ideal solution is one we can implement
> > without heroic efforts or havi
Information about the ironic deployment process including full workflows can be
found here:
https://docs.openstack.org/ironic/latest/user/index.html#deploy-process
Sam
On 28/07/2017, 12:49, "Waines, Greg"
mailto:greg.wai...@windriver.com>> wrote:
thanks Sam
What’s the 100,000 foot view of ho
Placement Update 30
# What Matters Most
Claims in the scheduler has merged, but first there was much gnashing
of teeth and pulling of hair at the many twisted webs we've weaved in
the scheduler and the resource tracker. While the base functionality
is now in master, it's not certain that it per
thanks Sam
What’s the 100,000 foot view of how ironic manages the configuration of a
baremetal server when it is booting an end-user’s OS image ?
e.g. my best guess so far from looking at ironic documentation
· ironic first deploys the ironic-python-agent to the server
oironic-pyt
Thanks for the info Mark.
A dumb question ... can’t seem to find the answer in ironic documentation ...
· I understand how the interface over which the bare metal instance
network boots/installs gets configured ...
i.e. thru DHCP response/configuration from the ironic conductor dhcp/boot
On 07/28/2017 12:58 AM, Tony Breeds wrote:
> On Fri, Jul 28, 2017 at 10:55:53AM +0800, ChangBo Guo wrote:
>> For the specific case with method "last_bytes", it's also used in other
>> projects [1], an alternative solution is that add this method in
>> oslo.utils.fileutils, then consume it from os
On 07/28/2017 09:12 AM, Andreas Jaeger wrote:
On 2017-07-27 21:40, Doug Hellmann wrote:
[...]
Please encourage everyone there to explore options that require the
least amount of effort. An ideal solution is one we can implement
without heroic efforts or having to recruit an army of contributors.
Hey everyone,
We tagged Horizons Pike-3 milestone about 12 hours, so I wanted to quickly run
through the next steps for the release. At this point, we are in "Feature
Freeze" and also "Soft String Freeze".
- Feature Freeze - No new features (blueprints or wishlist bugs) can be merged
without t
Hi all!
It was already announced on the meeting, but not on the ML.
Here is our planning etherpad for the PTG:
https://etherpad.openstack.org/p/ironic-queens-ptg
Please check "The Rules" section before proposing a topic. Please also add
yourself to the list of potential attendees in the bottom.
Andreas Jaeger wrote:
> On 2017-07-27 21:40, Doug Hellmann wrote:
>> [...]
>> Please encourage everyone there to explore options that require the
>> least amount of effort. An ideal solution is one we can implement
>> without heroic efforts or having to recruit an army of contributors.
>
> I agree
Hello Barbican Team,
I believe there were some discussions on room sharing between the security
project and barbican team.
We are still keen on this in the security project. How would you like to
work out logistics?
Should we share PTG planning etherpads?
We have 4 days between us, not sure if
Hi Greg,
Magnum clusters currently support using only a single network for all
communication. See the heat templates[1][2] in the drivers.
.
On the bare metal side, currently ironic effectively supports using only a
single network interface due to a lack of support for physical network
awareness.
Hi!
This is the weekly update on Technical Committee initiatives. You can
find the full list of all open topics at:
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
== Recently-approved changes ==
* Declare plainly the current state of PostgreSQL in OpenStack [1]
* Clean up remainin
Hi Rajeev,
The Chain Monitoring is the missing piece in networking-sfc . Vikram and
myself were discussed to introduce "SFC Manager" [1] (basically OAM tool )
few cycle before.
It'll continuously monitor an existing SFC chain, when any SF VM goes down
or any packet drop. It'll trigger alert and
On 2017-07-27 21:40, Doug Hellmann wrote:
> [...]
> Please encourage everyone there to explore options that require the
> least amount of effort. An ideal solution is one we can implement
> without heroic efforts or having to recruit an army of contributors.
I agree with the points made in general
On 2017-07-27 21:40, Doug Hellmann wrote:
> [...]
> Regarding point 2, if we don't have the space to host the content
> indefinitely, then we need to set a fixed, but longer, retention
> period before deleting it. Several years, at least. In the mean
> time, we could delete builds for intermediate
On 2017-07-28 01:10, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2017-07-27 19:05:16 -0400:
>> Excerpts from Jeremy Stanley's message of 2017-07-27 22:07:33 +:
>>> On 2017-07-27 15:40:22 -0400 (-0400), Doug Hellmann wrote:
>>> [...]
Are we over-emphasizing the scale of
Just a reminder, please add your name and topic in the etherpad if you
will join the discussion abouth Oslo at the PTG.
2017-07-10 21:48 GMT+08:00 ChangBo Guo :
> Hi Oslo folks,
>
> I created a planning etherpad[1] for topics for the next PTG in Denver.
> Please add any topics there, then we ca
47 matches
Mail list logo
