At Catalyst Cloud:
On Sat, Apr 28, 2018 at 3:04 AM Jim Rollenhagen
To the best of my knowledge the closest place where we do similar
sequence of actions (post deployment build and append environment
files to the deploy command and re-run overcloud deploy on top of an
already deployed overcloud) is tripleo-upgrade. As we discussed on IRC
I was reluctant
On Fri, Apr 27, 2018 at 11:41 AM, Emilien Macchi wrote:
> +1, thanks Tobias for your contributions!
> On Fri, Apr 27, 2018 at 8:21 AM, Iury Gregory wrote:
>> On Fri, Apr 27, 2018, 12:15 Mohammed Naser wrote:
Thanks a lot Michael.
On Fri, 27 Apr 2018, 19:57 Michael Johnson, wrote:
> Hi Artem,
> You are correct that the API reference at
> https://developer.openstack.org/api-ref/network/v2/index.html#pools is
> incorrect. As you figured out, someone mistakenly merged the long
You are correct that the API reference at
incorrect. As you figured out, someone mistakenly merged the long
dead/removed LBaaS v1 API specification into the LBaaS v2 API
specification at that link.
The current, and
+1, thanks Tobias for your contributions!
On Fri, Apr 27, 2018 at 8:21 AM, Iury Gregory wrote:
> On Fri, Apr 27, 2018, 12:15 Mohammed Naser wrote:
>> Hi everyone,
>> I'm proposing that we add Tobias Urdin to the core Puppet OpenStack
I am sorry to hear you are having trouble with the queens release of
Octavia. It is true that a lot of work has gone into the failover
capability, specifically working around a python threading issue and
making it more resistant to certain neutron failure situations
PS: If you have general questions on the schedule, additional updates to
an abstract, or changes to the speaker list, please send them along to
April 27, 2018 at 11:04 AM
Hello all -
Please take a look here for the
Excerpts from Doug Hellmann's message of 2018-04-27 10:02:08 -0400:
> The latest release of reno tries to add anchors to the page in a way
> that ensures they are named consistently across builds. For projects
> with the same version number in multiple series (which can happen for
I got started on kuryr-libnetwork but never finished the init/systemd scripts
but all dependencies in control file should be ok.
I uploaded it here: https://github.com/tobias-urdin/deb-kuryr-libnetwork (not a
After fixing kuryr-libnetwork one can get starting packaging Zun.
Hello all -
Please take a look here for the posted Forum schedule:
You should also see it update on your Summit App.
Thank you and see you in Vancouver!
On Fri, Apr 27, 2018 at 11:23 AM, Tobias Urdin
> I was very interested in packaging Zun for Ubuntu however I did not have
> the time to properly get started.
> I was able to package kuryr-lib, I've uploaded it here for now
Recently I starting looking at how we implement password changes in an
existing deployment, and found that there were issues. This made me
wonder whether we needed a test job to confirm that password changes
(and other config changes) are in fact executed properly.
As far as I understand
On Fri, Apr 27, 2018 at 2:07 AM Paul Bourke wrote:
> +1, always great working with Mark :)
> On 26/04/18 16:31, Jeffrey Zhang wrote:
> > Kolla core reviewer team,
> > It is my pleasure to nominate
> > mgoddard for kolla core team.
> > Mark has been
I was made aware today that new installations of ARA were not working
or failing to generate reports in a variety of gate jobs with a stack
trace that ends with:
AttributeError: 'Blueprint' object has no attribute 'json_encoder'
The root cause was identified to be a new release of Flask,
I was very interested in packaging Zun for Ubuntu however I did not have the
time to properly get started.
I was able to package kuryr-lib, I've uploaded it here for now
Would love to see both Zun and Qinling in Ubuntu to get a good grip
On Fri, Apr 27, 2018, 12:15 Mohammed Naser wrote:
> Hi everyone,
> I'm proposing that we add Tobias Urdin to the core Puppet OpenStack
> team as they've been putting great reviews over the past few months
> and they have directly contributed in resolving all the Ubuntu
I'm proposing that we add Tobias Urdin to the core Puppet OpenStack
team as they've been putting great reviews over the past few months
and they have directly contributed in resolving all the Ubuntu
deployment issues and helped us bring Ubuntu support back and make the
# Keystone Team Update - Week of 23 April 2018
### scope_types in nova
We've had some good discussions incorporating scope_types into nova . Thanks
to mriedem and jaypipes for helping out. The discussion flushed out some work
needed in keystonemiddleware  and oslo.context ,
On Wed, Apr 18, 2018 at 11:17 AM, Artom Lifshitz
> Hi all,
> A CI issue  caused by tempest thinking some filters are enabled
> when they're really not, and a proposed patch  to add
> (Same|Different)HostFilter to the default filters as a workaround, has
On Fri, Apr 27, 2018 at 10:20 AM, Hongbin Lu wrote:
> Thanks for the information. Would you clarify what is "working packages
> from the community"?
> Best regards,
Sorry I guess that comment is probably a bit vague.
The OpenStack packages are
On 4/27/2018 4:02 AM, Tomáš Vondra wrote:
Also, Windows host isolation is done using image metadata. I have filled
a bug somewhere that it does not work correctly with Boot from Volume.
Likely because for boot from volume the instance.image_id is ''. The
request spec, which the filter has
On Fri, Apr 27, 2018 at 6:43 AM, Dmitry Tantsur wrote:
I would like to run at least one TripleO CI job with cleaning enabled. Any
> objections to that? If not, what would be the best job (it has to run
> ironic, obviously)?
Thanks for the information. Would you clarify what is "working packages
from the community"?
On Fri, Apr 27, 2018 at 9:30 AM, Corey Bryant
> On Fri, Apr 27, 2018 at 9:03 AM, Hongbin Lu wrote:
The latest release of reno tries to add anchors to the page in a way
that ensures they are named consistently across builds. For projects
with the same version number in multiple series (which can happen for
non-milestone projects that haven't tagged for rocky yet), this causes
Okay, it seems like the idea was not well received, but I do have some action
items out of the discussion (thanks all!):
1. Simplify running cleaning per node. I've proposed patches  to add a new
command (documentation to follow) to do it.
2. Consider running metadata cleaning during
On 04/26/2018 07:16 PM, Tim Bell wrote:
My worry with changing the default is that it would be like adding the
following in /etc/environment,
alias ls=' rm -rf / --no-preserve-root'
i.e. an operation which was previously read-only now becomes irreversible.
Well, deleting instances
On Fri, Apr 27, 2018 at 9:03 AM, Hongbin Lu wrote:
> Hi Corey,
> What are the requirements to include OpenStack Zun into the Ubuntu
> packages? We have a comprehensive installation guide  that are using by
> a lot of users when they were installing Zun. However, the
Welcome to placement update 18-17. This is an expand update, meaning
I've gone searching for new stuff to add to the lists.
In other news: I'll be on holiday next week so there won't be one of
these next week, unless somebody else wants to do one.
# Most Important
A great deal of stuff is
What are the requirements to include OpenStack Zun into the Ubuntu
packages? We have a comprehensive installation guide  that are using by
a lot of users when they were installing Zun. However, the missing of
Ubuntu packages is inconvenient for our users. What the Zun team can help
With yesterday’s release of Ubuntu 18.04 LTS (the Bionic Beaver) the Ubuntu
OpenStack team at Canonical is pleased to announce the general availability
of OpenStack Queens on Ubuntu 18.04 LTS. This release of Ubuntu is a Long
Term Support release that will be supported for 5 years.
Thanks for confirmation.Ticket https://bugs.launchpad.net/mistral/+bug/1767352I will try to fix it. 27.04.2018, 12:02, "Renat Akhmerov" :Yep, agree that this is a bug. We need to fix that. Would you please create a ticket at LP?ThanksRenat Akhmerov@NokiaOn 27 Apr 2018,
Valence team is happy to announce the initial release of Valence-0.9.0 to
PyPi. Please find the details below.
Valence PyPi url: https://pypi.org/project/valence/ .
Documentation and Release Notes for the release can be found at:
Release Notes :
I have to cancel the next notification subteam meeting as it happens to
be on 1st of May which is (inter)national holiday. So the next meeting
expected to be held on 8th of May.
Thanks for bringing this up.
Having run into the topic for a few combination of deps, I'll certainly
agree that we need something better than what we currently have.
I don't feel that I've enough perspective on the whole system and
practices to give a strong opinion on what we
On 25/04/2018 18:40, Jeremy Stanley wrote:
This came up again a few days ago for sahara-dashboard. We talked
through some obvious alternatives to keep its master branch from
depending on an unreleased state of horizon and the situation today
is that plugin developers have been relying on
According to requirements and comments, now we opened the CI runs with
run_validation = True
And according to  below, for example,  need the ssh validation passed
And there are a couple of comments need some enhancement on the logs of CI
such as format and legacy incorrect links of
Can someone please help me with why this build ended with TIMED_OUT?
OpenStack Development Mailing List (not for usage
This is the weekly summary of Technical Committee initiatives. You can
find the full list of currently-considered changes at:
We also track TC objectives for the cycle using StoryBoard at:
+1, always great working with Mark :)
On 26/04/18 16:31, Jeffrey Zhang wrote:
Kolla core reviewer team,
It is my pleasure to nominate
mgoddard for kolla core team.
Mark has been working both upstream and downstream with kolla and
kolla-ansible for over two years, building bare metal
What we‘ve got in our small public cloud:
Yep, agree that this is a bug. We need to fix that. Would you please create a
ticket at LP?
On 27 Apr 2018, 12:53 +0700, Vitalii Solodilov , wrote:
> > No matter at what stage the task is, but if it’s still in RUNNING state or
> > FAILED but we
Everyone migrated away from tempest-lib to tempest, but there's still 2
packages that are remaining, still using the old deprecated tempest-lib.
Does anyone volunteer for the job? It'd be nice if that happened, so we
could get completely rid of the tempest-lib packages in distros and
Mail list logo