Hi all,
I proposed https://review.openstack.org/#/c/143193 to ironic-python-agent, in
an attempt to make Hardware Manager loading more sane. As it works today, the
most specific hardware manager is the only one chosen. This means in order to
use a mix of hardware managers, you have to compose
: Wednesday, April 09, 2014 4:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic][Agent]
On Wed, Apr 9, 2014 at 9:01 AM, Stig Telfer
stel...@cray.commailto:stel...@cray.com wrote:
-Original Message-
From: Matt Wagner
[mailto:matt.wag
-Original Message-
From: Matt Wagner [mailto:matt.wag...@redhat.com]
Sent: Tuesday, April 08, 2014 6:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic][Agent]
On 08/04/14 14:04 +0400, Vladimir Kozhukalov wrote:
snip
0
On Wed, Apr 9, 2014 at 9:01 AM, Stig Telfer stel...@cray.com wrote:
-Original Message-
From: Matt Wagner [mailto:matt.wag...@redhat.com]
Sent: Tuesday, April 08, 2014 6:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic
On Tue, Apr 8, 2014 at 3:04 AM, Vladimir Kozhukalov
vkozhuka...@mirantis.com wrote:
Guys, thank you very much for your comments,
I thought a lot about why we need to be so limited in IPA use cases. Now
it much clearer for me. Indeed, having some kind of agent running inside
host OS is not
Guys, thank you very much for your comments,
I thought a lot about why we need to be so limited in IPA use cases. Now it
much clearer for me. Indeed, having some kind of agent running inside host
OS is not what many people want to see. And now I'd rather agree with that.
But there are still some
Guys, thank you very much for your comments,
I thought a lot about why we need to be so limited in IPA use cases. Now it
much clearer for me. Indeed, having some kind of agent running inside host OS
is not what many people want to see. And now I'd rather agree with that.
But there are still
From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com]
Sent: Tuesday, April 08, 2014 9:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic][Agent]
Guys, thank you very much for your comments,
I thought a lot about why we need to be so
On 08/04/14 14:04 +0400, Vladimir Kozhukalov wrote:
snip
0) There are a plenty of old hardware which does not have IPMI/ILO at all.
How Ironic is supposed to power them off and on? Ssh? But Ironic is not
supposed to interact with host OS.
I'm more accustomed to using PDUs for this type of
Excerpts from Vladimir Kozhukalov's message of 2014-04-08 03:04:38 -0700:
Guys, thank you very much for your comments,
I thought a lot about why we need to be so limited in IPA use cases. Now it
much clearer for me. Indeed, having some kind of agent running inside host
OS is not what many
I'm more accustomed to using PDUs for this type of thing. I.e., a
power strip you can ssh into or hit via a web API to toggle power to
individual ports.
Machines are configured to power up on power restore, plus PXE boot.
You have less control than with IPMI -- all you can do is toggle power
Comments inline.
On 4/8/14, 11:16 AM, Josh Gachnang wrote:
I'm more accustomed to using PDUs for this type of thing. I.e., a
power strip you can ssh into or hit via a web API to toggle power to
individual ports.
Machines are configured to power up on power restore, plus PXE
Vladimir Kozhukalov vkozhuka...@mirantis.com wrote on 08/04/2014
01:04:38 PM:
1) We agreed that Ironic is that place where we can store hardware
info ('extra' field in node model). But many modern hardware
configurations support hot pluggable hard drives, CPUs, and even
memory. How
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 04/04/2014 08:24 AM
Subject:[openstack-dev] [Ironic][Agent]
Hello, everyone,
I'd like to involve more people to express their opinions about the way
how we are going to run Ironic-python
+1
From: Ling Gao [mailto:ling...@us.ibm.com]
Sent: Friday, April 04, 2014 10:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic][Agent] Ironic-python-agent
Hello Vladimir
@lists.openstack.org,
Date: 04/04/2014 08:24 AM
Subject: [openstack-dev] [Ironic][Agent]
Hello, everyone,
I'd like to involve more people to express their opinions about the
way how we are going to run Ironic-python-agent. I
On Fri, Apr 4, 2014 at 5:19 AM, Vladimir Kozhukalov
vkozhuka...@mirantis.com wrote:
On the other hand, it is easy to imagine a situation when you want to run
agent on every node of your cluster after installing OS. It could be useful
to keep hardware info consistent (for example, many
On April 4, 2014 at 9:12:56 AM, Devananda van der Veen
(devananda@gmail.com) wrote:
Ironic's responsibility ends where the host OS begins. Ironic is a bare metal
provisioning service, not a configuration management service.
+1
// jim
___
There are lots of configuration management agents already out there (chef?
puppet? salt? ansible? ... the list is pretty long these days...) which you
can bake into the images that you deploy with Ironic, but I'd like to be
clear that, in my opinion, Ironic's responsibility ends where the host
Excerpts from Vladimir Kozhukalov's message of 2014-04-04 05:19:41 -0700:
Hello, everyone,
I'd like to involve more people to express their opinions about the way how
we are going to run Ironic-python-agent. I mean should we run it with root
privileges or not.
From the very beginning
/04/2014 01:16 PM
Subject:Re: [openstack-dev] [Ironic][Agent]
There are lots of configuration management agents already out there (chef?
puppet? salt? ansible? ... the list is pretty long these days...) which
you can bake into the images that you deploy with Ironic, but I'd like
Ironic's responsibility ends where the host OS begins. Ironic is a bare
metal provisioning service, not a configuration management service.
I agree with the above, but just to clarify I would say that Ironic
shouldn't *interact* with the host OS once it booted. Obviously it can
still perform
22 matches
Mail list logo
