Hello list,
I've been busy investigating how to best introduce HA to Ironic Inspector
and I got referred to TaskFlow.
With Ironic Inspector, besides handling other issues, each Node being
introspected undergoes couple of steps with side-effects.
This can be described using a finite automaton[1].
Please, please, please, let's use that in case we decide to have a next
major release :D
--
milan
2015-12-04 16:38 GMT+01:00 Dmitry Tantsur :
> On 12/04/2015 04:30 PM, Thierry Carrez wrote:
>
>> Julien Danjou wrote:
>>
>>> On Fri, Dec 04 2015, Dmitry Tantsur wrote:
>>>
>>> Specifically, I'm talk
+1 Ruby if my vote counts ;)
I hope Deva and Jay will return one day!
--
milan
čt 27. 4. 2017 v 18:10 odesílatel John Villalovos <
openstack@sodarock.com> napsal:
> Not sure if I get a vote but +1 for Ruby! :)
>
> Sorry to hear about the removals :(
>
> John
>
> On Thu, Apr 27, 2017 at 7:21
út 16. 5. 2017 v 18:03 odesílatel Dmitry Tantsur
napsal:
> On 05/15/2017 09:10 PM, Julia Kreger wrote:
> > All,
> >
> > In our new reality, in order to maximize velocity, I propose that we
> > loosen the review requirements for ironic-ui to allow faster
> > iteration. To this end, I suggest we mo
Best of luck, jroll!
<3
milan
čt 8. 6. 2017 v 14:46 odesílatel Jim Rollenhagen
napsal:
> Hey friends,
>
> I've been mostly missing for the past six weeks while looking for a new
> job, so maybe you've forgotten me already, maybe not. I'm happy to tell you
> I've found one that I think is a grea
Hi,
> 1) create a new API endpoint e.g. 'v1/service' that can report which
conductor is managing given node. Additionally it can also report aliveness
of all Ironic conductors and on which hosts they are running (similar to
nova service-list)
> 2) expose conductor_affinity in node-show (but re
John++
Thanks for looking into this!
--
milan
po 17. 7. 2017 v 17:13 odesílatel John Villalovos <
openstack@sodarock.com> napsal:
> Hi Infra,
>
> We were hoping to get a review of:
> https://review.openstack.org/483059
> Add the ironic-inspector services to features.yaml
> openstack-infra/d
makes sense, +1
Cheers,
milan
út 22. 8. 2017 v 11:38 odesílatel Vladyslav Drok
napsal:
> Hey Dmitry,
>
> On Tue, Aug 22, 2017 at 12:24 PM, Dmitry Tantsur
> wrote:
>
>> Hi all!
>>
>> This email concerns the ironic-staging-drivers project which is outside
>> of the official Ironic governance. Pl
čt 24. 8. 2017 v 12:19 odesílatel Alexandra Settle
napsal:
> Hey Ruby!
>
>
>
> Good point – thanks for bringing it up :)
>
>
>
> I was brought up to think that red was one of those colours that people
> had different (and sometimes really negative) associations with. When I
> look at our latest a
+1 :)
--
milan
út 3. 10. 2017 v 18:02 odesílatel Vladyslav Drok
napsal:
> +1 for Shiv
>
>
> On 3 Oct 2017 11:20 a.m., "Sam Betts (sambetts)"
> wrote:
>
> +1,
>
>
>
> Sam
>
>
>
> On 03/10/2017, 08:21, "tua...@vn.fujitsu.com"
> wrote:
>
>
>
> +1 , Yes, I definitely agree with you.
>
>
>
> Regar
Folks,
as there have been multiple questions about Inspector that I couldn't
answer due to my PTG absence, I've decided to make it up to You and
organise a virtual inspector-focused PTG call (over some BlueJeans or TBD).
The other Inspector Cores gracefully agreed to. I've selected the times all
odesílatel milanisko k napsal:
> Folks,
>
> as there have been multiple questions about Inspector that I couldn't
> answer due to my PTG absence, I've decided to make it up to You and
> organise a virtual inspector-focused PTG call (over some BlueJeans or TBD).
>
> Th
Hi,
without any deeper investigation (yet) I'd like to share this patch status
https://review.openstack.org/#/c/468712/
Seems Zuul voted -1 even though all jobs were green...
Cheers,
milan
2017-10-11 7:31 GMT+02:00 Rikimaru Honjo :
> Hello,
>
> I'm trying to install & configure nodepool for Zuu
pad[2].
Thanks for Your votes and looking forward to see You there!
milan
[1] https://beta.doodle.com/poll/q7m4mnvv3h7k8eae#table
[2] https://etherpad.openstack.org/p/inspector-queens-virtual-ptg
po 9. 10. 2017 v 11:59 odesílatel milanisko k napsal:
> Folks,
>
> I'd like to gently r
Hi Dan!
thanks for the testing! I've got couple of questions...
po 16. 10. 2017 v 20:04 odesílatel Dan Prince napsal:
> On Wed, 2017-10-04 at 15:10 +0200, Dmitry Tantsur wrote:
> > (top-posting, as it is not a direct response to a specific line)
> >
> > This is your friendly reminder that we'r
út 17. 10. 2017 v 13:06 odesílatel Dan Prince napsal:
> On Tue, 2017-10-17 at 10:06 +0000, milanisko k wrote:
> >
> > Does it mean dnsmasq was run from a stand-alone container?
>
> Yes. There are separate containers for the ironic-inspector and
> dnsmasq.
>
> >
út 17. 10. 2017 v 17:14 odesílatel Dan Prince napsal:
> On Tue, 2017-10-17 at 11:46 +0000, milanisko k wrote:
> >
> > How about the shared container? Wouldn't it be better not have to
> > rely on t-h-t especially if we're "scheduling" (and probably
Folks,
=
I've got a dilemma right now about how to proceed with containerising
ironic-inspector:
Fat Container
--
put ironic-inspector and dnsmasq into a single container i.e consider a
container as a complete inspection service shipping unit, use supervisord
inside to fork an
> On 11/1/17 7:04 PM, milanisko k wrote:
> > Folks,
> > =
> >
> > I've got a dilemma right now about how to proceed with containerising
> > ironic-inspector:
> >
> > Fat Container
> > --
> > put ironic-inspector and dns
Folks,
I'd like to share the progress of the HA Inspector effort with you.
TL;DR I'm able to run 2 instances of ironic inspector in an active-active
fashion in a modified devstack deployment.
I've uploaded a Github repo containing my config&steps[1] to take to
reproduce as well as a video[2] of m
Folks,
as announced already on the Ironic upstream meeting, I'm hereby resigning
my core-reviewer duties. I've changed my downstream occupation recently and
I won't be able to keep up anymore.
Thank you all, I really enjoyed collaborating with the wonderful Ironic
community!
Best regards,
milan
čt 4. 1. 2018 v 10:00 odesílatel Dmitry Tantsur
napsal:
> On 01/03/2018 04:24 PM, milanisko k wrote:
> > Folks,
> >
> > as announced already on the Ironic upstream meeting, I'm hereby
> resigning my
> > core-reviewer duties. I've changed my downstream
> 1. we agreed on whether the 'network_interface' was, or was not, an
interface that was similar to the existing power, deploy, ... interfaces so
that it fit into the driver composition work
with the network interface being environment- (binding a node to a
particular Switch type) rather than HW-d
Hi Jay,
I think it might be useful to share the list of those specs in here.
Cheers,
milan
čt 4. 8. 2016 v 21:41 odesílatel Jay Faulkner napsal:
> Hi all,
>
> I'd like to abandon any ironic-specs reviews that haven't had any updates
> in 6 months or more. This works out to about 27 patches. Th
It doesn't have to be a star picture; maybe more of a star theme. Helium as
simple example
https://www.phy.anl.gov/mep/atta/images/he4_he6_he8_figure.jpg or the Alpha
particle
http://www.ionactive.co.uk/glossaryimages/002AlphaParticle_200by200.jpg or
just the Alpha symbol
http://natickhighwebdesign
Thanks guys! :D
--
milan
po 26. 9. 2016 v 14:46 odesílatel Jim Rollenhagen
napsal:
> // jim
>
>
> On Mon, Sep 26, 2016 at 5:24 AM, Dmitry Tantsur
> wrote:
> > Hi folks!
> >
> > As you probably know, Imre has decided to leave us for other challenges,
> so
> > our small core team has become even
Dear Stackers,
I'd like to gather some overview on the $Sub: is there some infrastructure
in place to gather such stats? Are there any groups interested in it? Any
plans to establish such infrastructure?
Thanks!
milan
PS: I used to maintain a tool[1] that once collect multi-node integration
test
Hello Stackers!
The ironic inspector project keeps track of introspection finished_at time
stamps.
We're just discussing how to reasonably query time ranges over the API[1]
to serve matching introspection statuses to the user.
Wikipedia[2] mentions the ISO8601 time interval specification (and ther
100-fold.
I'm curious if the OS projects want to execute similar code measurements on
e.g daily basis w/ selected DSVM jobs to collect stats.
> On Tue, Sep 27, 2016 at 1:06 PM, Jordan Pittier <
> jordan.pitt...@scality.com> wrote:
>
>> Hi,
>>
>> On Tue, Sep 27, 2
, let this be c'
>
> Let diff = c \ c'
>
> 'diff' is where you're missing unit and functional tests coverage.
>
Assaf, the tool I linked is a monkey-patched coverage.py but the collector
stores the stats in Redis --- gives the same accumulative collecting.
I
út 27. 9. 2016 v 18:05 odesílatel Doug Hellmann
napsal:
> Excerpts from milanisko k's message of 2016-09-27 12:30:09 +:
> > Hello Stackers!
> >
> > The ironic inspector project keeps track of introspection finished_at
> time
> > stamps.
> > We're just discussing how to reasonably query time r
Thanks guys! :)
Cheers,
milan
po 3. 10. 2016 v 10:49 odesílatel Dmitry Tantsur
napsal:
> The change is in effect. Thanks for your hard work Milan!
>
> On 09/26/2016 02:55 PM, milanisko k wrote:
> > Thanks guys! :D
> >
> > --
> > milan
> >
> > po 2
util/issues/295
[2]
https://review.openstack.org/#/c/375045/5/specs/list-introspection-statuses.rst@69
čt 29. 9. 2016 v 19:05 odesílatel Julien Danjou napsal:
On Tue, Sep 27 2016, milanisko k wrote:
> I'd like to ask whether other projects need to parse time intervals and/or
> how do th
Dear API WG,
We've got ourselves into a bike shedding situation[1] w/r the WG filtering
suggestion[2]. What we find difficult is to express the ISO8601 time
intervals[3][4] in accordance to the filtering suggestion. We'd like to
have support for specifying multiple time intervals a node introspecti
e referenced in the beginning of this thread used to enable
tracing this way (with some filtering applied).
Cheers,
milan
[1]
https://coverage.readthedocs.io/en/coverage-4.2/subprocess.html#configuring-python-for-sub-process-coverage
> andrea
>
> On Thu, Sep 29, 2016 at 12:12 PM Assaf Mul
Guys,
thanks for the suggestions! I like the coma separation as well, it's the
closest to the ISO style.
Let me propose the update.
Cheers,
milan
čt 6. 10. 2016 v 19:28 odesílatel Jay Pipes napsal:
> On 10/06/2016 11:43 AM, Jeremy Stanley wrote:
> > On 2016-10-06 10:30:30 -0500 (-0500), Kevin
FYI The patch: https://review.openstack.org/#/c/383862/
Cheers,
milan
pá 7. 10. 2016 v 10:13 odesílatel milanisko k napsal:
> Guys,
>
> thanks for the suggestions! I like the coma separation as well, it's the
> closest to the ISO style.
> Let me propose the update.
>
>
lol, I'm definitely carving a special meeting pumpkin :)
Cheers,
milan
st 19. 10. 2016 v 18:01 odesílatel Loo, Ruby napsal:
> Hi,
>
>
>
> Since the Barcelona summit is next week, the Monday (Oct 24) ironic
> meeting is cancelled.
>
>
>
> We'll have a spooky meeting the week after (Oct 31). Feel
Hello API WG!
I'd like to ask about possible ``=in:``[1] operator negation implementation
Should the implementation be a negative field name such as
``?state=in:a,b,c¬_state=in:x,y,z``?
Or rather a negated operator: ``?state=in:a,b,c&state=not_in:x,y,z``?
There already is the ``=neq:`` operator sp
Guys,
thanks for the responses, so far we've got (if I'm not mistaken):
?state=nin: 3 (including me)
?state=not_in: 1
?state=out: 0
?not_state=in: 0
I'd like to finish this poll by EOW so that more folks have the opportunity
to express their preference.
Cheers,
milan
2016-11-15 13:50
Sorry Ed,
was a bank holiday in here yesterday.
Did the API WG conclude on a preferred operator name?
Cheers,
milan
st 16. 11. 2016 v 15:43 odesílatel Ed Leafe napsal:
On Nov 16, 2016, at 7:42 AM, Ian Cordasco wrote:
> If you're including me as a vote for nin, you should also consider me as
a
No prob!
Just needed a hint preferably before we'd merge the new API endpoint spec
for the inspector [1]
Cheers,
milan
[1]
https://review.openstack.org/#/c/375045/10/specs/list-introspection-statuses.rst
pá 18. 11. 2016 v 11:26 odesílatel Chris Dent
napsal:
> On Fri, 18 Nov 2016, mil
42 matches
Mail list logo
