k.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
Principal Software Engineer
(c) 704.236.9385
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
_____________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Brad P. Croc
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Brad P. Croc
On Mon, Jan 29, 2018 at 8:02 PM, Doug Hellmann wrote:
> Excerpts from zuul's message of 2018-01-30 00:40:13 +:
>> Build failed.
>>
>> - release-openstack-python
>> http://logs.openstack.org/53/533a5ee424ebf6937f03d3b1d9d5b52e8ecb/pre-release/release-openstack-python/44f2fd4/
>> : FAILURE
On Mon, Dec 11, 2017 at 5:20 PM Alex Schultz wrote:
> On Mon, Dec 11, 2017 at 1:20 PM, Brad P. Crochet wrote:
> >
> >
> > On Fri, Dec 8, 2017 at 6:35 PM Alex Schultz wrote:
> >>
> >> Hey folks,
> >>
> >> So I went through the list of bl
s-action
There is a good chance of these being completed in the coming week.
Thanks,
Brad
>
> --
Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
Principal Software Engineer
(c) 704.236.9385
__
OpenStack Development Mailing List
(not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
Principal S
e to bring any feedback.
> Thanks everyone,
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
will start by reviewing what you have
so far.
> --
> -- James Slagle
> --
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@
/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
penstack-dev
> >
>
> __________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailma
ontributor/check_gates.html
>>
>>
>> __________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.o
> On 17 Apr 2017, 22:17 +0700, Brad P. Crochet , wrote:
>
> Hi y'all...
>
> In the midst of trying to track down some errors being seen with tempest
> tests whilst running under mod_wsgi/apache, I've made it so that the
> devstack plugin is capable of also runn
d devstack jobs. So, as you can see, I've migrated
the kombu job to be such a thing. It should also be possible to combine
them.
[1] https://review.openstack.org/#/c/454710/
[2] https://review.openstack.org/#/c/457106/
--
Brad P. Crochet, RHCA, RHCE, RH
On Wed, Nov 23, 2016 at 11:07 AM, Ben Nemec wrote:
>
>
> On 11/22/2016 08:18 PM, Emilien Macchi wrote:
>>
>> Even if I was part of those who approved this feature, I still have
>> some comments, inline:
>>
>> On Tue, Nov 22, 2016 at 1:30 PM, Alex Schultz wrote:
>>>
>>> On Tue, Nov 22, 2016 at 11:
On Thu, Aug 18, 2016 at 4:25 AM, mathieu bultel wrote:
> On 08/18/2016 09:29 AM, Marios Andreou wrote:
>> On 17/08/16 15:46, Jiří Stránský wrote:
>>> On 16.8.2016 21:08, Brad P. Crochet wrote:
>>>> Hello TripleO-ians,
>>>>
>>>> I've start
Hello TripleO-ians,
I've started to look again at the introduced, but unused/undocumented
upgrade commands. It seems to me that given the current state of the
upgrade process (at least from Liberty -> Mitaka), these commands make
a lot less sense.
I see one of two directions to take on this. Of c
tack baremetal node console [--enable, --disable] UUID
>
> openstack baremetal node boot-device [--supported, --set CDROM, PXE, DISK]
> UUID
>
>
> openstack baremetal [node/driver] vendor NAME_OR_UUID METHOD
>
>
> WDYT?
>
>
> Sam
>
>
> ___________
13th).
>
+1
> Cheers,
> Greg
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Brad P. Crochet, RHCA, RHCE, RHCVA,
On Tue, Nov 10, 2015 at 10:53 AM, Dean Troyer wrote:
> On Tue, Nov 10, 2015 at 9:32 AM, Brad P. Crochet wrote:
>>
>> In this case, the noun is actually 'baremetal provision state'. The
>> 'action' is the states themselves. It doesn't fit exactly
anging it to "activate" or
> "provision".
>
> My next candidate is #6. Though it's also not a verb, it reads pretty
> easily.
>
> Thanks!
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ
;
> --
>
> Dean Troyer
> dtro...@gmail.com
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub
ingle API call. I'd say it is *possible*, but probably not ideal.
>
> My next candidate is #6. Though it's also not a verb, it reads pretty
> easily.
Might be too generic for my tastes.
>
> Thanks!
>
> __
If it's a HEAD call, how
> about "check"?
>
> What's "manage" does it update a resource? Can you use "set" instead?
>
> What are the natural opposites between provide/activate/abort/boot/shutdown?
>
> reboot and rebuild seem good
>
&g
On Mon, Nov 9, 2015 at 7:44 AM, Dmitry Tantsur wrote:
> Hi OOO'ers, hopefully the subject caught your attentions :)
>
> Currently, tripleoclient exposes several commands in "openstack baremetal"
> and "openstack baremetal introspection" namespaces belonging to ironic and
> ironic-inspector accordi
On Tue, Nov 10, 2015 at 8:42 AM, Lennart Regebro wrote:
> These changes are fine to me.
>
> I'm not so sure about the idea that we can't "hijack" other projects
> namespaces. If only ironic is allowed to use the prefix "baremetal",
> then the prefix should not have been "baremetal" in the first pl
https://review.openstack.org/#/c/235569/
--
Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
Principal Software Engineer
(c) 704.236.9385 (w) 919.301.3231
__
OpenStack Development Mailing List (not for usage qu
On 24/08/15 19:31 +0200, Dmitry Tantsur wrote:
On 08/24/2015 07:25 PM, Brad P. Crochet wrote:
On 24/08/15 17:56 +0200, Dmitry Tantsur wrote:
On 08/24/2015 05:41 PM, Jay Pipes wrote:
On 08/24/2015 08:03 AM, Brad P. Crochet wrote:
I am working on extending the current set of patches that
nds like that
is not possible.
-Original Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: 24 August 2015 19:31
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Ironic] Command structure for OSC plugin
On 08/24/2015 07:25 PM, Brad P. Crochet wrote:
>
On 24/08/15 19:31 +0200, Dmitry Tantsur wrote:
On 08/24/2015 07:25 PM, Brad P. Crochet wrote:
On 24/08/15 17:56 +0200, Dmitry Tantsur wrote:
On 08/24/2015 05:41 PM, Jay Pipes wrote:
On 08/24/2015 08:03 AM, Brad P. Crochet wrote:
I am working on extending the current set of patches that
On 24/08/15 17:56 +0200, Dmitry Tantsur wrote:
On 08/24/2015 05:41 PM, Jay Pipes wrote:
On 08/24/2015 08:03 AM, Brad P. Crochet wrote:
I am working on extending the current set of patches that implement
the OSC plugin for Ironic. I would like some discussion/guidance about
a couple of command
On 24/08/15 11:03 -0400, Brad P. Crochet wrote:
I am working on extending the current set of patches that implement
the OSC plugin for Ironic. I would like some discussion/guidance about
a couple of command structures.
[...snip...]
Secondly, maintenance mode makes sense to be part of
what it does, but it was suggested that display of
the maintenance field would need to change.
Comments? Suggestions?
--
Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
Principal Software Engineer
(c) 704.236.9385 (w) 919.301.3231
33 matches
Mail list logo
