Re: [openstack-dev] [Spam] Re: [Openstack][TripleO] [Ironic] What if undercloud machines down, can we reboot overcloud machines?

On August 28, 2014 8:58:11 AM PDT, Clint Byrum cl...@fewbar.com wrote: Excerpts from Jyoti Ranjan's message of 2014-08-27 21:20:19 -0700: I do agree but it create an extra requirement for Undercloud if we high availability is important criteria. Because of this, undercloud has to be there

Re: [openstack-dev] [Ironic] [Horizon] Ironic Horizon API

On September 2, 2014 9:28:15 PM PDT, Akihiro Motoki amot...@gmail.com wrote: Hi, Good to know we will have Ironic support. I can help the integration. Let me clarify the situation as Horizon core team. I wonder why it is ASAP. Horizon is released with integrated projects and it is true in Juno

Re: [openstack-dev] [Ironic] Error in deploying ironicon Ubuntu 12.04

On September 11, 2014 3:52:59 AM PDT, Lucas Alvares Gomes lucasago...@gmail.com wrote: Oh, it's because Precise doesn't have the docker.io package[1] (nor docker). AFAIK the -infra team is now using Trusty in gate, so it won't be a problem. But if you think that we should still support Ironic

Re: [openstack-dev] [tripleo][heat][ironic] Heat Ironic resources and ready state orchestration

On Mon, Sep 15, 2014 at 12:44:24PM +0100, Steven Hardy wrote: All, Starting this thread as a follow-up to a strongly negative reaction by the Ironic PTL to my patches[1] adding initial Heat-Ironic integration, and subsequent very detailed justification and discussion of why they may be

Re: [openstack-dev] [Ironic][Agent]

On April 4, 2014 at 9:12:56 AM, Devananda van der Veen (devananda@gmail.com) wrote: Ironic's responsibility ends where the host OS begins. Ironic is a bare metal provisioning service, not a configuration management service. +1 // jim ___

Re: [openstack-dev] [Ironic] Nominating David Shrewsbury to ironic-core

Unclear if I get a vote, but if so, +1 it is. :) On July 11, 2014 4:18:55 PM PDT, Chris K nobody...@gmail.com wrote: another +1 from /me. On Fri, Jul 11, 2014 at 3:50 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all! While David (Shrews) only began working on Ironic in

Re: [openstack-dev] [Ironic] Proposal for slight change in our spec process

On August 7, 2014 at 8:36:16 AM, Matt Wagner (matt.wag...@redhat.com) wrote: On 07/08/14 14:17 +0200, Dmitry Tantsur wrote:  snip  2. We'll need to speed up spec reviews, because we're adding one more  blocker on the way to the code being merged :) Maybe it's no longer a  problem actually, we're

Re: [openstack-dev] [Ironic][Agent]

Guys, thank you very much for your comments, I thought a lot about why we need to be so limited in IPA use cases. Now it much clearer for me. Indeed, having some kind of agent running inside host OS is not what many people want to see. And now I'd rather agree with that. But there are still

[openstack-dev] [Ironic] Merging the agent driver

Hi all, As Deva requested, our team put up a merge request for the IPA driver (https://review.openstack.org/#/c/84795/) as soon as Juno opened. We’ve continued to update this patch and iterate on the agent model. We are doing our best not to get too far ahead of master, but we also want to get

[openstack-dev] [Ironic] Status of the agent driver

Hi folks! Deva and I talked a bit more about the agent driver last night, and I wanted to give everyone a quick status update on where we stand with merging the agent driver into Ironic itself. First off, we’ve taken all of the agent driver patches we had and squashed them into the main agent

Re: [openstack-dev] [Ironic] Node uuid and Nova Hypervisor ID

Hi François, You can hit the Ironic nodes API and filter by instance_uuid. Something like: curl http://ironic:6385/v1/nodes?instance_uuid=blablabla Hope that helps. // jim On May 6, 2014 at 2:28:30 AM, François Rossigneux (francois.rossign...@inria.fr) wrote: Hi all, I need to retrieve the

Re: [openstack-dev] [Ironic] A mascot for Ironic

On Sun, Nov 16, 2014 at 01:14:13PM +, Lucas Alvares Gomes wrote: Hi Ironickers, I was thinking this weekend: All the cool projects does have a mascot so I thought that we could have one for Ironic too. The idea about what the mascot would be was easy because the RAX guys put bear

Re: [openstack-dev] [Ironic] Proposing new meeting times

On Tue, Nov 18, 2014 at 01:00:04AM +, Devananda van der Veen wrote: Hi all, As discussed in Paris and at today's IRC meeting [1] we are going to be alternating the time of the weekly IRC meetings to accommodate our contributors in EMEA better. No time will be perfect for everyone, but as

[openstack-dev] [Ironic] Weekly Status Update

Hi all, Ironic has decided to email a weekly status report for all subteams. This is the inaugural issue of that. :) This is and will be a copy and paste from the Ironic whiteboard.[0] Testing (adam_g) (deva) - make Ironic voting -- needs to be rebased again, but has been approved Bugs

Re: [openstack-dev] [nova] [ironic] how to remove check-tempest-dsvm-ironic-pxe_ssh on Nova check

On Tue, Nov 25, 2014 at 08:02:56AM -0500, Sean Dague wrote: When at Summit I discovered that check-tempest-dsvm-ironic-pxe_ssh is now voting on Nova check queue. The reasons given is that the Nova team ignored the interface contract that was being provided to Ironic, broke them, so the Ironic

[openstack-dev] [Ironic] Weekly subteam status report

Hi all, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Testing (adam_g) - Nova stable merges are being bit by a race in the sideways grenade job: https://bugs.launchpad.net/devstack/+bug/1398128 /

Re: [openstack-dev] [Ironic] Fuel agent proposal

as the first step. For sure this is going to have a lot more steps to make it better and more generic. On 09 Dec 2014, at 01:46, Jim Rollenhagen j...@jimrollenhagen.com wrote: On December 8, 2014 2:23:58 PM PST, Devananda van der Veen devananda@gmail.com wrote: I'd like to raise

[openstack-dev] [Ironic] Weekly subteam status report

Hi all, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Testing (adam_g) Bugs (dtantsur) (as of Mon, 8 Dec 17:00 UTC) Open: 108 (+6). 5 new (+1), 26 in progress (+1), 0 critical, 12 high (+2) and 3 incomplete

Re: [openstack-dev] [Ironic] thoughts on the midcycle

On Mon, Dec 29, 2014 at 10:45:57PM +, Devananda van der Veen wrote: I'm sending the details of the midcycle in a separate email. Before you reply that you won't be able to make it, I'd like to share some thoughts / concerns. In the last few weeks, several people who I previously thought

[openstack-dev] [Ironic] Weekly subteam status report

Hi all, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (As of Mon, 19 Jan, 11:00 UTC) Open: 122 (-11). 4 new (-10), 31 in progress (-1), 0 critical (-1), 14 high (+1) and 6

Re: [openstack-dev] [Ironic] RAID interface - backing disk hints

On Tue, Jan 20, 2015 at 07:28:46PM +0530, Ramakrishnan G wrote: Hi All, This is regarding the RAID configuration spec that was posted for review some time back: https://review.openstack.org/#/c/135899/ This review consists of a generic RAID interface currently proposed jointly by Redhat

Re: [openstack-dev] [Ironic] Weekly subteam status report

On Tue, Jan 20, 2015 at 06:41:50AM -0800, Jim Rollenhagen wrote: Hi all, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (As of Mon, 19 Jan, 11:00 UTC) Open: 122 (-11). 4 new (-10), 31

[openstack-dev] [Ironic] Weekly subteam status report

Hi all, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. I'm going to start keeping this trimmed down to just the new stuff. Drivers iRMC (naohirot) [power driver] needs code review towords kilo-2:

[openstack-dev] [Ironic] Bay Area Midcycle

Hi all, Devananda proposed having a second Ironic midcycle meetup a few weeks ago.[0] Well, it's happening. :) To be clear, this is a developer-focused code sprint, *not* a planning meeting. We want to land code, not write specs or plan roadmaps. The meetup will be February 11-13 at Rackspace

Re: [openstack-dev] [Ironic] Bay Area Midcycle

On Tue, Jan 13, 2015 at 10:28:08AM -0800, Jim Rollenhagen wrote: Hi all, Devananda proposed having a second Ironic midcycle meetup a few weeks ago.[0] Well, it's happening. :) Oops, forgot my link here: http://lists.openstack.org/pipermail/openstack-dev/2014-December/053618.html // jim

[openstack-dev] [Ironic] Weekly subteam status report

Hi all, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (As of Mon, 12 Jan, 12:00 UTC) Open: 133 (+15). 14 new (+5), 32 in progress (+3), 1 critical (+1), 13 high (+2) and 5

Re: [openstack-dev] [Ironic] proposing rameshg87 to ironic-core

Ramakrishnan has clearly been reviewing tons of code lately, and more importantly the quality of the reviews and the knowledge of the code base, the problem space, and the edge cases has shown through as nothing short of awesome. Enthusiastic +2 from me! // jim On Mon, 2015-03-09 at 22:03

Re: [openstack-dev] [Glance] Nitpicking in code reviews

On Thu, Mar 12, 2015 at 09:07:30AM -0500, Flavio Percoco wrote: On 11/03/15 15:06 -1000, John Bresnahan wrote: FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough thing to get right and speaks to the quality standard to which the product is held even in commit messages

Re: [openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

I’m not sure that recommending one or the other is best. We should lay out the options (as you just did) and let folks decide what works best for them. For things like discoverd, where you have many users, perhaps you should allow the user to pass a version (for example, option 2 depends on the

Re: [openstack-dev] [Ironic] weekly meetings and sub-team reports and people

On Tue, Jun 09, 2015 at 04:33:41PM -0400, Ruby Loo wrote: Hi, I noticed (from reading the logs[1]) that there weren't many folks in this week's weekly meeting. And no cores attended. And the sub-team reports (in our etherpad[2]) were woefully lacking. I guess that means only driver

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On Tue, Jun 16, 2015 at 08:56:37AM +0200, Dmitry Tantsur wrote: On 06/04/2015 08:58 AM, Xu, Hejie wrote: Hi, guys, I’m working on adding Microversion into the API-WG’s guideline which make sure we have consistent Microversion behavior in the API for user. The Nova and Ironic already have

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

On Thu, May 28, 2015 at 12:55:50PM -0700, Jim Rollenhagen wrote: [snip] I also put an informational spec about this change up in the ironic-specs repo: https://review.openstack.org/#/c/185171/. My goal was to discuss this in the spec, but the mailing list is fine too. There are some

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

On Mon, Jun 15, 2015 at 01:07:39PM -0400, Jay Pipes wrote: It has come to my attention in [1] that the microversion spec for Nova [2] and Ironic [3] have used the project name -- i.e. Nova and Ironic -- instead of the name of the API -- i.e. OpenStack Compute and OpenStack Bare Metal -- in the

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

On Thu, May 28, 2015 at 12:54:58PM -0400, Monty Taylor wrote: On 05/28/2015 12:41 PM, Devananda van der Veen wrote: Hi all, tl;dr; At the summit, the Ironic team discussed the challenges we've had with the current release model and came up with some ideas to address them. I had a

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

On Wed, Aug 19, 2015 at 09:48:29AM +0100, Lucas Alvares Gomes wrote: 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

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

On Thu, Aug 20, 2015 at 09:57:14PM +0100, Lucas Alvares Gomes wrote: 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

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

On Tue, Jul 28, 2015 at 09:55:03PM -0400, Julia Kreger wrote: So if we do this, simply shipping the code doesn't break anyone. Nobody has disagreed on this yet, best I can tell. So let's ship some code. :) // jim I'm not sure we can just ship some code, unless I've missed

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

On Thu, Jul 30, 2015 at 09:27:42AM +0200, Dmitry Tantsur 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 driver

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

On Tue, Aug 04, 2015 at 09:52:40AM +0100, Lucas Alvares Gomes wrote: 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

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

On Fri, Jul 31, 2015 at 02:37:52PM -0700, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-07-31 04:14:54 -0700: On 07/30/2015 04:58 PM, Devananda van der Veen wrote: snip Thoughts? * I'm assuming it is possible to make micro version changes to the 1.x

Re: [openstack-dev] [Cinder][Ironic] A possible solution for HA Active-Active

On Fri, Jul 31, 2015 at 12:47:34PM -0700, Joshua Harlow wrote: Joshua Harlow wrote: Mike Perez wrote: On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlowharlo...@outlook.com wrote: ...random thought here, skip as needed... in all honesty orchestration solutions like mesos

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

On Tue, Jul 28, 2015 at 08:23:34PM +, Devananda van der Veen wrote: On Mon, Jul 27, 2015 at 4:58 PM Sean Dague s...@dague.net wrote: On 07/27/2015 07:10 PM, Jim Rollenhagen wrote: On Mon, Jul 27, 2015 at 03:28:49PM -0700, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015

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

replying... so bear with me ... On Mon, Jul 27, 2015 at 1:36 PM Jim Rollenhagen j...@jimrollenhagen.com wrote: Hi friends. Ironic implemented API micro versions in Kilo. We originally did this to allow for breaking changes in the API while allowing users to opt in to the breakage

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

On Tue, Jul 28, 2015 at 09:19:46PM +, Devananda van der Veen wrote: On Tue, Jul 28, 2015 at 1:57 PM Jim Rollenhagen j...@jimrollenhagen.com wrote: On Tue, Jul 28, 2015 at 08:23:34PM +, Devananda van der Veen wrote: On Mon, Jul 27, 2015 at 4:58 PM Sean Dague s...@dague.net wrote

Re: [openstack-dev] [Ironic] Was there a meeting yesterday (August 4, 2015 at 0500 UTC)

On Wed, Aug 05, 2015 at 09:13:18AM -0400, Ruby Loo wrote: Hi, Was there an ironic meeting yesterday (August 4, 2015 at 0500 UTC)? I don't see any meeting logs from then. There was not.

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

On Mon, Jul 27, 2015 at 01:35:25PM -0700, Jim Rollenhagen wrote: Now we've landed a patch[0] with a new version (1.11) that is not backward compatible. It causes newly added Node objects to begin life in the ENROLL state, rather than AVAILABLE. This is a good thing, and people should want

[openstack-dev] [Ironic] Specs tree re-organization

Hi folks, To align with our independent release model, we also re-organized our specs tree. New specs should be proposed to the approved directory. The proposal process is documented further in the README[0]. I've gone through existing specs proposals and placed a -1 on specs proposing to the

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

Hi friends. Ironic implemented API micro versions in Kilo. We originally did this to allow for breaking changes in the API while allowing users to opt in to the breakage. Since then, we've had a default version for our client that we bump to something sensible with each release. Currently it is

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

On Mon, Jul 27, 2015 at 03:28:49PM -0700, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-07-27 13:41:20 -0700: So the CLI should actually break less often, and will expose the most functionality you can get out of your cloud. What I find odd about this is that I want the

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

On Thu, Jul 16, 2015 at 04:23:29PM -0400, Mathieu Gagné wrote: Hi, I stubble on this review [1] which proposes adding info about provider networks in network_data.json. snip [1] https://review.openstack.org/#/c/152703/5 Just to loop back on this - we talked about it a bit at the Nova

Re: [openstack-dev] [Ironic] NoFreeConductorWorker going away with move to Futurist?

On Wed, Jul 22, 2015 at 02:40:47PM +0200, Dmitry Tantsur wrote: Hi all! Currently _spawn_worker in the conductor manager raises NoFreeConductorWorker if pool is already full. That's not very user friendly (potential source of retries in client) and does not map well on common async worker

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

On Fri, Jul 17, 2015 at 01:06:46PM +0100, John Garbutt wrote: On 17 July 2015 at 11:23, Sean Dague s...@dague.net wrote: On 07/16/2015 06:06 PM, Sean M. Collins wrote: On Thu, Jul 16, 2015 at 01:23:29PM PDT, Mathieu Gagné wrote: So it looks like there is a missing part in this feature.

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

the instance should tag packets, +1, I think that should work. // jim On Fri, Jul 17, 2015 at 9:51 AM, Jim Rollenhagen j...@jimrollenhagen.com wrote: On Fri, Jul 17, 2015 at 01:06:46PM +0100, John Garbutt wrote: On 17 July 2015 at 11:23, Sean Dague s...@dague.net wrote: On 07/16/2015

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

On Fri, Jul 17, 2015 at 10:43:37AM -0700, Jim Rollenhagen wrote: On Fri, Jul 17, 2015 at 10:56:36AM -0600, Kevin Benton wrote: Check out my comments on the review. Only Neutron knows whether or not an instance needs to do manual tagging based on the plugin/driver loaded. For example

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

want to quash that ASAP. As far as Neutron sending the flag to decide whether the instance should tag packets, +1, I think that should work. // jim On Fri, Jul 17, 2015 at 9:51 AM, Jim Rollenhagen j...@jimrollenhagen.com wrote: On Fri, Jul 17, 2015 at 01:06:46PM +0100, John

Re: [openstack-dev] [nova] Exposing provider networks in network_data.json

On Mon, Jul 20, 2015 at 12:56:10PM +, Sean M. Collins wrote: On Sun, Jul 19, 2015 at 02:26:32PM EDT, Jim Rollenhagen wrote: For a little background, this patch came from code that is running in production today, where we're trunking two VLANs down to the host -- it isn't a theoretical

Re: [openstack-dev] [Ironic] how about those alternating meeting times?

On Mon, Jul 13, 2015 at 06:41:55PM +, Devananda van der Veen wrote: This is a much-overdue follow up to this poll, which got 17 responses. snip So, though it saddens me, I would like to propose that we change back to a single meeting time effective the week following our midcycle (Aug

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

On Tue, Jul 21, 2015 at 02:24:14PM +0200, Dmitry Tantsur wrote: Hi folks! If you're not aware already, I'm working on solving node is locked problems breaking users (and tracking it at https://etherpad.openstack.org/p/ironic-locking-reform). We have retries in place in client, but we all

Re: [openstack-dev] [ironic] Ironic design summit schedule

On Thu, Oct 22, 2015 at 12:48:07AM -0700, Wan-yen Hsu wrote: > Hi Jim, > > I have asked techtalk coordinator to switch my techtalk session time so > there is no need to change group management session schedule. You can keep > it at 2:50pm Wed.. Thanks! Okay, I've now moved these back to the

Re: [openstack-dev] [ironic] Ironic design summit schedule

On Wed, Oct 21, 2015 at 02:24:08PM -0700, Wan-yen Hsu wrote: > Hi Jim, > >My techtalk is supposed to finish by 2:45pm. However, techtalk schedule > is not as well monitored as formal sessions so it could get delayed. > That's why I was exploring whether the group management session can be >

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On Wed, Oct 21, 2015 at 03:30:05PM -0700, Wan-yen Hsu wrote: > As mentioned in the weekly IRC, 3rd-party vendor drivers are ranked lower > priority and therefore their code tend to merge at the late cycle of a > release. Therefore, it leads little time for driver author to submit > document and

[openstack-dev] [ironic] Next meeting is November 9

Hi folks, Since we'll all be at the summit next week, and presumably recovering the following week, the next Ironic meeting will be on November 9, in the usual place and time. See you there! :) // jim __ OpenStack

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

On Wed, Nov 11, 2015 at 12:16:34PM -0500, Ruby Loo wrote: > On 10 November 2015 at 12:08, Dmitry Tantsur wrote: > > > On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: > > > >> Hi, > >> > >> In the last Ironic meeting [1] we started a discussion about whether > >> we need

Re: [openstack-dev] [Ironic][Nova][Neutron] Multi-tenancy support

On Mon, Nov 16, 2015 at 06:38:28PM +, Sean M. Collins wrote: > On Mon, Nov 16, 2015 at 12:47:13PM EST, Vasyl Saienko wrote: > > [0] https://github.com/jumpojoy/neutron > > The way you created the repository in GitHub, it is impossible to diff > it against master to see what you did. > >

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

On Tue, Nov 10, 2015 at 12:19:08PM +, Sam Betts (sambetts) wrote: > So you would end up with a set of commands that look like this: After reading through this thread, I think this is mostly good, other than some word choices. I've changed a few inline to feel more natural (IMHO of course). :)

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

On Wed, Nov 04, 2015 at 02:55:49PM -0500, Sean Dague wrote: > On 11/04/2015 02:42 PM, Jim Rollenhagen wrote: > > On Wed, Nov 04, 2015 at 04:08:18PM -0300, Gabriel Bezerra wrote: > >> Em 04.11.2015 11:32, Jim Rollenhagen escreveu: > >>> On Wed, Nov 04, 2015 at 08:

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

On Wed, Nov 04, 2015 at 04:08:18PM -0300, Gabriel Bezerra wrote: > Em 04.11.2015 11:32, Jim Rollenhagen escreveu: > >On Wed, Nov 04, 2015 at 08:44:36AM -0500, Jay Pipes wrote: > >On 11/03/2015 11:40 PM, Gabriel Bezerra wrote: > >>Hi, > >> > >>The cha

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

On Thu, Nov 05, 2015 at 11:55:50AM -0500, Jay Pipes wrote: > On 11/04/2015 04:21 PM, Shraddha Pandhe wrote: > >Hi Salvatore, > > > >Thanks for the feedback. I agree with you that arbitrary JSON blobs will > >make IPAM much more powerful. Some other projects already do things like > >this. > > :(

[openstack-dev] [ironic] Mitaka priorities

Hi folks, I posted a review to add our Mitaka priorities to our specs repo: https://review.openstack.org/#/c/241223/ Ruby made a good point that not everyone was at the summit and she'd like buyoff on the patch from all cores before we land it. I tend to agree, so I ask that cores that were not

[openstack-dev] [ironic] Summit recap

Hi friends, I wrote a recap of the summit (from my perspective) that some of you may find interesting. Feedback is very welcome. :) http://words.jimrollenhagen.com/mitaka-summit-recap/ // jim __ OpenStack Development

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

On Wed, Nov 04, 2015 at 12:19:37PM -0800, Jim Rollenhagen wrote: [snip] > Yeah, no worries there. So you're good with unreleased changes just > being 3 months, no cycle boundaries? If so, I'll push up a change to the > governance repo for that. That change is here: https://review.open

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

On Wed, Oct 14, 2015 at 08:44:08AM +, Tan, Lin wrote: > Hi guys, > > I am looking at https://bugs.launchpad.net/ironic/+bug/1502903 which > is related to rolling upgrade and here is Jim's patch > https://review.openstack.org/#/c/234450 I really have a concern or > question about how to do

Re: [openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

On Wed, Oct 07, 2015 at 12:41:55PM -0700, Devananda van der Veen wrote: > Ramesh, > > I thought about your points over night, and then looked at our in-tree > driver code from stable/kilo and asked myself, "what if this driver was out > of tree?" They'd all have broken -- for very similar reasons

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On Thu, Oct 15, 2015 at 09:23:18PM +0530, Ramakrishnan G wrote: > Hi All, > > This mail is related to driver-specific documentation in Ironic. > > First a bit of context. I work on iLO drivers in Ironic. Our team would > like to document both Ironic driver related stuff (which is related to >

Re: [openstack-dev] [ironic] [horizon] ironic panels

On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: > > Hi all, > > I am currently in the process of writing an Ironic panel in Horizon > upstream. It was originally intended for this panel to be written in > Angular JS, however, as I understand, no horizon angular work will > merge for

Re: [openstack-dev] [ironic] Ironic design summit schedule

On Mon, Oct 19, 2015 at 02:33:57PM -0700, Wan-yen Hsu wrote: > Hi Jim, > > Is it possible to switch Group management session to Thursday? I > have a techtalk at 2:30pm on Wednesday and it makes it very tight for me > and Shiv to attend the group management at 2:50 pm. Since Shiv and

[openstack-dev] [release][ironic] Announcing Ironic 4.2.1

Hi all, We're excited to announce the release of Ironic 4.2.1. This is a patch release in the OpenStack Liberty series. This release imports Japanese translations as our first translated language, and also fixes some bugs around running on systems with the Japanese locale. Release notes can be

Re: [openstack-dev] [Ironic] OpenStack Ironic dinner

BadCub and I have been working to find a venue that can host that many people, and haven't had any luck at all. :( I think we'll need to skip a formal team dinner this time, sorry folks. I'd still love to do something informal on Thursday night with some of you - we can work it out next week. //

Re: [openstack-dev] [ironic] [horizon] ironic panels

On Tue, Oct 20, 2015 at 04:50:04PM +0100, Beth Elwell wrote: > Hi Jim, > > I have replied inline to your comments below: > > On 19/10/2015 19:38, Jim Rollenhagen wrote: > >On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: > >>Hi all, > >> >

Re: [openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

Cross posting to the ops list for visibility. To follow up on this, we decided not to fix this after all. Besides Ramesh's (very valid) points below, we realized that fixing this for out of tree drivers that depended on Kilo behavior would break out of tree drivers that implemented their own boot

Re: [openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

One more try on the ops list as it turns out I wasn't subscribed... :( // jim > On Oct 14, 2015, at 17:39, Jim Rollenhagen <j...@jimrollenhagen.com> wrote: > > Cross posting to the ops list for visibility. > > To follow up on this, we decided not to fix this after al

[openstack-dev] [ironic] Ironic design summit schedule

Hey all, I sorted out the design summit schedule today, attempting to reduce conflicts and such as much as possible. The schedule is here: http://mitakadesignsummit.sched.org/type/Ironic I created a general summit etherpad for us, that is here:

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

On Wed, Oct 14, 2015 at 04:09:07PM -0700, Dan Smith wrote: > > Conductors will always need to talk to the database. APIs may not need > > to talk to the database. I think we can just roll conductor > > upgrades through, and then update ironic-api after that. This should > > just work, as long as

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

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 to core based on a good knowledge of *some* of the code base, and trust them not to +2 things they

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

On Thu, Oct 08, 2015 at 02:47:01PM -0700, 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

Re: [openstack-dev] [Neutron][Ironic] Testing Ironic multi-tenancy feature

On Mon, Oct 12, 2015 at 07:45:55AM +, Pavlo Shchelokovskyy wrote: > Hi all, > > we would like to start preliminary testing of Ironic multi-tenant network > setup which is supported by Neutron in Liberty according to [1]. According > to Neutron design integration with network equipment is done

[openstack-dev] [release][ironic] Announcing ironic-python-agent 1.0.0

Hi all, We're ecstatic to announce the release of ironic-python-agent 1.0.0. This is the first ever release of this project, and is the basis for a stable/liberty branch. We will continue to do intermediary releases and stable branches for IPA, following Ironic's release model. IPA is the heart

Re: [openstack-dev] [ironic] final release in Liberty cycle

On Thu, Aug 27, 2015 at 10:53:43PM -0400, Ruby Loo wrote: > Hi, > > As (most of) you are aware, in this cycle, ironic decided to switch to a > feature-based release model[0]. > > Our first semver release, 4.0.0, was tagged this week but a few more things > need to be ironed out still (hopefully

[openstack-dev] [Ironic] ironic-lib updates

Hi all, As you know, we've been working toward moving some code to ironic-lib[0] to be consumed by both Ironic and ironic-python-agent. Today I've created a new Launchpad project[1] for ironic-lib, as the managed release process requires a separate Launchpad for each deliverable. I've also

Re: [openstack-dev] [all] Mitaka Design Summit - Proposed slot allocation

On Fri, Sep 04, 2015 at 01:52:41PM +0200, Dmitry Tantsur wrote: > On 09/04/2015 12:14 PM, Thierry Carrez wrote: > >Hi PTLs, > > > >Here is the proposed slot allocation for every "big tent" project team > >at the Mitaka Design Summit in Tokyo. This is based on the requests the > >liberty PTLs have

Re: [openstack-dev] OpenStack support for Amazon Concepts - was Re: cloud-init IPv6 support

> On Sep 6, 2015, at 09:43, Monty Taylor wrote: > >> On 09/05/2015 06:19 PM, Sean M. Collins wrote: >>> On Fri, Sep 04, 2015 at 04:20:23PM EDT, Kevin Benton wrote: >>> Right, it depends on your perspective of who 'owns' the API. Is it >>> cloud-init or EC2? >>> >>> At

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

On Tue, Sep 01, 2015 at 07:17:56AM -0400, Sean Dague wrote: > The current failure rate for the ironic pxe_ssh job is 100% - >

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

> On Sep 1, 2015, at 04:32, Lucas Alvares Gomes wrote: > > Hi, > >> The current failure rate for the ironic pxe_ssh job is 100% - >>

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

On Tue, Sep 01, 2015 at 09:21:39AM -0400, Julia Kreger wrote: > On Tue, Sep 1, 2015 at 9:17 AM, Jim Rollenhagen <j...@jimrollenhagen.com> > wrote: > > > > > Why don't we just use the pre-built agent ramdisks we already publish? > > AFAIK we already have a job for

[openstack-dev] [Ironic] Liberty release plans

Hi all, I wanted to lay down my thoughts on the rest of the cycle here. As you may know, we recently released Ironic 4.0.0. We've also released python-ironicclient 0.8.0 and ironic-lib 0.1.0 this week. Yay! I'd like to do two more server releases this cycle. * 4.1.0 - minor release to clean up

[openstack-dev] [Ironic] Introducing ironic-lib 0.1.0

Hi all, I'm proud to announce the initial release of ironic-lib! This library was built to share code between various Ironic projects. The initial release contains an up-to-date copy of Ironic's disk partitioning code, to be shared between Ironic and ironic-python-agent. At the beginning of the

Re: [openstack-dev] [Ironic] Suggestion to split install guide

On Fri, Sep 11, 2015 at 10:56:07AM +0200, Dmitry Tantsur wrote: > Hi all! > > Our install guide is huge, and I've just approved even more text for it. > WDYT about splitting it into "Basic Install Guide", which will contain bare > minimum for running ironic and deploying instances, and "Advanced

[openstack-dev] [Ironic] PTL Candidacy

Hi friends, I'd like to throw in my hats (yes, all of them, I'll get to that shortly) for the Ironic PTL election. In case you don't immediately recognize me, I'm 'jroll' on IRC, where you can always find me. I've been working on the Ironic project for a year and a half now, as one of an

[openstack-dev] [ironic] [tripleo] Deprecating the bash ramdisk

Hi all, We have a spec[0] for deprecating our bash ramdisk during Liberty, so we can remove it in Mitaka and have everything using IPA. The last patch remaining[1] is to mark it deprecated in disk-image-builder. This has been sitting with 4x +2 votes for 3 weeks or so now. Is there any reason we

Re: [openstack-dev] Apache2 vs uWSGI vs ...

On Thu, Sep 17, 2015 at 06:48:50PM -0400, Davanum Srinivas wrote: > In the fuel project, we recently ran into a couple of issues with Apache2 + > mod_wsgi as we switched Keystone to run . Please see [1] and [2]. > > Looking deep into Apache2 issues specifically around "apache2ctl graceful" > and

  1   2   3   4   5   >