Dear team,
I would like to organize a team meeting on Thursday next week:
- Date: 30 August 2018
- Time: 15:00 UTC
- Channel: #openstack-meeting-4
All existing core members and new contributors are welcome.
Here is the Searchlight's Etherpad for Stein, all ideas are welcomed:
On Fri, Aug 24, 2018 at 8:01 PM Jeremy Stanley wrote:
> On 2018-08-24 18:51:08 -0500 (-0500), Matt Riedemann wrote:
> [...]
> > So just follow me here people, what if we had this common shared
> > library where code could incubate and then we could write some
> > tools to easily copy that common
2018-08-18 20:25 GMT+08:00 Chris Dent :
> On Fri, 17 Aug 2018, Doug Hellmann wrote:
>
> If we ignore the political concerns in the short term, are there
>> other projects actually interested in using placement? With what
>> technical caveats? Perhaps with modifications of some sort to support
>>
On 2018-08-24 18:51:08 -0500 (-0500), Matt Riedemann wrote:
[...]
> So just follow me here people, what if we had this common shared
> library where code could incubate and then we could write some
> tools to easily copy that common code into other projects...
If we do this, can we at least put
On 8/23/2018 2:05 PM, Chris Dent wrote:
On Thu, 23 Aug 2018, Dan Smith wrote:
...and it doesn't work like mock.sentinel does, which is part of the
value. I really think we should put this wherever it needs to be so that
it can continue to be as useful as is is today. Even if that means just
This is just an FYI that I have proposed that we deprecate the
core/ram/disk filters [1]. We should have probably done this back in
Pike when we removed them from the default enabled_filters list and also
deprecated the CachingScheduler, which is the only in-tree scheduler
driver that benefits
On Fri, Aug 24, 2018 at 2:17 AM Juan Badia Payno wrote:
>
> Recently, I did a little test regarding fluentd logging on the gates
> master[1], queens[2], pike [3]. I don't like the status of it, I'm still
> working on them, but basically there are quite a lot of misconfigured logs
> and some
On 7/30/2018 1:55 PM, Jay Pipes wrote:
ack. will review shortly. thanks, Chris.
For those on the edge of their seats at home, we have merged [1] in
Stein and assuming things don't start failing in weird ways after some
period of time, we'll probably backport it. OVH is already running with
On 08/22/2018 07:49 AM, Lance Bragstad wrote:
>
> On 08/22/2018 03:23 AM, Adrian Turjak wrote:
>> Bah! I saw this while on holiday and didn't get a chance to respond,
>> sorry for being late to the conversation.
>>
>> On 11/08/18 3:46 AM, Colleen Murphy wrote:
>>> ### Self-Service Keystone
>>>
On 8/22/2018 4:46 AM, Gorka Eguileor wrote:
The solution is conceptually simple. We add a new API microversion in
Cinder that adds and optional parameter called "generic_keep_source"
(defaults to False) to both migrate and retype operations.
But if the problem is that users are not using the
On 8/21/2018 5:36 AM, Lee Yarwood wrote:
I'm definitely in favor of hiding this from users eventually but
wouldn't this require some form of deprecation cycle?
Warnings within the API documentation would also be useful and even
something we could backport to stable to highlight just how fragile
On 8/20/2018 10:29 AM, Matthew Booth wrote:
Secondly, is there any reason why we shouldn't just document then you
have to delete snapshots before doing a volume migration? Hopefully
some cinder folks or operators can chime in to let me know how to back
them up or somehow make them independent
+operators
On 8/24/2018 4:08 PM, Matt Riedemann wrote:
On 8/23/2018 10:22 AM, Sean McGinnis wrote:
I haven't gone through the workflow, but I thought shelve/unshelve
could detach
the volume on shelving and reattach it on unshelve. In that workflow,
assuming
the networking is in place to
On 8/23/2018 10:22 AM, Sean McGinnis wrote:
I haven't gone through the workflow, but I thought shelve/unshelve could detach
the volume on shelving and reattach it on unshelve. In that workflow, assuming
the networking is in place to provide the connectivity, the nova compute host
would be
On Aug 24, 2018, at 7:36 AM, Chris Dent wrote:
> Over the past few days a few of us have been experimenting with
> extracting placement to its own repo, as has been discussed at
> length on this list, and in some etherpads:
>
>https://etherpad.openstack.org/p/placement-extract-stein
>
On Fri, Aug 24, 2018 at 2:40 PM Emilien Macchi wrote:
> Welcome to the twenty-ninthest edition of a weekly update in TripleO world!
> The goal is to provide a short reading (less than 5 minutes) to
> learnwhat's new this week.
> Any contributions and feedback are welcome.
> Link to the previous
On 8/23/2018 12:07 PM, Gorka Eguileor wrote:
I haven't checked the PTG agenda yet, but is there a meeting on this?
Because we may want to have one to try to understand the requirements
and figure out if there's a way to do it with current Cinder
functionality of if we'd need something new.
I
On 8/22/2018 9:14 PM, Sam Morrison wrote:
I think in our case we’d only migrate between cells if we know the network and
storage is accessible and would never do it if not.
Thinking moving from old to new hardware at a cell level.
If it's done via the resize API at the top, initiated by a
+1 to all the changes.
On Fri, Aug 24, 2018 at 12:12 PM Sam Betts (sambetts)
wrote:
> +1
>
>
>
> Sam
>
>
>
> On 23/08/2018, 21:38, "Mark Goddard" wrote:
>
>
>
> +1
>
>
>
> On Thu, 23 Aug 2018, 20:43 Jim Rollenhagen,
> wrote:
>
> ++
>
>
>
> // jim
>
>
>
> On Thu, Aug 23, 2018 at 2:24 PM, Julia
Hello everyone,
A new release candidate for nova for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/nova/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Welcome to the twenty-ninthest edition of a weekly update in TripleO world!
The goal is to provide a short reading (less than 5 minutes) to learnwhat's
new this week.
Any contributions and feedback are welcome.
Link to the previous version:
>
> After some prompting from gibi, that code has now been adjusted so
> that requirements.txt and tox.ini [1] make sure that the extract
> placement branch is installed into the test virtualenvs. So in the
> gate the unit and functional tests pass. Other jobs do not because
> of [1].
>
> In the
On Fri, 24 Aug 2018, Doug Hellmann wrote:
I guess all of the people who complained so loudly about the global in
oslo.config are gone?
It's a diffent context. In a testing environment where there is
already a well established pattern of use it's not a big deal.
Global in oslo.config is still
So...
Restore the PS of the oslo_utils version that exposed the global [1]?
Or use the forced-singleton pattern from nova [2] to put it in its own
importable module, e.g. oslo_utils.uuidutils.uuidsentinel?
(FTR, "import only modules" is a thing for me too, but I've noticed it
doesn't seem to be
Hello Everyone!
As we approach the Summit (still a ways away thankfully), I thought I would
kick off the Community Contributor Award nominations early this round.
For those of you that already know what they are, here is the form[1].
For those of you that have never heard of the CCA, I'll
On Thu, 2018-08-23 at 10:42 -0400, Dan Prince wrote:
> On Tue, Aug 14, 2018 at 1:53 PM Jill Rouleau wrote:
> >
> >
> > Hey folks,
> >
> > Like Alex mentioned[0] earlier, we've created a bunch of ansible
> > roles
> > for tripleo specific bits. The idea is to start putting some basic
> >
On 08/24/2018 10:15 AM, Colleen Murphy wrote:
> # Keystone Team Update - Week of 20 August 2018
>
> ## News
>
> We ended up releasing an RC2 after all in order to include placeholder
> sqlalchemy migrations for Rocky, thanks wxy for catching it!
>
> ## Open Specs
>
> Search query:
On Fri, 24 Aug 2018, Chris Dent wrote:
That work is in gerrit at
https://review.openstack.org/#/c/596291/
with a hopefully clear commit message about what's going on. As with
the rest of this work, this is not something to merge, rather an
experiment to learn from. The hot spots in the
On Fri, 2018-08-24 at 09:13 -0500, Matt Riedemann wrote:
> On 8/24/2018 8:58 AM, Stephen Finucane wrote:
> > Using this won't add a NUMA topology - it'll just control how any
> > topology present will be mapped to the guest. You need to enable
> > dedicated CPUs or a explicitly request a NUMA
Gilles,
Ok. Added the patches in Gerrit to this coming Tuesday Neutron weekly
meeting agenda. I will highlight the patches during the meeting
Regards
On Thu, Aug 23, 2018 at 7:09 PM, Gilles Dubreuil
wrote:
>
>
> On 24/08/18 04:58, Slawomir Kaplonski wrote:
>
>> Hi Miguel,
>>
>> I’m not sure
On Fri, Aug 24, 2018 at 9:09 AM, Emilien Macchi wrote:
> We just released Rocky RC1 and branched stable/rocky for most of tripleo
> repos, please let us know if we missed something.
> Please don't forget to backport the patches that land in master and that you
> want in Rocky.
>
> We're currently
On 8/23/2018 12:07 PM, Gorka Eguileor wrote:
On 23/08, Dan Smith wrote:
I think Nova should never have to rely on Cinder's hosts/backends
information to do migrations or any other operation.
In this case even if Nova had that info, it wouldn't be the solution.
Cinder would reject migrations
# Keystone Team Update - Week of 20 August 2018
## News
We ended up releasing an RC2 after all in order to include placeholder
sqlalchemy migrations for Rocky, thanks wxy for catching it!
## Open Specs
Search query: https://bit.ly/2Pi6dGj
Lance reproposed the auth receipts and application
Hi again Andy,
Thanks for the update. Sounds like there is some work to do in various
client libraries first.
I also just tried to launch a Sahara cluster against a community
image-- it failed, because our current validation wants the image ID
to actually appear in the image list. So there will
We just released Rocky RC1 and branched stable/rocky for most of tripleo
repos, please let us know if we missed something.
Please don't forget to backport the patches that land in master and that
you want in Rocky.
We're currently investigating if we whether or not we'll need an RC2 so
don't be
Hello everyone,
A new release candidate for tripleo-puppet-elements for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/tripleo-puppet-elements/
Unless release-critical issues are found that warrant a release
candidate
Hello everyone,
A new release candidate for tripleo-image-elements for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/tripleo-image-elements/
Unless release-critical issues are found that warrant a release
candidate respin,
Hello everyone,
A new release candidate for nova_powervm for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/nova-powervm/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will
Hello everyone,
A new release candidate for tripleo-heat-templates for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/tripleo-heat-templates/
Unless release-critical issues are found that warrant a release
candidate respin,
My co-worker has it working on OOO, Pike release bm not containers. There was a
plan to clean up the code and open it up since it’s all ansible-playbooks doing
the work.
Remo
> On Aug 24, 2018, at 07:37, Ben Nemec wrote:
>
>
>
> On 08/24/2018 04:17 AM, Juan Badia Payno wrote:
>>
See below for links to a release job failure for python-jenkins.
This was a ReadTheDocs publishing job. It appears to have failed due to the
necessary steps missing from this earlier post:
http://lists.openstack.org/pipermail/openstack-dev/2018-August/132836.html
- Forwarded message from
On 08/24/2018 04:17 AM, Juan Badia Payno wrote:
Recently, I did a little test regarding fluentd logging on the gates
master[1], queens[2], pike [3]. I don't like the status of it, I'm still
working on them, but basically there are quite a lot of misconfigured
logs and some services that they
On 8/24/2018 8:58 AM, Stephen Finucane wrote:
Using this won't add a NUMA topology - it'll just control how any
topology present will be mapped to the guest. You need to enable
dedicated CPUs or a explicitly request a NUMA topology for this to
work.
openstack flavor set --property
On Fri, 2018-08-24 at 07:55 +, Guo, Ruijing wrote:
> Hi, All,
>
> I am verifying numa aware vwitch features
> (https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/numa-aware-vswitches.html).
> But the result is not my expectation.
>
> What I missing?
>
>
> Nova
Hello all Puppeteers!
Welcome to the weekly Puppet recap for week 34.
This is a weekly overview of what has changed in the Puppet OpenStack
project the past week.
CHANGES
===
We haven't had much changes this week, mostly CI fixes due to changes in
packaging.
* We've merged all
Over the past few days a few of us have been experimenting with
extracting placement to its own repo, as has been discussed at
length on this list, and in some etherpads:
https://etherpad.openstack.org/p/placement-extract-stein
On Wed, Aug 22, 2018 at 4:21 AM Csatari, Gergely (Nokia - HU/Budapest)
wrote:
>
> Hi,
>
> This is good news. We could even have an hour session to discuss ideas about
> TripleO-s place in the edge cloud infrastructure. Would you be open for that?
Yes, that sounds good. I'll add something to the
Hello everyone,
A new release candidate for keystone for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/keystone/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be
Matt Riedemann wrote:
On 8/23/2018 4:00 AM, Thierry Carrez wrote:
In the OpenStack governance model, contributors to a given piece of
code control its destiny.
This is pretty damn fuzzy.
Yes, it's definitely not binary.
So if someone wants to split out nova-compute
into a new
Hi!
The PTG starts in two weeks in Denver! As in Dublin, we'll have some
presentations running during the second half of the lunch break in the
lunch room. Here is the schedule:
Monday: Welcome to the PTG
Welcome new teams / Ops meetup, Housekeeping, Community update, Set
stage for the
Recently, I did a little test regarding fluentd logging on the gates
master[1], queens[2], pike [3]. I don't like the status of it, I'm still
working on them, but basically there are quite a lot of misconfigured logs
and some services that they are not configured at all.
I think we need to put
+1
Sam
On 23/08/2018, 21:38, "Mark Goddard"
mailto:m...@stackhpc.com>> wrote:
+1
On Thu, 23 Aug 2018, 20:43 Jim Rollenhagen,
mailto:j...@jimrollenhagen.com>> wrote:
++
// jim
On Thu, Aug 23, 2018 at 2:24 PM, Julia Kreger
mailto:juliaashleykre...@gmail.com>> wrote:
Greetings everyone!
In
Hi Darshan,
I believe you are referring to the recent Foreshadow / l1tf vulnerability?
If that's the case OpenStack compute workloads are protected with all
relevant to the specific hypervisor type mechanisms.
AFAIK OpenStack at this moment supports KVM-Qemu, Xen, vSphere/ESXI and
Hyper-V
Hi, All,
I am verifying numa aware vwitch features
(https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/numa-aware-vswitches.html).
But the result is not my expectation.
What I missing?
Nova configuration:
[filter_scheduler]
track_instance_changes = False
enabled_filters =
54 matches
Mail list logo
