Sorry to see you go Sam. You were a big asset to the community! Good luck
for the future.
John
On Thu, Oct 11, 2018 at 4:41 AM Sam Betts (sambetts)
wrote:
> As many of you will have seen on IRC, I've mostly been appearing AFK for
> the last couple of development cycles. Due to other tasks
Good morning Ironic,
I have come to realize that I don't have the time needed to be able to
devote the attention needed to continue as an Ironic core.
I'm hopeful that in the future I will work on Ironic or OpenStack again! :)
The Ironic (and OpenStack) community has been a great one and I have
Very sorry to see you go :( You have been a great contributor to Ironic!
And a pleasure to work with.
Best of luck for you and your future :)
John
On Fri, Feb 23, 2018 at 1:02 AM, Vasyl Saienko
wrote:
> Hey Ironic community!
>
> Unfortunately I don't work on Ironic as
+1
On Mon, Feb 5, 2018 at 10:12 AM, Julia Kreger
wrote:
> I would like to nominate Hironori Shiina to ironic-core. He has been
> working in the ironic community for some time, and has been helping
> over the past several cycles with more complex features. He has
>
I have updated the bug with info I found out:
https://bugs.launchpad.net/oslo.serialization/+bug/1728368
Also I did a test patch with a proposed change:
https://review.openstack.org/#/c/535166/
This patch causes the unit tests to work.
As a note there is a deprecation warning in the current
The ironic tempest plugin code that was in openstack/ironic and
openstack/ironic-inspector has been moved to
openstack/ironic-tempest-plugin/
As of 10-Jan-2018 (Wednesday) the plugin code was deleted from
openstack/ironic and openstack/ironic-inspector. All users of the tempest
plugin code need
in this thread (15-Dec-2017) about
removing the code.
Thanks,
John
On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <openstack@sodarock.com
> wrote:
> I wanted to send out a note to any 3rd Party CI or other users of the
> tempest plugin code inside either openstack/ironic or
> o
Please feel free to reach out to me (jlvillal) on IRC (#openstack-ironic)
or here if anyone has questions on how to transition over. For our Ironic
jobs it was about a 4 line change per job.
See the openstack/ironic patch here:
https://review.openstack.org/#/c/527730/
Basically need to bring in
weeks.
>
> Thanks,
>
> Arkady
>
>
>
> *From:* John Villalovos [mailto:openstack@sodarock.com]
> *Sent:* Monday, December 18, 2017 10:59 AM
> *To:* openstack-dev <openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Ironic] Removal of tem
/ironic and openstack/ironic-inspector on Tuesday
19-Dec-2017. If your CI depends on that code, please update to use the new
openstack/ironic-tempest-plugin repository.
On Mon, Dec 18, 2017 at 8:33 AM, John Villalovos <openstack@sodarock.com
> wrote:
>
>
> On Fri, Dec 15, 2017 a
On Fri, Dec 15, 2017 at 7:27 AM, John Villalovos <openstack@sodarock.com
> wrote:
> I wanted to send out a note to any 3rd Party CI or other users of the
> tempest plugin code inside either openstack/ironic or
> openstack/ironic-inspector. That code has been migrated to the
>
I wanted to send out a note to any 3rd Party CI or other users of the
tempest plugin code inside either openstack/ironic or
openstack/ironic-inspector. That code has been migrated to the
openstack/ironic-inspector-plugin repository. We have been busily (
Does this mean we can now get more user friendly names for the log files?
Currently I see names like:
screen-dstat.txt.gz
screen-etcd.txt.gz
screen-g-api.txt.gz
screen-g-reg.txt.gz
screen-ir-api.txt.gz
screen-ir-cond.txt.gz
screen-keystone.txt.gz
screen-n-api-meta.txt.gz
screen-n-api.txt.gz
Hi Infra,
We were hoping to get a review of:
https://review.openstack.org/483059
Add the ironic-inspector services to features.yaml
openstack-infra/devstack-gate
As it is needed to fix the ironic-inspector grenade job.
Thanks,
John
I don't get a real vote but +1 from me :)
John
On Fri, Jun 30, 2017 at 9:10 AM, Dmitry Tantsur wrote:
> Hi all!
>
> I'd like to propose another round of changes to the ironic-stable-maint
> group [0]:
>
> 1. Add Julia Kreger (TheJulia) to the group. Julia is one of the top
I am proposing that the following people be removed as core reviewers from
the hacking project: https://review.openstack.org/#/admin/groups/153,members
Joe Gordon
James Carey
Joe Gordon:
Has not done a review in OpenStack since 16-Feb-2017
http://stackalytics.com/?release=all_id=jogo
Has not
Just getting back from vacation and I read this :(
So sorry to see you go. Thank you for all your help over the years with
Ironic and helping me with Ironic!
Best of luck with your new work. Your new employer is very lucky!
John
On Thu, Jun 8, 2017 at 5:45 AM, Jim Rollenhagen
No!!!
Thanks for everything Lucas. Always a pleasure working with you and thanks
for all your help. Especially when I first joined Ironic.
Good luck for the future!
John
On Tue, May 9, 2017 at 7:15 AM, Lucas Alvares Gomes
wrote:
> Hi all,
>
> This
Mario,
So sorry you won't be working with us on Ironic anymore :( You have been an
great part of Ironic and I'm glad I got to know you.
Hopefully I will get to work with you again. Best of luck for the future!
John
On Fri, Apr 28, 2017 at 9:12 AM, Mario Villaplana <
mario.villapl...@gmail.com>
Not sure if I get a vote but +1 for Ruby! :)
Sorry to hear about the removals :(
John
On Thu, Apr 27, 2017 at 7:21 AM, Dmitry Tantsur wrote:
> Hi all!
>
> I'd like to propose the following changes to the ironic-stable-maint group
> [0]:
>
> 1. Add Ruby Loo (rloo) to the
Very sad to have you go Jay :( Big loss for the Ironic team. Best of luck
with the future. Hope to keep chatting with you in #openstack-ironic
Thanks for all of your help with Ironic. You helped me a lot!
John
On Wed, Apr 26, 2017 at 12:42 PM, Jay Faulkner wrote:
> Hi all,
>
>
>
+1. Reminds me a lot of our current logo. I like this version the best of
the official stylized logos. Thanks.
On Fri, Mar 10, 2017 at 8:28 AM, Heidi Joy Tretheway wrote:
> Hi Ironic team,
> Here’s an update on your project logo. Our illustrator tried to be as true
> as
+1 to both Vasyl and Mario.
Hopefully Deva will be able to come back again to Ironic in the future.
On Fri, Feb 17, 2017 at 10:42 AM, Julia Kreger
wrote:
> Thank you Dmitry!
>
> I’m +1 to all of these actions. Vasyl and Mario will be great additions.
> As for
Of the proposed logos, I do like the latest version the best. It appears
friendly and fun. So I'm +1 on it.
On Wed, Feb 1, 2017 at 12:43 PM, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com> wrote:
> Hi,
>
> +1 to Jay, the 3.0 version looks ok - it is friendly and rocking :)
>
> Cheers,
>
>
I prefer our current homegrown logo. I wish we could just keep using that.
On Wed, Feb 1, 2017 at 9:40 AM, Jay Faulkner wrote:
> I concur with most of the other comments on the thread. I have a strong
> preference for our existing mascot, and don’t think the new one is an
>
On Mon, Jan 2, 2017 at 1:06 PM, Davanum Srinivas wrote:
> Folks,
>
> Other teams:
> Please consider adding DSVM jobs with USE_PYTHON3=True for your
> projects. This will hopefully help us get to our Pike goal for Python
> 3.x [10]
>
>
As a note the variable name for DSVM jobs
On Fri, Dec 23, 2016 at 1:11 PM, Monty Taylor wrote:
> I think this is the most important point. We have automated style tools.
> Humans should not be doing code review on code style. Humans should be
> doing code review on logic and intent and whether a design is a good
>
We believe the error is caused by a bad wheel for lxml 3.7.0 that was
pushed today to PyPi
Thanks to everyone working together on this issue in #openstack-infra !
A patch is proposed to blacklist that release and we are testing it now.
Gate jobs seem to be intermittently broken across all of OpenStack.
Bug filed:
https://bugs.launchpad.net/openstack-gate/+bug/1652186
They appear during the keystone phase of devstack and look like this:
http://logs.openstack.org/39/414339/2/check/gate-tempest-
I for one do not like \ continuation lines. I think they look ugly and
prefer using () and formatting code to avoid them.
On Thu, Dec 22, 2016 at 3:28 PM, Sean McGinnis
wrote:
> Looking for input from everyone, particularly those with more in-depth
> Python knowledge.
>
>
On Mon, Dec 12, 2016 at 2:45 AM, Thierry Carrez
wrote:
> There was a thread in the past discussing renaming -alt to -2 but it
> concluded that it was not worth the hassle (losing the 489 people
> hanging there).
>
I was thinking maybe #openstack-meeting-alt could be
On Wed, Dec 7, 2016 at 5:29 AM, Thierry Carrez
wrote:
> So how about:
> - we enable an #openstack-meeting-5 to instantly relieve scheduling
> pressure
>
Any reason it isn't #openstack-meeting-2 ?
The -2 channel is owned by openstackinfra.
Ah, thanks a lot for that info :) I think that is what I need.
On Wed, Nov 9, 2016 at 7:36 AM, Jeremy Stanley <fu...@yuggoth.org> wrote:
> On 2016-11-09 07:19:04 -0800 (-0800), John Villalovos wrote:
> > Sort of related, what is the plan for supporting requirements which are
&g
Sort of related, what is the plan for supporting requirements which are
Python 3 only packages?
In particular the package: mypy-lang
https://pypi.python.org/pypi/mypy-lang
I was considering adding some type hints to the ironic-lib project in the
future. But it needs to run the mypy program to do
I have added an RFE about starting work on adding static type hint checking
to Ironic:
https://bugs.launchpad.net/ironic-lib/+bug/1633756
And a starting patch to openstack/ironic-lib:
https://review.openstack.org/#/c/386892/
A patch to add the 'typing' package to openstack/requirements/global-
On Fri, Sep 30, 2016 at 12:12 PM, Amrith Kumar wrote:
> :)
>
> Clark ...
>
> If I git clone a brand new repository and edit the tox.ini with the proposed
> change:
>
>> > PYTHONDONTWRITEBYTECODE = 1
>
> I had assumed that no .pyc's would get created.
That is correct for
Projects may want to add to their tox.ini something like this:
https://github.com/openstack/ironic/blob/c445c19285c2f3ee6a099f9f7473dd6fe087116b/tox.ini#L10
Basically add:
PYTHONDONTWRITEBYTECODE = 1
On Fri, Sep 30, 2016 at 7:20 AM, Ihar Hrachyshka wrote:
> Michał Dulko
enstack.org/summit/barcelona-2016/travel/#visa
> and got the invitation letter but it's in English language. Problem is that
> Visa centers in India are demanding this invitation letter in English as well
> as Spanish language.
>
> Thank you,
>
> Abhishek Kekane
>
> -
There is information on the Visa process at:
https://www.openstack.org/summit/barcelona-2016/travel/#visa
Not sure if you have already read that information.
They talk about the steps needed to get an invitation letter.
Good luck!
On Wed, Sep 14, 2016 at 8:51 PM, Kekane, Abhishek
On Wed, Aug 31, 2016 at 11:58 AM, Jeremy Stanley wrote:
> No, as I understand it, since we set capability.emailReviewers="deny
> group Third-Party CI" in the global Gerrit configuration it should
> avoid sending E-mail for any of their comments.
>
On Fri, Aug 26, 2016 at 9:48 AM, Clark Boylan wrote:
> As someone that semi frequently has to reproduce gate results my current
> setup involves semi frequently building the infra test images locally
> using openstack-infra/project-config/tools/build-image.sh then booting
>
On Fri, Aug 12, 2016 at 10:31 AM, Andreas Jaeger wrote:
> TL;DR: Projects can use bindep.txt to document in a programmatic way
> their binary dependencies
>
>
Maybe I missed it, but it would be nice if the documentation had some
sample commented bindep.txt files.
Thanks,
John
I personally like Option #1 as an additional goal is to make it easy for
developers to also run the functional tests with 'tox -efunctional'. And
also run the functional tests as part of a normal tox run.
On Mon, Jan 11, 2016 at 6:54 AM, Serge Kovaleff
wrote:
> Option 3
Me too :)
+1 for trying a virtual midcycle
On Thu, Nov 19, 2015 at 8:55 AM, Lucas Alvares Gomes
wrote:
> 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
My order of preference would be:
1. Coordinated regional mid-cycles
2. Normal mid-cycle
3. Virtual mid-cycle
4. No mid-cycle
Thanks,
John
On Tue, Nov 10, 2015 at 10:45 AM, Lucas Alvares Gomes wrote:
> Hi,
>
> In the last Ironic meeting [1] we started a discussion about
We have just started a weekly meeting to discuss Ironic QA, testing, and
3rd party CI
More info here:
https://wiki.openstack.org/wiki/Meetings/Ironic-QA
Weekly meeting on Wednesdays at 1700 UTC on #openstack-meeting
__
Did we come to a decision on what day for the Ironic dinner?
On Mon, Oct 12, 2015 at 11:07 AM, Lucas Alvares Gomes wrote:
> 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
yslav Drok (vdrok) for the core team. His
>> reviews
>> > have been super high quality, and the quantity is ever-increasing. He's
>> > also started helping out with some smaller efforts (full tempest, for
>> > example), and I'd love to see that continue with larger efforts.
&g
Sorry to see you go Josh :( Always great working with you.
Best of luck with the new job!
John
On Mon, Sep 21, 2015 at 8:49 AM, Josh Gachnang
wrote:
> 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.
On Sat, May 9, 2015 at 3:10 AM, John Garbutt j...@johngarbutt.com wrote:
On 6 May 2015 at 19:04, John Villalovos openstack@sodarock.com wrote:
JohnG,
I work on Ironic and would be willing to be a cross project liaison for Nova
and Ironic. I would just need a little info on what to do
JohnG,
I work on Ironic and would be willing to be a cross project liaison for
Nova and Ironic. I would just need a little info on what to do from the
Nova side. Meetings to attend, web pages to monitor, etc...
I assume I would start with this page:
Ruby,
What you say makes sense to me. On keeping things consistent. So sounds
good to me to always use them and not have them be optional.
John
On Thu, Feb 19, 2015 at 9:32 AM, Ruby Loo rlooya...@gmail.com wrote:
I think that if there is a use case for an *ED state, then we should have
it.
Can the *ED states be optional? If a state would be a NO-OP, then don't
use it. But if it is useful then use it.
It seems ugly to me to just have two 'change state' calls to move it
through the *ED state.
If an *ED state needs to be added later I think it could be added without
too much
Thanks. I will try these solutions. I think it is because I have not yet
joined the foundation.
John
On Tue, Feb 3, 2015 at 9:40 AM, Abhishek L abhishek.lekshma...@gmail.com
wrote:
Hi
On Tue, Feb 3, 2015 at 10:47 PM, John Villalovos
openstack@sodarock.com wrote:
I have attempted
I have attempted over the last two days to sign the ICLA (
OpenStack Individual Contributor License Agreement)
Each time I do it I get the following error:
Code Review - Error
Server Error
Cannot store contact information
Any ideas who I can contact to fix this?
Thanks,
John
55 matches
Mail list logo