Re: [openstack-dev] [ironic] versioning of IPA, it is time or is it?

ge questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [ironic] versioning of IPA, it is time or is it? 2 июня 2016 г. 10:19 PM пользователь "Loo, Ruby" <ruby@intel.com> написал: > > Hi, > > I recently reviewed a patch [1] th

[openstack-dev] [ironic] weekly subteam status report

Hi, We are stoked to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 23 May 2016) - Ironic: 204 bugs (+12) + 178 wishlist items. 8 new (+8), 138 in progress, 0

Re: [openstack-dev] [ironic] looking for documentation liaison

Hi, Thank you Vlad and Jay for volunteering! Neither of you love documentation, but Jay is “very willing”, so Jay wins :D --ruby On 2016-05-31, 1:23 PM, "Loo, Ruby" <ruby@intel.com> wrote: >Hi, > >We¹re looking for a documentation liaison [1]. If you love (Œl

[openstack-dev] [ironic] versioning of IPA, it is time or is it?

Hi, I recently reviewed a patch [1] that is trying to address an issue with ironic (master) talking to a ramdisk that has a mitaka IPA lurking around. It made me think that IPA may no longer be a teenager (yay, boo). IPA now has a stable branch. I think it is time it grows up and acts

[openstack-dev] [ironic] looking for documentation liaison

Hi, We¹re looking for a documentation liaison [1]. If you love (Œlike¹ is also acceptable) documentation, care that ironic has great documentation, and would love to volunteer, please let us know. The position would require you to: - attend the weekly doc team meetings [2] (or biweekly,

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

Hi, >But the issue here is just capacity. Whether or not we keep an instance >in a deleting state, or when we release quota, doesn't change the >Tempest failures from what I can tell. The suggestions below address >that. > > >> >> > > > >> > > > I think we should go with #1, but instead of

Re: [openstack-dev] [ironic] process for making decisions?

Hi Jim, Thanks for responding. >If we do think we need a formal process for making decisions as you >define above, I think it should be something like: > >* bring it up on the mailing list >* someone /must/ propose a solution along the way, in gerrit, perhaps > the person that started the

Re: [openstack-dev] [ironic] usage of ironic-lib

ananda van der Veen wrote: >> On 05/16/2016 07:14 AM, Lucas Alvares Gomes wrote: >> > On Mon, May 16, 2016 at 2:57 PM, Loo, Ruby <ruby@intel.com> wrote: >> >> Hi, >> >> >> >> A patch to ironic-lib made me wonder about what is our supported u

[openstack-dev] [ironic] weekly sub team status report

Hi, We are rambunctious to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 16 May 2016) - Ironic: 192 bugs (+2) + 178 wishlist items (+1). 0 new, 138 in progress

Re: [openstack-dev] [ironic] usage of ironic-lib

Ooo, thanks for that data point Pavlo! Thanks Lucas, Sam, Shivanand and Pavlo for commenting. From the replies, it seems like the original intent of ironic-lib was to solely be used by ironic and ironic-python-agent projects. But that doesn’t seem to have been communicated properly (because I

[openstack-dev] [ironic] process for making decisions?

Hi, I think it would be good if we came up with some general guidelines wrt the processes by which decisions are made. By ³decisions², I mean decisions that we, as a community, will try to abide by ? I have noticed in the past, that discussions in the mailing list (ML) sometimes peter out

[openstack-dev] [ironic] weekly sub team status report

Hi, We are quick to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 9 May 2016): - Ironic: 190 bugs (0) + 177 wishlist items (+4). 0 new (-17), 134 in progress (+1),

Re: [openstack-dev] [ironic][openstackclient] deprecation process

tackclient/blob/b4c3adbd308e65679489c4c64680cbe0324f4bc7/openstackclient/volume/v1/volume.py#L53-L63 On Thu, May 12, 2016 at 9:46 AM, Loo, Ruby <ruby@intel.com<mailto:ruby@intel.com>> wrote: Hi OpenStackClient folks, Ironic is following the standard deprecation process [1].

[openstack-dev] [ironic] usage of ironic-lib

Hi, A patch to ironic-lib made me wonder about what is our supported usage of ironic-lib. Or even the intent/scope of it. This patch changes a method, ‘bootable’ parameter is removed and ‘boot_flag’ parameter is added [1]. If this library/method is used by some out-of-tree thing (or even some

Re: [openstack-dev] [ironic] [OpenstackClient] deprecations

for the duplicate email. ‹ruby On 2016-05-11, 11:46 AM, "Jim Rollenhagen" <j...@jimrollenhagen.com> wrote: >On Wed, May 11, 2016 at 02:35:12PM +, Loo, Ruby wrote: >> Hi ironic¹ers, >> >> I thought we had decided that we would follow the standard

[openstack-dev] [ironic][openstackclient] deprecation process

Hi OpenStackClient folks, Ironic is following the standard deprecation process [1]. We added an OSC plugin and realized that we didn’t get the commands quite right. This patch [2] adds the right commands and deprecates the wrong ones. My question is what the deprecation process might be. Since

[openstack-dev] [ironic] deprecations

Hi ironic’ers, I thought we had decided that we would follow the standard deprecation process [1], but I see that ironic isn’t tagged with that [2]. Although we have documented guidelines wrt deprecations [3]. But I am not sure we’ve been good about sending out email about deprecations. Does

Re: [openstack-dev] [ironic] Midcycle: virtual or physical?

The poll closes Sunday night/Monday morning. Ie, whenever Jim gets around to looking at the numbers Monday (May 16) morning, before our weekly ironic meeting :) ‹ruby On 2016-05-09, 6:24 PM, "Jim Rollenhagen" wrote: >Hey all, > >In this morning's meetings we

<    1   2