Glad to hear that the API meeting is happening again, I would also love to
join.
On Mon, Jun 11, 2018 at 10:49 AM Ghanshyam wrote:
> Hi All,
>
> As you might know, we used to have Nova API subteam meeting on Wed [1] but
> we did not continue that this year due to unavailability of members.
>
>
Hi Eric,
The format of the vitrage_id was changed to UUID in Pike release. It appears
that the API documentation [1] is outdated. I’ll fix it.
The vitrage_id that you get in the webhook notification should match the one
coming from ‘vitrage alarm list’. The ‘id’ field is determined by the
Hi, stackers.
We are distributing OpenStack to kubernetes using the docker image
generated by kolla. I recently upgraded from ocata to pike and found that
the cinder-api container does not run as a cinder user.
So it does not pass our unit test.
This seems to have been fixed in the following
Hi,
>From Pike cinder-api only runs as a wsgi process and container has been
migrated into an apache process, currenty we run apache as root user and
not as service's user.
Regards
2018-06-11 10:46 GMT+02:00 Jae Sang Lee :
> Hi, stackers.
>
> We are distributing OpenStack to kubernetes using
Hi Eric,
Apparently we have inconsistent behavior between the different datasources. The
format of the timestamp should be '%Y-%m-%dT%H:%M:%SZ' as defined in [1]. We
need to go over the code and make sure all datasources are aligned. I created a
bug for it [2].
[1]
Hi everyone,
As some of the OpenStack deliverables get more mature, we need to adjust
our release policies to best handle the case of deliverables that do not
need to be updated that much. This discussion started with how to handle
those "stable" libraries, but is actually also relevant for
On Fri, Jun 08, 2018 at 11:35:45AM +0200, Kashyap Chamarthy wrote:
> On Thu, Jun 07, 2018 at 01:07:48PM -0500, Matt Riedemann wrote:
> > On 6/7/2018 12:56 PM, melanie witt wrote:
> > > Recently, we've received interest about increasing the maximum number of
> > > allowed volumes to attach to a
Hi,
Going inline.
-Original Message-
From: Erno Kuvaja [mailto:ekuv...@redhat.com]
Sent: Friday, June 8, 2018 3:18 PM
Hi,
Answering inline.
Best,
Erno "jokke" Kuvaja
On Thu, Jun 7, 2018 at 11:49 AM, Csatari, Gergely (Nokia -
HU/Budapest) wrote:
> Hi,
>
>
>
> I did some work ont
Hi Eduardo,
Just for curiosity, do you know the motivation why many OS services were
moved to run on apache instead of just listen? Any reference about that?
Erlon
Em seg, 11 de jun de 2018 às 06:02, Eduardo Gonzalez
escreveu:
> Hi,
>
> From Pike cinder-api only runs as a wsgi process and
Hey everyone,
Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.
--
Kind regards,
Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
On Mon, 11 Jun 2018, Ghanshyam wrote:
2. If no member from USA/Europe TZ then, myself and Alex will
conduct the API meeting as office hour on Nova channel during our
day time (something between UTC+1 to UTC + 9). There is not much
activity on Nova channel during our TZ so it will be ok to use
On Mon, 11 Jun 2018, Thierry Carrez wrote:
2/ Do not force releases, but still create branches from latest releases
In this variant we would not force an artificial re-release, but we would
still create a branch from the last available release, in order to be able to
land future patches and
The 1.15.0 release of neutron-lib contains a syntax error in a LOG debug
call that was fixed with [1].
We are working to release the fix with 1.16.0 [2].
If you are running into this error [3], it maybe necessary to exclude
neutron-lib 1.15.0 and pickup 1.16.0 once we get it released.
Feel free
Hi,
I’m not sure about Queens but recently with [1] we switched default security
group driver in devstack to „openvswitch”.
Since at least month we have scenario gate job with this SG driver running as
voting and gating.
Currently, after switch devstack default driver to openvswitch it’s tested
Hi,
I don't want to hijack the initial thread, but am now feeling somewhat
guilty about not being vocal wrt Storyboard. Yes, ironic migrated to
Storyboard in the beginning of this cycle. To date, I have not been pleased
with replacing Launchpad with Storyboard. I believe that Storyboard is
Hi,
On 06/11/2018 03:53 PM, Ruby Loo wrote:
Hi,
I don't want to hijack the initial thread, but am now feeling somewhat guilty
about not being vocal wrt Storyboard. Yes, ironic migrated to Storyboard in the
beginning of this cycle. To date, I have not been pleased with replacing
Launchpad
Hi,
See a global openstack goal to move into wsgi
https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
And spec for cinder
https://review.openstack.org/#/c/192683/6/specs/liberty/non-eventlet-wsgi-app.rst
Regards
2018-06-11 14:36 GMT+02:00 Erlon Cruz :
> Hi Eduardo,
>
> Just
Thanks!
Em seg, 11 de jun de 2018 às 11:07, Eduardo Gonzalez
escreveu:
> Hi,
>
> See a global openstack goal to move into wsgi
> https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
> And spec for cinder
>
>
>
# Keystone Team Update - Week of 4 June 2018
## News
Sorry this didn't make it out last week.
This week we were busy wrapping up specification discussion before spec
freeze. Most of which revolved around unified limits [0]. We're also
starting to see implementations for MFA receipts [1] and
Excerpts from Dmitry Tantsur's message of 2018-06-11 16:00:41 +0200:
> Hi,
>
> On 06/11/2018 03:53 PM, Ruby Loo wrote:
> > Hi,
> >
> > I don't want to hijack the initial thread, but am now feeling somewhat
> > guilty
> > about not being vocal wrt Storyboard. Yes, ironic migrated to Storyboard
Hi,
Thanks for the comments.
I’ve updated the wiki:
https://wiki.openstack.org/wiki/Image_handling_in_edge_environment#Several_Glances_with_an_independent_syncronisation_service.2C_synch_using_the_backend
Br,
Gerg0
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: Friday, June 8,
Hi,
Here is the latest notification subteam update.
Bugs
[Medium] https://bugs.launchpad.net/nova/+bug/1739325 Server operations
fail to complete with versioned notifications if payload contains unset
non-nullable fields
This is also visible in tssurya's environment. I'm wondering if we
Excerpts from Thierry Carrez's message of 2018-06-11 11:53:52 +0200:
> Hi everyone,
>
> As some of the OpenStack deliverables get more mature, we need to adjust
> our release policies to best handle the case of deliverables that do not
> need to be updated that much. This discussion started
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard
Excerpts from Doug Hellmann's message of 2018-06-05 12:14:19 -0400:
> The review team [1] for the project-team-guide repository (managed
> by the TC) hasn't been updated for a while. I would like to propose
> removing a few reviewers who are no longer active, and adding one
> new reviewer.
>
> My
On Mon, Jun 11, 2018 at 11:55:29AM +0200, Sahid Orentino Ferdjaoui wrote:
> On Fri, Jun 08, 2018 at 11:35:45AM +0200, Kashyap Chamarthy wrote:
> > On Thu, Jun 07, 2018 at 01:07:48PM -0500, Matt Riedemann wrote:
[...]
> > > The 26 volumes thing is a libvirt driver restriction.
> >
> > The
I thought we were leaning toward the option where nova itself doesn't
impose a limit, but lets the virt driver decide.
I would really like NOT to see logic like this in any nova code:
> if kvm|qemu:
> return 256
> elif POWER:
> return 4000
> elif:
> ...
On
Jumping into the general Storyboard topic, but distinct from the previous
questions about searching, is there any equivalent in Storyboard to the
Launchpad series and milestones diagrams? e.g.:
https://launchpad.net/nova/+series
https://launchpad.net/neutron/+series
All,
I have gotten the Vancouver Summit Forum session recordings uploaded to
YouTube. You can see the links in our wiki here:
https://wiki.openstack.org/wiki/VancouverSummit2018Summary
Let me know if you have any questions.
Thanks!
Jay
On 6/11/2018 3:31 PM, Doug Hellmann wrote:
As we shift teams over to Storyboard, we have another opportunity
to review the processes and to decide how to use the new tool. Some
teams with lightweight processes will be able to move directly with
little impact. Other teams who are doing more
A few small status updates inline.
On 6/11/2018 4:14 PM, melanie witt wrote:
Hi everybody,
This is just a brief status about the blueprints currently occupying
review runways [0] and an ask for the nova-core team to give these
reviews priority for their code review focus.
* Certificate
On 04/06/18 10:13, Zane Bitter wrote:
On 31/05/18 14:35, Julia Kreger wrote:
Back to the topic of nitpicking!
I virtually sat down with Doug today and we hammered out the positive
aspects that we feel like are the things that we as a community want
to see as part of reviews coming out of this
Matt Riedemann wrote:
>The specs thing was mentioned last week in IRC when talking about blueprints
>in launchpad and I just want to reiterate the specs are
>more about high level designs and reviewing those designs in Gerrit which was
>/ is a major drawback in the 'whiteboard' in launchpad
Announcing the 18.05 release of the OpenStack Charms.
The 18.05 charms have full support for the Bionic Ubuntu series.
Encryption at rest has been implemented in the storage charms.
In addition, the vault and neutron-dynamic-routing charms have been
introduced. 72 bugs have been fixed and
Hi,
The tempest plugin error remember me something we got in telemetry gate
a while back.
We fix the telemetry tempest plugin with
https://github.com/openstack/telemetry-tempest-plugin/commit/11277a8bee2b0ee0688ed32cc0e836872c24ee4b
So I propose the same for heat tempest plugin:
On 6/11/2018 3:23 PM, Jeremy Stanley wrote:
If you recall the "specs" experiment years
ago, a few teams tried mildly different solutions for moving from LP
blueprints with random wiki page links to tracking specifications in
Git repositories, and over time they learned successful patterns
from
On Tue, Jun 12, 2018 at 10:33 AM, Mehdi Abaakouk wrote:
>
> Hi,
>
> The tempest plugin error remember me something we got in telemetry gate a
> while back.
>
> We fix the telemetry tempest plugin with https://github.com/openstack/t
>
Doug Hellmann wrote:
>I'm not sure what sort of project-specific documentation we think we need.
Perhaps none if there is a standard, but is there a standard? Can you give me
examples in Storyboard of "standard" views that present information even
vaguely similar to
On 11/06/18 10:23, Doug Hellmann wrote:
Excerpts from Dmitry Tantsur's message of 2018-06-11 16:00:41 +0200:
Hi,
On 06/11/2018 03:53 PM, Ruby Loo wrote:
Hi,
I don't want to hijack the initial thread, but am now feeling somewhat guilty
about not being vocal wrt Storyboard. Yes, ironic
On 6/11/2018 11:17 AM, CARVER, PAUL wrote:
Jumping into the general Storyboard topic, but distinct from the previous
questions about searching, is there any equivalent in Storyboard to the
Launchpad series and milestones diagrams? e.g.:
https://launchpad.net/nova/+series
Excerpts from Jay S Bryant's message of 2018-06-11 11:42:52 -0500:
>
> On 6/11/2018 11:17 AM, CARVER, PAUL wrote:
> > Jumping into the general Storyboard topic, but distinct from the previous
> > questions about searching, is there any equivalent in Storyboard to the
> > Launchpad series and
Hi,
I will be traveling tomorrow so I can’t chair CI meeting on 12.06.2018 so it is
cancelled.
Next meeting will be normally at 19.06.2018.
—
Slawek Kaplonski
Senior software engineer
Red Hat
__
OpenStack Development
Thank you, Ifat!
From: "Afek, Ifat (Nokia - IL/Kfar Sava)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, June 11, 2018 at 2:12 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [vitrage]
Thank you for the explanation!
Eric
From: "Afek, Ifat (Nokia - IL/Kfar Sava)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, June 11, 2018 at 1:34 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev]
Hi,
There were total of 15 new bugs reported I categorized below depending on if
they are related to CI or neutron-client or RFE. Only one
Was critical bug 1775183 for which fixed is released. There's one high priority
bug 1775220 confirmed. Some bugs were marked invalid
and incomplete and
On 08/06/18 22:28, Rico Lin wrote:
Zane Bitter mailto:zbit...@redhat.com>> 於 2018年6
月9日 週六 上午9:20寫道：
>
> IIUC you're talking about a Heat resource that calls out to a service
> broker using the Open Service Broker API? (Basically acting like the
> Kubernetes Service Catalog.) That would
On 2018-06-11 17:17:23 + (+), CARVER, PAUL wrote:
[...]
> Perhaps none if there is a standard, but is there a standard? Can
> you give me examples in Storyboard of "standard" views that
> present information even vaguely similar to
> https://launchpad.net/nova/+series and
>
Greetings,
I wanted to let everyone know that we have a keystone only deployment and
upgrade job in check non-voting. I'm asking everyone in TripleO to be
mindful of this job and to help make sure it continues to pass as we move
it from non-voting check to check and eventually gating.
Upgrade
Others likely have more detailed answers to some of your other
points, but as for the ones I happen to know off the top of my
head...
On 2018-06-11 12:39:36 -0400 (-0400), Zane Bitter wrote:
[...]
> * There's no help link anywhere. (This appears to be because there's nothing
> to link to.)
It's
Hi everybody,
This is just a brief status about the blueprints currently occupying
review runways [0] and an ask for the nova-core team to give these
reviews priority for their code review focus.
* Certificate Validation -
https://blueprints.launchpad.net/nova/+spec/nova-validate-certificates
On 6/11/2018 1:57 PM, Jeremy Stanley wrote:
So... of the_minority_ of projects (from that arbitrarily-chosen
but presumably "important" sample) who are actually using that
feature, how many of them are simply doing it because they thought
the release team was still making use of that
On 6/11/2018 11:54 AM, Doug Hellmann wrote:
Excerpts from Jay S Bryant's message of 2018-06-11 11:42:52 -0500:
On 6/11/2018 11:17 AM, CARVER, PAUL wrote:
Jumping into the general Storyboard topic, but distinct from the previous
questions about searching, is there any equivalent in
Excerpts from CARVER, PAUL's message of 2018-06-11 19:53:47 +:
> Jeremy Stanley wrote:
>
> >I'm just going to come out and call bullshit on this one. How many of the
> >>800 official OpenStack deliverable repos have a view like that with any
> >actual relevant detail? If it's "standard"
On 2018-06-11 15:09:55 -0500 (-0500), Jay S Bryant wrote:
[...]
> Fair enough. It would help if we had buy-in from all of the
> projects but you are right that nothing prevents us from achieving
> consensus from those are are willing to participate.
[...]
Yes, we started out thinking that was
Answering here questions related to mixmatch, as I'm the main developer.
- If I understood [[1](https://mixmatch.readthedocs.io/en/latest/)] correctly
mixmatch can help Nova to attach a remote volume, but it will not help in
synchronizing the images. is this true?
Correct, it will not
Updated subject to include [aodh] and [telemetry]
On Tue, Jun 5, 2018 at 11:41 AM, Doug Hellmann wrote:
> Excerpts from Ken Giusti's message of 2018-06-05 10:47:17 -0400:
>> Hi,
>>
>> The telemetry integration test for oslo.messaging has started failing
>> on the stable/queens branch [0].
>>
>>
Jeremy Stanley wrote:
>I'm just going to come out and call bullshit on this one. How many of the >800
>official OpenStack deliverable repos have a view like that with any actual
>relevant detail? If it's "standard" then certainly more than half, right?
Well, that's a bit rude, so I'm not
On 2018-06-11 19:53:47 + (+), CARVER, PAUL wrote:
[...]
> Well, that's a bit rude
[...]
Apologies for the strong language; I did not intend any offense, and
it was indeed unnecessary for purposes of my point.
> So, are you saying the information shown in the examples I gave is
> not
On Tue, Jun 5, 2018 at 9:08 AM, Doug Hellmann wrote:
[snip]
> When all of this is done, a viable project with real users will be
> open source instead of closed source. Those contributors, and users,
> will be a part of our community instead of looking in from the
> outside. The path is ugly,
59 matches
Mail list logo
