driver is a point solution for our PDUs, but why not make
it generalised? We'd be happy to contribute it.
OpenStack-dev mailing list
Our project is a point solution at your step 6. The rest of the workflow looks
complimentary and solves the unanswered questions in our bp proposal. As
indeed would the neutron-external-ports spec.
From: Russell Haering [mailto:russellhaer
Is there anyone out there who has done this and can comment on their experience?
From: Devananda van der Veen [mailto:email@example.com]
Sent: Thursday, May 22, 2014 1:03 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Ironic] handling
Hi Dmitry -
> On 11 May 2017, at 15:56, Dmitry Tantsur wrote:
> Hi all!
> While people are enjoying the Forum, I also have something to show.
> I've got a lot of questions about auto-discovery, so I've recorded a demo
> of it using TripleO Ocata:
Hi Moshe -
It seems a bit risky to automatically apply firmware updates. For example,
given a node will probably be rebooted for firmware updates to take effect, if
other vendors also did this then perhaps the node could reboot unexpectedly in
the middle of your update. In theory.
Hello Ironicers -
We’ve booked the same venue for the Scientific SIG for Wednesday evening, and
hopefully we’ll see you there. There’s plenty of cross-over between our
groups, particularly at an operator level.
> On 29 Oct 2018, at 14:58, Dmitry Tantsur wrote:
> Hi folks!