Hello Ifat and Vitrage team.
I would like to explain more about the implementation part of the mail I
sent last time.
The flow is as follows.
Vitrage-dashboard (action-list-panel) -> Vitrage-api -> check component
The last time I mentioned it as api-handler, it would be better to call the
c
On 28.03.2018 19:07, melanie witt wrote:
We were reviewing a bug fix for the vmware driver [0] today and we noticed it
appears that the VMware NSX CI is no longer running, not even on only the
nova/virt/vmwareapi/ tree.
From the third-party CI dashboard, I see some claims of it running but whe
Hi,
Can we consider to add objgraph [1] to OpenStack global requirements? I found
this library extremely useful for investigating memory leaks in Python programs
but unfortunately I can’t push upstream any code using it. It seems to be
pretty mature and supports all needed Python versions.
Or
On Fri, Mar 16, 2018 at 02:29:51PM +, Kwan, Louie wrote:
> In the stable/queens branch, since openstacksdk0.11.3 and
> os-service-types1.1.0 are described in openstack's upper-constraints.txt,
>
> https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L411
> https
On Thu, Mar 15, 2018 at 10:57:58AM +, Jean-Philippe Evrard wrote:
> Looks good to me.
This has been done now. Thanks for being patient :)
Yours Tony.
signature.asc
Description: PGP signature
__
OpenStack Development Ma
After some discussion in IRC on this topic there was an idea just to write and
push upstream needed tools using objgraph w/o having it in the requirements.txt
at all. We just need to make sure that those tools are never used during
production runs and unit tests (CI will help to verify that). If
Hi all,
At Sydney we started the process of change on the stable branches.
Recently we merged a TC resolution[1] to alter the EOL process. The
next step is refinining the stable policy itself.
I've created a review to do that. I think it covers most of the points
from Sydney and Dublin.
Ple
On Thu, 29 Mar 2018 10:44:52 +0300, Radoslav Gerganov wrote:
On 28.03.2018 19:07, melanie witt wrote:
We were reviewing a bug fix for the vmware driver [0] today and we noticed it
appears that the VMware NSX CI is no longer running, not even on only the
nova/virt/vmwareapi/ tree.
From the th
Hi,
Here is an example where the CI has run on a recent patch - yesterday -
https://review.openstack.org/557256
Thanks
Gary
On 3/29/18, 1:04 PM, "melanie witt" wrote:
On Thu, 29 Mar 2018 10:44:52 +0300, Radoslav Gerganov wrote:
> On 28.03.2018 19:07, melanie witt wrote:
>> We were
On Thu, 29 Mar 2018 10:09:09 +, Gary Kotton wrote:
Here is an example where the CI has run on a recent patch - yesterday
-https://review.openstack.org/557256
Thanks. Just curious, how is the CI passing if the driver is currently
broken for detach_volume? I had thought maybe particular tes
Hi Minwook,
Why do you think the request should pass through the Vitrage API? Why can’t
vitrage-dashboard call the check component directly?
And another question: what should happen if the user closes the check window
before the checks are over? I assume that the checks will finish, but the use
Hello Ifat,
Thanks for your reply. : )
I wrote my opinion on your comment.
Why do you think the request should pass through the Vitrage API? Why can’t
vitrage-dashboard call the check component directly?
Authentication issues:
I think the check component is a separate component based on th
Agree with that, whatever the tweak inventory or traits, none of them works.
Same as VGPU, we can support pre-programmed mode for multiple-functions
region, and each region only can support one type function.
There are two reasons why Cyborg has a filter:
* records the usage of functions in a reg
Hi,all
This is the spec [0] about rebuild the volumed backed server.The question
raised in the spec is about how to bandle the root volume.Finally,in Nova
team,we think that the cleanest / best solution to this is to add a volume
action API to cinder for re-imaging the volume.Once that i
> >
> > It's not mentioned here, but I discovered today that Cinder is using the
> > sphinx.ext.autodoc module. Is there any issue with using this?
> >
>
> Nope - sphinx-apidoc and the likes use autodoc under the hood. You can
> see this by checking the output in 'contributor/api' or the likes.
melanie witt wrote on 03/29/2018 06:03:26 AM:
> I would like to see the VMware CI running again and it need only run on
> changes under the nova/virt/vmwareapi/ tree, to save on your resources.
> And on our side, I'd like us to add VMware subteam members to VMware
> driver patch reviews (I belie
On Wed, Mar 28, 2018 at 07:37:19PM -0400, Doug Hellmann wrote:
> Excerpts from corvus's message of 2018-03-28 13:21:38 -0700:
> > Hi,
> >
> > I've proposed a change to devstack which slightly alters the
> > LIBS_FROM_GIT behavior. This shouldn't be a significant change for
> > those using legacy
Excerpts from Renat Akhmerov's message of 2018-03-29 15:33:58 +0700:
> After some discussion in IRC on this topic there was an idea just to write
> and push upstream needed tools using objgraph w/o having it in the
> requirements.txt at all. We just need to make sure that those tools are never
>
Sundar-
To be clear, *all* of the solutions will have race conditions. There's
no getting around the fact that we need to account for situations where
an allocation is made, but then can't be satisfied by cyborg (or
neutron, or nova, or cinder, or whoever). That failure has to bubble up
On 3/29/2018 5:19 AM, melanie witt wrote:
Thanks. Just curious, how is the CI passing if the driver is currently
broken for detach_volume? I had thought maybe particular tests were
skipped in response to my original email that linked the bug fix patch,
but it looks like that run was from before
On 3/29/2018 7:53 AM, William M Edmonds wrote:
running only on virt/vmwareapi changes would not catch problems caused
by changes elsewhere, such as compute/manager.py or virt/driver.py
Right, I think virt driver 3rd party CI should run on at least some
select sub-trees, the major ones that com
On Thu, 2018-03-29 at 07:47 -0500, Sean McGinnis wrote:
> > >
> > > It's not mentioned here, but I discovered today that Cinder is using the
> > > sphinx.ext.autodoc module. Is there any issue with using this?
> > >
> >
> > Nope - sphinx-apidoc and the likes use autodoc under the hood. You can
>
> This is the spec [0] about rebuild the volumed backed server.
> The question raised in the spec is about how to bandle the root volume.
> Finally,in Nova team,we think that the cleanest / best solution to this is to
> add a volume action API to cinder for re-imaging the volume.Once that is
On 3/29/2018 2:44 AM, Radoslav Gerganov wrote:
While running the VMware CI continues to be a challenge, I must say this
patch fixes a regression introduced by Matt Riedemann's patch:
https://review.openstack.org/#/c/549411/
for which the VMware CI clearly indicated there was a problem and
nev
Sean McGinnis writes:
> On Wed, Mar 28, 2018 at 07:37:19PM -0400, Doug Hellmann wrote:
>> Excerpts from corvus's message of 2018-03-28 13:21:38 -0700:
>> > Hi,
>> >
>> > I've proposed a change to devstack which slightly alters the
>> > LIBS_FROM_GIT behavior. This shouldn't be a significant cha
I am happy to announce that I have finally acquired two machines to be
used towards our external CI infrastructure. (Thanks very much to
Cisco for their generosity!)
Now that we have accomplished the hard part, getting a hardware
donation, we can finally move on to the next step of actually
deploy
Cool! This is the really good news! I am ready to help
On Mar 29, 2018, 7:16 PM +0400, Jeremy Freudberg ,
wrote:
> I am happy to announce that I have finally acquired two machines to be
> used towards our external CI infrastructure. (Thanks very much to
> Cisco for their generosity!)
>
> Now that
>
> tl;dr: You don't _have_ to automate this stuff, but it helps.
>
> sphinx-apidoc generates stub files containing a whole load of autodoc
> directives. As noted above, you can check the output of a sphinx-apidoc
> run and you'll see just this. If I were to guess, Cinder simply checked
> in the
>
> Neither local nor third-party CI use should be affected. There's no
> change in behavior based on current usage patterns. Only the caveat
> that if you introduce an error into LIBS_FROM_GIT (e.g., a misspelled or
> non-existent package name), it will not automatically be caught.
>
> -Jim
P
Welcome to our regular release countdown email.
Development Focus
-
Team focus should be on spec approval and implementation for priority features.
General Information
---
We would love to have all the liaisons attend the release team meeting every
Friday[1].
[1
Hi everyone,
During the recent PTG in Dublin, it was decided that we'd prototype a way
forward with Ansible tasks in TripleO that adhere to Ansible best
practises, creating dedicated roles with unique git repositories and RPM
packaging per role.
With a view to moving in this direction, a couple o
We discussed this on IRC [1], hangout, and etherpad [2]. Here is the
summary, which we mostly seem to agree on:
There are two different classes of device we're talking about
modeling/managing. (We don't know the real nomenclature, so forgive
errors in that regard.)
==> Fully dynamic: You can pr
On 03/28/2018 07:03 PM, Nadathur, Sundar wrote:
Thanks, Eric. Looks like there are no good solutions even as candidates,
but only options with varying levels of unacceptability. It is funny
that that the option that is considered the least unacceptable is to let
the problem happen and then fail
On 3/29/2018 9:28 AM, Sean McGinnis wrote:
I do not think changing the revert to snapshot implementation is appropriate
here. There may be some cases where this can get the desired result, but there
is no guarantee that there is a snapshot on the volume's base image state to
revert to. It also wo
On 3/29/2018 3:36 AM, Tony Breeds wrote:
Hi all,
At Sydney we started the process of change on the stable branches.
Recently we merged a TC resolution[1] to alter the EOL process. The
next step is refinining the stable policy itself.
I've created a review to do that. I think it covers mos
Hi,
So as a current Kolla-Kubernetes Core - I have a slightly different opinion
than most, I'll try to verbalize it coherently.
Lets talk about what Kolla is:
Kolla is a project that builds OpenStack docker images, stores them on
dockerhub, and provides tools to build your own images from your o
Nice!
I don't have a strong opinion
about this but what I might recommend would be to chat with the
openshift-ansible [1] and the kolla-ansible [2] folks.
I'm happy to do the introductions if necessary !
Their models, requirements or context might be different than ours but at
the end of
Greetings OpenStack community,
Chaotic but fun API-SIG meeting today. elmiko has done some review of the
long-in-progress microversion history doc [7] and reports that it is worth
finishing and publishing as a historical document explaining why microversions
exist. Having greater context on t
> That means that for the (re)-programming scenarios you need to
> dynamically adjust the inventory of a particular FPGA resource provider.
Oh, see, this is something I had *thought* was a non-starter. This
makes the "single program" case way easier to deal with, and allows it
to be handled on th
> ==> Fully dynamic: You can program one region with one function, and
> then still program a different region with a different function, etc.
Note that this is also the case if you don't have virtualized multi-slot
devices. Like, if you had one that only has one region. Consuming it
consumes the
On Mar 29, 2018, at 12:57 PM, Eric Fried wrote:
>
>> That means that for the (re)-programming scenarios you need to
>> dynamically adjust the inventory of a particular FPGA resource provider.
>
> Oh, see, this is something I had *thought* was a non-starter.
I need to work on my communication s
On 29/03/18 18:26, Richard Wellum wrote:
> Hi,
>
> So as a current Kolla-Kubernetes Core - I have a slightly different
> opinion than most, I'll try to verbalize it coherently.
>
> Lets talk about what Kolla is:
>
> Kolla is a project that builds OpenStack docker images, stores them on
> docke
Hi everybody!
As the subject reads, the "S" release of OpenStack is officially "Stein". As
been with previous elections this wasn't the first choice, that was "Solar".
Solar was judged to have legal risk, so as per our name selection process, we
moved to the next name on the list.
Thanks to ever
Greeting folks,
During the last PTG we spent time discussing some ideas around an
All-In-One installer, using 100% of the TripleO bits to deploy a single
node OpenStack very similar with what we have today with the containerized
undercloud and what we also have with other tools like Packstack or
D
One of the topics that came up at during the Ironic sessions at the
Rocky PTG was firmware management.
During this discussion, we quickly reached the consensus that we
lacked the ability to discuss and reach a forward direction without:
* An understanding of capabilities and available vendor mech
Hi,
By default, all jobs currently benefit from the generation of a static
ARA report located in the "ara" directory at the root of the log
directory.
Due to scalability concerns, these reports were only generated when a
job failed and were not available on successful runs.
I'm happy to announce
On Thu, Mar 29, 2018 at 06:14:06PM -0400, David Moreau Simard wrote:
> Hi,
>
> By default, all jobs currently benefit from the generation of a static
> ARA report located in the "ara" directory at the root of the log
> directory.
> Due to scalability concerns, these reports were only generated whe
On Wed, Mar 28, 2018, at 8:13 AM, Jeremy Stanley wrote:
> On 2018-03-28 09:26:49 -0500 (-0500), Sean McGinnis wrote:
> [...]
> > I believe the ARA logs are only captured on failing jobs.
>
> Correct. This was a stop-gap some months ago when we noticed we were
> overrunning our inode capacity on th
On Wed, Mar 28, 2018, at 7:59 AM, Takashi Yamamoto wrote:
> hi,
>
> i'm thinking about publishing the latest release of tap-as-a-service on pypi.
> background: https://review.openstack.org/#/c/555788/
> iirc, the naming (tap-as-a-service vs neutron-taas) was one of concerns
> when we talked about
In hindsight, it would be much fun the R release named Ramm :P
On Fri, Mar 30, 2018 at 3:10 AM, Paul Belanger
wrote:
> Hi everybody!
>
> As the subject reads, the "S" release of OpenStack is officially "Stein".
> As
> been with previous elections this wasn't the first choice, that was
> "Solar".
>
> >
> >Ideally, from my perspective, Nova would take care of the detach/attach
> >portion
> >and Cinder would only need to take care of imaging the volume.
>
> Agree. :) And yeah, I pointed this out in the nova spec for volume-backed
> rebuild also. I think nova can basically handle this like
Dear All,
Thanks Rich for putting thoughts on continuation with kolla-k8s.
On Fri, Mar 30, 2018 at 2:26 AM, Richard Wellum wrote:
>
> Hi,
>
> So as a current Kolla-Kubernetes Core - I have a slightly different opinion
> than most, I'll try to verbalize it coherently.
>
> Lets talk about what K
cool. kolla will try to implement it.
On Fri, Mar 30, 2018 at 7:12 AM, Paul Belanger
wrote:
> On Thu, Mar 29, 2018 at 06:14:06PM -0400, David Moreau Simard wrote:
> > Hi,
> >
> > By default, all jobs currently benefit from the generation of a static
> > ARA report located in the "ara" directory
Hi Gema,
On Thu, Mar 29, 2018 at 2:48 PM Gema Gomez wrote:
>
>
> On 29/03/18 18:26, Richard Wellum wrote:
> > Hi,
> >
> > So as a current Kolla-Kubernetes Core - I have a slightly different
> > opinion than most, I'll try to verbalize it coherently.
> >
> > Lets talk about what Kolla is:
> >
> >
On Thu, Mar 29, 2018 at 8:14 PM Surya Singh
wrote:
> Dear All,
>
> Thanks Rich for putting thoughts on continuation with kolla-k8s.
>
>
> On Fri, Mar 30, 2018 at 2:26 AM, Richard Wellum
> wrote:
> >
> > Hi,
> >
> > So as a current Kolla-Kubernetes Core - I have a slightly different
> opinion tha
On 3/29/2018 6:50 PM, Sean McGinnis wrote:
May we can add a "Reimaging" state to the volume? Then Nova could poll for it
to go from that back to Available?
That would be fine with me, and maybe similar to how 'extending' and
'retyping' work for an attached volume?
Nova wouldn't wait for the
Hi all,
A routing metric is a quantitative value used to evaluate the path cost.
But neutron can't specify a different metric with the same destination address,
which is useful to realize FRR(Fast Reroute) in Telecoms and NFV scenario.
So we are going to introduce a new metric value for the route
There is spec proposal to fix a bug of createBackup API with microversion. (
https://review.openstack.org/#/c/511825/)
When rotation parameter is '0', the createBackup API just do a snapshot,
and then delete all the snapshots. That is meaningless behavier.
But there is thing hope to get wider sug
On Fri, Mar 30, 2018 at 11:44 AM, Alex Xu wrote:
> There is spec proposal to fix a bug of createBackup API with microversion.
> (https://review.openstack.org/#/c/511825/)
>
> When rotation parameter is '0', the createBackup API just do a snapshot, and
> then delete all the snapshots. That is meani
59 matches
Mail list logo
