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
>
On 11/10/2015 05:26 AM, John Trowbridge wrote:
>
>
> On 11/09/2015 07: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
On Tue, Nov 10, 2015 at 9:03 AM, Brad P. Crochet wrote:
> Actually, the 'baremetal' namespace is exactly what it should be,
> based on other OSC clients. For instance, Neutron uses 'network', Nova
> uses 'server', etc. The idea is that the client should use the service
> type,
On 11/10/2015 10:43 AM, Ben Nemec wrote:
> On 11/10/2015 05:26 AM, John Trowbridge wrote:
>>
>>
>> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote:
>>> Hi OOO'ers, hopefully the subject caught your attentions :)
>>>
>>> Currently, tripleoclient exposes several commands in "openstack
>>> baremetal"
On Tue, Nov 10, 2015 at 7:42 AM, Lennart Regebro
wrote:
> 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 place,
> it
On 11/10/2015 05:18 PM, Ben Nemec wrote:
+1 to moving anything we can into Ironic itself.
I do want to note that if we rename anything, we can't just rip and
replace. We have users of the current commands, and we need to
deprecate those to give people a chance to move to the new ones.
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
+1 to moving anything we can into Ironic itself.
I do want to note that if we rename anything, we can't just rip and
replace. We have users of the current commands, and we need to
deprecate those to give people a chance to move to the new ones.
A few more thoughts inline.
On 11/09/2015 06:44
On 11/10/2015 11:18 AM, Dmitry Tantsur wrote:
> On 11/10/2015 06:08 PM, Ben Nemec wrote:
>> On 11/10/2015 10:28 AM, John Trowbridge wrote:
>>>
>>>
>>> On 11/10/2015 10:43 AM, Ben Nemec wrote:
On 11/10/2015 05:26 AM, John Trowbridge wrote:
>
>
> On 11/09/2015 07:44 AM, Dmitry
On 11/10/2015 10:28 AM, John Trowbridge wrote:
>
>
> On 11/10/2015 10:43 AM, Ben Nemec wrote:
>> On 11/10/2015 05:26 AM, John Trowbridge wrote:
>>>
>>>
>>> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote:
Hi OOO'ers, hopefully the subject caught your attentions :)
Currently,
On 11/10/2015 06:08 PM, Ben Nemec wrote:
On 11/10/2015 10:28 AM, John Trowbridge wrote:
On 11/10/2015 10:43 AM, Ben Nemec wrote:
On 11/10/2015 05:26 AM, John Trowbridge wrote:
On 11/09/2015 07:44 AM, Dmitry Tantsur wrote:
Hi OOO'ers, hopefully the subject caught your attentions :)
On 09/11/15 07:44, Dmitry Tantsur wrote:
As we already have "openstack undercloud" and "openstack overcloud"
prefixes for TripleO, I suggest we move these commands under "openstack
overcloud nodes" namespace. So we end up with:
overcloud nodes import
overcloud nodes configure ready state
On 11/10/2015 10:40 AM, Dmitry Tantsur wrote:
> On 11/10/2015 05:18 PM, Ben Nemec wrote:
>> +1 to moving anything we can into Ironic itself.
>>
>> I do want to note that if we rename anything, we can't just rip and
>> replace. We have users of the current commands, and we need to
>> deprecate
On 11/09/2015 07: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 accordingly.
On 11/10/2015 12:26 PM, John Trowbridge wrote:
On 11/09/2015 07: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
On 11/10/2015 02:42 PM, 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 place,
it should
- Original Message -
> From: "Lennart Regebro" <lrege...@redhat.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Sent: Tuesday, 10 November, 2015 1:42:52 PM
> Subject: Re
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 place,
it should have been "ironic". Which of course means it would
On 9 November 2015 at 12:44, 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
>
On 11/09/2015 03:04 PM, Dougal Matthews wrote:
On 9 November 2015 at 12:44, Dmitry Tantsur > wrote:
Hi OOO'ers, hopefully the subject caught your attentions :)
Currently, tripleoclient exposes several commands in "openstack
20 matches
Mail list logo