Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, > Another idea is to modify test that it will: > 1. Check how many ports are in tenant, > 2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is > now, > 3. Try to add 2 ports - exactly as it is now, > > I think that this should be still backend agnostic and should fix

[openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, The tests below are failing in the tempest API / Scenario job that runs in the networking-ovn gate (non-voting): neutron_tempest_plugin.api.admin.test_quotas_negative.QuotasAdminNegativeTestJSON.test_create_port_when_quotas_is_full

Re: [openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

Hi, > Please tell me who from the OVN group is ready to take the burden, and > I will make you part of neutron-stable-maint. I think it's ok to be > more laissez faire with backports for subprojects than we were used > to, with the recent drop in core team membership and reduced capacity. Great!

Re: [openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

Hi, >> Hi all, >> >> Just sending this email to try to understand the model for stable branch >> maintenance in networking-ovn (potentially other neutron drivers too). >> >> Right now, only members of the ``neutron-stable-maint`` gerrit group are >> able to approve patches for the stable

[openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

Hi all, Just sending this email to try to understand the model for stable branch maintenance in networking-ovn (potentially other neutron drivers too). Right now, only members of the ``neutron-stable-maint`` gerrit group are able to approve patches for the stable branches; this can cause some

Re: [openstack-dev] [ovs-discuss] [Neutron][networking-ovn] OVN + Openstack Issues

Hi, > Hi Martin, > > I met exactly the same issue with yours, could you please show some details > about security groups deleting, resyncing and recreating? cause I cleared > DEFAULT security group and add 'ovn-sync-mode=repair' in config file then > restarted the neutron-server, but didn't work

[openstack-dev] [Neutron][ovn] networking-ovn core team update

Hi all, I would like to welcome Daniel Alvarez to the networking-ovn core team! Daniel has been contributing with the project for a good time already and helping *a lot* with reviews and code. Welcome onboard man! Cheers, Lucas

Re: [openstack-dev] [networking-ovn] Error while running unit tests(master branch)

Hi Pranab, > I don't see any errors in final results. But, as you can see here [1], > couple of tests are showing ERROR before that. > > [1] http://paste.openstack.org/show/624436/ > Ah, I see what you mean now. Off the top of my head I don't know what is the cause, I will need to some

Re: [openstack-dev] [networking-ovn] Error while running unit tests(master branch)

Hi Pranab, Thanks for the interest in OVN. > # tox > .. > {9}networking_ovn.tests.unit.ovsdb.test_ovsdb_monitor.TestOvnConnection.test_connection_sb_start > [0.015743s] ... ok > Mechanism driver 'ovn' failed in create_port_precommit > Traceback (most recent call last): > File >

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Hi Greg, > I’m an ironic newbie ... > First of, welcome to the community (-: > where can I find a good / relatively-current (e.g. PIKE) demo of Ironic > integrated within OpenStack ? > I would recommend deploying it with DevStack on a VM and playing with it, you can follow this document in

[openstack-dev] [Ironic] Stepping down from core

Hi all, This is a difficult email to send. As some of you might already know, lately I've been focusing on the OVS/OVN (and related) projects and I don't have much time left to dedicate on reviewing patches in Ironic, at least for now. My biggest priority for this cycle was to create a basic

Re: [openstack-dev] [ironic] Resigning as a core reviewer

Hi, It's sad to see you go Jay, thanks for all your great work and input on things you've helped to shape Ironic into what it's today. The project will certainly miss you and so will the people involved. Cheers, Lucas On Wed, Apr 26, 2017 at 8:42 PM, Jay Faulkner wrote: > Hi all,

Re: [openstack-dev] [ironic] Translations removal

Hi, >> Possible options to handle that: >> >> 1) Duplicate messages: >> >> LOG.error(“”, {: }) >> >> raise Exception(_(“”) % {: }) >> >> 2) Ignore this error >> >> 3) Talk to hacking people about possible upgrade of this check >> >> 4) Pass translated text to LOG in such cases

Re: [openstack-dev] [ironic] New mascot design

Hi, Thanks for the update Heidi. I think this version is fine so +1 from me, it carries the essence of the original Pixie :-) Cheers, Lucas On Fri, Mar 10, 2017 at 4:28 PM, Heidi Joy Tretheway wrote: > Hi Ironic team, > Here’s an update on your project logo. Our

Re: [openstack-dev] [ironic] End-of-Ocata core team updates

Hi, Thanks Dmitry for putting this up! > I'd like to propose a few changes based on the recent contributor activity. > > I have two candidates that look very good and pass the formal barrier of 3 > reviews a day on average [1]. > > First, Vasyl Saienko (vsaienk0). I'm pretty confident in him,

Re: [openstack-dev] [ironic] New mascot design

Hi, > Hi Ironic team, > > [TL;DR - we agree to Miles’ proposal for two images (one mascot, one logo) > for different contexts. We’re looking for any final feedback on the stylized > logo for use on the website, while the PixieBoots mascot remains yours for > swag, etc.] > > I’m doing my best

Re: [openstack-dev] [ironic] New mascot design

Hi Heidi, Thanks for the email. I don't wanna be rude but we left the last ML thread [0] with many questions without an answer. It would be good to keep the discussion in one thread only to make it easier for people to read about it in the future. I don't think we have much of a choice, so, the

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi, Just a FYI, we have had similar discussions about the proposed logo for Ironic, there's still many unanswered questions but, if you guys are interested this is the link to the ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html Cheers, Lucas On Tue, Feb

Re: [openstack-dev] [ironic] New mascot design

Hi, > I'm with the group here. > > Let's find something that looks nice and is not offensive to anyone. > +1 ... Also, Heidi, I forgot to ask in the previous emails and I couldn't find in the guidelines[0]: What license will these images have ? Will people be allowed to share and create

Re: [openstack-dev] [ironic] New mascot design

I may be biased to some extent but I don't like it. The mascot doesn't seem to have any personality. It also looks odd because he has this straight face while he's doing the sign of horns, it just doesn't work. I remember when I first saw a logo related to Ironic in that presentation that Jay

Re: [openstack-dev] [ironic] iscsi-deploy vs agent-deploy comparison

Hi Pavlo, On Tue, Dec 13, 2016 at 11:52 AM, Pavlo Shchelokovskyy wrote: > Hi all, > > recent comments in some of my patches hinted me that I might be missing some > understanding of ironic workings, so I'd like to ask the following question: > > What

Re: [openstack-dev] [Ironic] OpenStack Summit Barcelona: Ironic Meetup (evening)

On Wed, Oct 26, 2016 at 3:01 PM, Lucas Alvares Gomes <lucasago...@gmail.com> wrote: > Hi all, > > Good news, I got a reservation for 20 people in the El Clot Restaurant > tomorrow (Thursday 26/10) [0] at 7:00 PM!

Re: [openstack-dev] [Ironic] OpenStack Summit Barcelona: Ironic Meetup (evening)

, Oct 17, 2016 at 8:45 PM, Lucas Alvares Gomes <lucasago...@gmail.com> wrote: > Hi everyone, > > We are planning to have an evening Ironic contributors meetup at some > point in the Barcelona Summit and we need to decide which day of that > week would be most suited for all/m

[openstack-dev] [Ironic] OpenStack Summit Barcelona: Ironic Meetup (evening)

Hi everyone, We are planning to have an evening Ironic contributors meetup at some point in the Barcelona Summit and we need to decide which day of that week would be most suited for all/most of us. So, if you are willing to attend please put your name and possible days at

Re: [openstack-dev] [ironic] today's meeting is cancelled

> Due the holidays in USA and Canada (maybe other countries) we are not > having an upstream Ironic meeting today because there's no quorum. The > next meeting will be on Monday, September 11. > Sorry, September 12. __

[openstack-dev] [ironic] today's meeting is cancelled

Hi, Due the holidays in USA and Canada (maybe other countries) we are not having an upstream Ironic meeting today because there's no quorum. The next meeting will be on Monday, September 11. Cheers, Lucas __ OpenStack

Re: [openstack-dev] [ironic][OpenStackClient] two openstack commands for the same operation?

On Mon, Aug 29, 2016 at 3:41 PM, Loo, Ruby wrote: > Hi, > > In ironic, we have these ironic CLI commands: > - ironic node-vendor-passthru (calls the specified passthru method) > - ironic node-get-vendor-passthru-methods (lists the available passthru > methods) > > For their

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

Hi, I overall agree with the proposed plan. I like the idea of having a "supported" flag (or another name as per Kurt's email) that makes it easy mark a driver as "unsupported" indicating it might be removed soon. About point #3 I'm indifferent, it's a common approach in the project to log a

Re: [openstack-dev] how to add ironic db version file. now install don't copying db version file. how to do?

Hi Paul, I want add a db version file. can tell me how to do ? very very thank you > !!! > To create a migration script you have to do: $ cd ironic/ironic/db/sqlalchemy $ alembic revision -m "create foo table" We maintain a FAQ as part of the Ironic documentation that answer this and other

Re: [openstack-dev] [tripleo] [ironic] Exception registering nodes when Ironic API with apache

Hi, > On Friday we landed a patch in TripleO to deploy Ironic API in WSGI with > Apache. > Since then, our baremetal CI jobs were failing randomly, and a lot of > time, with an exception. > I decided to revert the patch to bring our CI back: > https://review.openstack.org/#/c/349281/ (+2 from

Re: [openstack-dev] I want to consult ironic problems

Hi Paul, > I want to consult ironic problems > do there have bare metal management man? > Ironic is developed by a community, if you have problems running/developing there are a couple of ways to solicit help: * Send an email to this mail list (openstack-dev) with your question(s) (and add

Re: [openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

Hi, >> I would say we should add a job to the IPA gate to verify the >> functional tests, just like swift does [0]. >> >> We may also need to revert/fix that patch that broke those tests. > > > I'm -1 to reverting anything until we have the test in the gate. > Fair enough. I've opened two bugs:

Re: [openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

Hi, On Wed, Jun 22, 2016 at 10:53 AM, Sam Betts (sambetts) wrote: > This patch https://review.openstack.org/#/c/324909/ merged last night and > has broken the IPA functional tests. > > To verify pull master and run "tox -r -e func" and it¹ll fail to run. If > you git checkout

Re: [openstack-dev] [ironic] Proposing two new cores

Hi, > Both Sam and Jay are to the point where I consider their +1 or -1 as > highly as any other core, so I think it's past time to allow them to +2 > as well. > > Current cores, please reply with your vote. > Great work Sam and Jay! +1 for both Cheers, Lucas

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Hi, >> I agree in general with the idea but I think it needs a tad more >> context. We need to remember that Ironic (ex-Nova Baremetal) was >> created to fill a gap in OpenStack that was missing for TripleO >> project to get off the ground. That was the problem being solved and >> these aspects

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Hi, Thanks for writing it down Jim. > So, I've been thinking about this quite a bit. We've also talked about > doing a v2 API (as evil as that may be) in Ironic here and there. We've > had lots of lessons learned from the v1 API, mostly that our API is > absolutely terrible for humans. I'd love

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

Hi, Thanks for bringing this up Vasyl! > At the moment Nova with ironic virt_driver consider instance as deleted, > while on Ironic side server goes to cleaning which can take a while. As > result current implementation of Nova tempest tests doesn't work for case > when Ironic is enabled. > >

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi, > I'm working with Tien who is a submitter of one[1] of console specs. > I joined the console session in Austin. > > In the session, we got the following consensus. > - focus on serial console in Newton > - use nova-serial proxy as is > > We also got some requirements[2] for this feature in

Re: [openstack-dev] [ironic] Newton priorities and primary contacts

Hi, > I see in the priority list that "redfish support" is still highly wanted (4 > +1). > And we are still very interested to provide that. It took much more time > than expected, as we first decided that we wanted a good low level library > to help us dialog following the Redfish standard to

Re: [openstack-dev] [tripleo] Nodes management in our shiny new TripleO API

Hi, > This sounds like an Ironic bug to me. Cleaning (wiping a disk) and > removing state that would break subsequent installations on a different > drive are different things. In TripleO I think the reason we disable > cleaning is largely because of the extra time it takes and the fact > that

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

Hi, > So… how does any library get ready to be used by others? Clearly it is being > used now by the fuel-agent. Do we say ‘sorry fuel-agent, we don’t guarantee > yet that we won’t break you’? Or ‘fuel-agent, just so you know. Ironic-lib > isn’t quite ready to be used so we cannot guarantee that

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

Hi, On Mon, May 16, 2016 at 3:56 PM, Sam Betts (sambetts) wrote: > I personally disagree with saying that if we wanted it make it usable by > projects other than ones in the Ironic umbrella it should go into oslo. I > think that non-ironic projects directly related to Ironic

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

Hi, Thanks for starting this discussion Ruby. On Mon, May 16, 2016 at 2:57 PM, Loo, Ruby wrote: > 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’

Re: [openstack-dev] [ironic] Nominating Julia Kreger for core reviewer

Hi, > I'm nominating Julia Kreger (TheJulia in IRC) for ironic-core. She runs > the Bifrost project, gives super valuable reviews, is beginning to lead > the boot from volume efforts, and is clearly an expert in this space. > > All in favor say +1 :) > +1 from me, welcome Julia!

Re: [openstack-dev] [ironic] Midcycle summary part 3/6

Hi Daisuke, On Thu, Mar 3, 2016 at 10:53 AM, Fujita, Daisuke wrote: > Hi, Jim, Julia, and Ironicers, > > I have some questions about the BFV. > >> > * Hardware supports the UEFI 2.4 spec > > Could you please explain the reason that chose version not

Re: [openstack-dev] [ironic] Remember to follow RFE process

Hi, > Ironic'ers, please remember to follow the RFE process; especially the cores. > > I noticed that a patch [1] got merged yesterday. The patch was associated > with an RFE [2] that hadn't been approved yet :-( What caught my eye was > that the commit message didn't describe the actual API

Re: [openstack-dev] [ironic] [stable] Suggestion to remove stable/liberty and stable branches support from ironic-python-agent

Hi, By removing stable branches you mean stable branches for mitaka and newer releases or that includes stable/liberty which already exist as well? I think the latter is more complicated, I don't think we should drop stable/liberty like that because other people (apart from TripleO) may also

[openstack-dev] [Ironic] Heads up: Third Party CI systems

Hi, This email is just a heads up to the people working on 3rd Party CI systems for Ironic. There's a patch in the review queue now [0] that may break you guys (the fix is simple). The patch is adding the ability to deploy nodes using the {pxe, agent}_ipmitool drivers with VMs. But, the problem

[openstack-dev] [all] [Ironic] New project: Ironic Staging Drivers

Hi, I would like to quickly announce the creation of a new project called Ironic Staging Drivers. What the Ironic Staging Drivers project is? - As context, in the Tokyo design summit it was decided that drivers in the Ironic tree will

[openstack-dev] [Ironic] Heads up for devstack IRONIC_QEMU_HOOK_PATH variable change

Hi, Hi this email is just a heads up to alert people that the "IRONIC_QEMU_HOOK_PATH" variable for DevStack is not available anymore, a path [0] was merged and replaced that variable with another one called "IRONIC_LIBVIRT_HOOKS_PATH" without deprecating it first. For context, the

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

Hi, > 1. "baremetalintrospection" - named after the process we > implement +1 for baremetal-introspection ( or inspection ? ) Cheers, Lucas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [ironic]Create vm fails when using IronicDriver

Hi Zhi, > And the error message is: > InstanceDeployFailure: RPC do_node_deploy failed to validate deploy or power > info. Error: Node d71babdd-aa91-450d-b957-dc8c633c41f2 is configured to use > the agent_ssh driver which currently does not support deploying partition > images. > > Could someone

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

I'm +1 for re-enabling it in Ironic. I think ironic plays a big role in the tripleo puzzle so we should be aware of breakages in the tripleo project. On Mon, Nov 30, 2015 at 3:19 PM, Derek Higgins wrote: > Hi All, > > A few months tripleo switch from its devtest based CI

Re: [openstack-dev] [ironic][security] what is OK to put in DEBUG logs?

Hi, > Also keep in mind that DEBUG logging, while still should have some masking > of data, since it is explicitly called out (or should be) as not safe for > production, can contain some " sensitive" data. Credentials should still be > scrubbed, but I would say the swift temp URL is something

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

Hi, > I sent a new idea to openstack-dev, and nobody has opinions? :P > > I'd like to get consensus on this soon, please do reply if you have > thoughts on this. > Sorry for the delay... Yeah, I've no problem giving this virtual midcycle idea a go, so +1

[openstack-dev] [Ironic] Do we need to have a mid-cycle?

Hi, In the last Ironic meeting [1] we started a discussion about whether we need to have a mid-cycle meeting for the Mitaka cycle or not. Some ideas about the format of the midcycle were presented in that conversation and this email is just a follow up on that conversation. The ideas presented

Re: [openstack-dev] [Ironic] Quick poll: OpenStackClient command for provision action

Hi, > Let's have a quick poll, which would you prefer and why: > > 1. openstack baremetal provision state --provide UUID > 2. openstack baremetal provision --provide UUID > 3. openstack baremetal provide UUID > 4. openstack baremetal set provision state --provide UUID > 5. openstack baremetal set

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

> It's still not 100% consistent, "power" is a noun, "provision" is a verb. > Not sure it matters, though, adding OSC folks so that they can weigh in. > "provision" can also be a noun [1]. But since the OSC syntax suggest having a verb we could have something like: $ openstack baremetal set

Re: [openstack-dev] [Ironic] BIOS Configuration

Hi, > I am interested in remote BIOS configuration. > There is "New driver interface for BIOS configuration specification" > https://review.openstack.org/#/c/209612/ > > Is it possible to implement this without REST API endpoint? > I may be missing something here but without the API how will the

[openstack-dev] [Ironic] OpenStack Ironic dinner

Since many of us is going to be in Tokyo for the summit, who's interested in an OpenStack Ironic dinner? Let's first decide what day of the week suits most people, so please vote here: http://doodle.com/poll/2nqbemmrdd9a5ypd if you have any food requirements or restrictions please add it to the

Re: [openstack-dev] [ironic] Nominating two new core reviewers

Hi, On Thu, Oct 8, 2015 at 10:47 PM, Jim Rollenhagen wrote: > Hi all, > > I've been thinking a lot about Ironic's core reviewer team and how we might > make it better. > > I'd like to grow the team more through trust and mentoring. We should be > able to promote someone

Re: [openstack-dev] [Ironic] Stepping down from IPA core

> Hey y'all, it's with a heavy heart I have to announce I'll be stepping down > from the IPA core team on Thurs, 9/24. I'm leaving Rackspace for a > healthcare startup (Triggr Health) and won't have the time to dedicate to > being an effective OpenStack reviewer. > -2 Sad to see you go Josh I

Re: [openstack-dev] [Ironic] There is a function to display the VGA emulation screen of BMC in the baremetal node on the Horizon?

Hi, > We are investigating how to display on the Horizon a VGA > emulation screen of BMC in the bare metal node that has been > deployed by Ironic. > If it was already implemented, I thought that the connection > information of a VNC or SPICE server (converted if necessary) > for a VGA emulation

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

Hi, > Disclaimer: I don't know much about OSC or its syntax, command > structure, etc. These may not be well-formed thoughts. :) > Same here, I don't know much about OSC in general. > So, many of the nova commands (openstack server foo) don't make sense in > an Ironic context, and vice versa.

[openstack-dev] [DevStack][Keystone][Ironic][Swit] FYI: Defaulting to Keystone v3 API

Hi, This is email is just a FYI: Recently the patch [1] got merged in DevStack and broke the Ironic gate [2], I haven't had time to dig into the problem yet so I reverted the patch [3] to unblock our gate. The work to convert to v3 seems to be close enough but not yet there so I just want to

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

Hi, > The current failure rate for the ironic pxe_ssh job is 100% - >

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

Hi, If you just want to shoot the breeze please respond here. If you have specific comments on the spec please response there. I have been thinking about doing it for Ironic as well so I'm looking for options. IMHO after using WSME I would think that one of the most important criteria we

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

Hi, On Thu, Aug 27, 2015 at 5:43 PM, Clint Byrum cl...@fewbar.com wrote: Excerpts from Lucas Alvares Gomes's message of 2015-08-27 02:40:26 -0700: On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger juliaashleykre...@gmail.com wrote: My apologies for not expressing my thoughts on this matter

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger juliaashleykre...@gmail.com wrote: My apologies for not expressing my thoughts on this matter sooner, however I've had to spend some time collecting my thoughts. To me, it seems like we do not trust our users. Granted, when I say users, I mean

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

Hi, +1, yeah I kinda agree with the major version bump. But also it's important to note that Ironic which was affected by that was relying on be able to POST nonexistent fields to create resources and WSME would just ignore those on versions = 0.8.0. That's a legitimate bug that have been

Re: [openstack-dev] [wsme] potential issues with WSME 0.8.0

On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote: On Wed, 26 Aug 2015, Dmitry Tantsur wrote: Note that this is an API breaking change, which can potentially break random users of all projects using wsme. I think we should communicate this point a bit louder, and I also

Re: [openstack-dev] [Ironic] [Inspector] Addition to ironic-inspector-core: Sam Betts

Congrats! Well deserved On Tue, Aug 25, 2015 at 12:24 PM, Yuiko Takada yuikotakada0...@gmail.com wrote: Sam, congrats and welcome! Yuiko Takada 2015/08/25 19:53、Dmitry Tantsur dtant...@redhat.com のメッセージ: Hi all! Please join me in welcoming Sam to our team! He has been doing very smart

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

Hi, 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. Currently provisioning state is set via 'openstack baremetal set --provision-state

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

Hi On 21 Aug 2015 6:45 am, Jim Rollenhagen +1, there are tons of dragons here. Now that we're to the point where our state machine is well-defined with a single entrypoint, I think I'm clearly confused. When was 1.6 deleted? It wasn't and won't be AFAICT. But I think Jim is talking about

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

Hi, After thinking about this some more, I'm not actually going to address Rob's points above. What I want to do is go back and discuss... what do people think about having an API that allows the initial provision state to be specified, for a node that is created in Ironic. I'm assuming that

Re: [openstack-dev] [Ironic] Let's talk about API versions

HI Hi, I'd like to make sure I understand. Is it the case that ideally, if we could go back in time, we'd like to change the client so it defaults to 1.1? AFAIUI, yes But since we can't, the next client that we ship/release will have the most reasonable oldest version? If so, then since the

Re: [openstack-dev] [Ironic] reminder: meeting time change

Hi, Thanks for the reminder. Just a quick reminder - we're switching back to a consistent meeting time, at 18:00 UTC Mondays. The time is actually 17:00 UTC [1] [1] https://wiki.openstack.org/wiki/Meetings/Ironic#Next_Meeting Cheers, Lucas

Re: [openstack-dev] [nova][ironic] Scheduler filtering based on instances

Hi, Our initial solution [1] was to simply disable instance queries in the IronicHostManager, as they were never needed, and were painful to execute. But subsequent discussion on IRC brought up some potential (although not very likely) use cases where this might not be true. One example was

Re: [openstack-dev] [Ironic] Let's talk about API versions

Hi, It sounds like we all agree -- the client we ship should default to a fixed, older version. Anyone who wants newer functionality can pass a newer version to their client. Here's the current state of things: server: - stable/kilo: 1.6 - current: 1.11 client: - stable/kilo: 1.6 -

Re: [openstack-dev] [Ironic] Lenovo driver submission requests

On Thu, Jul 30, 2015 at 8:27 AM, Dmitry Tantsur dtant...@redhat.com wrote: On 07/30/2015 08:59 AM, Kai KH Huang wrote: Dear Devananda I'm the development leader of Lenovo Cloud Solution. Lenovo is planning to contribute its Ironic driver to the OpenStack community. The Ironic

Re: [openstack-dev] [Ironic] Let's talk about API versions

1. yes 2. no -- the client should default to the minimum supported version. We got that wrong previously, and that's what is hurting us now. So if we do this, simply shipping the code doesn't break anyone. Nobody has disagreed on this yet, best I can tell. We would still need a deprecation

Re: [openstack-dev] [Ironic] Let's talk about API versions

Hi, Could you combine 1 and 4? Deprecate not specifying the version, but pin to the oldest one for now? That way users get the warnings that they need to adapt, but things keep working? Could be switched to just 4 after a few months. This is similar to what I would like to suggest. But I

Re: [openstack-dev] [ironic] AttributeError: 'GitReviewException' object has no attribute 'EXIT_CODE'

Hi, malhar@ubuntu:~/Documents/contribution/temp/ironic$ git review -s Using global/system git-review config files (/etc/git-review/git-review.conf) is deprecated Could not connect to gerrit. Enter your gerrit username: myusername Trying again with

Re: [openstack-dev] [ironic] AttributeError: 'GitReviewException' object has no attribute 'EXIT_CODE'

Hi, Please make sure you have the correct access rights and the repository exists. error: Could not fetch gerrit Problems encountered installing commit-msg hook The following command failed with exit code 1 scp -P29418 malhar_...@review.openstack.org:hooks/commit-msg

Re: [openstack-dev] [Ironic] What to do with reservation check in node update API?

Hi, So, it looks like the only reason we check the reservation field here is because we want to return a 409 for node is locked rather than a 400, right? do_node_deploy and such will raise a NodeLocked, which should do the same as this check. It's unclear to me why we can't just remove this

Re: [openstack-dev] [Ironic] What to do with reservation check in node update API?

Hi, Another question folks: while the problem above is valid and should be solved, I was actually keeping in mind another one: https://github.com/openstack/ironic/blob/master/ironic/api/controllers/v1/node.py#L1052-L1057 This is also not retried, and it prevents updating during power

Re: [openstack-dev] [Ironic] [Inspector] Addition to ironic-inspector-core, switching to 2x +2 rule

Hi, Please welcome Yuiko Takada to ironic-inspector-core team. Yuiko has been with the team for some time already. She did substantial work on porting ironic-inspector to Oslo libraries and on our new devstack gate job. Congratulations, well deserved!

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

Hi, If renaming Ironic to the other, is it still necessary to keep the name in the header? There are some projects which are already renamed like Neutron, Zaqar and the others. So OpenStack-API-Version which doesn't contain project name seems reasonable for me. I don't think we should make

Re: [openstack-dev] [Ironic] Proposal to add a new repository

Hi, I see that ahc is storing its information in swift. That's clever, but if Ironic provided a blob store for each node, would that be better? I can try to answer that. The initial implementation was doing that but, AHC collect a fine-grained amount of data, e.g: * it runs benchmark on all

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

Hi, I don't want to have to diverge much from the topic of this thread, I've done this already as pointed out by Sean. But I feel like replying to this. Sorry I might be missing something. I don't think one thing justify the other, plus the problem seems to be the source of truth. I thought

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

Hi So if our min_version is 2.1 and the max_version is 2.50. That means alternative implementations need implement all the 50 versions api...that sounds pain... Yes, it's pain, but it's no different than someone who is following the Amazon EC2 API, which cuts releases at a regular

Re: [openstack-dev] [Ironic] ironic-lib library

Hi, I haven't paid any attention to ironic-lib; I just knew that we wanted to have a library of common code so that we didn't cut/paste. I just took a look[1] and there are files there from 2 months ago. So far, everything is under ironic_lib (ie, no subdirectories to group things). Going

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

Hi, Actually that makes an alternative implementation more valuable. Without microversions those alternative implementations would have to wait a long time to implement fixes to the API, but now can implement and publish the fix as soon as the microversion lands. This means that alternative

Re: [openstack-dev] [Ironic] When to bump the microversion?

Hi Ruby, Thanks for starting this thread, just like you I've been always confused about when and when not bump the microversioning of the API. Backwards compatible API adds with no user signaling is a fallacy because it assumes the arrow of time flows only one way. If at version 1.5 you have

Re: [openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

Hi Note, that will need some scheduling anyway, so that we can slow down a week before. So probably still some milestone process required, wdyt? We can cut a release and establish it one or two weeks before the official OpenStack release. But prior to that we can just cut a release whenever

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Thanks for all the work Ghe. The project will certainly miss you. Cheers, Lucas On Mon, May 25, 2015 at 5:45 PM, Ghe Rivero g...@debian.org wrote: My focus on the Ironic project has been decreasing in the last cycles, so it's about time to relinquish my position as a oslo-ironic liaison so new

Re: [openstack-dev] [Nova][Ironic] Large number of ironic driver bugs in nova

Hi I noticed last night that there are 23 bugs currently filed in nova tagged as ironic related. Whilst some of those are scheduler issues, a lot of them seem like things in the ironic driver itself. Does the ironic team have someone assigned to work on these bugs and generally keep an eye

Re: [openstack-dev] [wsme] [ironic] [ceilometer] [magnum] [kite] [tuskar] WSME unmaintained ?

On Fri, 17 Apr 2015, Lucas Alvares Gomes wrote: /me also deliberately volunteers cdent to wsme core :-) Feh. I suppose since most of the recent code and conversation has been you and me, that makes sense. If people agree, I'm happy to participate, but only if you're there too. That's only

Re: [openstack-dev] [wsme] [ironic] [ceilometer] [magnum] [kite] [tuskar] WSME unmaintained ?

Hi, * Should projects relying on WSME start thinking about migrating their APIs to another technology? Maybe not migrating, but at least not starting something new with it. Oh no, FWIW I don't even consider starting something new as a valid option here. Err, yeah, right. There are 4

[openstack-dev] [wsme] [ironic] [ceilometer] [magnum] [kite] [tuskar] WSME unmaintained ?

Hi, We have a couple of Openstack projects that uses WSME for their REST APIs[1], but WSME project looks abandoned. The review stats are not good, for the last 40 days the project didn't have a single review from a core reviewer[2], the bugs are not being triaged nor fixed [3], I have been trying

  1   2   >