On Mon, 2014-09-15 at 11:04 -0700, Jim Rollenhagen wrote:
On Mon, Sep 15, 2014 at 12:44:24PM +0100, Steven Hardy wrote:
All,
Starting this thread as a follow-up to a strongly negative reaction by the
Ironic PTL to my patches[1] adding initial Heat-Ironic integration, and
subsequent
On Tue, 2014-09-16 at 15:42 -0400, Zane Bitter wrote:
On 16/09/14 15:24, Devananda van der Veen wrote:
On Tue, Sep 16, 2014 at 11:44 AM, Zane Bitter zbit...@redhat.com wrote:
On 16/09/14 13:56, Devananda van der Veen wrote:
On Mon, Sep 15, 2014 at 9:00 AM, Steven Hardy sha...@redhat.com
On Wed, 2014-09-17 at 10:36 +0100, Steven Hardy wrote:
On Tue, Sep 16, 2014 at 02:06:59PM -0700, Devananda van der Veen wrote:
On Tue, Sep 16, 2014 at 12:42 PM, Zane Bitter zbit...@redhat.com wrote:
On 16/09/14 15:24, Devananda van der Veen wrote:
On Tue, Sep 16, 2014 at 11:44 AM, Zane
Hi. This seems to be related:
https://bugs.launchpad.net/openstack-ci/+bug/1274135
We also encountered this.
On Tue, 2014-02-11 at 14:56 +0530, Swapnil Kulkarni wrote:
Hello,
I created a new devstack environment today and installed tox 1.7.0,
and getting error tox.ConfigError: ConfigError:
to be updated
manually.
- Do not implement editing, only creating and deleting (that's what I
did for now in https://review.openstack.org/#/c/73576/ ).
Any ideas on what to do?
Thanks in advance,
Dmitry Tantsur
___
OpenStack-dev mailing list
OpenStack
I think we still are going to multiple flavors for I, e.g.:
https://review.openstack.org/#/c/74762/
On Thu, 2014-02-20 at 08:50 -0500, Jay Dobies wrote:
On 02/20/2014 06:40 AM, Dmitry Tantsur wrote:
Hi.
While implementing CRUD operations for node profiles in Tuskar (which
+1, much awaited!
On Fri, 2014-07-11 at 15:50 -0700, Devananda van der Veen wrote:
Hi all!
It's time to grow the team :)
Jim (jroll) started working with Ironic at the last mid-cycle, when
teeth became ironic-python-agent. In the time since then, he's
jumped into Ironic to help
+1
On Fri, 2014-07-11 at 15:50 -0700, Devananda van der Veen wrote:
Hi all!
While David (Shrews) only began working on Ironic in earnest four
months ago, he has been working on some of the tougher problems with
our Tempest coverage and the Nova-Ironic interactions. He's also
become
Hi!
On Thu, 2014-07-31 at 10:45 +0100, Chris Dent wrote:
One of the things I like to be able to do when in the middle of making
changes is sometimes run all the tests to make sure I haven't accidentally
caused some unexpected damage in the neighborhood. If I have I don't
want the tests to all
Hi!
This list is not for usage question, it's for OpenStack developers. The
best way to get a quick help should be using
https://ask.openstack.org/en/questions/ or joining #openstack on
Freenode and asking there.
Good luck!
On Thu, 2014-07-31 at 15:59 +0530, shailendra acharya wrote:
hello
Hi!
Didn't read the spec thoroughly, but I'm concerned by it's huge scope.
It's actually several specs squashed into one (not too detailed). My
vote is splitting it into a chain of specs (at least 3: power driver,
discovery, other configurations) and seek exception separately.
Actually, I'm +1 on
Hi!
On Tue, 2014-08-05 at 12:33 -0700, Devananda van der Veen wrote:
Hi all!
The following idea came out of last week's midcycle for how to improve
our spec process and tracking on launchpad. I think most of us liked
it, but of course, not everyone was there, so I'll attempt to write
out
On Thu, 2014-05-22 at 09:48 +0100, Lucas Alvares Gomes wrote:
On Thu, May 22, 2014 at 1:03 AM, Devananda van der Veen
devananda@gmail.com wrote:
I'd like to bring up the topic of drivers which, for one reason or another,
are probably never going to have third party CI testing.
Take
Great news! Even being non-voting, it already helped me 2-3 times to
spot a subtle error in a patch.
On Fri, 2014-05-23 at 18:56 -0700, Devananda van der Veen wrote:
Just a quick heads up to everyone -- the tempest-dsvm-virtual-ironic
job is now fully voting in both check and gate queues for
Hi Ironic folks, hi Devananda!
I'd like to share with you my thoughts on asynchronous API, which is
spec https://review.openstack.org/#/c/94923
First I was planned this as comments to the review, but it proved to be
much larger, so I post it for discussion on ML.
Here is list of different
Hi folks,
Inspired by great work by Sean Dague [1], I have created a review
dashboard for Ironic projects. Main ideas:
Ordering:
0. Viewer's own patches, that have any kind of negative feedback
1. Specs
2. Changes w/o negative feedback, with +2 already
3. Changes that did not have any feedback
Hi everyone!
It's hard to stop polishing things, and today I got an updated review
dashboard. It's sources are merged to Sean Dague's repository [1], so I
expect this to be the final version. Thank you everyone for numerous
comments and suggestions, especially Ruby Loo.
Here is nice link to it:
Hi!
Workflow is not entirely documented by now AFAIK. After PXE boots deploy
kernel and ramdisk, it exposes hard drive via iSCSI and notifies Ironic.
After that Ironic partitions the disk, copies an image and reboots node
with final kernel and ramdisk.
On Wed, 2014-06-04 at 19:20 +0800, 严超
+r as stated in Glance metadata for an image - they will be
used for booting after deployment.
Best Regards！
Chao Yan
--
My twitter：Andy Yan @yanchao727
My Weibo：http://weibo.com/herewearenow
--
2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com
.
The first set is defined in the ironic node definition.
How do we define the second set correctly ?
Best Regards！
Chao Yan
--
My twitter：Andy Yan @yanchao727
My Weibo：http://weibo.com/herewearenow
--
2014-06-04 21:00 GMT+08:00 Dmitry Tantsur dtant...@redhat.com
@yanchao727
My Weibo：http://weibo.com/herewearenow
--
2014-06-04 21:27 GMT+08:00 Dmitry Tantsur dtant...@redhat.com:
On Wed, 2014-06-04 at 21:18 +0800, 严超 wrote:
Thank you !
I noticed the two sets of k+r in tftp configuration of
ironic
On 09/25/2014 06:23 PM, Lucas Alvares Gomes wrote:
Hi,
Today we have hit the problem of having an outdated sample
configuration file again[1]. The problem of the sample generation is
that it picks up configuration from other projects/libs
(keystoneclient in that case) and this break the Ironic
On 09/30/2014 02:03 PM, Soren Hansen wrote:
2014-09-12 1:05 GMT+02:00 Jay Pipes jaypi...@gmail.com:
If Nova was to take Soren's advice and implement its data-access layer
on top of Cassandra or Riak, we would just end up re-inventing SQL
Joins in Python-land.
I may very well be wrong(!), but
On 10/02/2014 01:30 PM, Lucas Alvares Gomes wrote:
Hi,
I don't know if it's a known issue, but we have this patch in Ironic
here https://review.openstack.org/#/c/124610/ and the gate jobs for
python26 and python27 are failing because of some import error[1] and
it doesn't show me what is the
Hi Jim,
On 10/16/2014 07:23 PM, Jim Mankovich wrote:
All,
I would like to get some feedback on a proposal to change to the
current sensor naming implemented in ironic and ceilometer.
I would like to provide vendor specific sensors within the current
structure for IPMI sensors in ironic and
On 10/21/2014 02:11 AM, Devananda van der Veen wrote:
Hi all,
I was reminded in the Ironic meeting today that the words hardware
discovery are overloaded and used in different ways by different
people. Since this is something we are going to talk about at the
summit (again), I'd like to start
On 11/12/2014 10:47 PM, Victor Lowther wrote:
Hmmm... with this thread in mind, anyone think that changing DISCOVERING
to INTROSPECTING in the new state machine spec is a good idea?
As before I'm uncertain. Discovery is a troublesome term, but too many
people use and recognize it, while IMO
On 11/12/2014 08:06 PM, Doug Hellmann wrote:
During our “Graduation Schedule” summit session we worked through the list of
modules remaining the in the incubator. Our notes are in the etherpad [1], but as
part of the Write it Down” theme for Oslo this cycle I am also posting a
summary of the
: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: Thursday, November 13, 2014 2:20 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Ironic] disambiguating the term discovery
On 11/12/2014 10:47 PM, Victor Lowther wrote:
Hmmm... with this thread in mind, anyone think
On 11/13/2014 01:15 PM, Lucas Alvares Gomes wrote:
This was discussed in the Contributor Meetup on Friday at the Summit
but I think it's important to share on the mail list too so we can get
more opnions/suggestions/comments about it.
In the Ironic weekly meeting we dedicate a good time of the
On 11/18/2014 02:00 AM, Devananda van der Veen wrote:
Hi all,
As discussed in Paris and at today's IRC meeting [1] we are going to be
alternating the time of the weekly IRC meetings to accommodate our
contributors in EMEA better. No time will be perfect for everyone, but
as it stands, we rarely
On 11/18/2014 06:13 PM, Chris K wrote:
Hi all,
In an effort to keep the Ironic specs review queue as up to date as
possible, I have identified several specs that were proposed in the Juno
cycle and have not been updated to reflect the changes to the current
Kilo cycle.
I would like to set a
On 11/20/2014 04:38 PM, Ruby Loo wrote:
Hi, we had an interesting discussion on IRC about whether or not we
should be maintaining backwards compatibility within a release cycle. In
this particular case, we introduced a new decorator in this kilo cycle,
and were discussing the renaming of it, and
Hi all!
As our state machine and discovery discussion proceeds, I'd like to ask
your opinion on whether we need an IntrospectionInterface
(DiscoveryInterface?). Current proposal [1] suggests adding a method for
initiating a discovery to the ManagementInterface. IMO it's not 100%
correct, because:
Hi!
On 11/28/2014 11:41 AM, Murray, Paul (HP Cloud) wrote:
Hi All,
Looking at the ironic virt driver code in nova it seems that a Conflict
(409) response from the ironic client results in the driver re-trying
the request. Given the comment below in the ironic code I would imagine
that is not
Hi folks,
Thank you for additional explanation, it does clarify things a bit. I'd
like to note, however, that you talk a lot about how _different_ Fuel
Agent is from what Ironic does now. I'd like actually to know how well
it's going to fit into what Ironic does (in additional to your
On 12/09/2014 03:40 PM, Vladimir Kozhukalov wrote:
Vladimir Kozhukalov
On Tue, Dec 9, 2014 at 3:51 PM, Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com wrote:
Hi folks,
Thank you for additional explanation, it does clarify things a bit.
I'd like to note, however
Hi all!
As you know I actively promote ironic-discoverd project [1] as one of
the means to do hardware inspection for Ironic (see e.g. spec [2]), so I
decided it's worth to give some updates to the community from time to
time. This email is purely informative, you may safely skip it, if
Hi!
A bit earlier than expected due to personal circumstances I'm announcing
first stable release of ironic-discoverd: 1.0.0 [1]. It contains
implementations of 6 blueprints and fixes for 17 bugs. Full release
notes can be found at [2], here is the summary:
* Redesigned API, including
Hi all!
That's pure information email about discoverd, feel free to skip it, if
not interested.
For those interested I'm glad to announce that ironic-discoverd 1.0.0 is
feature complete and is scheduled to release on Feb 5 with Kilo-2
milestone. Master branch is under feature freeze now and
Hi everyone!
On one of our meetings [1] we agreed on keeping *ED states (DELETED,
INSPECTED, CLEANED, etc) as no-ops for now. Since then, however, the
inspection patch [2] got several comments from cores requesting removal
of INSPECTED state. That was done by Nisha.
Today we decided to
On 02/20/2015 06:14 AM, Ganapathy, Sandhya wrote:
Hi All,
I would like to discuss the Chassis Discovery Tool Blueprint -
https://review.openstack.org/#/c/134866/
The blueprint suggests Hardware enrollment and introspection for
properties at the Chassis layer. Suitable for micro-servers that
Zhenzan
-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: Thursday, December 11, 2014 10:35 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Ironic] ironic-discoverd status update
Hi all!
As you know I actively promote
On 01/09/2015 08:12 PM, Stefano Maffulli wrote:
Dear all,
if you've tried the topics on this mailing list and haven't received
emails, well... we had a problem on our side: the topics were not setup
correctly.
Luigi Toscano helped isolate the problem and point at the solution[1].
He noticed
new to automate the enrollment of
new nodes:-)
Collecting IPMI info into a csv file is still a trivial job...
BR
Zhou Zhenzan
-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com
mailto:dtant...@redhat.com]
Sent: Thursday, January 8, 2015 5:19
. Please see https://review.openstack.org/#/c/135605/ for
details on future interaction between discoverd and Ironic.
Just a thought, thanks.
BR
Zhou Zhenzan
-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: Monday, January 5, 2015 4:49 PM
To: openstack-dev
On 01/09/2015 02:37 PM, Ihar Hrachyshka wrote:
On 01/09/2015 02:33 PM, Andreas Jaeger wrote:
On 01/09/2015 02:25 PM, Ihar Hrachyshka wrote:
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our
) will be a
driver for discoverd.
No idea what the progress is with regard to implementation within the
Kilo cycle though.
For now we hope to get it merged in K.
cheers
Matt
Just a thought.
-Om
-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: 07
understand from the below mentioned spec is that the Node is registered,
but the spec will help ironic discover other properties of the node.
that's what discoverd does currently.
-Om
-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: 07 January 2015 20:20
This is an informational email about upcoming ironic-discoverd-1.1.0
[1]. If you're not interested in discoverd, you may safely skip it.
Hi all!
Do you know what time is coming? Release time! I'm hoping to align this
ironic-discoverd release with the OpenStack one. Here's proposed plan,
On 03/12/2015 05:05 PM, Devananda van der Veen wrote:
Without further ado, and since everyone (even though some haven't
replied here) has +1'd this, and since we could really use ramesh's +2's
in the run up to Kilo-3 and feature freeze, even without the customary
waiting/voting period being
On 02/28/2015 07:28 AM, Ramakrishnan G wrote:
Hello All,
Hi!
This is about adding vendor drivers in Ironic.
In Kilo, we have many vendor drivers getting added in Ironic which is a
very good thing. But something I noticed is that, most of these reviews
have lots of hardware-specific code
2015-02-27 17:27 GMT+01:00 Dolph Mathews dolph.math...@gmail.com:
On Fri, Feb 27, 2015 at 8:39 AM, Dmitry Tantsur dtant...@redhat.com
wrote:
Hi all!
This (presumably) pretty basic question tortures me for several months
already, so I kindly seek for help here.
I'm working on a Flask
Hi all!
This (presumably) pretty basic question tortures me for several months
already, so I kindly seek for help here.
I'm working on a Flask-based service [1] and I'd like to use Keystone
tokens for authentication. This is an admin-only API, so we need to
check for an admin role. We ended
Hi all!
I've made a bug fix release for ironic-discoverd today, and it's
available on PyPI! Two issues fixed:
* Authentication was too strict, and it wasn't possible to talk to the
API using Ironic service user. Unfortunately fixing it lead to a new
dependency on keystonemiddleware and new
On 02/25/2015 05:26 PM, Ruby Loo wrote:
Hi,
I was wondering what people thought about patches that only fix
grammatical issues or misspellings in comments in our code.
I can't believe I'm sending out this email, but as a group, I'd like it
if we had a similar understanding so that we treat
Hi all!
Today I got an internal email, stating that new ironicclient brakes
ironic-discoverd. Indeed, after rebase to the latest ironicclient git
master, discoverd started receiving AVAILABLE state instead of None
for newly enrolled nodes. It's not a valid state for introspection,
valid are
Hi folks.
Recently I got several requests to implement API aborting introspection
in discoverd. This is useful mostly when debugging, when you know that
introspection has failed, and you want to stop it right now. I've put a
blueprint
Hi folks!
A bit earlier than expected to to my PTO I'm announcing ironic-discoverd
1.1.0. Download it from PyPI: https://pypi.python.org/pypi/ironic-discoverd
We've spent substantial amount of time polishing existing features and
fixing bugs. Highlights are:
* New config options for tuning
Hi all!
This time I'm trying to roughly follow OpenStack release procedures, so
ironic-discoverd just got a stable/1.1 branch, which is equivalent to
RC. I'm proud to say that the upcoming 1.1.0 release (which is scheduled
on Apr 30, just like other projects) is mostly about polishing
factored into a reusable thing (eg, ironic/utils or
ironic/driver/utils or such) then it should be.
Cheers,
-Deva
On Tue, Apr 14, 2015 at 1:40 PM, Dmitry Tantsur divius.ins...@gmail.com wrote:
Hi,
actually 2 possibilities here:
1. discoverd itself handles TFTP
2. DiscoverdInspect hanldes TFTP
I
(assuming such integration was desired by the cloud operator)?
-Deva
On Fri, Apr 10, 2015 at 12:31 AM, Dmitry Tantsur dtant...@redhat.com
wrote:
On 04/10/2015 01:43 AM, Jaromir Coufal wrote:
Hey Dmitry,
o/
I wanted to ask you about ironic-discoverd.
At the moment, after build
if version 1.1. So the only way to
avoid it is to default to 1.0, which will make it harder and less
intuitive to access new features.
On Fri, Apr 3, 2015 at 1:59 PM, Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com wrote:
Hi all!
Today I got an internal email
is the must IMO. While client
is in 0.x range and we're free to break it occasionally, people still
don't expect us to :) I think we also need to put information about the
header and how it affects people in ironicclient docs introduction.
-Deva
On Fri, Apr 3, 2015 at 1:31 AM Dmitry Tantsur
Hi again, hope you're not tired of this topic :D
I'm seeking for advice on what to do with microversions in discoverd.
Basically I have the following options:
1. Do nothing. Get whatever behavior I can get from installed Ironic and
Ironic client. Though unlikely, may get broken by future
versions or new features. That's what bothered me
a bit with the whole microversioning as we implemented it.
Anyway I think we should have a document laying out stuff like that.
Hope that helps. :)
// jim
On April 7, 2015 at 6:07:57 AM, Dmitry Tantsur (dtant...@redhat.com
mailto:dtant...@redhat.com
On 04/08/2015 12:53 PM, Sean Dague wrote:
On 04/08/2015 03:58 AM, Dmitry Tantsur wrote:
On 04/08/2015 06:23 AM, Ken'ichi Ohmichi wrote:
Hi,
Now Nova and Ironic have implemented API microversions in Kilo.
Nova's microversions are v2.1 - v2.3.
Ironic's microversions are v1.1 - v1.6.
Now
On 04/08/2015 06:23 AM, Ken'ichi Ohmichi wrote:
Hi,
Now Nova and Ironic have implemented API microversions in Kilo.
Nova's microversions are v2.1 - v2.3.
Ironic's microversions are v1.1 - v1.6.
Now Tempest is testing the lowest microversion on the gate, and
Ironic's microversions test patch[1]
On 06/04/2015 05:27 PM, Lucas Alvares Gomes wrote:
Hi Ruby,
Thanks for starting this thread, just like you I've been always
confused about when and when not bump the microversioning of the API.
Backwards compatible API adds with no user signaling is a fallacy
because it assumes the arrow of
On 06/04/2015 06:18 PM, Devananda van der Veen wrote:
On Jun 4, 2015 5:53 AM, Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com wrote:
Hi!
While working on the enroll spec [1], I got a thinking: within the
new state machine, when should we allow to change a node driver
do it, if we have something to
release by the time Ironic releases, but I suggest deciding it on
case-by-case basis.
Best Regards,
Yuiko Takada(Inspector team member)
2015-06-08 20:38 GMT+09:00 Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com:
Hello, Inspector team
Hello, Inspector team!
The renaming process is going pretty well, the last thing we need to do
is to get Infra approval and actual rename [1][2].
I'd like to allow people (e.g. myself) to start packaging inspector
under it's new name, so I'd like to make 2.0.0 release as soon as
possible
GMT+09:00 Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com:
On 06/10/2015 09:40 AM, Ken'ichi Ohmichi wrote:
To solve it, we have decided the scope of Tempest as the etherpad
mentioned.
Are there any hints now on where we can start with our integration
tests
?
Best Regards,
Yuiko Takada
2015-06-09 15:59 GMT+09:00 Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com:
On 06/09/2015 03:49 AM, Yuiko Takada wrote:
Hi, Dmitry,
Thank you for notifying.
I've updated our summit etherpad [3] with whatever priorities I
On 06/10/2015 09:40 AM, Ken'ichi Ohmichi wrote:
Hi Dmitry,
2015-06-10 16:11 GMT+09:00 Dmitry Tantsur dtant...@redhat.com:
Hi, QA folks!
As ironic-inspector is joining the openstack/* crows, we're faces with
integration testing question. At the summit we discussed with Devananda that
it makes
On 06/04/2015 05:43 PM, Sean Dague wrote:
On 06/04/2015 11:27 AM, Dmitry Tantsur wrote:
On 06/04/2015 05:03 PM, Sean Dague wrote:
On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work
:
On Jun 4, 2015 8:57 AM, Monty Taylor mord...@inaugust.com wrote:
On 06/04/2015 11:27 AM, Dmitry Tantsur wrote:
On 06/04/2015 05:03 PM, Sean Dague wrote:
On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progress. There is an effort now to add microversion into the
API-WG's guidelines, to provide a consistent way of using microversions
across OpenStack projects [1]. Specifically, in the
On 06/04/2015 05:03 PM, Sean Dague wrote:
On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progress. There is an effort now to add microversion into the
API-WG's guidelines, to provide
On 06/16/2015 08:16 PM, Georgy Okrokvertskhov wrote:
In Murano project we do see a positive impact of BigTent model. Since
Murano was accepted as a part of BigTent community we had a lot of
conversations with potential users. They were driven exactly by the fact
that Murano is now officially
On 06/22/2015 04:19 PM, Devananda van der Veen wrote:
Hi John,
Thanks for the excellent summary! I found it very helpful to get caught
up. I'd like to make sure I understand the direction ahc is going. A
couple questions...
Let me add my $0.5 :)
I see that ahc is storing its information in
from us.
Just one clarifying question: shouldn't b) and c) be compatible-with:
1.4, as 1.4 was a breaking change?
Yes -- (b) and (c) are identical responses.
Discuss.
-Devananda
On Tue, Jun 16, 2015 at 7:13 AM Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com wrote:
On 06
Dmitry Tantsur dtant...@redhat.com
wrote:
On 06/16/2015 03:47 PM, Jim Rollenhagen wrote:
On Tue, Jun 16, 2015 at 08:56:37AM +0200, Dmitry Tantsur wrote:
On 06/04/2015 08:58 AM, Xu, Hejie wrote:
Hi, guys,
I’m working on adding Microversion into the API-WG’s guideline
which
make
26 июня 2015 г. 2:48 пользователь GHANSHYAM MANN ghanshyamm...@gmail.com
написал:
On Thu, Jun 25, 2015 at 5:18 PM, Ken'ichi Ohmichi ken1ohmi...@gmail.com
wrote:
Sorry for late response here,
2015-06-20 9:14 GMT+09:00 Devananda van der Veen
devananda@gmail.com:
Long version...
On 06/25/2015 05:33 PM, Anne Gentle wrote:
On Thu, Jun 25, 2015 at 7:10 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
On 06/25/2015 04:42 AM, Ken'ichi Ohmichi wrote:
2015-06-25 17:25 GMT+09:00 Lucas Alvares Gomes
lucasago...@gmail.com mailto:lucasago...@gmail.com:
On 06/25/2015 06:04 PM, Anne Gentle wrote:
On Thu, Jun 25, 2015 at 10:55 AM, Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com wrote:
On 06/25/2015 05:33 PM, Anne Gentle wrote:
On Thu, Jun 25, 2015 at 7:10 AM, Sean Dague s...@dague.net
mailto:s...@dague.net
On 06/24/2015 09:18 AM, Nanda Devi Sahu wrote:
Hello,
I have downloaded the redfish available code and I want to run the
test_redfish program to understand what happens.
Whenever I set the host name and give the username and password and try
to run the file test_redfish.py I get the below
On 06/25/2015 10:18 AM, Ken'ichi Ohmichi wrote:
Sorry for late response here,
2015-06-20 9:14 GMT+09:00 Devananda van der Veen devananda@gmail.com:
Long version...
Every HTTP response from Ironic today includes three headers: min, max, and
version. The service can present an older API
On 06/25/2015 11:11 AM, Ken'ichi Ohmichi wrote:
2015-06-25 17:31 GMT+09:00 Dmitry Tantsur dtant...@redhat.com:
On 06/25/2015 10:18 AM, Ken'ichi Ohmichi wrote:
Sorry for late response here,
2015-06-20 9:14 GMT+09:00 Devananda van der Veen
devananda@gmail.com:
Long version...
Every HTTP
:08 PM Devananda van der Veen
devananda@gmail.com mailto:devananda@gmail.com wrote:
I'm
On Mon, Jun 22, 2015 at 8:19 AM John Trowbridge tr...@redhat.com
mailto:tr...@redhat.com wrote:
On 06/22/2015 10:40 AM, Dmitry Tantsur wrote:
On 06/22/2015 04:19 PM
On 06/26/2015 01:14 PM, Sean Dague wrote:
On 06/16/2015 09:51 AM, Dmitry Tantsur wrote:
On 06/16/2015 08:56 AM, Dmitry Tantsur wrote:
To sum this long post up, I'm seeing that hiding new features based on
microversions brings much more problems, than it solves (I'm not aware
of the latter
On 06/26/2015 04:08 PM, Sean Dague wrote:
On 06/26/2015 07:43 AM, Dmitry Tantsur wrote:
On 06/26/2015 01:14 PM, Sean Dague wrote:
On 06/16/2015 09:51 AM, Dmitry Tantsur wrote:
On 06/16/2015 08:56 AM, Dmitry Tantsur wrote:
To sum this long post up, I'm seeing that hiding new features based
On 06/26/2015 04:57 PM, Joe Gordon wrote:
On Fri, Jun 26, 2015 at 7:39 AM, Dmitry Tantsur dtant...@redhat.com
mailto:dtant...@redhat.com wrote:
On 06/26/2015 04:08 PM, Sean Dague wrote:
On 06/26/2015 07:43 AM, Dmitry Tantsur wrote:
On 06/26/2015 01:14 PM, Sean Dague
-- unless we
include a version number along with your feature string? And now we're
right back where we started.
Ok, maybe this idea is just as broken. Still, the current proposal
brings more problems than it solves.
-Deva
On Fri, Jun 26, 2015, 07:41 Dmitry Tantsur dtant...@redhat.com
On 06/16/2015 03:47 PM, Jim Rollenhagen wrote:
On Tue, Jun 16, 2015 at 08:56:37AM +0200, Dmitry Tantsur wrote:
On 06/04/2015 08:58 AM, Xu, Hejie wrote:
Hi, guys,
I’m working on adding Microversion into the API-WG’s guideline which
make sure we have consistent Microversion behavior in the API
On 06/16/2015 08:56 AM, Dmitry Tantsur wrote:
On 06/04/2015 08:58 AM, Xu, Hejie wrote:
Hi, guys,
I’m working on adding Microversion into the API-WG’s guideline which
make sure we have consistent Microversion behavior in the API for user.
The Nova and Ironic already have Microversion
16 июня 2015 г. 13:52 пользователь Jay Pipes jaypi...@gmail.com написал:
On 06/16/2015 04:36 AM, Alex Xu wrote:
So if our min_version is 2.1 and the max_version is 2.50. That means
alternative implementations need implement all the 50 versions
api...that sounds pain...
Yes, it's pain, but
On 06/17/2015 06:54 AM, Ken'ichi Ohmichi wrote:
2015-06-17 12:38 GMT+09:00 Yuiko Takada yuikotakada0...@gmail.com:
Then, as you and Matt and Dimitry talked about this on IRC few days ago,
We can add Ironic/Ironic-inspector tests into Tempest still, right?
So that I've started to implement a
On 06/17/2015 03:35 AM, Ken'ichi Ohmichi wrote:
2015-06-16 21:16 GMT+09:00 Jay Pipes jaypi...@gmail.com:
On 06/16/2015 08:00 AM, Dmitry Tantsur wrote:
16 июня 2015 г. 13:52 пользователь Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com написал:
On 06/16/2015 04:36 AM, Alex Xu
On 06/04/2015 08:58 AM, Xu, Hejie wrote:
Hi, guys,
I’m working on adding Microversion into the API-WG’s guideline which
make sure we have consistent Microversion behavior in the API for user.
The Nova and Ironic already have Microversion implementation, and as I
know Magnum
1 - 100 of 629 matches
Mail list logo
