Re: [openstack-dev] [ironic] inclusion of openstack/networking-generic-switch project under OpenStack baremetal program

2017-11-14 Thread Villalovos, John L
Thanks for sending this out. I would vote for Option 1. Thanks, John From: Pavlo Shchelokovskyy [mailto:pshchelokovs...@mirantis.com] Sent: Tuesday, November 14, 2017 8:16 AM To: OpenStack Development Mailing List (not for usage questions) Subject:

[openstack-dev] [Ironic] FYI: Making changes required for Ironic multi-node grenade to work

2017-03-13 Thread Villalovos, John L
In order for Ironic multi-node grenade testing work we have to correct a mistake we (well really I) made. We need to remove the enabling of the ironic plugin in our devstack/upgrade/settings file and move it to openstack-infra/project-config. As enabling the plugin in that file works for

Re: [openstack-dev] [ironic] Core team updates

2016-10-18 Thread Villalovos, John L
I just want to give a big thank you to Haomeng Wang and Chris Krelle for all their contributions to Ironic! And especially thanks to Chris (NobodyCam) for all of his help while I was learning about Ironic. It helps we were in the same timezone, so we overlapped in IRC often :) John >

[openstack-dev] [Ironic] The Ironic Grenade gate job is currently broken. Please don't do recheck on patches

2016-09-28 Thread Villalovos, John L
Currently the Ironic Grenade gate job is broken. Until the issue is resolved please don't do recheck on openstack/ironic patch. Work is ongoing to figure out why it stopped working. __ OpenStack Development Mailing List

[openstack-dev] [Ironic] QA Meeting cancelled today

2016-09-07 Thread Villalovos, John L
To focus on the Newton work. The Ironic QA meeting is cancelled for today. Thanks, John __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

2016-08-19 Thread Villalovos, John L
> -Original Message- > From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] > Sent: Friday, August 19, 2016 7:15 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [ironic] Driver removal policies -

Re: [openstack-dev] [ironic] UFCG OneView CI comments missing recheck command

2016-06-28 Thread Villalovos, John L
> -Original Message- > From: Thiago Paiva [mailto:thia...@lsd.ufcg.edu.br] > Sent: Tuesday, June 28, 2016 17:00 > To: OpenStack Development Mailing List (not for usage questions) > Cc: ufcg-oneview...@lsd.ufcg.edu.br > Subject: Re: [openstack-dev] [ironic] UFCG OneView CI comments

[openstack-dev] [Ironic] Grenade non-voting test results

2016-06-17 Thread Villalovos, John L
TL;DR: In my opinion Grenade job is performing reliably. Using the table at: http://ci-watch.tintri.com/project?project=ironic=7+days Note: Unable to extract the data out of the web page to do more thorough data evaluation. The Grenade job appears to be performing successfully. On Thursday

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

2016-06-16 Thread Villalovos, John L
> -Original Message- > From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] > Sent: Thursday, June 16, 2016 08:13 > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [ironic] Proposing two new cores > > Hi all, > > I'd like to propose Jay Faulkner (JayF) and Sam Betts

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

2016-05-16 Thread Villalovos, John L
> -Original Message- > From: Lucas Alvares Gomes [mailto:lucasago...@gmail.com] > What I don't think we should do is say that the library's _right now_ > ready for it, the interfaces we have at the moment should not be > considered stable, Ironic is very opinionated in many aspects >

Re: [openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

2016-05-13 Thread Villalovos, John L
> From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] > On Thu, May 12, 2016 at 06:48:02AM -0400, Sean Dague wrote: > > Let me make sure I understand the crux of the issue: services may need > > to create additional custom networking in order for the rest of the > > resource flow to work

[openstack-dev] [Ironic] Grenade testing work

2016-05-02 Thread Villalovos, John L
During the OpenStack Summit it was decided that getting Grenade to work for Ironic would be the highest priority for the Ironic project. Because without Grenade, we won't have upgrade testing and we need upgrade testing for features we want to land to ensure we don't break anything. We will be

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

2016-03-24 Thread Villalovos, John L
+1 for me. Julia has been an awesome resource and person in the Ironic community :) John -Original Message- From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] Sent: Thursday, March 24, 2016 12:09 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [ironic] Nominating

[openstack-dev] [Ironic] Preparing for functional testing in Ironic. Will likely break any in-flight patches.

2015-09-28 Thread Villalovos, John L
Just to give a heads up to people. I have proposed the following patch: https://review.openstack.org/228612 This moves the tests in ironic/tests/ to ironic/tests/unit/ Likely this patch will break most in-flight patches, so rebasing will be required when this patch goes in. If you have any

[openstack-dev] [Ironic] Functional testing for Ironic. Interested parties wanted

2015-08-27 Thread Villalovos, John L
Hello, I'm John Villalovos aka jlvillal on IRC. I am working primarily on the Ironic project and have been asked to work on functional testing for Ironic. My main starting focus will be the openstack/python-ironicclient and openstack/ironic projects. I am trying to find out who else would be

[openstack-dev] [Ironic] Python 3.4 unit tests enabled on the gate for openstack/ironic

2015-05-13 Thread Villalovos, John L
With this commit: https://review.openstack.org/181034 Python 3.4 unit tests are now being run for openstack/ironic. The unit tests are a voting job. Thanks to Victor Sergeyev for all of his work to update the Ironic code to make it pass the unit tests using Python 3.4: