Hi everyone,
Thanks for the updates and support, that appreciated.
@Gilles, did you already implemented all the service types?
What is left to do? You already want to merge the feature branch with
master?
@tristan I’d like to work on the feature branch but I’ll wait for gilles
answers as I
On 22/06/18 09:21, Tristan Cacqueray wrote:
Hi Flint,
On June 21, 2018 5:32 pm, Flint WALRUS wrote:
Hi everyone, sorry for the late answer but I’m currently trapped into a
cluster issue with cinder-volume that doesn’t give me that much time.
That being said, I’ll have some times to work on
Hello,
I originally posted this to the general openstack list to get a sanity
check on what I was seeing. Jeremy F reached out and confirmed that, so I'm
going to re-post the details here to begin a discussion.
>From what I can see, anti-affinity is not working at all in Sahara. I was
able to
Hi Flint,
On June 21, 2018 5:32 pm, Flint WALRUS wrote:
Hi everyone, sorry for the late answer but I’m currently trapped into a
cluster issue with cinder-volume that doesn’t give me that much time.
That being said, I’ll have some times to work on this feature during the
summer (July/August)
A nice and short one this week...
Development Focus
-
Teams should be focused on implementing planned work for the cycle. It is also
a good time to review those plans and reprioritize anything if needed based on
the what progress has been made and what looks realistic to complete
>
> Apparently heat-translator has a healthy ecosystem of contributors and
> users, but not of maintainers, and it remaining a deliverable of the Heat
> project is doing nothing to alleviate the latter problem. I'd like to find
> it a home that _would_ help.
>
I'd be interested to hear thoughts
On 20/06/18 17:59, Adam Harwell wrote:
Looks like I missed this so I'm late to the party, but:
Ade is technically correct, Octavia doesn't explicitly depend on
Barbican, as we do support castellan generically.
*HOWEVER*: we don't just store and retrieve our own secrets -- we rely
on loading
On 06/21/2018 04:48 PM, Nate Johnston wrote:
> I will continue to debug the issue tomorrow. I see no lonkage at this
> point with any of the previously listed constraints on this scenario.
> So I am going to copy Brian Haley for his L3 expertise, as well as the 3
> FWAaaS cores to see if this
On 20/06/18 18:59, Doug Hellmann wrote:
According to
https://governance.openstack.org/tc/reference/projects/heat.html the
Heat PTL*is* the PTL for heat-translators. Any internal team structure
that implies otherwise is just that, an internal team structure.
Yes, correct.
I'm really unclear
On 21/06/18 07:39, Rabi Mishra wrote:
Looks like that's a bug where we create a domain specific role for
'default' domain[1], when domain is not specified.
[1]
https://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/keystone/role.py#L54
You can _probably_ pass
Hi everyone, sorry for the late answer but I’m currently trapped into a
cluster issue with cinder-volume that doesn’t give me that much time.
That being said, I’ll have some times to work on this feature during the
summer (July/August) and so do some coding once I’ll have catched up with
your
Greetings OpenStack community,
Today's meeting was on the shorter side but covered several topics. We
discussed the migration to StoryBoard, and noted that we need to send
word to Gilles and the GraphQL experimentors that the board is in
place and ready for their usage. The GraphQL work was also
On 06/21/2018 07:04 AM, Artom Lifshitz wrote:
As I understand it, Artom is proposing to have a larger race window,
essentially
from when the scheduler selects a node until the resource audit runs on that
node.
Exactly. When writing the spec I thought we could just call the
On 06/21/2018 07:50 AM, Mooney, Sean K wrote:
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Side question... does either approach touch PCI device management
during live migration?
I ask because the only workloads I've ever seen that pin guest vCPU
threads to
[bringing a side email conversation onto the main mailing list]
I have been looking into the issue with neutron_fwaas having an error
when running under the neutron-l3-agent on Debian when using wsgi.
Here's what I have tracked it down to at this point. I am going to lay
it all out there,
On Thu, Jun 21, 2018 at 09:36:58AM -0400, Jay Pipes wrote:
> On 06/18/2018 10:16 AM, Artom Lifshitz wrote:
> > Hey all,
> >
> > For Rocky I'm trying to get live migration to work properly for
> > instances that have a NUMA topology [1].
> >
> > A question that came up on one of patches [2] is
> Side question... does either approach touch PCI device management during
> live migration?
Nope. I'd need to do some research to see what, if anything, is needed
at the lower levels (kernel, libvirt) to enable this.
> I ask because the only workloads I've ever seen that pin guest vCPU threads
Hello,
As suggested by eyalb on irc I am posting my problem here.
Basically I have 10 nova hosts named in nags as follows:
nova0
nova1
.
.
.
nova10
I’ve made config file for the vitrage to map hosts to real hosts in Openstack
named like:
nova0.domain.com
nova1.domain.com
.
.
.
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Thursday, June 21, 2018 2:37 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] NUMA-aware live migration: easy but
> incomplete vs complete but hard
>
> On 06/18/2018 10:16 AM,
On 20-06-18 13:54:29, Lee Yarwood wrote:
> On 20-06-18 07:32:08, Matt Riedemann wrote:
> > On 6/20/2018 6:54 AM, Lee Yarwood wrote:
> > > We can bump the minimum here but then we have to play a game of working
> > > out the oldest version the above fix was backported to across the
> > > various
On 06/18/2018 10:16 AM, Artom Lifshitz wrote:
Hey all,
For Rocky I'm trying to get live migration to work properly for
instances that have a NUMA topology [1].
A question that came up on one of patches [2] is how to handle
resources claims on the destination, or indeed whether to handle that
>
> As I understand it, Artom is proposing to have a larger race window,
> essentially
> from when the scheduler selects a node until the resource audit runs on
> that node.
>
Exactly. When writing the spec I thought we could just call the resource
tracker to claim the resources when the
On 2018-06-20 16:59:30 -0500 (-0500), Adam Harwell wrote:
> Looks like I missed this so I'm late to the party, but:
>
> Ade is technically correct, Octavia doesn't explicitly depend on Barbican,
> as we do support castellan generically.
>
> *HOWEVER*: we don't just store and retrieve our own
Looks like that's a bug where we create a domain specific role for
'default' domain[1], when domain is not specified.
[1]
https://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/keystone/role.py#L54
You're welcome to raise a bug and propose a fix where we should be just
Hi!
There was a new 'domain' property added to OS::Keystone::Role
(https://storyboard.openstack.org/#!/story/1684558,
https://review.openstack.org/#/c/459033/).
With "openstack role create" CLI command it is still possible to create roles
with no associated domains; but it seems that the same
On Thu, Jun 21, 2018 at 1:41 AM, Juan Antonio Osorio
wrote:
> It is unfortunately a known issue and is present in queens and master as
> well. I think Michele (bandini on IRC) was working on it.
>
See [1], and note that [2] merged to stable/queens just a couple days ago.
[1]
On 19 June 2018 at 10:27, Renat Akhmerov wrote:
> Hi,
>
> I’d like to promote Vitalii Solodilov to the core team of Mistral. In my
> opinion, Vitalii is a very talented engineer who has been demonstrating it
> by providing very high quality code and reviews in the last 6-7 months.
> He’s one of
+1
On 19 June 2018 at 10:47, Dougal Matthews wrote:
>
>
> On 19 June 2018 at 10:27, Renat Akhmerov wrote:
>
>> Hi,
>>
>> I’d like to promote Vitalii Solodilov to the core team of Mistral. In my
>> opinion, Vitalii is a very talented engineer who has been demonstrating it
>> by providing very
On Mon, Jun 18, 2018 at 10:16:05AM -0400, Artom Lifshitz wrote:
> Hey all,
>
> For Rocky I'm trying to get live migration to work properly for
> instances that have a NUMA topology [1].
>
> A question that came up on one of patches [2] is how to handle
> resources claims on the destination, or
HI Muhammad,
Here is the code (run in controller node) that decides whether a service is
up https://github.com/openstack/zun/blob/master/zun/api/servicegroup.py .
There are several possibilities to cause a service to be 'down':
1. The service was being 'force_down' via API (e.g. explicitly
Hi folks,
Time for a new meeting for the Public Cloud WG. Agenda draft can be
found at https://etherpad.openstack.org/p/publiccloud-wg, feel free to
add items to that list.
See you all at IRC 1400 UTC in #openstack-publiccloud
Cheers,
Tobias
--
Tobias Rydberg
Senior Developer
Twitter &
31 matches
Mail list logo
