[openstack-dev] [openstack-ansible] So long, farewell, auf wiedersehen

[Truman, Travis]

OpenStack-Ansible team,

I've very much enjoyed being part of the OpenStack community over the past 14 
months. My time in the OpenStack-Ansible community has been one of the most 
rewarding experiences of my career. However, my career is changing directions 
and I'll no longer be able to invest the time and energy required to maintain 
my involvement in the community.

As a result, I'm resigning my core reviewer status effective immediately.

Thank you to all of you in the community that I've worked with in IRC, at 
summits in Austin and Barcelona and to all of you who gave your time to review 
and improve my contributions.

Travis Truman

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core reviewer

[Truman, Travis]

+1 for Marc joining the core reviewer team. His work on CentOS support has been 
impressive.

Travis Truman

From: Jesse Pretorius 
>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Friday, February 3, 2017 at 8:33 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core 
reviewer

Hi everyone,

I'd like to propose Marc Gariepy [1] as a core reviewer for OpenStack-Ansible. 
His tireless effort to get CentOS as a supported platform in the last two 
cycles is getting very close to completion, and I feel that it's important that 
he's able to safeguard this work and help grow the maintenance community for it.

[1] 
http://stackalytics.com/?module=openstackansible-group_id=mgariepy=ocata=person-day

Best regards,

Jesse
IRC: odyssey4me


Rackspace Limited is a company registered in England & Wales (company 
registered number 03897010) whose registered office is at 5 Millington Road, 
Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be 
viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may 
contain confidential or privileged information intended for the recipient. Any 
dissemination, distribution or copying of the enclosed material is prohibited. 
If you receive this transmission in error, please notify us immediately by 
e-mail at ab...@rackspace.com and delete the 
original message. Your cooperation is appreciated.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

[Truman, Travis]

+1 on spotz for core. I can always count on Amy to provide great reviews.

Travis Truman

From: Alexandra Settle >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Friday, January 27, 2017 at 9:29 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Cc: "a...@demarco.com" 
>, Andy McCrae 
>
Subject: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

Hi OpenStack-Ansible team,

I would like to propose Amy Marrich for the core team for OpenStack-Ansible.

Amy has been consistently in the top 10 reviewers for our team in the last 30 
[1] and 90 [2] days, respectively, this release alone.

She has been an active and diligent member of the OpenStack-Ansible team since 
the end of 2015 and has continuously provided assistance for code and 
documentation reviews.

I think she will make a great addition to the core team and will help move code 
and doc issues forward quicker.

+1 from me

Thanks,

Alex

[1] http://stackalytics.com/report/contribution/openstackansible-group/30
[2] http://stackalytics.com/report/contribution/openstackansible-group/90







__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] Project Mascot

[Truman, Travis]

I like the bull, cape buffalo and oxen ideas. Any would work well for us.

From: Matt Thompson >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Friday, July 15, 2016 at 9:49 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [openstack-ansible] Project Mascot

Hi Jesse,

I like the idea of a water buffalo, as they're working animals used in farming 
etc.  This links nicely to the project as these animals 'do the heavy lifting', 
so to speak.  An ox, etc. could be another appropriate mascot.

--Matt


On Fri, Jul 15, 2016 at 2:15 PM, Jesse Pretorius 
> wrote:
Hi everyone,

As discussed in the community meeting yesterday [1] the foundation wishes each 
project to select a mascot for the project [2][3]. The mascot needs to be 
appropriate (please read the links for the constraints) and in some way linked 
to the project. We need to come up with a list of 3-5 options.

Options discussed and agreed as appropriate in the meeting yesterday:

  1.  A Bull (links directly to Ansible's mascot, although ours can be 
different).
  2.  A Cape Buffalo (distinctive, and reasonably close to a Bull).

Please consider and reply with more options, explaining the link to the project 
so that we can all discuss the options at the next meeting to finalise our list.

[1] 
http://eavesdrop.openstack.org/meetings/openstack_ansible/2016/openstack_ansible.2016-07-14-15.58.log.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-July/099046.html
[3] http://www.openstack.org/project-mascots

Thanks,

Jesse
IRC: odyssey4me




Rackspace Limited is a company registered in England & Wales (company 
registered number 03897010) whose registered office is at 5 Millington Road, 
Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be 
viewed at 
www.rackspace.co.uk/legal/privacy-policy
 - This e-mail message may contain confidential or privileged information 
intended for the recipient. Any dissemination, distribution or copying of the 
enclosed material is prohibited. If you receive this transmission in error, 
please notify us immediately by e-mail at 
ab...@rackspace.com and delete the original 
message. Your cooperation is appreciated.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

[Truman, Travis]

Jean-Philippe has been providing great code reviews and patches for some time. 
His recent commitment to running bug triage every week shows his willingness to 
step up and take responsibilities within the community. He's also found an 
opportunity to innovate by introducing an improved bug triage process. He can 
often be found in #openstack-ansible as evrardjp providing support to deployers 
in a welcoming and friendly manner.

In short, just the kind of contribution our community desires from core 
reviewers.

Thanks for all that you do for the community Jean-Philippe,
Travis Truman





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Ansible] Splitting out generic testing components

[Truman, Travis]

Nice work Andy. I'm strongly in favor of getting the central test repo into 
Gerrit for broader reviews and once done, getting one or two patches up with 
roles making use of it.

- Travis Truman

From: Andy McCrae >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Friday, June 3, 2016 at 11:41 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [OpenStack-Ansible] Splitting out generic testing 
components

TL;DR We're doing a PoC to split out common testing plays/vars into a generic 
repository, for the purposes of making in-role testing more uniform and 
generic. Looking for feedback, comments, informal reviews, ideas etc! 
https://github.com/andymcc/openstack-ansible-testing-core (Includes a simple 
README)


We now have a lot of duplication after moving to a single role per repository 
structure with specific testing per role. For example, almost all repositories 
require Galera/Rabbit/Keystone in order to deploy testing successfully. This 
has led to a scenario where each repository essentially carries the same 
deployment code.


Aims:
- The primary aim of extracting the testing infrastructure into a single 
repository is to reduce the cases where a simple change is needed, which 
dominoes, causing a patch to each of 15 repositories. Instead, a change to the 
uniform testing repository would resolve the issue for all other repository's 
testing.
- In the future, we are looking to deploy scenario testing. For example, we may 
want to test glance with a swift backend, or keystone with memcache. If the 
testing play to deploy swift is already in a uniform repository, the changes 
required to get glance testing enabled for that use case would be minimal.
- This allows new projects to consume existing structure/playbooks to deploy 
common components and vars, which should simplify the manner in which new 
openstack-ansible projects set up their testing.


Steps taken so far:
- The deployment plays for each project have been split out into the separate 
testing role.
- Each role only carries a specific "Test project" play.
- The test playbooks have been made generic so it uses the inventory specified 
per repository (defining what hosts/roles there are).
- The test-vars have been put in the testing-repository and moved out of the 
generic role.
- An override file has been created for each project and included using "-e" 
(the highest precedence) but at present, of the 4 projects converted the 
maximum number of overrides used is 2, so these overrides are minimal.
- Adjustments to tox.ini and var files references have been made to use the new 
repository.


Further work to look into:
- It may be worth looking into making the tox.ini more generic, if we were to 
make a sweeping change that impacts on tox.ini we would still need to do 
changes to each repository. (I am not sure on how feasible this is though)


Raised concerns:
- This creates a situation where a change may require me to make a change to 
the central testing repository before changing the role repository. For 
example, in order to get the generic testing for a keystone change I would have 
to change the testing repository in advance, and then change the keystone 
repository. Or override the var, adjust the testing repo and then remove the 
keystone override.
- Changes to the testing-repo can cause all other repo tests (aside from the 
overarching openstack-ansible repository) from breaking.


Where to find the PoC, what next?

The repository can be found here: 
https://github.com/andymcc/openstack-ansible-testing-core

This is a proof of concept so in no way is it considered complete or perfect, 
we are asking for more eyes on this; test it, let us know what you like/do not 
like/want changed/additional ideas to improve.

Thanks!

Andy
irc: andymccr
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-ansible] OpenStack-Ansible and Open vSwitch

[Truman, Travis]

I’ve been anxiously awaiting Open vSwitch support in the OpenStack-Ansible
project and it looks like we¹ve made great progress in the Newton cycle
thanks to efforts from many in the community.

After spending some time testing the current implementation in my lab, I
wanted to throw together a quick blog post to explain how I structured
my OSA configuration to achieve the end results I was looking for.

Please find the post here:
http://trumant.github.io/openstack-ansible-openvswitch.html

I hope others find this useful and that it may serve as a good reference
point when the community begins building scenario-based documentation.

- Travis Truman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] Mid-cycle date selection (need input!)

[Truman, Travis]

I¹m okay with either 1 or 2. Thanks for running with this Major.

On 6/9/16, 2:51 PM, "Major Hayden"  wrote:

>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Hey folks,
>
>I've been able to secure a few dates at Rackspace's headquarters in San
>Antonio, Texas:
>
>  1) August 10-12
>  2) August 22-26
>  3) August 29 - September 2
>
>During the meeting earlier today, #3 was determined to cause a lot of
>conflicts for people.  #1 seems to be the most preferred.  I have emails
>out to ask about deals on local hotels and I'm waiting to hear back on
>those.
>
>The room should seat about 20-25 people and we would have at least one
>projector.
>
>Please reply with your thoughts and a date preference!  Once we get that
>sorted out, we can fire up an etherpad for everyone to sign up for a spot.
>
>- --
>Major Hayden
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v2
>
>iQIcBAEBCAAGBQJXWbqdAAoJEHNwUeDBAR+xMUYP/1/SN69gCraGCO2XxR52ZKIN
>NWzbeY7mw44eQyoeUBXtJLLo/qFxeQniR6ybaz/zMhqhxOliOys0rDn3Q1Xawtkn
>Mq8IN/aStnGXLn1dXY2DkkaOksvKZTAKhHTvM5ojzGh2laso0Qeh9DK6aItmmljn
>fibzU0FNkYlSOj3LQLW+dnxSYUaovs+1Ir1QlCGq5dB49pQF7wEVU0adMabYkL7n
>6GsjYCfsiy/Iyr1TEc8vjcbVwyteOLS59ibN1c+Y0Yp42jBb+zpA8VmupiL2Y9yM
>aUvNgmtyO0lx2LWGh2MWBrxeNgcA6aLpxgOG4oOLK7U5CRQkXy/Rw9BfeA5X5WB4
>A6DWptzSYR3HiVqoD6BG2sH4Ube5Xd3PLMIcfG7ar0lSvN1s6fNugS/u1/tKnCHf
>/e16zhZ/2m96s7Pe6pX1hckgDYUbLyDrw7FwyO4QZZBPeILk6QBHJ978/n2PH2yD
>kaka04A4mqbr+wD2iaoPURM46RPuk5I2noDTjW+udm12tN4dBLdc5PZ6M5tIjhUM
>G3GY82B4lOLlgGZUlwyu1Whq8jVkctdgbq0gjK7jy+iWl4c/77V+KUgKbfAjIx0W
>cPgW7/adKK1x0Ev02L9j5oMcqYlOz0QpKPrILUY1G+jjwBVX5+74zbNTgBTopBw0
>Q0fSm4KIMeuF5cD2pvAS
>=J7ZQ
>-END PGP SIGNATURE-
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

[Truman, Travis]

Major has made an incredible number of contributions of code and reviews to the 
OpenStack-Ansible community. Given his role as the primary author of the 
openstack-ansible-security project, I can think of no better addition to the 
core reviewer team.

Travis Truman


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] OpenVSwitch support

[Truman, Travis]

Curtis,

Please take a look at https://review.openstack.org/#/c/298765/ as its
probably a good place to start digging into OVS.

Travis Truman
IRC: automagically

On 3/24/16, 12:37 PM, "Curtis" <serverasc...@gmail.com> wrote:

>OK thanks everyone. I will put on my learnening hat and start digging
>into this.
>
>Thanks,
>Curtis.
>
>On Thu, Mar 24, 2016 at 10:07 AM, Truman, Travis
><travis_tru...@cable.comcast.com> wrote:
>> Michael Gugino and I were going to work on OVS and I believe we both got
>> sidetracked. I¹ll echo Kevin¹s offer to help out where possible, but at
>> the moment, I¹ve been tied up with other items.
>>
>> On 3/24/16, 11:55 AM, "Kevin Carter" <kevin.car...@rackspace.com> wrote:
>>
>>>I believe the OVS bits are being worked on, however I don't remember by
>>>whom and I don't know the current state of the work. Personally, I'd
>>>welcome the addition of other neutron plugin options and if you have
>>>time
>>>to work on any of those bits I'd be happy to help out where I can and
>>>review the PRs.
>>>
>>>--
>>>
>>>Kevin Carter
>>>IRC: cloudnull
>>>
>>>
>>>
>>>From: Curtis <serverasc...@gmail.com>
>>>Sent: Thursday, March 24, 2016 10:33 AM
>>>To: OpenStack Development Mailing List (not for usage questions)
>>>Subject: [openstack-dev] [openstack-ansible] OpenVSwitch support
>>>
>>>Hi,
>>>
>>>I'm in the process of building OPNFV style labs [1]. I'd prefer to
>>>manage these labs with openstack-ansible, but I will need things like
>>>OpenVSwitch.
>>>
>>>I know there was talk of supporting OVS in some fashion [2] but I'm
>>>wondering what the current status or thinking is. If it's desirable by
>>>the community to add OpenVSwitch support, and potentially other OPNFV
>>>related features, I have time to contribute to work on them (as best I
>>>can, at any rate).
>>>
>>>Let me know what you think,
>>>Curtis.
>>>
>>>[1]: https://www.opnfv.org/
>>>[2]: https://etherpad.openstack.org/p/osa-neutron-dvr
>>>
>>>
>>>__
>>>OpenStack Development Mailing List (not for usage questions)
>>>Unsubscribe: 
>>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>__
>>>OpenStack Development Mailing List (not for usage questions)
>>>Unsubscribe: 
>>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>-- 
>Blog: serverascode.com
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [OpenStack-Infra] - Unable to save contact information in Gerrit

[Truman, Travis]

Receive a server error response when attempting to save Gerrit contact 
information on both the settings screen as well as when creating a new 
individual contributor agreement.

Screenshot of error received: 
https://www.dropbox.com/s/0q7u0kku18132xg/Screenshot%202015-12-18%2010.32.09.png?dl=0

I've been able to reproduce consistently since Gerrit came back up following 
the upgrade.

Thanks,
Travis Truman

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev