Hi,
Thanks for all the help and support over the years. Both LBaaS (Octavia) and
FWaaS wouldn’t be what they are today without your leadership and advice –
All the best + good luck,
German
From: "Armando M."
Reply-To: "OpenStack Development Mailing List (not for usage
On Wed, Dec 13, 2017 at 4:17 PM, Thierry Carrez wrote:
> Hi everyone,
>
> Over the past year, it has become pretty obvious to me that our
> self-imposed rhythm no longer matches our natural pace. It feels like we
> are always running elections, feature freeze is always just
# Keystone Team Update - Week of 18 December 2017
## News
### Unified Limits
We accepted the Limits API spec[1] last week, for which we had made a
spec freeze exception.
### Allowing control over project ID generation
At our weekly meeting, we had a productive conversation[2] about a
On 12/21/2017 07:27 PM, Matt Riedemann wrote:
On 12/21/2017 4:37 PM, Joshua Harlow wrote:
My 3 cents are that this isn't something that u get asked to put in
from operators, it's something that is built in from the start. Just
look at other workflow systems (which is really what
Follow up, have been testing some integration runs on a tmp machine.
Had to fix the following:
* Ceph repo key E84AC2C0460F3994 perhaps introduced in [0]
* Run glance-manage db_sync (have not seen in integration tests)
* Run neutron-db-manage upgrade heads (have not seen in integration tests)
*
This is just a public service announcement, so no immediate action is needed.
Just raising awareness as something to think about.
We have several libraries, and a few services, for projects that are still
using a 0.x release version:
http://paste.openstack.org/show/629645/
This is fine, and may
Sad to hear. You brought a lot to the community in particular in
helping the Neutron Stadium take shape.
Thank you for that and all the rest!
Hoping you'll keep contributing as actively as possible,
-Thomas
Armando M., 2017-12-15 11:01:
> Hi neutrinos,
>
> To some of you this email may not
Hi!
This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
If you are working on something (or plan to work on something) that is
not on the tracker, feel
Dear all,
a few persons have put their name in the edge etherpad, thanks:
https://etherpad.openstack.org/p/2017_edge_computing_working_sessions (see line
21).
in order to finalise the logistic details, I would like to make a first
proposal for the agenda:
* Monday afternoon - internal
Ignore that, seems like it's the networking-l2gw package that fails[0]
Seems like it hasn't been packaged for queens yet[1] or more it seems
like a release has not been cut for queens for networking-l2gw[2]
Should we try to disable l2gw like done in[3] recently for CentOS?
[0]
2017-12-22 9:18 GMT+00:00 Tobias Urdin :
> Follow up on Alex[1] point. The db sync upgrade for neutron fails here[0].
>
> [0] http://paste.openstack.org/show/629628/
This seems to be a known issue, see [2]. Also I think that this is a
red herring caused by the database
Follow up on Alex[1] point. The db sync upgrade for neutron fails here[0].
[0] http://paste.openstack.org/show/629628/
On 12/22/2017 04:57 AM, Alex Schultz wrote:
>> Just a note, the queens repo is not currently synced in the infra so
>> the queens repo patch is failing on Ubuntu jobs. I've
Matt Riedemann wrote:
> On 12/14/2017 2:24 PM, Sean McGinnis wrote:
>> Hey all,
>>
>> As we get closer to Queens-3 and our final RCs, I wanted to remind
>> everyone
>> about the new 'cycle-highlights' we have added to our deliverable info.
>>
>> Background
>> --
>>
>> As a reminder on the
13 matches
Mail list logo