i went through existing bugs and prioritized them.
i'd recommend the others to do the same. there are not too many of them.
i also updated series and milestones.
On Mon, Jul 2, 2018 at 7:02 PM, Takashi Yamamoto wrote:
> hi,
>
> I created a LP team "tap-as-a-service-drivers",
> whose initial
I've had a few operators complain about the permissive rule tripleo
creates for ssh. The current alternatives seems to be to either disable
tripleo firewall management completely, or move from the default-deny
model to a set of rules that include higher-priority blacklist rules
for ssh traffic.
On Wed, Jul 11, 2018 at 10:39:30AM -0600, Alex Schultz wrote:
> Currently open with pending patches (may need FFE):
> - https://blueprints.launchpad.net/tripleo/+spec/multiarch-support
I'd like an FFE for this, the open reviews are in pretty good shape and
mostly merged. (or +W'd).
We'll need
On Thu, Jul 12, 2018 at 11:31:34AM -0500, Monty Taylor wrote:
> there is also
>
> https://review.openstack.org/#/c/580730/
>
> which adds a role to install docker and configure it to use the correct
> registry.
shiny! That'll take care of all the docker setup nice!
Can I create a job
On Thu, Jul 12, 2018 at 11:05:09AM -0500, Matthew Thode wrote:
> I'm of the opinion that we should decouple from distro supported python
> versions and rely on what versions upstream python supports (longer
> lifetimes than our releases iirc).
Using docker/pyenv does this decoupling but I'm not
On Thu, Jul 12, 2018 at 11:31:34AM -0500, Monty Taylor wrote:
> FWIW, I use pyenv for python versions on my laptop and love it. I've
> completely given up on distro-provided python for my own usage.
Hmm okay I'll look at that and how it'd play with the generate job.
It's quite possible I'm
On Thu, Jul 12, 2018 at 01:52:56PM +, Jeremy Stanley wrote:
> On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote:
> [...]
> > I think most of the problems with Fedora stability are around
> > bringing up a new Fedora every 6 months or so. They tend to change
> > sufficiently within that
On Thu, Jul 12, 2018 at 06:37:52AM -0700, Clark Boylan wrote:
> On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote:
> > 1. Build pythons from source and use that to construct the venv
> >[please no]
>
> Fungi mentions that 3.3 and 3.4 don't build easily on modern linux distros.
> However,
On Tue, Jul 10, 2018 at 10:22 AM Jiří Stránský wrote:
> Hi,
>
> with the move to config-download deployments, we'll be moving from
> executing external installers (like ceph-ansible) via Heat resources
> encapsulating Mistral workflows towards executing them via Ansible
> directly (nested
Here it is for nova.
https://review.openstack.org/#/c/582392/
>> also don't love that immediately bumping the lower bound for tox is
>> going to be kind of disruptive to a lot of people.
By "kind of disruptive," do you mean:
$ tox -e blah
ERROR: MinVersionError: tox version is 1.6, required
DB work is now pushed for the single transaction reshape() function:
https://review.openstack.org/#/c/582383
Note that in working on that, I uncovered a bug in
AllocationList.delete_all() which needed to first be fixed:
https://bugs.launchpad.net/nova/+bug/1781430
A fix has been pushed
Hi everyone!
It's yet another of these emails where I'm going to complain out of
frustration because of OpenStack having bugs when running with the
newest stuff... Sorry in advance ! :)
tl;dr: It's urgent, we need Python 3.7 uwsgi + SSL gate jobs.
Longer version:
When Python 3.6 reached
Greetings! We've been deploying with Kolla on CentOS 7 now for a while, and
we've recently noticed a rather troubling behavior when we shutdown
hypervisors.
Somewhere between systemd and libvirt's systemd-machined integration,
we see that guests get killed aggressively by SIGTERM'ing all of the
Development Focus
-
Teams should be focused on implementing planned work. Work should be
wrapping up on non-client libraries to meet the lib deadline Thursday,
the 19th.
General Information
---
We are now getting close to the end of the cycle. The non-client
On 07/12/2018 11:05 AM, Matthew Thode wrote:
On 18-07-12 13:52:56, Jeremy Stanley wrote:
On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote:
[...]
I think most of the problems with Fedora stability are around
bringing up a new Fedora every 6 months or so. They tend to change
sufficiently
Greetings OpenStack community,
Today's meeting was very brief as both cdent and dtantsur were out.
There were no major items of discussion, but we did acknowledge the
efforts of the GraphQL proof of concept work[7] being led by Gilles
Dubreuil. This work continues to make progress and should
On 07/12/2018 08:37 AM, Clark Boylan wrote:
On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote:
Hi Folks,
We have a pit of a problem in openstack/requirements and I'd liek to
chat about it.
Currently when we generate constraints we create a venv for each
(system) python supplied on the
All the cool kids are doing it, so here's one for Oslo:
https://etherpad.openstack.org/p/oslo-stein-ptg-planning
I've populated it with a few topics that I expect to discuss, but feel
free to add anything you're interested in.
Thanks.
-Ben
On 7/11/2018 1:20 AM, Luke Hinds wrote:
On Tue, Jul 10, 2018 at 9:08 PM, Jim Rollenhagen
mailto:j...@jimrollenhagen.com>> wrote:
On Tue, Jul 10, 2018 at 3:28 PM, Martin Chlumsky
mailto:martin.chlum...@gmail.com>> wrote:
It is the workaround that is right and the
On 18-07-12 13:52:56, Jeremy Stanley wrote:
> On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote:
> [...]
> > I think most of the problems with Fedora stability are around
> > bringing up a new Fedora every 6 months or so. They tend to change
> > sufficiently within that time period to make
Hi team,
I've created an etherpad [1] to gather topics for PTG discussions in
Denver.
Please, do not hesitate to add any topic you think is valuable even you
won't
attend PTG.
I hope to see all of you in September!
[1] https://etherpad.openstack.org/p/horizon-ptg-planning-denver-2018
On 7/11/18 7:39 PM, Alex Schultz wrote:
Hello everyone,
As milestone 3 is quickly approaching, it's time to review the open
blueprints[0] and their status. It appears that we have made good
progress on implementing significant functionality this cycle but we
still have some open items. Below
On Wed, 2018-07-11 at 10:39 -0600, Alex Schultz wrote:
> Hello everyone,
>
> As milestone 3 is quickly approaching, it's time to review the open
> blueprints[0] and their status. It appears that we have made good
> progress on implementing significant functionality this cycle but we
> still have
Let's just get the darn thing done in Rocky. I will have the DB work up
for review today.
-jay
On 07/12/2018 10:45 AM, Matt Riedemann wrote:
Continuing the discussion from the nova meeting today [1], I'm trying to
figure out what the risk / benefit / contingency is if we don't get the
Continuing the discussion from the nova meeting today [1], I'm trying to
figure out what the risk / benefit / contingency is if we don't get the
reshaper stuff done in Rocky.
In a nutshell, we need reshaper to migrate VGPU inventory for the
libvirt and xenapi drivers from the root compute
Dear Stackers,
I'm currently looking for some inputs in order to get a new validation,
ran as a "preflight check" on the undercloud.
The aim is to ensure we actually have enough disk space for all the
files and, most importantly, the registry, being local on the
undercloud, or remote (provided
Hey all,
This month's bug day went pretty well! We discussed about 20 bugs (half
old, half new). Many were triaged, some got marked invalid. For meeting
minutes and details, see the etherpad [0].
The attendance was a bit low (Thank you for attending Julia and Adam!),
but could be due to
On 07/12/2018 02:53 AM, Takashi Yamamoto wrote:
hi,
queens branch of networking-midonet has had no changes merged since
its creation.
the following commit would tell you how many gate blockers have been
accumulated.
https://review.openstack.org/#/c/572242/
it seems the stable team doesn't have
On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote:
[...]
> I think most of the problems with Fedora stability are around
> bringing up a new Fedora every 6 months or so. They tend to change
> sufficiently within that time period to make this a fairly
> involved exercise. But once working
On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote:
> Hi Folks,
> We have a pit of a problem in openstack/requirements and I'd liek to
> chat about it.
>
> Currently when we generate constraints we create a venv for each
> (system) python supplied on the command line, install all of
>
On 7/12/18 4:10 AM, Takashi Yamamoto wrote:
> On Thu, Jul 12, 2018 at 6:13 PM, Tony Breeds wrote:
>>
>> No we need more contributors to stable and extended maintenance periods.
>> This is not a new problem, and one we're trying to correct.
>
> actually it is a new problem. at least worse than
You probably also need to change the parameters being added to the
structure to match the chosen padding mechanism.
mech = self.ffi.new("CK_MECHANISM *")
mech.mechanism = CKM_AES_CBC_PAD
iv = self._generate_random(16, session)
mech.parameter = iv
hi,
On Thu, Jul 12, 2018 at 6:13 PM, Tony Breeds wrote:
> On Thu, Jul 12, 2018 at 03:53:22PM +0900, Takashi Yamamoto wrote:
>> hi,
>>
>> queens branch of networking-midonet has had no changes merged since
>> its creation.
>> the following commit would tell you how many gate blockers have been
>>
Hi folks,
I'm working on the kuryr-kubernetes namespace feature to enable
isolation between the different namespaces, i.e., pods on namespace A
cannot 'talk' to pods or services on namespace B.
For the pods isolation, there is already a patch working:
https://review.openstack.org/#/c/579181
On Thu, Jul 12, 2018 at 03:53:22PM +0900, Takashi Yamamoto wrote:
> hi,
>
> queens branch of networking-midonet has had no changes merged since
> its creation.
> the following commit would tell you how many gate blockers have been
> accumulated.
> https://review.openstack.org/#/c/572242/
>
> it
Hi all,
The requirements team is only a light user of Launchpad and we're
looking at moving to StoryBoard as it looks like for the most part it'll
be a better fit.
To date the thing that has stopped us doing this is the handling of
bugs/stories that are shared between LP and SB.
Assume that
hi,
queens branch of networking-midonet has had no changes merged since
its creation.
the following commit would tell you how many gate blockers have been
accumulated.
https://review.openstack.org/#/c/572242/
it seems the stable team doesn't have a bandwidth to review subprojects
in a timely
37 matches
Mail list logo
