Re: [OpenStack-Infra] Resigning from infra-core

[Anita Kuno]

On 2019-12-09 6:28 p.m., Joshua Hesketh wrote:

It has been a highlight of both my
career and in some cases my life.


The feeling is mutual. be well in all you do.

Anita

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Low Key Monday Evening Get Together

[Anita Kuno]

On 2019-04-28 1:27 p.m., Clark Boylan wrote:

Zuul has been confirmed.


Congratulations Zuul team.

Hope you have a lovely celebration.

Anita

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] lists upgrade seems to be complete

[Anita Kuno]

On 2019-04-12 1:52 p.m., Clark Boylan wrote:

This message acts both as an indication that the upgrade was completed and a 
sanity check that our lists are functioning.

Clark

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



Received.

Thanks to Clark and Jeremy for doing this upgrade.

Seems to be working for me.
Anita

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] The wikipage examle as meant to be copied not over-written

[Anita Kuno]

Hello:

I see you are working on setting up a third party ci system, thank you.

The wikipage example at: 
https://wiki.openstack.org/wiki/ThirdPartySystems/Example is meant to be 
an example for you to follow, in order for you to create your own page, 
like all the pages linked to this page: 
https://wiki.openstack.org/wiki/ThirdPartySystems


The example is not meant to be over-written by any individual third 
party ci operator for their own system. The example needs to stay as it 
is for everyone to be able to view and follow. I have rolled back your 
edit of the example page.


Please read the instructions again and create a new page for yourself 
with your own title and content in it which is specific to your system. 
Then ensure your new page with your content is linked to this page: 
https://wiki.openstack.org/wiki/ThirdPartySystems


If you continue to have difficulty, please reply to this email or find 
us in the #openstack-infra irc channel on the freenode network: 
https://docs.openstack.org/infra/manual/irc.html


Thank you,
Anita

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Volunteer Systems Administrator

[Anita Kuno]

On 2018-08-19 04:46 AM, Marcin Koprowski wrote:

Hello,

First of all, allow me to introduce myself. My name is Marcin and I work in
Poland as an Infrastructure Analyst. I used to be a Systems Administrator,
IT Manager, IT Support Analyst, etc. I have a few years of experience
administering Ubuntu Server and a bunch of Open Source
applications/services.

I don't have any experience with OpenStack, but I'm very keen to learn.

The reason why I'm writing here is that I have more than 10 hours per week
to spare and I would like to help you out somehow. My interest is Systems
Administration and DevOps. Please let me know if you are interested, and if
you are, I will provide you with my CV and link to my Linkedin profile.

Thank you.

Best regards,

Marcin


Hi Marcin:

You are more than welcome to participate, no application process necessary.

There are plenty of tasks available for you to help with, the best way 
to find out which ones and how to learn the systems are by spending time 
in the infra channel (#openstack-infra on the freenode network, you will 
need to register your irc nickname to join the channel) and by 
participating in the weekly infra meeting, #openstack-meeting 19:00 utc 
on Tuesdays.


Root access to servers is granted to those who demonstrate commitment 
and experience with our systems and the only way to get experience is to 
participate.


Your participation would be appreciated. There is usually someone in the 
irc channel in most time zones, weekends tend to be quiet.


Welcome,
Anita



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Dublin PTG recap

[Anita Kuno]

On 2018-03-07 08:54 AM, Clark Boylan wrote:

I've made it home after the PTG and am jet lagged which means it is a great 
time to try and recap some of what happened at the PTG. I'm not going to go 
into a ton of detail for each topic as I think that would make this turn into a 
novel but if people are interested in specific items feel free to start new 
threads for them and we can dig in more there (this has already happened for at 
least one or two topics). Also you can refer back to the PTG etherpad, 
https://etherpad.openstack.org/p/infra-rocky-ptg, for more information and 
notes that were taken at the time.

First thing that everyone should know is that the weather did not cooperate 
with us and resulted in much travel uncertainty and disruption. Mention this so 
that we aren't surprised if some people are slow to respond or otherwise AFK 
while finding their way home. It also meant that by Thursday we had largely 
abandoned our PTG schedule. Apologies if this meant that a topic you were 
interested in was not covered.

For this PTG we ended up having three major themes. There was the cross project 
(helproom) time, zuul topics, and infra services conversations. I think we 
managed to do a reasonable job covering these themes despite the weather and 
illness.

During the cross project conversations we were able to spend time helping 
projects like neutron, ironic, swift, and glance better take advantage of Zuul 
v3. We covered how the gate works, how to convert jobs to native Zuul v3, 
cleaning up old unused jobs, and how to run multinode jobs. We also had a 
conversation with keystone about how they might run performance testing on 
infra. There was also quite a bit of time spent working with the QA team to 
work out how multinode devstack would work in Zuul v3, how to make irrelevant 
files lists more intuitive, and how to wind down grenade testing on our oldest 
supported branch.

Kashyapc brought up nested virt support again which is becoming more important 
with post meltdown/spectre performance slowdowns. This resulted in a few of us 
crashing the public cloud working group's room for a discussion on how to have 
better communication between devs and clouds. Rough plan there is to spin up a 
new neutral mailing list to spark conversations over tools like nested virt 
between all the involved parties.

We covered a number of Zuul topics ranging from scaling out the scheduler to 
dashboard improvements to tenant label restrictions and executor affinity. None 
of these topics seemed controversial and I think we captured good notes on the 
etherpad for these topics in particular. I will call out the tenant label 
restrictions and executor affinity features as items that seemed to come up 
quite a bit from various users for various use cases so I think the importance 
of these features may have gone up after the PTG. One Zuul topic that we 
couldn't quite get into due to illness and last minute travel changes was Zuul 
support for containers. As I understand it there was some pre PTG talk about 
this, but we should probably try to have a proper discussion on the mailing 
list once people are back to normal operating hours.

For infra services we talked about upgrading Gerrit, better multi arch support, 
and rolling out Bionic. The rough plan (details on etherpad) for the Gerrit 
upgrade is to update the operating system for Java 8 this cycle then early next 
cycle upgrade Gerrit to 2.14 or 2.15 depending on which process is simpler for 
us (we will have to test that between now and then). Multi arch support is now 
something we have to think about with the arm64 Linaro cloud roll out. We seem 
to have largely decided that things are moving and largely working and we'll 
tackle problems as they come up. We also have Bionic beta images available. The 
one restriction we'd like to see there is to not gate on them but projects can 
(and in some cases should) go ahead and start using them to determine future 
compatibility particularly with python3.6.

One last major item that came up was how the OpenStack Foundation's CI/CD focus 
area will affect the infra team. This was a topic at the board meeting in 
Dublin which I had to miss due to helping run the helproom, but there were 
discussions with members of the infra team later in the week. The most concrete 
result of that seemed to be a shared understanding of three facets to this 
focus area: 1) The how to and best practices of doing CI/CD properly and 
effectively 2) Zuul and related software as a set of tools to enable (1) and 3) 
the current set of services run by the infra team which may be useful to 
developers outside of OpenStack. We've been promised a proper thread of its own 
from the foundation to start this conversation more broadly with the infra team 
soon so keep an eye out for that.

I've probably forgotten/skipped/missed other topics that are important and 
worth calling out. It was a long week and I'm now jetlagged so you have my 
ap

Re: [OpenStack-Infra] Help needed?

[Anita Kuno]

On 2018-02-05 11:09 PM, David Logan wrote:

Hi Folks,

I'm a Unix/Linux Admin of some years experience, looking to contribute to
Openstack as a community Sysadmin.

I have experience in RH/SuSE/CentOS etc, use Puppet daily and am starting
to look at Ansible. Am reasonably cloud aware, used AWS and Azure to a
limited extent. Not much Openstack but we are looking :)

If I can be of any help, please feel free to contact me.

Cheers
David Logan



Hi David:

My suggestion would be to join the #openstack-infra channel on irc, the 
freenode network.


Introduce yourself to clarkb, the Infra program team lead (ptl) and 
settle in for some reading of the backscroll. It is the most immediate 
and up to date source of information of the current goings on.


Clark or others can help you find your way about, getting oriented with 
docs and links and such.


I'm sure someone else has a more through suggestion but this approach 
would be a start.


Welcome to infra,
Anita.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Announcing Gertty 1.5.0

[Anita Kuno]

On 2017-07-30 11:08 AM, James E. Blair wrote:

Announcing Gertty 1.5.0
===

Gertty is a console-based interface to the Gerrit Code Review system.

Gertty is designed to support a workflow similar to reading network
news or mail.  It syncs information from Gerrit to local storage to
support disconnected operation and easy manipulation of local git
repos.  It is fast and efficient at dealing with large numbers of
changes and projects.

The full README may be found here:

   https://git.openstack.org/cgit/openstack/gertty/tree/README.rst

Changes since 1.4.0:


* Added support for sorting dashboards and change lists by multiple
   columns

* Added a Unicode graphic indication of the size of changes in the
   change list

* Added the number of changes to the status bar in the change list

* Added a trailing whitespace indication (which can be customized or
   ignored in a custom palette)

* Several bug fixes related to:
   * Negative topic search results
   * Crashes on loading changes with long review messages
   * Avoiding spurious sync failures on conflict queries
   * Errors after encounting a deleted project
   * Better detection of some offline errors
   * Fetching missing refs
   * Gerrit projects created since Gertty started
   * Re-syncing individual changes after a sync failure

Thanks to the following people whose changes are included in this
release:

   Jim Rollenhagen
   Kevin Benton
   Masayuki Igawa
   Matthew Thode

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


Congratulations Jim and Gertty contributors.

Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Ballot for Openstack elections

[Anita Kuno]

On 2017-02-23 02:12 PM, Jeremy Stanley wrote:

On 2017-02-23 18:37:49 + (+), Cathy Zhang wrote:

I strongly support the proposal to mandate this. To be fair, I
think TC should mandate this across all projects. In many
complicated and technically hard commits, co-author does not make
any less amount of technical contribution to the commit. If just
the owner is counted, people will start to fight for the ownership
of a commit which is not healthy for the open source community.

For my own case, it is well known that I am the initiator and
project lead of this networking-sfc project and have contributed a
lot to this project on the technical side and project management
side. I have done many reviews and approvals in this cycle and
co-authored quite some commits. It is a surprise to me that
co-author is not counted as technical contributor in Neutron.

The technical limitations for this in the past have been twofold:

1. Gerrit did not provide a usable API for querying arbitrary
substrings from commit messages.

2. Voters must be foundation individual members and we had no way to
query the foundation member database by contributor E-mail address.

The first is less of an issue in the version of Gerrit we're running
now and the second is a situation I'm collaborating with the
foundation's development team to attempt to resolve. In the
meantime, the solution has been that PTLs should entertain requests
from co-authors to be added to the "extra ATCs" list for their
project. I don't personally have any objection to letting change
co-authors vote in elections, we just don't (yet) have a solution to
be able to automatically verify whether they're authorized to vote
under our bylaws and charter.

Separately, there was a problem back when we used to provide free
conference passes to code contributors, where someone at a company
would submit a punctuation fix to a comment in some project, add
half a dozen of their co-workers as co-authors, and then ask for
free admission for all of them (this really happened). Relying on
PTLs to vet extra ATCs before adding them was how we mitigated this.
Now that we no longer rely directly on code contributions to decide
who should get free/discounted conference admission this issue
should hopefully be purely historical. People seem to be far less
interested in gaming elections than going to conferences (or in some
cases scalping free tickets as a money-making scheme).
In addition, under the bylaws 3. (b) (ii) 
https://www.openstack.org/legal/technical-committee-member-policy/ any 
individual may apply to the chair of the Technical Committee for 
extra-ATC status.


Now should anyone elect to do this, I would hope they would have 
conversed with the PTL of their applicable project prior to applying to 
the TC chair.


Also the governance repo, in which the extra-ATCs are recorded, is 
tagged in advance of each election so that any questions about the 
composition of the electoral roll have a common reference point. Should 
an individual elect to apply directly to the TC chair for extra-ATC 
consideration I would highly suggest they do so well in advance of any 
tagging cadence.


To be honest, I suspect any PTL would welcome assistance composing, 
verifying and submitting the list of extra-ATCs to the governance repo. 
People might consider offering to help here.


Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] MeetBot taking unauthorised vacation

[Anita Kuno]

On 16-08-17 10:45 AM, Stig Telfer wrote:

I think our meeting ran over time and the openstack bot exited at 1 minute past 
the end of the meeting.  So it’s quite likely there were supposed to be no 
meetings happening at that time, although in reality we were still at it.

Best wishes,
Stig



On 17 Aug 2016, at 15:09, David Moreau Simard  wrote:

I love this.

But on a serious note, the bot has to be restarted when commits are
done to it and usually cores are quite dilligent about not merging
reviews while there are meetings in progress.
Maybe something slipped this time ?

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]


On Wed, Aug 17, 2016 at 6:14 AM, Stig Telfer  wrote:

Hi All -

We just had a Scientific WG meeting in #openstack-meeting but the MeetBot left 
half way through.  Now the meeting cannot end (I’m sure it often feels that 
way).

Best wishes,
Stig


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


The last change to the file that contains the list of channels for 
meetbot merged yesterday at 15:23 GMT: 
http://git.openstack.org/cgit/openstack-infra/system-config/commit/hiera/common.yaml?id=6d3fc364f1f0d012672209b844a76b9554e916ea


So I don't think this theory has legs.

Bots disappear for all sorts of reasons, including code changes, I'm 
glad this one came back so you could end the meeting.


Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Announcing Gertty 1.4.0

[Anita Kuno]

On 07/26/2016 06:39 PM, James E. Blair wrote:
> Announcing Gertty 1.4.0
> ===
> 
> Gertty is a console-based interface to the Gerrit Code Review system.
> 
> Gertty is designed to support a workflow similar to reading network
> news or mail.  It syncs information from Gerrit to local storage to
> support disconnected operation and easy manipulation of local git
> repos.  It is fast and efficient at dealing with large numbers of
> changes and projects.
> 
> The full README may be found here:
> 
>   https://git.openstack.org/cgit/openstack/gertty/tree/README.rst
> 
> Changes since 1.3.0:
> 
> 
> * Gertty is now available in Gentoo.
> 
> * Large changes with many patchsets load faster.
> 
> * The change screen now displays changes which may conflict with the
>   current change.
> 
> * Added support for a command socket so that external applications may
>   request Gertty to open a change.  An example of how to configure
>   Gerrit URLs to automatically open in Gertty when clicked in the
>   unicode-rxvt terminal emulater is provided in the documentation.
> 
> * Added an optional vi-style keymap and navigation commands.
> 
> * Added "project topics" -- the ability to group projects in the
>   project list.
> 
> * Added support for the process mark on the project list.
> 
> * Email addresses are displayed in the change screen.
> 
> * Added support for the "projects:" search term.
> 
> * Added support for searching by last-seen.  This can be used to
>   create a dashboard of changes that have been recently viewed in
>   Gertty.  See the example config files for how to set this up.
> 
> * The project and change lists are now searchable with the interactive
>   search command.
> 
> * The change list now displays more columns if there is room.
> 
> * Added a navigation breadcrumb footer.
> 
> * Added a "Reply" button to the change screen to facilitate quoted
>   replies to messages.
> 
> * When re-reviewing a change, the review dialog defaults to previous
>   values.
> 
> * Added support for batch abandon and restore.
> 
> * Unified diff display now groups changed lines better.
> 
> * Added lockfile support to prevent multiple copies of Gertty from
>   accessing the same database.
> 
> * Added support for form-based authentication.
> 
> * Added an option to specify the URL for cloning git repos.
> 
> * In the default keymap, the sorting commands now take two keystrokes
>   (e.g., "Sn" for sort by number) to facilitate more sorting options.
> 
> * Multi-keystroke commands now display suggestion completions.
> 
> * Dashboards may now specify their default sorting option.
> 
> * Sphinx-based documentation now availablet at
>   http://gertty.readthedocs.io/
> 
> * Added an option to disable mouse support.
> 
> * Several bug fixes related to:
>   * Improved handling of abandoned related changes.
>   * Fixed "too many SQL variables" error which occurred in large
> projects.
>   * Corrected ordering of test results.
>   * Treat HTTP 503 responses as server-offline so that the action will
> be retried later.
>   * Handle additional python-requests SSL errors.
>   * Better handle missing git commits.
>   * Several Unicode fixes.
>   * Support more recent versions of GitPython.
>   * Better handle more than one change result when searching.
>   * Fix a crash on permissions-only changes.
>   * Fixes to support some changes in Gerrit 2.8 and 2.9.
>   * Python 3 improvements.
>   * Correct the display of comments at the start of a file.
> 
> Thanks to the following people whose changes are included in this
> release:
> 
>   Christoph Gysin
>   Cody A.W. Somerville
>   Craige McWhirter
>   David Shrewsbury
>   Doug Hellmann
>   Doug Wiegley
>   Jan Kundrát
>   Jay Pipes
>   Jim Rollenhagen
>   K Jonathan Harker
>   Martin André
>   Matthew Oliver
>   Matthew Thode
>   Matthew Treinish
>   Matthias Runge
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Congratulations Jim and all Gertty contributors. Nice work!

Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Infra priorities and spec cleanup

[Anita Kuno]

On 06/20/2016 09:22 PM, Jeremy Stanley wrote:
> On 2016-06-08 23:08:16 +1000 (+1000), Joshua Hesketh wrote:
>> On Mon, Jun 6, 2016 at 9:21 AM, Jeremy Stanley  wrote:
>> [...]
>>> Store Build Logs in Swift
>> [...]
>>> We should remove the original spec from our priority list (since
>>> that's basically already ceased to be an actual priority), and
>>> probably supercede it with the AFS proposal.
> [...]
>> Additionally the urgency of this spec seems to have been reduced (due to
>> limiting the retention on logs). We should perhaps reconsider if it's a
>> priority spec or not after we've decided on a path forward.
> 
> That makes sense, though I think we can agree the original spec (and
> accompanying implementation) has ceased to be treated as a priority
> so it's a bit disingenuous to leave it on our priority list.
> 
> Anyway, I've pushed a cleanup/update change at
> https://review.openstack.org/331903 which:
> 
>   * removes logs-in-swift
>   * replaces maniphest with task-tracker
>   * adds nodepool-zookeeper-workers due to its coupling with zuulv3
>   * updates the Gerrit query string/URL accordingly
> 
> I'll put it on the meeting agenda now for formal council vote this
> week. If approved, this leaves us at 6 priority specs, so if we
> consider that we were pretty well saturated at 8 last cycle, we can
> also discuss adding a couple more we expect to be spending
> significant time on over the remainder of this cycle or whether
> sticking with those 6 is perhaps better for focusing our efforts?
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Sorry if I should have replied before and didn't, like a game of double
dutch I try to time when it is my turn and sometimes I miss.

What is the status if Ipsilon? Since the task tracker spec
implementation phase 2 hinges on Ipsilon being in place I think Ipsilon
is a priority.

Thanks,
Anita.



___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Request help for ICLA error

[Anita Kuno]

On 06/17/2016 06:22 PM, Steven Dake (stdake) wrote:
> Soffie,
> 
> I'm happy to spend 15 minutes on a google hangout or webex where you can 
> screen share and I can walk you through getting your environment setup.  I 
> know every combination of problems related to ICLA setup helping my good 
> friends at Red Hat and Cisco get a basic setup going in their environment.
> 
> Ping me sdake on channel #openstack-kolla on freenode, and I'll provide a 
> link to webex.  You will need a mac or  windows machine to use webex.  Google 
> hangouts also has a screen sharing feature if you can set it up.  I am 
> usually around all the time. :)
> 
> Regards
> -steve

This is a generous offer, Steve.

I'd just like to make it clear to users that the infra team doesn't
support windows questions. So if this user goes to great efforts to get
access to windows to use webex, the use of that tool only goes as far as
Steve's offer, it is not indicative of what kind of support users can
expect from the infra team.

Thanks,
Anita.

> 
> 
> From: Soffie Huang 
> mailto:soffie.hu...@falconstor.com>>
> Date: Wednesday, June 15, 2016 at 3:58 AM
> To: openstack-infra 
> mailto:openstack-infra@lists.openstack.org>>
> Subject: [OpenStack-Infra] Request help for ICLA error
> 
> 
> Hello Infra Team,
> 
> I am trying to push the code changes for sanbox. But while initiating the
> review I am getting the following Error.
> 
> ---
> fatal: ICLA contributor agreement requires current contact information.
> Please review your contact information:
>   https://review.openstack.org/#/settings/contact
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> -
> 
> I have signed the ICLA by providing my email address and also I tried to
> update my contact details at the link given above. While updating the
> details I am getting server error.
> 
> Could you help me with this issue?
> 
> 
> Here is my detail information:
> 
> 
> 
> 
> 
> Thanks,
> 
> Soffie
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] A tool for slurping gerrit changes in to bug updates

[Anita Kuno]

On 05/25/2016 01:13 PM, Jeremy Stanley wrote:
> On 2016-05-25 11:43:39 -0500 (-0500), Gregory Haynes wrote:
> [...]
>> We are considering making a small project to connect to and read
>> from the Gerrit event stream and then update our bug tracker.
> [...]
>> If we implemented this, would this be something the -infra project
>> would like to have live upstream? It seems easy enough to make
>> this generally useful to others with similar requirements.
>>
>> Any other thoughts/comments that might help :).
> 
> Please collaborate with the storyboard team on this. I believe the
> Gerrit integration plan there has always been to have an independent
> service which consumes the Gerrit event stream and then performs
> arbitrary callouts (likely over localhost on the storyboard server)
> to a task tracker API. Your goals seem closely aligned.
> 

I believe this is the patch that is in progress:
https://review.openstack.org/#/c/302912/

I think Zara would welcome help on it if you want to talk to her in
#storyboard.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerrit question: Rebases

[Anita Kuno]

On 05/24/2016 11:30 AM, Kevin L. Mitchell wrote:
> I've noticed that when a patch set is rebased, Gerrit is not sending me
> an email alerting me to that.  It does send out an email when a new
> patch set is uploaded, just not when one is rebased.  This is causing
> problems for me with the Global Requirements uploads, as they frequently
> get rebased, and since I'm not notified, I have to notice that the
> review hasn't merged yet and check up on it.
> 
> Is there some setting I need to click to get Gerrit to send me
> notifications about rebases, or is this something systemic that needs to
> be reported upstream as a bug?
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Hi Kevin:

It seems that gerrit once had this functionality and someone didn't like
it: https://groups.google.com/forum/#!topic/repo-discuss/NSM5aio2oHs

The patch to disable notification emails on rebase was merged a year
ago: https://gerrit-review.googlesource.com/#/c/53740/

I'm uncertain how to evaluate which release this patch is in but we did
upgrade to 2.11 late last November, so am going with this patch is in
our current production instance of gerrit.

Suggestions:
perhaps add to the mailing list thread on the topic that you would like
this feature to be accessible in a toggleable setting
work through the comments on the merged patch (I have not) and see if
there is any opposition to making it toggleable
submit a patch (Khai Do - zaro - is a good person to talk to here) to
make the feature toggleable

Thanks for your clear description of your experience, Kevin, I
appreciate it.

Thanks,
Anita.



signature.asc
Description: OpenPGP digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [OT] Call for speaker submissions

[Anita Kuno]

On 05/03/2016 02:19 PM, Morgan Fainberg wrote:
> On Tue, May 3, 2016 at 10:19 AM, Paul Belanger 
> wrote:
> 
>> On Tue, May 03, 2016 at 10:01:06AM -0700, Elizabeth K. Joseph wrote:
>>> On Mon, May 2, 2016 at 11:55 AM, Spencer Krum 
>> wrote:
 I think this is a good conversation to have. I would recommend we start
 a thread-per-conference for simplicity. Folks can use this to
>> coordinate
 attendance, ensure we submit unique presentations, and to help each
 other groom presentations. I doubt that anyone on the team would feel
 any offense at someone else submitting on infra topics, but
>> coordination
 sounds good. Whenever we are presenting on an infra topic, being clear
 to put credit for building and supporting the technology in the correct
 place is something we should be careful to do.

 We've always used the publications repo to archive an collaborate on
 talks, but I think our use of that isn't quite correct at this time.
>>>
>>> Yeah, we don't tend to prepare the presentations until after our talks
>>> have been accepted and that's when we use the publications repo.
>>>
>>> I like using the mailing list as a notification mechanism but I think
>>> we should also maintain an etherpad with a listing so we can keep it
>>> all organized in the longer term.
>>>
>> I'd be happy to see a etherpad URL we can use to list conferences and talks
>> people are thinking of talking at.
>>
>>> --
>>> Elizabeth Krumbach Joseph || Lyz || pleia2
>>>
>>
>>
> I like the coordination, sometimes it is useful if suddenly two folks are
> interested in talking at the same conference (either can be a cooler bigger
> talk, or each can be more specialized). :)
> 
> --Morgan
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

I think co-ordination is a great idea and has been mentioned several
times already will help to ensure coverage at important conferences and
giving correct attribution to tool authors and contributors.

I do want to state that I don't think it is a requirement. As an
example, I found out about PyCon CA the Sunday after the proposals
closed the Friday prior and submitted a proposal within 15 minutes of
discovering the conference. (My talk was accepted.) So my point is,
don't let the process prevent you from submitting a talk if you have a
tight deadline. Submit by all means, then co-ordinate after, as fits
your use case.

Thanks for starting the conversation Paul,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] April 13th Infra StoryBoard bug day and low-hanging-fruit tagging

[Anita Kuno]

On 04/12/2016 01:53 PM, Elizabeth K. Joseph wrote:
> On Tue, Apr 5, 2016 at 1:30 PM, Elizabeth K. Joseph
>  wrote:
>> Hi everyone,
>>
>> Back in 2013 and 2014 we hosted quarterly bug days where we'd go
>> through the Infra bugs to evaluate status, make updates and generally
>> triage the queue of bugs. When we moved off of Launchpad and on to
>> StoryBoard, we stopped doing these days. As discussed at our meeting
>> today, StoryBoard has come a long way and it seems we're in a place
>> where it's technically possible for us to resume bug days.
>>
>> So we'll be once again hosting an Infra bug day! It will begin on
>> Wednesday, April 13th at 15:00 UTC and go for 24 hours, as time zones
>> allow for participants, in #openstack-sprint
>>
>> We should plan on working on the following:
>>
>>  * General review, evaluation and triage of outstanding bugs
>>  * Make sure low-hanging-fruit tags are still valuable and accurate,
>> and hopefully add more so that new contributors have tasks they can
>> tackle
>>  * As we do all this work on StoryBoard, chat with some of the
>> StoryBoard developers, Zara and SotK, about what we still need from
>> StoryBoard itself to support our work
>>
>> An etherpad has been created here where we'll brainstorm, coordinate
>> updates and *possibly* have a listing of bugs like we did with past
>> bug days (I'll be looking into that):
>> https://etherpad.openstack.org/p/cibugreview-april2016
> 
> Quick reminder that this is coming up tomorrow, April 13th.
> 
> Zara pointed me in the direction of python-storyboardclient so I'm
> going to try to make time this afternoon to see about getting it to
> spit out a bug list a la our past bug days with Launchpad,

If I can help at all with this effort, I'm happy to help. I'll follow up
on irc.

> but no
> promises, the library has been neglected for some time. Even if we
> don't have a useful bug listing in the Etherpad I think this will
> still be a productive day, there are a lot of bugs going back months
> that we have to triage, so a slightly less organized pile on to get
> through the queue should be ok for this first StoryBoard-using bug
> day.

I think it will be a productive day as well. We haven't looked at bugs
for a while so any time spent on it will be good.

Looking forward to tomorrow, thanks for putting this together, Lyz.

Thanks,
Anita.

> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Help! I lost the password for the Enterprise WG administrator access

[Anita Kuno]

On 04/07/2016 10:25 AM, Barrett, Carol L wrote:
> Can you reset it?
> Thanks
> Carol
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
I don't understand what tool we are discussing.

Is this a mailing list? Is this some other sort of tool?

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [Infra] Request for adding me in core member for networking-hpe repo

[Anita Kuno]

On 04/05/2016 12:56 PM, Elizabeth K. Joseph wrote:
> On Tue, Apr 5, 2016 at 12:19 AM, S.Selva Kumar  
> wrote:
>> We have created a new repo name networking-hpe under openstack  few days
>> ago, and now I would request Infra team to provide me access  to add me as
>> core member in this project so that we can +2 approver for Gerrit.
>>
>> Below is the group link for networking-hpe-core .
>>
>> https://review.openstack.org/#/admin/groups/1347,members
> 
> Review here: https://review.openstack.org/#/c/295775/
> 
> It looks like Koteswara Rao Kelam  is the one
> who submitted this patch, so I've included them on this email. We can
> add you once we have confirmation from the patch author that you
> should be the initial member of this team.
> 
> Should anyone be added as the initial member of networking-hpe-release?
> 
Hi Lyz:

I told S. Selya that you would just add the owner of the patch. He asked
earlier in irc.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Austin Design Summit space needs

[Anita Kuno]

On 03/23/2016 02:47 PM, Wayne Warren wrote:
> On Wed, Mar 23, 2016 at 11:20 AM, Anita Kuno  wrote:
> 
>> On 03/23/2016 02:12 PM, Wayne Warren wrote:
>>> On Tue, Mar 22, 2016 at 3:23 PM, Elizabeth K. Joseph <
>> l...@princessleia.com>
>>> wrote:
>>>
>>>> On Fri, Mar 11, 2016 at 9:27 AM, Elizabeth K. Joseph
>>>>  wrote:
>>>>> https://etherpad.openstack.org/p/infra-newton-summit-planning
>>>>
>>>> I've also gone ahead and added a section at the bottom for "Other
>>>> sessions of interest" for non-infra sessions that an infra presence
>>>> would be particularly valuable at.
>>>>
>>>
>>> Would this be a good place to propose JJB design discussion (both my
>> recent
>>> 2.x work and more general YamlParser features moving forward)?
>>
>> Yes, it is a good place to propose any design discussion related to infra.
>>
>> We will look at all proposed ideas and make decisions about what gets a
>> slot and when in a bit (not sure when we will start) so all ideas are
>> welcome at this stage.
>>
>> Hopefully you will be attending summit and will identify yourself as
>> chair/moderator of the session you are proposing.
>>
> 
> I'll definitely be attending the summit and will make sure my proposed
> discussion has plenty of background links for evaluation.

Wonderful, thank you.

Also we usually discuss slot selection at an infra meeting so if you can
attend the infra meetings that will help in case folks have questions
when we are deciding.

Thanks Wayne,
Anita.

> 
> 
>>
>> Detail is appreciated as not everyone may understand the significance of
>> your proposal.
>>
>> Thank you,
>> Anita.
>>
>>>
>>>
>>>>
>>>> We've been pretty good at divide and conquer on the fly at summits,
>>>> but with the team growing I thought it would be valuable to call out
>>>> some of the key sessions ahead of time to make sure we have coverage.
>>>> I know I could always use some infra backup at the translations
>>>> sessions, which I've added a reference to seed this section.
>>>>
>>>> --
>>>> Elizabeth Krumbach Joseph || Lyz || pleia2
>>>>
>>>> ___
>>>> OpenStack-Infra mailing list
>>>> OpenStack-Infra@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Austin Design Summit space needs

[Anita Kuno]

On 03/23/2016 02:12 PM, Wayne Warren wrote:
> On Tue, Mar 22, 2016 at 3:23 PM, Elizabeth K. Joseph 
> wrote:
> 
>> On Fri, Mar 11, 2016 at 9:27 AM, Elizabeth K. Joseph
>>  wrote:
>>> https://etherpad.openstack.org/p/infra-newton-summit-planning
>>
>> I've also gone ahead and added a section at the bottom for "Other
>> sessions of interest" for non-infra sessions that an infra presence
>> would be particularly valuable at.
>>
> 
> Would this be a good place to propose JJB design discussion (both my recent
> 2.x work and more general YamlParser features moving forward)?

Yes, it is a good place to propose any design discussion related to infra.

We will look at all proposed ideas and make decisions about what gets a
slot and when in a bit (not sure when we will start) so all ideas are
welcome at this stage.

Hopefully you will be attending summit and will identify yourself as
chair/moderator of the session you are proposing.

Detail is appreciated as not everyone may understand the significance of
your proposal.

Thank you,
Anita.

> 
> 
>>
>> We've been pretty good at divide and conquer on the fly at summits,
>> but with the team growing I thought it would be valuable to call out
>> some of the key sessions ahead of time to make sure we have coverage.
>> I know I could always use some infra backup at the translations
>> sessions, which I've added a reference to seed this section.
>>
>> --
>> Elizabeth Krumbach Joseph || Lyz || pleia2
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/22/2016 02:45 PM, Colleen Murphy wrote:
> On Mon, Mar 21, 2016 at 10:17 AM, Colleen Murphy 
> wrote:
> 
>> On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy 
>> wrote:
>>
>>> The networking team at HPE received our request and would like to have a
>>> call next week to review it. Our liaison, Venu, should have a draft network
>>> diagram we can review. Who would like to join, and what times/days work
>>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
>>> meeting).
>>>
>>> Colleen
>>>
>> A call has been scheduled for 1800-1845 UTC on Tuesday, March 22.
>> Invitations were sent out to folks who expressed interest in attending and
>> I can share the meeting phone number and conference ID with anyone who was
>> missed.
>>
>> Allison brought up using the asterisk server for the call and it was not
>> responded to - I suspect either they didn't understand or didn't feel
>> comfortable with it. It would be my preference to not push the issue, as
>> they are extending the invitation to us, not the other way around. Instead
>> I can commit to taking and dispersing detailed notes.
>>
>> Colleen
>>
> Notes from today's meeting:
> 
> 1) 1G or 10G?
>  - 10G useful for image transfers and mirrors in cloud
>  - Venu to connect with DC ops ensure 10G
> 
> 2) ipv6?
>  - Venu to ask verizon to activate /48 block, will take a couple of days
> 
> 3) how many vlans?
>  - one untagged for pxe/management, one tagged for public
> 
> 4) keep 10.10.16.0/24 for internal network
> 
> 5) Do we need nic bonding?
>  - no
> 
> 6) Any load balancing requirement?
>  - no
>  - if we were to add load balancing we would host it ourselves
> 
> 5) Access requirements?
>  - full inbound/outbound internet access - no ports blocked
>  - firewalls managed locally
> 
> The network diagram will need to have some parts redacted before we can
> share it publicly.
> 
> Colleen
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Thanks Colleen,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/21/2016 01:17 PM, Colleen Murphy wrote:
> On Thu, Mar 17, 2016 at 11:48 AM, Colleen Murphy 
> wrote:
> 
>> The networking team at HPE received our request and would like to have a
>> call next week to review it. Our liaison, Venu, should have a draft network
>> diagram we can review. Who would like to join, and what times/days work
>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
>> meeting).
>>
>> Colleen
>>
> A call has been scheduled for 1800-1845 UTC on Tuesday, March 22.
> Invitations were sent out to folks who expressed interest in attending and
> I can share the meeting phone number and conference ID with anyone who was
> missed.
> 
> Allison brought up using the asterisk server for the call and it was not
> responded to - I suspect either they didn't understand or didn't feel
> comfortable with it. It would be my preference to not push the issue, as
> they are extending the invitation to us, not the other way around. Instead
> I can commit to taking and dispersing detailed notes.
> 
> Colleen
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
I look forward to your detailed notes.

Thanks Colleen,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/17/2016 03:13 PM, Paul Belanger wrote:
> On Thu, Mar 17, 2016 at 03:10:25PM -0400, Anita Kuno wrote:
>> On 03/17/2016 03:05 PM, Paul Belanger wrote:
>>> On Thu, Mar 17, 2016 at 02:55:33PM -0400, Anita Kuno wrote:
>>>> On 03/17/2016 02:48 PM, Colleen Murphy wrote:
>>>>> The networking team at HPE received our request and would like to have a
>>>>> call next week to review it. Our liaison, Venu, should have a draft 
>>>>> network
>>>>> diagram we can review. Who would like to join, and what times/days work
>>>>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
>>>>> meeting).
>>>>>
>>>>> Colleen
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> OpenStack-Infra mailing list
>>>>> OpenStack-Infra@lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>>
>>>>
>>>> Is there any possibility we can use asterisk? Then we can just dial in:
>>>> https://wiki.openstack.org/wiki/Infrastructure/Conferencing
>>>>
>>>> Thanks Colleen for putting this together,
>>>> Anita.
>>>>
>>> I'd also like to suggest we record the audio, if people are okay with that. 
>>> This
>>> way people who cannot make the call will be able to review at a later date.
>>>
>>
>> I'm supportive of this suggestion. I've already tested asterisk for
>> recording and my experience is it works well. The issue raised last time
>> was where to store the audio file generated.
>>
>> Note, we would have to have permission of participants for recording. I
>> just got an audible "agreed" with the person saying their name when we
>> did it before.
>>
>> Last time I uploaded to afs after recording.
>>
> Right, we could default specific conference rooms in asterisk that record by
> default.  We'd also play a nice warning to each user explaining this.  After
> the conference room was deleted, we'd then sync the recording to some 
> location.
> 
> There might not be enough time to do all that for this call, but moving 
> forward
> it would be an option.

That sounds reasonable. Yeah we just need something to cover off privacy
laws about recording for various countries. The warning should satisfy
informed consent.

Thanks,
Anita.

> 
>> Thanks Paul,
>> Anita.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/17/2016 02:48 PM, Colleen Murphy wrote:
> The networking team at HPE received our request and would like to have a
> call next week to review it. Our liaison, Venu, should have a draft network
> diagram we can review. Who would like to join, and what times/days work
> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
> meeting).
> 
> Colleen
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Is there any possibility we can use asterisk? Then we can just dial in:
https://wiki.openstack.org/wiki/Infrastructure/Conferencing

Thanks Colleen for putting this together,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [new-project] Please add me to devstack-plugin-apr-* gerrit groups

[Anita Kuno]

On 03/17/2016 08:44 PM, Tony Breeds wrote:
> On Thu, Mar 17, 2016 at 08:37:52PM -0400, Paul Belanger wrote:
> 
>> Greeting OpenStack contributor! I've successfully added you to both groups.
>> Happy hacking.
> 
> Yagg thanks mtey!
> (for Anita)
> 
> Yours Tony.
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Ha ha ha.

Thanks Tony, I chuckled. :)
Anita.



signature.asc
Description: OpenPGP digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Network Requirements for Infracloud Relocation Deployment

[Anita Kuno]

On 03/17/2016 03:05 PM, Paul Belanger wrote:
> On Thu, Mar 17, 2016 at 02:55:33PM -0400, Anita Kuno wrote:
>> On 03/17/2016 02:48 PM, Colleen Murphy wrote:
>>> The networking team at HPE received our request and would like to have a
>>> call next week to review it. Our liaison, Venu, should have a draft network
>>> diagram we can review. Who would like to join, and what times/days work
>>> best? I would propose Tuesday at 1800 UTC (one hour before the Infra
>>> meeting).
>>>
>>> Colleen
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>
>> Is there any possibility we can use asterisk? Then we can just dial in:
>> https://wiki.openstack.org/wiki/Infrastructure/Conferencing
>>
>> Thanks Colleen for putting this together,
>> Anita.
>>
> I'd also like to suggest we record the audio, if people are okay with that. 
> This
> way people who cannot make the call will be able to review at a later date.
> 

I'm supportive of this suggestion. I've already tested asterisk for
recording and my experience is it works well. The issue raised last time
was where to store the audio file generated.

Note, we would have to have permission of participants for recording. I
just got an audible "agreed" with the person saying their name when we
did it before.

Last time I uploaded to afs after recording.

Thanks Paul,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] InfraCloud Project, Weekly Status Update - March 7th 2016

[Anita Kuno]

On 03/07/2016 11:08 PM, Cody A.W. Somerville wrote:
> InfraCloud Project, Weekly Status Update - March 7th 2016
> 
> Updates:
> 
> 1. Relocation of HW:
>  a. All HW in "US East" was shipped as of today, March 7th.
>  b. Shipment of HW in "US West" is delayed.
> 
> Risks:
> 
> 1. "US West" HW now must comply with DC decommission policy and procedures
> affecting all HW in US West HPE Cloud data centre. No ship date available
> at this time.
> 
> Changes Merged:
> 
> 1. Add infracloud runbook to regenerate images
>https://review.openstack.org/#/c/283856/
> 2. Safely fail when logs cannot be found
>https://review.openstack.org/#/c/284999/
> 3. Set the neutron parameters mandatory for controller
>https://review.openstack.org/#/c/284835/
> 4. Use unversioned identity endpoints
>https://review.openstack.org/#/c/288194/
> 5. Upgrade from kilo to liberty
>https://review.openstack.org/#/c/267817/
> 6. Upgrade infra-cloud to liberty
>https://review.openstack.org/#/c/267863/
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Thanks Cody:

I really like the very simple format. Very easy to digest.

I appreciate you taking this on.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [Third-party-announce] Four Cisco CI systems are disabled

[Anita Kuno]

Moving this post to the openstack-infra mailing list thread for
discussion. The third-party-announce thread is meant to be low traffic
for contacting third party ci operators. Discussion of third party tools
and systems are to take place on the openstack-infra mailing list.
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Thank you,
Anita.

On 03/07/2016 09:58 PM, Wan, Sam wrote:
> Hi,
>  
>  Our CI's ran into this issue too recently.
>  I've followed your suggestion to change merge-failure to only send SMTP 
> message.
>  But could you tell me why this issue happened?
> 
>  I've upgraded my zuul to latest 2.1.0. Is this OK?
>  Also someone told me that I might need to clean local zuul cache from time 
> to time, is that correct?
> 
> Thanks and regards.
> 
> --
> Shan Wan (Sam)  
> e2e Validation Lab (E-LAB) | Engineering Operations, Services & Solutions 
> (EOS2)
> w: (86)28.8296.6713 | 8F, C12, Tianfu Software Park, Chengdu, SC. China
> --
> 
> -Original Message-
> From: Bob Ball [mailto:bob.b...@citrix.com] 
> Sent: Monday, March 07, 2016 11:17 PM
> To: Announcements for third party CI operators.; Anita Kuno
> Subject: Re: [Third-party-announce] Four Cisco CI systems are disabled
> 
> Yes Yaroslav.
> 
> See 
> https://git.openstack.org/cgit/openstack-infra/project-config-example/tree/zuul/layout.yaml
>  for the recommended layout for a third party CI.
> 
> In this layout, merge-failure only sends an SMTP message and does not vote on 
> the change.
> 
> Thanks,
> 
> Bob
> 
> -Original Message-
> From: Yaroslav Morkovnikov (ymorkovn) [mailto:ymork...@cisco.com]
> Sent: 07 March 2016 08:10
> To: Anita Kuno 
> Cc: Announcements for third party CI operators. 
> 
> Subject: Re: [Third-party-announce] Four Cisco CI systems are disabled
> 
> Hi, Anita
> 
> Ok got It. 
> So the problem was on our end with zuul-merger. It brakes our sandbox where 
> mergers are goingAll next merges were unsuccessful. 
> We did not have handler for "merge-failure" event as result a default message 
> was posted So for now it configured as  
> merge-failure:
>   gerrit:
> verified: -1
> 
> Do you think that configuring like 
> merge-failure:
>   smtp:
> to: third_party...@example.com
> from: z...@example.com
> subject: .
> Is more correct and zull do not send message again? If so I will do that 
> instead
> merge-failure:
>   gerrit:
> verified: -1
> 
> Regards
> Yaroslav
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: Friday, March 04, 2016 7:34 PM
> To: Yaroslav Morkovnikov (ymorkovn)
> Cc: Announcements for third party CI operators.
> Subject: Re: [Third-party-announce] Four Cisco CI systems are disabled
> 
> On 03/04/2016 05:24 AM, Yaroslav Morkovnikov (ymorkovn) wrote:
>> Rebase was done. We have disabled sending -1 in case of fails. Could you 
>> unlock account. We will see how it's going on our end.
>>
>> _
>> From: Yaroslav Morkovnikov (ymorkovn)
>> Sent: Friday, March 04, 2016 11:31 AM
>> To: 'ante...@anteaya.info'
>> Cc: 'Announcements for third party CI operators.'
>> Subject: RE: [Third-party-announce] Four Cisco CI systems are disabled
>>
>>
>> Hi, Anita
>>
>> I have updated wiki regarding UCSm according requirements. As well 
>> UCSm CI do not post "-1" while bug is not resolved. I think it could 
>> be unblocked
>>
>> For other jobs what you mentioned I do not see any issues on my end. 
>> All of them are configured  like ...
>> pipelines:
>>   - name: check-pnr
>> manager: IndependentPipelineManager
>> trigger:
>>   gerrit:
>> - event: patchset-created
>> - event: change-restored
>> - event: comment-added
>>   comment_filter: (?i)^(Patch Set [0-9]+:\n\n)?\s*recheck\s*$
>> - event: comment-added
>>   comment_filter: (?i)^(Patch Set [0-9]+:\n\n)?\s*recheck 
>> cisco-nexus\s*$
>> success:
>>   gerrit:
>> verified: 1
>> failure:
>>   gerrit:
>> verified: -1
>> .
>>
>> It were not changed last 6 month.
>> Could you provide more details from your end?
>>
>> Regards
>> Yaroslav
>>
>> -Original

Re: [OpenStack-Infra] Austin Design Summit space needs

[Anita Kuno]

On 03/06/2016 11:18 PM, Joshua Hesketh wrote:
> This sounds good to me, thanks Jeremy. Do we have an etherpad for sessions
> yet? (I wonder if correlating to the two would be helpful).
> 
> On Mon, Mar 7, 2016 at 12:59 PM, Jeremy Stanley  wrote:
> 
>> This is woefully overdue, but I need to get back to Thierry and Mike
>> on Infra's design summit allocation request. Since it seemed like
>> Tokyo went remarkably well I'm inclined to just request the same as
>> we had last time (3 fishbowls, 4 workrooms, and a shared meetup day
>> with one or more other teams).
>>
>> If anyone has any serious objections to this and thinks we need
>> more/less of one or the other let me know.
>> --
>> Jeremy Stanley
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
This sounds good to me as well.

Thanks Jeremy,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerritbot

[Anita Kuno]

On 03/01/2016 10:02 AM, C.J. Collier wrote:
> Thanks for the clarification.  I'll bring my thoughts to gerrit in that
> case!

Wonderful, thank you C.J.,
Anita.

> On Mar 1, 2016 06:57, "Anita Kuno"  wrote:
> 
>> On 03/01/2016 09:39 AM, C.J. Collier wrote:
>>> Hello Anita,
>>>
>>> You bet.  I'll get it in to gerrit shortly.  It's not ready to be merged
>>> quite yet.  I just wanted to start a conversation.
>>
>> I totally understand. Having a conversation before a patch is merged
>> makes perfect sense.
>>
>> For us, that conversation takes place in gerrit on a patch rather than
>> on a mailing list in a thread. Gerrit has the option of setting workflow
>> -1 on a patch so the owner of the patch can indicate the patch is not
>> ready to be merged.
>>
>> When conversations about patches and approaches take place in gerrit,
>> folks who may not have been present for the beginning of the
>> conversation are able to see the history of comments on the patch and
>> can get themselves up to date. Contributors have become very adept at
>> using gerrit to sort patches and follow a conversation as it is ongoing
>> for patches in which they are interested.
>>
>> For instance here is a conversation that has been going on for 2 weeks
>> and is on its 10th patchset: https://review.openstack.org/#/c/282295/
>>
>> Let us know in infra if you have any questions about submitting a
>> patchset to gerrit.
>>
>> Thanks C.J.,
>> Anita.
>>
>>>
>>> For instance, would anyone be opposed to using a syslog sink for logging
>>> rather than opening up a dedicated file?  There are a lot of files (pid,
>>> log, config, channel list) being handled here, and directories for output
>>> files (/var/run/gerritbot, /var/log/gerritbot) need to be managed by the
>>> init script and kept in sync with the values in the config files.  Fewer
>> is
>>> better in my opinion, and hooking in to the syslog infrastructure means
>>> getting remote logging for no additional cost.  However, for systems
>>> without syslog facilities, I guess it make sense to have a dedicated log
>>> file.
>>>
>>> Let me know what you think,
>>>
>>> C.J.
>>> On Mar 1, 2016 00:16, "Anita Kuno"  wrote:
>>>
>>>> On 03/01/2016 01:22 AM, C.J. Collier wrote:
>>>>> Thanks Clark!  I found the same thing.  I've added a few of options
>> and a
>>>>> dependency on the getopt library.  Take a look at this patch and let me
>>>>> know if there's anything you'd like me to add / remove.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> C.J.
>>>>
>>>> Thanks for the patch, C.J.
>>>>
>>>> We put all our patches up in gerrit for review rather than attaching
>>>> diffs to emails, it is just our workflow.
>>>>
>>>> You might find http://docs.openstack.org/infra/manual/developers.html
>>>> interesting as it outlines our workflow including steps to get all the
>>>> account signups in order so you can submit a patch to gerrit.
>>>>
>>>> Thanks for your interest in gerritbot, C.J. We appreciate it.
>>>>
>>>> Anita.
>>>>
>>>>>
>>>>>
>>>>> On Mon, Feb 29, 2016 at 6:47 PM, Clark Boylan 
>>>> wrote:
>>>>>
>>>>>> On Mon, Feb 29, 2016, at 01:26 PM, C.J. Collier wrote:
>>>>>>> Hey folks,
>>>>>>>
>>>>>>> I'm having a heck of a time getting gerritbot working.  It currently
>>>>>>> exits
>>>>>>> prematurely without any console output and returns 0 to the calling
>>>>>>> process.  No entries in the logs.  Very frustrating.  Can I get some
>>>> help
>>>>>>> with this?
>>>>>>>
>>>>>>
>>>>>> Looking at the source [0] it uses a default pid lock file path, if I
>> had
>>>>>> to guess the user running the process isn't able to write to that
>>>>>> directory or it does not exist. You can specify an alternate path
>> under
>>>>>> ircbot.pid in the ini config file if I am reading that correctly.
>>>>>>
>>>>>> [0]
>>>>>>
>>>>>>
>>>>
>> https://git.openstack.org/cgit/openstack-infra/gerritbot/tree/gerritbot/bot.py#n344
>>>>>>
>>>>>> Hope this helps,
>>>>>> Clark
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> OpenStack-Infra mailing list
>>>>> OpenStack-Infra@lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>>
>>>>
>>>>
>>>> ___
>>>> OpenStack-Infra mailing list
>>>> OpenStack-Infra@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>
>>>
>>
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerritbot

[Anita Kuno]

On 03/01/2016 09:39 AM, C.J. Collier wrote:
> Hello Anita,
> 
> You bet.  I'll get it in to gerrit shortly.  It's not ready to be merged
> quite yet.  I just wanted to start a conversation.

I totally understand. Having a conversation before a patch is merged
makes perfect sense.

For us, that conversation takes place in gerrit on a patch rather than
on a mailing list in a thread. Gerrit has the option of setting workflow
-1 on a patch so the owner of the patch can indicate the patch is not
ready to be merged.

When conversations about patches and approaches take place in gerrit,
folks who may not have been present for the beginning of the
conversation are able to see the history of comments on the patch and
can get themselves up to date. Contributors have become very adept at
using gerrit to sort patches and follow a conversation as it is ongoing
for patches in which they are interested.

For instance here is a conversation that has been going on for 2 weeks
and is on its 10th patchset: https://review.openstack.org/#/c/282295/

Let us know in infra if you have any questions about submitting a
patchset to gerrit.

Thanks C.J.,
Anita.

> 
> For instance, would anyone be opposed to using a syslog sink for logging
> rather than opening up a dedicated file?  There are a lot of files (pid,
> log, config, channel list) being handled here, and directories for output
> files (/var/run/gerritbot, /var/log/gerritbot) need to be managed by the
> init script and kept in sync with the values in the config files.  Fewer is
> better in my opinion, and hooking in to the syslog infrastructure means
> getting remote logging for no additional cost.  However, for systems
> without syslog facilities, I guess it make sense to have a dedicated log
> file.
> 
> Let me know what you think,
> 
> C.J.
> On Mar 1, 2016 00:16, "Anita Kuno"  wrote:
> 
>> On 03/01/2016 01:22 AM, C.J. Collier wrote:
>>> Thanks Clark!  I found the same thing.  I've added a few of options and a
>>> dependency on the getopt library.  Take a look at this patch and let me
>>> know if there's anything you'd like me to add / remove.
>>>
>>> Cheers,
>>>
>>> C.J.
>>
>> Thanks for the patch, C.J.
>>
>> We put all our patches up in gerrit for review rather than attaching
>> diffs to emails, it is just our workflow.
>>
>> You might find http://docs.openstack.org/infra/manual/developers.html
>> interesting as it outlines our workflow including steps to get all the
>> account signups in order so you can submit a patch to gerrit.
>>
>> Thanks for your interest in gerritbot, C.J. We appreciate it.
>>
>> Anita.
>>
>>>
>>>
>>> On Mon, Feb 29, 2016 at 6:47 PM, Clark Boylan 
>> wrote:
>>>
>>>> On Mon, Feb 29, 2016, at 01:26 PM, C.J. Collier wrote:
>>>>> Hey folks,
>>>>>
>>>>> I'm having a heck of a time getting gerritbot working.  It currently
>>>>> exits
>>>>> prematurely without any console output and returns 0 to the calling
>>>>> process.  No entries in the logs.  Very frustrating.  Can I get some
>> help
>>>>> with this?
>>>>>
>>>>
>>>> Looking at the source [0] it uses a default pid lock file path, if I had
>>>> to guess the user running the process isn't able to write to that
>>>> directory or it does not exist. You can specify an alternate path under
>>>> ircbot.pid in the ini config file if I am reading that correctly.
>>>>
>>>> [0]
>>>>
>>>>
>> https://git.openstack.org/cgit/openstack-infra/gerritbot/tree/gerritbot/bot.py#n344
>>>>
>>>> Hope this helps,
>>>> Clark
>>>>
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerritbot

[Anita Kuno]

On 03/01/2016 01:22 AM, C.J. Collier wrote:
> Thanks Clark!  I found the same thing.  I've added a few of options and a
> dependency on the getopt library.  Take a look at this patch and let me
> know if there's anything you'd like me to add / remove.
> 
> Cheers,
> 
> C.J.

Thanks for the patch, C.J.

We put all our patches up in gerrit for review rather than attaching
diffs to emails, it is just our workflow.

You might find http://docs.openstack.org/infra/manual/developers.html
interesting as it outlines our workflow including steps to get all the
account signups in order so you can submit a patch to gerrit.

Thanks for your interest in gerritbot, C.J. We appreciate it.

Anita.

> 
> 
> On Mon, Feb 29, 2016 at 6:47 PM, Clark Boylan  wrote:
> 
>> On Mon, Feb 29, 2016, at 01:26 PM, C.J. Collier wrote:
>>> Hey folks,
>>>
>>> I'm having a heck of a time getting gerritbot working.  It currently
>>> exits
>>> prematurely without any console output and returns 0 to the calling
>>> process.  No entries in the logs.  Very frustrating.  Can I get some help
>>> with this?
>>>
>>
>> Looking at the source [0] it uses a default pid lock file path, if I had
>> to guess the user running the process isn't able to write to that
>> directory or it does not exist. You can specify an alternate path under
>> ircbot.pid in the ini config file if I am reading that correctly.
>>
>> [0]
>>
>> https://git.openstack.org/cgit/openstack-infra/gerritbot/tree/gerritbot/bot.py#n344
>>
>> Hope this helps,
>> Clark
>>
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Not able to login in review.openstack.org

[Anita Kuno]

On 02/16/2016 08:31 PM, Jeremy Stanley wrote:
> On 2016-02-16 12:17:13 -0800 (-0800), Suhani Gupta wrote:
>> I am sorry I have mailed earlier confirming that I will not be
>> using my personal account for third party CI.

Your first email went to me personally and I'm traveling at the moment
so I'm glad Jeremy was able to help you out.

Please email the list for communication not me personally as the group
can operate more effectively in cases such as this one, than any one
individual.

Thank you,
Anita.

>> If someone can
>> enable my account again that would be of great help.
> 
> I have reactivated account 20395 now. Thanks for following up!
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Not able to login in review.openstack.org

[Anita Kuno]

On 02/16/2016 08:01 AM, Suhani Gupta wrote:
> Hi,
> 
> I am trying to login to gerrit review.openstack.org and is not able to
> login. It says:
> https://review.openstack.org/#SignInFailure,SIGN_IN,Contact+site+administrator
> 
> Please suggest what to do? I
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hello:

Someone was using your account to run a third party ci system so we
disabled your account.

http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-02-10.log.html#t2016-02-10T21:35:58

Personal accounts are not to be used to run third party ci accounts. We
disable personal gerrit accounts that are used for that purpose.

If your objective is to run a third party ci system you need to ensure
you are aware of all of the requirements on this page:
http://docs.openstack.org/infra/system-config/third_party.html

Once you are able to confirm and agree to use your personal gerrit
account for personal commiting and reviewing only, we can re-enable it.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerrit downtime on Friday 2016-02-12 at 22:00 UTC

[Anita Kuno]

On 02/11/2016 10:30 AM, Mateusz Matuszkowiak wrote:
> Hello!
> 
> I have created a small patch [0] which is about renaming 
> "openstack/fuel-plugin-astra” to "openstack/fuel-plugin-astara” (one 
> character missing).
> Please also include it within Gerrit downtime.
> 
> Thanks in advance.
> 
> [0] https://review.openstack.org/#/c/279138/ 
> 
> 
> Regards,
> --
> Fuel DevOps
> Mateusz Matuszkowiak

Thank you for letting us know, please add the patch to our list of
rename patches here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames

This is the list we consult when preparing for a rename window.

Thank you,
Anita.

> 
> 
> 
> 
>> On Feb 10, 2016, at 12:05 AM, Elizabeth K. Joseph  
>> wrote:
>>
>> Hi everyone,
>>
>> On Friday, February 12th at 22:00 UTC Gerrit will be unavailable for
>> about 60 minutes while we rename some projects.
>>
>> Existing reviews, project watches, etc, should all be carried over.
>> Currently, we plan on renaming the following projects:
>>
>> openstack/ceilometer-specs -> openstack/telemetry-specs
>> openstack/sahara-scenario -> openstack/sahara-tests
>>
>> This list is subject to change.
>>
>> If you have any questions about the maintenance, please reply here or
>> contact us in #openstack-infra on Freenode.
>>
>> -- 
>> Elizabeth Krumbach Joseph || Lyz || pleia2
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Mitaka Infra Sprint

[Anita Kuno]

On 02/09/2016 05:53 PM, Elizabeth K. Joseph wrote:
> On Wed, Dec 9, 2015 at 9:17 PM, Joshua Hesketh  
> wrote:
>> Hi all,
>> As discussed during the infra-meeting on Tuesday, the infra team will be
>> holding a mid-cycle sprint to focus on infra-cloud.
> 
> Some of this was covered at our meeting today[0] but I wanted to
> repeat and add a couple other things I was able to learn by making
> some calls and writing emails today:
> 
> If you're not renting a car, all three of the hotels listed on the
> InfraMitakaSprint wiki page[1] offer a local shuttle service that will
> take you anywhere within 3-5 miles, which includes the HPE office.
> You'll need to speak with hotel registration/concierge to arrange drop
> off/pick up each day, and you'll probably want to do this the night
> before to confirm availability. Airport transport-wise, you should
> also book the shuttle service in advance if you haven't already (I've
> added some links on the wiki).
> 
> In addition to a catered lunch each day, we will also be provided with
> morning coffee, tea and light breakfast items and 3PM coffee, tea and
> snacks. I've notified them about the dietary restrictions that people
> have included when they registered.

Also I don't know if anyone has mentioned but there is a cafeteria that
serves lunch which you can go to should you need to and there is also a
coffee shop that serves coffee and tea and has a few sweet things like
chocolate bars and cookies (not a large selection, but sugar). They
close early afternoon each day.

Thanks Lyz,
Anita.

> 
> As I mentioned at the meeting, if anyone has any other questions or
> concerns that I should pass along to our hosts, just let me know and
> I'll hunt down an answer.
> 
> [0] 
> http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-02-09-19.02.html
> [1] https://wiki.openstack.org/wiki/Sprints/InfraMitakaSprint
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] StoryBoard Midcycle Meetup

[Anita Kuno]

On 02/04/2016 10:47 AM, Zara Zaimeche wrote:
> Hi, all,
> 
> The StoryBoard[1] team is excited[2] to announce that we're hosting a
> meetup on the 17th of February, 2016, in Manchester, UK[3]! It's free to
> attend, and there will be cake.
> 
> Wiki Page: https://wiki.openstack.org/wiki/StoryBoard/Midcycle_Meetup
> 
> Etherpad: https://etherpad.openstack.org/p/StoryBoard_Mitaka_Midcycle
> 
> 
> This is just after the ops meetup [4], in the same city, so it should be
> convenient for anyone going there. Alternatively, why not come out on a
> spontaneous trip to Manchester? Actually, don't answer that. Anyway,
> please add yourself to the etherpad if interested, and/or specify a
> cake! :) And thanks to Codethink for sponsoring us.  We're happy to
> answer any questions in this thread or in #storyboard on freenode.
> 
> Best Wishes,
> 
> Zara
> 
> [1] https://storyboard.openstack.org/#!/page/about
> [2] We're even more excited to have finally gotten round to writing this
> email
> [3] Exact location:
> https://www.google.co.uk/maps/place/Ducie+House,+37+Ducie+St,+Manchester+M1+2JW/@53.4805451,-2.2308359,17z/data=!3m1!4b1!4m2!3m1!1s0x487bb1bc54a57815:0x5a08e799278b60b
> 
> [4] https://etherpad.openstack.org/p/MAN-ops-meetup
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Hey I heard there will be cake! Best doughnut I ever had was in Bristol.
I have high hopes for Manchester doughnuts.

Thanks Zara,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Mitaka Infra Sprint

[Anita Kuno]

On 01/18/2016 04:24 PM, Colleen Murphy wrote:
> On Wed, Dec 9, 2015 at 9:17 PM, Joshua Hesketh 
> wrote:
> 
>> Hi all,
>> As discussed during the infra-meeting on Tuesday[0], the infra team will
>> be holding a mid-cycle sprint to focus on infra-cloud[1].
>> The sprint is an opportunity to get in a room and really work through as
>> much code and reviews as we can related to infra-cloud while having each
>> other near by to discuss blockers, technical challenges and enjoy company.
>> Information + RSVP:
>> https://wiki.openstack.org/wiki/Sprints/InfraMitakaSprint
>> Dates:Mon. February 22nd at 9:00am to Thursday. February 25th
>> Location:HPE Fort Collins Colorado Office
>> Who:Anybody is welcome. Please put your name on the wiki page if you are
>> interested in attending.
>> If you have any questions please don't hesitate to ask.
>> Cheers,Josh + Infra team
>> [0]
>> http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-08-19.00.html[1]
>> https://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html
>>
>> Since I didn't see one, I started an etherpad for the sprint, and added it
> to the wiki page:
> 
> https://etherpad.openstack.org/p/mitaka-infra-midcycle
> 
> Colleen

Thanks Colleen,
Anita.

> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] can't login gerrit review.openstack.org with launchpad openid

[Anita Kuno]

On 01/04/2016 09:38 PM, Jerry Zhao wrote:
> 
>  Hi Infra
> I can't log into review.o.o with launchpad openid, although ssh to
> gerrit works and i can log into other openstack.org sites with openid as
> well.
> I kept being redirected to
> https://review.openstack.org/#SignInFailure,SIGN_IN,Contact+site+administrator
> with warning:
> "The page you requested was not found, or you do not have permission to
> view this page."
> 
> my username is zhaoxinyu, display name is Jerry Zhao and email is
> xyzje...@gmail.com
> 
> Could you investigate what it is going on?
> 
> Thanks!
> 
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Well as you stated in channel, the fact that you deleted one of your
launchpad emails today probably plays a role.

I don't know as I have encountered this situation before and don't know
what to advise.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Spot instances for CI

[Anita Kuno]

On 12/17/2015 11:55 AM, Jean-Daniel Bonnetot wrote:
> It’s not a technical question :)
> 
> The problem:
> The fact is CI need more resources, HP will quite and we need to find more 
> ressources, right?
> As a provider, I can tell you that is not easy to provide ressources and I 
> had to ask invests in our company to provide you what you need. As your needs 
> are huge, the invest is high… But I would like to do more.
> 
> The solution:
> OpenStack CI could be base on available ressources at many providers (which 
> means compute nodes not used or not full).
> You just need to manage when a spot instance is killed (because a customer 
> pays for a resource) and restart the job elsewhere.
> 
> The benefits:
> As providers we can give you more ressources, more quickly, more easily, 
> without asking for a large budget to our companies.
> 
> —
> Jean-Daniel Bonnetot
> http://www.ovh.com
> @pilgrimstack

Thank you Jean-Daniel:

We really appreciate all you do for us and your commitment to keeping us
running. It is really fantastic.

Our team upgraded Gerrit versions yesterday, which went well, now it
seems today we have multiple issues to contend with, isn't that always
the way. :)

Give us some time to discuss what you suggest and get back to you with a
response as a team.

We really appreciate your desire to help us and are very grateful for
your responsiveness on all things.

Thank you so much,
Anita.

> 
> 
> 
> 
>> Le 17 déc. 2015 à 16:08, Clint Byrum  a écrit :
>>
>> Excerpts from Jean-Daniel Bonnetot's message of 2015-12-17 01:24:33 -0800:
>>> Hi infra,
>>>
>>> You probably know that the foundation need more ressources for the CI.
>>> What do you think about pushing spot instances? 
>>> It could be a great solution for our CI and make a smaller step for 
>>> providers to give ressources « when they can ».
>>>
>>> https://review.openstack.org/#/c/104883/
>>
>> Help me map this to infra's needs. Right now generally a quota is given,
>> and that's as much as a provider can let infra use for free.
>>
>> So to take advantage of this, spot instances would need to have either
>> 0 impact on one's quota, or a separate quota. Yes? The word quota does
>> not appear in the spec, so I'm curious to hear how that would be managed
>> in general, but especially for nodepool usage by infra.
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [openstack-dev] [Congress] [infra] IRC broken

[Anita Kuno]

On 12/09/2015 08:29 PM, Tim Hinrichs wrote:
> The issue with #openstack-meeting seems to have resolved itself about 35
> minutes into our scheduled time.  The only thing that might be missing from
> the logs are messages where people were trying to figure out what was going
> on.  So if anyone missed the meeting, start at the 35 minute mark.
> 
> I included [infra] and a few more details below.

Infra has their own mailing list. I have included the infra mailing list
on this post.

It sounds like what you are describing is a netsplit:
https://en.wikipedia.org/wiki/Netsplit

This is common irc behaviour and has nothing to do with Infra or OpenStack.

Sorry your meeting was affected, glad you were able to carry on.

Thanks,
Anita.

> 
> - It seemed there was a partitioning in #openstack-meeting for a while.  I
> could #start the meeting, but except for 1 other person (masahito), no one
> could see my messages.  I could exchange messages with masahito, but
> neither of us could send messages to ekcs or ramineni.  I could, however,
> see ekcs and ramineni's messages to each other.
> 
> - We had the same problem with #congress.  I eventually called ekcs, and we
> tried to debug.
> 
> - I tried logging back in a couple of times, which eventually worked.  My
> nick changed.  At that point, I could exchange messages with ekcs and
> ramineni, and I could send messages to masahito, but I couldn't see
> messages from masahito.
> 
> - Just as we were about to cancel the meeting, #congress started working
> again.  Then #openstack-meeting started working, so we resumed the meeting.
>  (I'm not sure #congress started working first, or if we just all happened
> to notice #congress first.)
> 
> If anyone has any other pertinent details, please include them.
> 
> Tim
> 
> On Wed, Dec 9, 2015 at 5:07 PM Anita Kuno  wrote:
> 
>> On 12/09/2015 07:33 PM, Tim Hinrichs wrote:
>>> It seems IRC is broken for the meeting we're supposed to be having right
>>> now.  The symptom is that you can logon but may only see a fragment of
>> the
>>> users/messages that are being sent.  We even had a partitioning where 2
>>> people could exchange messages, and a different 2 people could exchange
>>> messages, but not all 4 people could exchange messages.
>>>
>>> Unless it fixes itself in the next few minutes, we'll cancel and have the
>>> discussion over email.  And given how late we're starting, we'll likely
>>> have an email discussion anyway.
>>>
>>> Tim
>>>
>>>
>>>
>>>
>> __
>>> 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
>>>
>>
>> It seems you were able to hold your meeting?
>>
>> http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-12-10-00.00.log.html
>>
>> I don't see anything wrong with the #openstack-meeting channel.
>>
>> Do let infra know if you have additional details.
>>
>> Thank you,
>> Anita.
>>
>> __
>> 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-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] QLogic CI Registration

[Anita Kuno]

On 12/02/2015 04:44 PM, Rick Hicksted wrote:
> rick.hicks...@qlogic.com
> rhicksted
> QLogic’s CI test account
> 
> Contact info:
> 
> Rick Hicksted
> 26650 Aliso Viejo Parkway
> Aliso Viejo CA 92656
> 
> Office:  949-389-6293
> Cell:  949-306-4893
> 
> ssh-rss 
> B3NzaC1yc2EDAQABgQCk7SgQiqJ67WQL4WT4EF664ynKjE20AGd5NKCz9OT8+CqupiPp95+XgSnn7Rvz21wVaFIcPm0uQYpRAgp0fNcHrd94Fw7JhMqwetSAb7JinJn6aJPJOTpZDOuWMxMX1BRgbN9Ivn/BcVpjylAH97g9pleK9NDK53cG+l3gVZs0tw==
>  rickhicks...@ricks-mbp.qlogic.org
> 
> Thanks,
> 
> Rick
> 
> 
> 
> This message and any attached documents contain information from the sending 
> company or its parent company(s), subsidiaries, divisions or branch offices 
> that may be confidential. If you are not the intended recipient, you may not 
> read, copy, distribute, or use this information. If you have received this 
> transmission in error, please notify the sender immediately by reply e-mail 
> and then delete this message.
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
I'm curious Rick, what prompted you to send this email to the infra
list? I am concerned you are following some very old instructions.

What instructions are you following and what are you hoping to achieve?

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [Infra] Gerrit downtime on November 18 2015

[Anita Kuno]

Sorry this got posted to the infra mailing list and missed the dev
mailing list.

Anita.

On 11/17/2015 08:04 PM, Spencer Krum wrote:
> Hello,
> 
> The infra team will not be upgrading gerrit tomorrow, as a result the
> planned outage will not occur. We do not have a date yet that we will be
> doing the upgrade, when we get one we will send out a notice to the
> list. If you have any questions you can hop in #openstack-infra and ask.
> 
> Thanks,
> Spencer
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] The gerrit account tingzhang has been deactivated

[Anita Kuno]

On 11/17/2015 03:03 AM, Anita Kuno wrote:
> On 11/17/2015 02:38 AM, Zhang, Monica wrote:
>> Ok, it seems that I find a solution, which is to use "silence mode" for 
>> gerrit plugin in Jenkins. ;)
> 
> Wonderful, I'm glad you found what you needed. None of the admins have
> been awake to address my request to re-enable your account so far, so it
> will have to wait probably another 9 or 10 hours.
> 
> Thanks for your patience Monica,
> Anita.

The account has been re-enabled. Thank you for your patience.

Anita.

> 
>>
>> -Original Message-
>> From: Zhang, Monica 
>> Sent: 2015年11月17日 14:21
>> To: 'Anita Kuno'
>> Cc: openstack-infra@lists.openstack.org
>> Subject: RE: The gerrit account tingzhang has been deactivated
>>
>> Thanks Anita! Nice to meeting you too!
>>
>> I learn from this lesson, also could you let me know besides gerrit plugin 
>> in Jenkins, is there any other plugin I can use to listen only the event, 
>> not publish to upstream? Or else, I need to create my own script or plugin 
>> to get gerrit event and do our customized pipeline.
>>
>> Thanks for your help~
>>
>> Regards,
>> Monica
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: 2015年11月17日 11:28
>> To: Zhang, Monica
>> Cc: openstack-infra@lists.openstack.org
>> Subject: Re: The gerrit account tingzhang has been deactivated
>>
>> On 11/16/2015 10:08 PM, Zhang, Monica wrote:
>>> Hi, Anita
>>>
>>> I was trying to setting up the Jenkins to listen the upstream merge event 
>>> via gerrit plugin, this is for our thirdparty CI to proactively merge 
>>> upstream event to our company repo, but somehow, during my experimental 
>>> test yesterday, since I don't understand gerrit plugin fully, haven't 
>>> disable the message part to send back to upstream gerrit. I'm sorry for 
>>> that. And I have removed my job in my Jenkins.  Sorry for the trouble I 
>>> made. And I'm appreciate your help and any advice for me to listen only for 
>>> upstream event and don't affect any upstream gerrit. Much thanks!
>>>
>>> Regards,
>>> Monica
>>
>> Wonderful, thank you, Monica. There are a number of experienced third party 
>> ci operators that can help with many of the common pitfalls new operators 
>> experience. Are you on irc at all? Here is a wikipage about
>> irc: https://wiki.openstack.org/wiki/IRC
>>
>> Our development workflow uses irc heavily and you and your team setting up 
>> your third party ci will do yourselves a big favour if you learn how to use 
>> irc, find a client you like and set up a bouncer so you can be available 
>> should someone have questions. The channels I suggest at minimum are 
>> #openstack-dev, #openstack-infra and whatever project channels for the 
>> projects you want to test with your third party system.
>>
>> Here is our meeting page: http://eavesdrop.openstack.org/ I suggest you 
>> participate in at least one third party meeting a week, there are three a 
>> week (I do believe) held in different time zones so hopefully you can find 
>> something that suits you.
>>
>> What your plugin did is just one of many common mistakes new operators make, 
>> we see it often but it does tire the community. By talking with and learning 
>> from some of the experienced third party operators you can learn how to 
>> avoid some of the other common mistakes.
>>
>> Thank you, Monica, I appreciate you sharing the details of your situation, 
>> allowing me to understand you, establish some trust and offer some support 
>> towards your goal.
>>
>> You can find me on irc as anteaya.
>>
>> I will request your gerrit account be reactivated, but it might take a while 
>> before someone is available to turn it back on.
>>
>> Thanks Monica, nice to meet you,
>> Anita.
>>
>>>
>>> -Original Message-
>>> From: Anita Kuno [mailto:ante...@anteaya.info]
>>> Sent: 2015年11月17日 11:02
>>> To: Zhang, Monica
>>> Cc: openstack-infra@lists.openstack.org
>>> Subject: Re: The gerrit account tingzhang has been deactivated
>>>
>>> On 11/16/2015 09:23 PM, Zhang, Monica wrote:
>>>> Hi, Anita
>>>>
>>>> I have disable my gerrit plugin to point to upstream, please reactivate my 
>>>> account.
>>>>
>>>> Thanks
>>>> Monica
>>>
>>> Hello Monica

Re: [OpenStack-Infra] The gerrit account tingzhang has been deactivated

[Anita Kuno]

On 11/17/2015 02:38 AM, Zhang, Monica wrote:
> Ok, it seems that I find a solution, which is to use "silence mode" for 
> gerrit plugin in Jenkins. ;)

Wonderful, I'm glad you found what you needed. None of the admins have
been awake to address my request to re-enable your account so far, so it
will have to wait probably another 9 or 10 hours.

Thanks for your patience Monica,
Anita.

> 
> -Original Message-
> From: Zhang, Monica 
> Sent: 2015年11月17日 14:21
> To: 'Anita Kuno'
> Cc: openstack-infra@lists.openstack.org
> Subject: RE: The gerrit account tingzhang has been deactivated
> 
> Thanks Anita! Nice to meeting you too!
> 
> I learn from this lesson, also could you let me know besides gerrit plugin in 
> Jenkins, is there any other plugin I can use to listen only the event, not 
> publish to upstream? Or else, I need to create my own script or plugin to get 
> gerrit event and do our customized pipeline.
> 
> Thanks for your help~
> 
> Regards,
> Monica
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: 2015年11月17日 11:28
> To: Zhang, Monica
> Cc: openstack-infra@lists.openstack.org
> Subject: Re: The gerrit account tingzhang has been deactivated
> 
> On 11/16/2015 10:08 PM, Zhang, Monica wrote:
>> Hi, Anita
>>
>> I was trying to setting up the Jenkins to listen the upstream merge event 
>> via gerrit plugin, this is for our thirdparty CI to proactively merge 
>> upstream event to our company repo, but somehow, during my experimental test 
>> yesterday, since I don't understand gerrit plugin fully, haven't disable the 
>> message part to send back to upstream gerrit. I'm sorry for that. And I have 
>> removed my job in my Jenkins.  Sorry for the trouble I made. And I'm 
>> appreciate your help and any advice for me to listen only for upstream event 
>> and don't affect any upstream gerrit. Much thanks!
>>
>> Regards,
>> Monica
> 
> Wonderful, thank you, Monica. There are a number of experienced third party 
> ci operators that can help with many of the common pitfalls new operators 
> experience. Are you on irc at all? Here is a wikipage about
> irc: https://wiki.openstack.org/wiki/IRC
> 
> Our development workflow uses irc heavily and you and your team setting up 
> your third party ci will do yourselves a big favour if you learn how to use 
> irc, find a client you like and set up a bouncer so you can be available 
> should someone have questions. The channels I suggest at minimum are 
> #openstack-dev, #openstack-infra and whatever project channels for the 
> projects you want to test with your third party system.
> 
> Here is our meeting page: http://eavesdrop.openstack.org/ I suggest you 
> participate in at least one third party meeting a week, there are three a 
> week (I do believe) held in different time zones so hopefully you can find 
> something that suits you.
> 
> What your plugin did is just one of many common mistakes new operators make, 
> we see it often but it does tire the community. By talking with and learning 
> from some of the experienced third party operators you can learn how to avoid 
> some of the other common mistakes.
> 
> Thank you, Monica, I appreciate you sharing the details of your situation, 
> allowing me to understand you, establish some trust and offer some support 
> towards your goal.
> 
> You can find me on irc as anteaya.
> 
> I will request your gerrit account be reactivated, but it might take a while 
> before someone is available to turn it back on.
> 
> Thanks Monica, nice to meet you,
> Anita.
> 
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: 2015年11月17日 11:02
>> To: Zhang, Monica
>> Cc: openstack-infra@lists.openstack.org
>> Subject: Re: The gerrit account tingzhang has been deactivated
>>
>> On 11/16/2015 09:23 PM, Zhang, Monica wrote:
>>> Hi, Anita
>>>
>>> I have disable my gerrit plugin to point to upstream, please reactivate my 
>>> account.
>>>
>>> Thanks
>>> Monica
>>
>> Hello Monica:
>>
>> Sorry I need to hear more from you. Why did you use a personal account to 
>> post automated messages and were you aware of what you were doing to patches 
>> on gerrit?
>>
>> Are you familiar with the contents of the third party page I linked to in my 
>> email to you?
>>
>> We need to establish some trust, you and I, just telling me to reactivate 
>> your account doesn't give me the trust I am looking for.
>>
>> Thanks Monica,
>> 

Re: [OpenStack-Infra] The gerrit account tingzhang has been deactivated

[Anita Kuno]

On 11/16/2015 10:08 PM, Zhang, Monica wrote:
> Hi, Anita
> 
> I was trying to setting up the Jenkins to listen the upstream merge event via 
> gerrit plugin, this is for our thirdparty CI to proactively merge upstream 
> event to our company repo, but somehow, during my experimental test 
> yesterday, since I don't understand gerrit plugin fully, haven't disable the 
> message part to send back to upstream gerrit. I'm sorry for that. And I have 
> removed my job in my Jenkins.  Sorry for the trouble I made. And I'm 
> appreciate your help and any advice for me to listen only for upstream event 
> and don't affect any upstream gerrit. Much thanks!
> 
> Regards,
> Monica

Wonderful, thank you, Monica. There are a number of experienced third
party ci operators that can help with many of the common pitfalls new
operators experience. Are you on irc at all? Here is a wikipage about
irc: https://wiki.openstack.org/wiki/IRC

Our development workflow uses irc heavily and you and your team setting
up your third party ci will do yourselves a big favour if you learn how
to use irc, find a client you like and set up a bouncer so you can be
available should someone have questions. The channels I suggest at
minimum are #openstack-dev, #openstack-infra and whatever project
channels for the projects you want to test with your third party system.

Here is our meeting page: http://eavesdrop.openstack.org/ I suggest you
participate in at least one third party meeting a week, there are three
a week (I do believe) held in different time zones so hopefully you can
find something that suits you.

What your plugin did is just one of many common mistakes new operators
make, we see it often but it does tire the community. By talking with
and learning from some of the experienced third party operators you can
learn how to avoid some of the other common mistakes.

Thank you, Monica, I appreciate you sharing the details of your
situation, allowing me to understand you, establish some trust and offer
some support towards your goal.

You can find me on irc as anteaya.

I will request your gerrit account be reactivated, but it might take a
while before someone is available to turn it back on.

Thanks Monica, nice to meet you,
Anita.

> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: 2015年11月17日 11:02
> To: Zhang, Monica
> Cc: openstack-infra@lists.openstack.org
> Subject: Re: The gerrit account tingzhang has been deactivated
> 
> On 11/16/2015 09:23 PM, Zhang, Monica wrote:
>> Hi, Anita
>>
>> I have disable my gerrit plugin to point to upstream, please reactivate my 
>> account.
>>
>> Thanks
>> Monica
> 
> Hello Monica:
> 
> Sorry I need to hear more from you. Why did you use a personal account to 
> post automated messages and were you aware of what you were doing to patches 
> on gerrit?
> 
> Are you familiar with the contents of the third party page I linked to in my 
> email to you?
> 
> We need to establish some trust, you and I, just telling me to reactivate 
> your account doesn't give me the trust I am looking for.
> 
> Thanks Monica,
> Anita.
> 
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: 2015年11月17日 5:30
>> To: Zhang, Monica
>> Cc: openstack-infra@lists.openstack.org
>> Subject: The gerrit account tingzhang has been deactivated
>>
>> Your gerrit account has been deactivated:
>>
>> {
>>   "_account_id": 11466,
>>   "name": "ting zhang",
>>   "email": "tingzh...@ebay.com",
>>   "username": "tingzhang",
>>   "avatars": []
>> }
>>
>> for leaving automated comments from a personal account:
>> https://review.openstack.org/#/c/231720/
>>
>> I am also informed this account has been deactivated previously for the same 
>> reason.
>>
>> This account will not be reactivated until the person responsible 
>> talks to me directly, demonstrating that they are aware of their 
>> actions and take responsibility for them. I will additionally be 
>> looking for a demonstration that those involved are aware of the 
>> information on this
>> page: http://docs.openstack.org/infra/system-config/third_party.html
>>
>> Thank you,
>> Anita.
>>
>> irc = anteaya
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] The gerrit account tingzhang has been deactivated

[Anita Kuno]

On 11/16/2015 09:23 PM, Zhang, Monica wrote:
> Hi, Anita
> 
> I have disable my gerrit plugin to point to upstream, please reactivate my 
> account.
> 
> Thanks
> Monica

Hello Monica:

Sorry I need to hear more from you. Why did you use a personal account
to post automated messages and were you aware of what you were doing to
patches on gerrit?

Are you familiar with the contents of the third party page I linked to
in my email to you?

We need to establish some trust, you and I, just telling me to
reactivate your account doesn't give me the trust I am looking for.

Thanks Monica,
Anita.

> 
> -----Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: 2015年11月17日 5:30
> To: Zhang, Monica
> Cc: openstack-infra@lists.openstack.org
> Subject: The gerrit account tingzhang has been deactivated
> 
> Your gerrit account has been deactivated:
> 
> {
>   "_account_id": 11466,
>   "name": "ting zhang",
>   "email": "tingzh...@ebay.com",
>   "username": "tingzhang",
>   "avatars": []
> }
> 
> for leaving automated comments from a personal account:
> https://review.openstack.org/#/c/231720/
> 
> I am also informed this account has been deactivated previously for the same 
> reason.
> 
> This account will not be reactivated until the person responsible talks to me 
> directly, demonstrating that they are aware of their actions and take 
> responsibility for them. I will additionally be looking for a demonstration 
> that those involved are aware of the information on this
> page: http://docs.openstack.org/infra/system-config/third_party.html
> 
> Thank you,
> Anita.
> 
> irc = anteaya
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] The gerrit account tingzhang has been deactivated

[Anita Kuno]

Your gerrit account has been deactivated:

{
  "_account_id": 11466,
  "name": "ting zhang",
  "email": "tingzh...@ebay.com",
  "username": "tingzhang",
  "avatars": []
}

for leaving automated comments from a personal account:
https://review.openstack.org/#/c/231720/

I am also informed this account has been deactivated previously for the
same reason.

This account will not be reactivated until the person responsible talks
to me directly, demonstrating that they are aware of their actions and
take responsibility for them. I will additionally be looking for a
demonstration that those involved are aware of the information on this
page: http://docs.openstack.org/infra/system-config/third_party.html

Thank you,
Anita.

irc = anteaya

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

[Anita Kuno]

On 11/04/2015 05:27 PM, Xicheng Chang wrote:
> Anita,
> 
> New change to move compass-install from stackforge to openstack namespace
> was submitted: https://review.openstack.org/#/c/241788/

Thank you,
Anita.

> 
> Weidong,
> 
> Please +2 https://review.openstack.org/#/c/241734/ ASAP to unretire
> compass-install.
> 
> Thanks,
> Xicheng
> 
> On Wed, Nov 4, 2015 at 12:43 PM, Anita Kuno  wrote:
> 
>> On 11/04/2015 03:42 PM, Xicheng Chang wrote:
>>> Will submit it soon. Thanks.
>>> Xicheng
>>
>> Thank you,
>> Anita.
>>
>>>
>>> On Wed, Nov 4, 2015 at 12:34 PM, Anita Kuno 
>> wrote:
>>>
>>>> On 11/03/2015 11:25 PM, Xicheng Chang wrote:
>>>>>>> This patch will allow the project to be moved to the openstack/
>>>>>>>>>> namespace as active projects are no longer in stackforge:
>>>>>>>>>> https://review.openstack.org/#/c/237753/ This patch is also
>>>> linked
>>>>>> here:
>>>>>>>>>>
>>>>>>>>>>
>>>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>>>>>>>>> oject_Renames
>>>>
>>>> We still need a patch for the rename to be offered to project-config.
>>>>
>>>> Thank you,
>>>> Anita.
>>>>
>>>
>>
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

[Anita Kuno]

On 11/04/2015 03:42 PM, Xicheng Chang wrote:
> Will submit it soon. Thanks.
> Xicheng

Thank you,
Anita.

> 
> On Wed, Nov 4, 2015 at 12:34 PM, Anita Kuno  wrote:
> 
>> On 11/03/2015 11:25 PM, Xicheng Chang wrote:
>>>>> This patch will allow the project to be moved to the openstack/
>>>>>>>> namespace as active projects are no longer in stackforge:
>>>>>>>> https://review.openstack.org/#/c/237753/ This patch is also
>> linked
>>>> here:
>>>>>>>>
>>>>>>>>
>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>>>>>>> oject_Renames
>>
>> We still need a patch for the rename to be offered to project-config.
>>
>> Thank you,
>> Anita.
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

[Anita Kuno]

On 11/03/2015 11:25 PM, Xicheng Chang wrote:
>>> This patch will allow the project to be moved to the openstack/
>>> > >> namespace as active projects are no longer in stackforge:
>>> > >> https://review.openstack.org/#/c/237753/ This patch is also linked
>> here:
>>> > >>
>>> > >> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>> > >> oject_Renames

We still need a patch for the rename to be offered to project-config.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

[Anita Kuno]

On 11/03/2015 11:25 PM, Xicheng Chang wrote:
> Please do not submit a duplicated CL as I have already submitted the first
> one:
> https://review.openstack.org/#/c/241410/
> <https://review.openstack.org/#/c/241410/>The second CL to revert the
> retirement of stack forge/compass-install was not successful because the
> repo now is read only. Please refer to my earlier email.
> 
> Thanks,
> Xicheng

Yes, the first change had to merge before we could reset permissions
manually.

The repo now can accept patch submissions:
https://review.openstack.org/#/admin/projects/stackforge/compass-install,access
please try to submit the second change now.

Thank you,
Anita.

> On Tuesday, November 3, 2015, Weidong.Shao  > wrote:
> 
>> Will send out a CL by tomorrow morning. I am on travel now.
>> On compass-monit, yes, it is to be deprecated as it has been.
>>
>> Thanks again for your help,
>> Weidong
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: Tuesday, November 03, 2015 11:45 AM
>> To: Weidong Shao; Weidong.Shao; mord...@inaugust.com;
>> openstack-infra@lists.openstack.org
>> Subject: Re: about move of stackforge - compass-install
>>
>> On 10/21/2015 01:22 AM, Weidong Shao wrote:
>>> Anita, Thanks for the detailed info!
>>>
>>> Weidong
>>
>> We still don't have patches up for moving this repo. We need them please.
>>
>> Also please reply with a clear intention that either compass-monit stays
>> where it is, retired in stackforge, or it is also moved at the same time as
>> compass-install. We don't want to have to do this a second time for
>> compass-monit.
>>
>> Thank you,
>> Anita.
>>
>>>
>>> On Tue, Oct 20, 2015 at 6:40 PM Anita Kuno  wrote:
>>>
>>>> On 10/20/2015 07:11 PM, Weidong.Shao wrote:
>>>>> Anita, Monty, and the infra-team:
>>>>>
>>>>> When I filled out the wiki regarding moving vs deprecating Compass
>>>> related repos, I made a mistake on compass-install.
>>>>> Now, is it still possible to make compass-install to openstack? We
>>>>> need
>>>> this for the installation of Compass.
>>>>>
>>>>> Thanks,
>>>>> Weidong
>>>>>
>>>>>
>>>>
>>>> Somehow this didn't get posted to the openstack-infra mailing list,
>>>> but I will reply including that list and hopefully it will post
>> successfully.
>>>>
>>>> Okay so this also happened to networking-bigswitch so the patches
>>>> that were offered to fix this were as follows:
>>>>
>>>> Someone on the infra team will have to manually change the gerrit
>>>> permissions on the repo before a patch to compass-install following
>>>> this pattern can merge:
>>>> https://review.openstack.org/#/c/237720/
>>>>
>>>> This patch reverts the removal of contents for the repo:
>>>> https://review.openstack.org/#/c/237741/
>>>>
>>>> This patch will allow the project to be moved to the openstack/
>>>> namespace as active projects are no longer in stackforge:
>>>> https://review.openstack.org/#/c/237753/ This patch is also linked
>> here:
>>>>
>>>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>>> oject_Renames
>>>>
>>>> In future should posts to the mailing list state activity is
>>>> happening to repos, please read the posts. Further if you receive an
>>>> email about your repo please read the email. If you are uncertain
>>>> about the information contained in the email and what it portends for
>>>> your repo, please ask. You can ask by sending an email to the
>>>> openstack-infra mailing list or by asking in the #openstack-infra irc
>> channel on freenode.
>>>>
>>>> The mass rename was a lot of work, changing repos that have been
>>>> retired is also a lot of work. The repo won't be moved from the
>>>> stackforge namespace until after we return from summit and then
>>>> decide on another gerrit downtime window to fix this.
>>>>
>>>> Thank you,
>>>> Anita.
>>>>
>>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Unretire compass-install

[Anita Kuno]

On 11/03/2015 06:36 PM, Xicheng Chang wrote:
> I see. Thanks, Anita. I will submit these changes ASAP. Should I just
> follow what networking-bigswitch  did for their repo?
> 
> Thanks,
> Xicheng

Yes please, follow what bigswitch did. Once the patches are up, we can
review them and suggest any changes that need to be made.

Thank you,
Anita.

> 
> On Tue, Nov 3, 2015 at 3:11 PM, Anita Kuno  wrote:
> 
>> On 11/03/2015 05:49 PM, Xicheng Chang wrote:
>>> Hi Anita,
>>>
>>> I am trying to understand the process to unretire compass-install and
>>> rename it to openstack namespace. In an earlier email you wrote:
>>> ">> Someone on the infra team will have to manually change the gerrit
>>>>> permissions on the repo before a patch to compass-install following
>>>>> this pattern can merge:
>>>>> https://review.openstack.org/#/c/237720/
>>>>>
>>>>> This patch reverts the removal of contents for the repo:
>>>>> https://review.openstack.org/#/c/237741/
>>>>>
>>>>> This patch will allow the project to be moved to the openstack/
>>>>> namespace as active projects are no longer in stackforge:
>>>>> https://review.openstack.org/#/c/237753/ This patch is also linked
>> here:
>>>>>
>>>>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>>>> oject_Renames
>>>>> "
>>>
>>> My understanding is that the first two CLs should be made by someone on
>> the
>>> infra team, and we are responsible for submitting the last CL. Am I
>> right?
>>>
>>> Thanks,
>>> Xicheng
>>>
>>
>> All the patches should be created by your team. Infra will only step in
>> to create patches if a patch is missing and we would miss the gerrit
>> downtime window if we didn't.
>>
>> My note on the first patch is that before the patch can be merged
>> someone with gerrit admin permissions needs to set the project
>> permissions manually to accept the merged patch. This would be an action
>> by the infra team and does not require a patch.
>>
>> Thanks for the email, do reply if you have any other questions. We are
>> set to rename this on Friday North America daytime so please don't delay
>> in ensuring this work is done.
>>
>> Thank you,
>> Anita.
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Unretire compass-install

[Anita Kuno]

On 11/03/2015 05:49 PM, Xicheng Chang wrote:
> Hi Anita,
> 
> I am trying to understand the process to unretire compass-install and
> rename it to openstack namespace. In an earlier email you wrote:
> ">> Someone on the infra team will have to manually change the gerrit
>>> permissions on the repo before a patch to compass-install following
>>> this pattern can merge:
>>> https://review.openstack.org/#/c/237720/
>>>
>>> This patch reverts the removal of contents for the repo:
>>> https://review.openstack.org/#/c/237741/
>>>
>>> This patch will allow the project to be moved to the openstack/
>>> namespace as active projects are no longer in stackforge:
>>> https://review.openstack.org/#/c/237753/ This patch is also linked here:
>>>
>>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>> oject_Renames
>>> "
> 
> My understanding is that the first two CLs should be made by someone on the
> infra team, and we are responsible for submitting the last CL. Am I right?
> 
> Thanks,
> Xicheng
> 

All the patches should be created by your team. Infra will only step in
to create patches if a patch is missing and we would miss the gerrit
downtime window if we didn't.

My note on the first patch is that before the patch can be merged
someone with gerrit admin permissions needs to set the project
permissions manually to accept the merged patch. This would be an action
by the infra team and does not require a patch.

Thanks for the email, do reply if you have any other questions. We are
set to rename this on Friday North America daytime so please don't delay
in ensuring this work is done.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] about move of stackforge - compass-install

[Anita Kuno]

On 11/03/2015 04:13 PM, Weidong.Shao wrote:
> Will send out a CL by tomorrow morning. I am on travel now. 
> On compass-monit, yes, it is to be deprecated as it has been. 
> 
> Thanks again for your help, 
> Weidong

Thank you for your quick, clear reply. I look forward to your patches
tomorrow. Safe travels.

Anita.

> 
> -Original Message-----
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Tuesday, November 03, 2015 11:45 AM
> To: Weidong Shao; Weidong.Shao; mord...@inaugust.com; 
> openstack-infra@lists.openstack.org
> Subject: Re: about move of stackforge - compass-install
> 
> On 10/21/2015 01:22 AM, Weidong Shao wrote:
>> Anita, Thanks for the detailed info!
>>
>> Weidong
> 
> We still don't have patches up for moving this repo. We need them please.
> 
> Also please reply with a clear intention that either compass-monit stays 
> where it is, retired in stackforge, or it is also moved at the same time as 
> compass-install. We don't want to have to do this a second time for 
> compass-monit.
> 
> Thank you,
> Anita.
> 
>>
>> On Tue, Oct 20, 2015 at 6:40 PM Anita Kuno  wrote:
>>
>>> On 10/20/2015 07:11 PM, Weidong.Shao wrote:
>>>> Anita, Monty, and the infra-team:
>>>>
>>>> When I filled out the wiki regarding moving vs deprecating Compass
>>> related repos, I made a mistake on compass-install.
>>>> Now, is it still possible to make compass-install to openstack? We 
>>>> need
>>> this for the installation of Compass.
>>>>
>>>> Thanks,
>>>> Weidong
>>>>
>>>>
>>>
>>> Somehow this didn't get posted to the openstack-infra mailing list, 
>>> but I will reply including that list and hopefully it will post 
>>> successfully.
>>>
>>> Okay so this also happened to networking-bigswitch so the patches 
>>> that were offered to fix this were as follows:
>>>
>>> Someone on the infra team will have to manually change the gerrit 
>>> permissions on the repo before a patch to compass-install following 
>>> this pattern can merge:
>>> https://review.openstack.org/#/c/237720/
>>>
>>> This patch reverts the removal of contents for the repo:
>>> https://review.openstack.org/#/c/237741/
>>>
>>> This patch will allow the project to be moved to the openstack/ 
>>> namespace as active projects are no longer in stackforge:
>>> https://review.openstack.org/#/c/237753/ This patch is also linked here:
>>>
>>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
>>> oject_Renames
>>>
>>> In future should posts to the mailing list state activity is 
>>> happening to repos, please read the posts. Further if you receive an 
>>> email about your repo please read the email. If you are uncertain 
>>> about the information contained in the email and what it portends for 
>>> your repo, please ask. You can ask by sending an email to the 
>>> openstack-infra mailing list or by asking in the #openstack-infra irc 
>>> channel on freenode.
>>>
>>> The mass rename was a lot of work, changing repos that have been 
>>> retired is also a lot of work. The repo won't be moved from the 
>>> stackforge namespace until after we return from summit and then 
>>> decide on another gerrit downtime window to fix this.
>>>
>>> Thank you,
>>> Anita.
>>>
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] about move of stackforge - compass-install

[Anita Kuno]

On 10/21/2015 01:22 AM, Weidong Shao wrote:
> Anita, Thanks for the detailed info!
> 
> Weidong

We still don't have patches up for moving this repo. We need them please.

Also please reply with a clear intention that either compass-monit stays
where it is, retired in stackforge, or it is also moved at the same time
as compass-install. We don't want to have to do this a second time for
compass-monit.

Thank you,
Anita.

> 
> On Tue, Oct 20, 2015 at 6:40 PM Anita Kuno  wrote:
> 
>> On 10/20/2015 07:11 PM, Weidong.Shao wrote:
>>> Anita, Monty, and the infra-team:
>>>
>>> When I filled out the wiki regarding moving vs deprecating Compass
>> related repos, I made a mistake on compass-install.
>>> Now, is it still possible to make compass-install to openstack? We need
>> this for the installation of Compass.
>>>
>>> Thanks,
>>> Weidong
>>>
>>>
>>
>> Somehow this didn't get posted to the openstack-infra mailing list, but
>> I will reply including that list and hopefully it will post successfully.
>>
>> Okay so this also happened to networking-bigswitch so the patches that
>> were offered to fix this were as follows:
>>
>> Someone on the infra team will have to manually change the gerrit
>> permissions on the repo before a patch to compass-install following this
>> pattern can merge:
>> https://review.openstack.org/#/c/237720/
>>
>> This patch reverts the removal of contents for the repo:
>> https://review.openstack.org/#/c/237741/
>>
>> This patch will allow the project to be moved to the openstack/
>> namespace as active projects are no longer in stackforge:
>> https://review.openstack.org/#/c/237753/ This patch is also linked here:
>>
>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames
>>
>> In future should posts to the mailing list state activity is happening
>> to repos, please read the posts. Further if you receive an email about
>> your repo please read the email. If you are uncertain about the
>> information contained in the email and what it portends for your repo,
>> please ask. You can ask by sending an email to the openstack-infra
>> mailing list or by asking in the #openstack-infra irc channel on freenode.
>>
>> The mass rename was a lot of work, changing repos that have been retired
>> is also a lot of work. The repo won't be moved from the stackforge
>> namespace until after we return from summit and then decide on another
>> gerrit downtime window to fix this.
>>
>> Thank you,
>> Anita.
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sit down to close gap due to cloud sunset

[Anita Kuno]

On 10/22/2015 07:46 AM, Anita Kuno wrote:
> This post is for organization and archival purposes. Posting opinions of
> a company's decision about their business strategy is off topic.
> 
> HP public cloud is going away as of 31 Jan 2016:
> http://h30499.www3.hp.com/t5/Grounded-in-the-Cloud/A-new-model-to-deliver-public-cloud/ba-p/6804409#.VifwJJcnFz3
> 
> Jim Meyer from HP would like to do what he can to close the gap with
> infra as a result of this decision.
> 
> In irc, it was decided to see if we could find a time to discuss this
> (Jim Meyer and infra developers who understand infra testing use of HP
> cloud).
> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-10-21.log.html#t2015-10-21T20:22:45
> 
> The current list i have of folks who should gather is Jim Meyer, Monty
> Taylor, Jim Blair, Jeremy Stanley, Clark Boylan, Elizabeth Joseph and
> myself, Anita Kuno.
> 
> Given that this is very short notice to organize a time to talk and that
> Jeremy and Clark arrive in Tokyo on Sunday night, as well as that it
> appears all of the above will be at the tc/board meeting on the Monday
> (I'm not positive about Elizabeth, can you share your plans Lyz?), the
> current plan is to try to find 15 or 20 minutes during lunch break to
> discuss this and create an agreement about next steps and a follow up plan.
> 
> I am informed the only room open during the Monday is the board room so
> we might have to make due with a hallway, lobby space, restaurant, or
> perhaps a corner of the room the board is meeting in. We might play this
> one by ear as I am expecting we will all be able to see each other
> during the Monday.
> 
> If you are reading this email and would like to donate public cloud
> resources, here is our documentation, please follow up with a thread to
> the infra list that is not a child of this post. Please start your own
> thread. http://docs.openstack.org/infra/system-config/contribute-cloud.html
> 
> If this development spurs you to want to discuss infra's relationship
> with companies who host public clouds, the Friday meetup at summit would
> be a good place to have that conversation. Doing so on this thread would
> again be considered off topic.
> 
> The infra team is very grateful and appreciative of the companies that
> take the time, trouble and take on the considerable work load to make a
> commitment to OpenStack's development and support it. We are grateful
> for our past relationship and we also acknowledge the speed with which
> Jim Meyer made contact with the infra team on irc to offer his support
> to find a way through this situation.
> 
> Conversations that imply that the infra team is not grateful to our host
> cloud companies is not a reflection of the perspective of infra.
> 
> Thank you to those who support OpenStack development and allow this
> conversation to proceed.
> 
> Anita.
> 

Does someone who was in attendance at this gathering feel like updating
the rest of us?

Given that my wishes were not honoured and someone who was well aware of
the organization of the meeting decided to gate crash rather than make
their desire to attend clear to everyone involved and following along on
the mailing list, I chose to not attend.

I am sure there are folks reading who are curious.

Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sit down to close gap due to cloud sunset

[Anita Kuno]

On 10/26/2015 11:59 AM, Clint Byrum wrote:
> Excerpts from Anita Kuno's message of 2015-10-26 11:39:46 +0900:
>> On 10/26/2015 11:30 AM, James E. Blair wrote:
>>> Anita Kuno  writes:
>>>
>>>> The current list i have of folks who should gather is Jim Meyer, Monty
>>>> Taylor, Jim Blair, Jeremy Stanley, Clark Boylan, Elizabeth Joseph and
>>>> myself, Anita Kuno.
>>>
>>> As this may relate to infra-cloud, it would be great if perhaps Clint
>>> and/or Colleen could join us as well.
>>>
>>> -Jim
>>>
>>
>> Thanks for speaking up Jim.
>>
>> Well two things, it being 11:35am and the board working lunch is
>> scheduled to begin at 11:45am
>> https://wiki.openstack.org/wiki/Governance/Foundation/26Oct2015BoardMeeting#Board_of_Directors_-_October_26.2C_2015_Meeting
>> (the board is running late, but the point is that we have to take the
>> chance to gather when it presents itself) one or both of Clint and
>> Colleen would need to be present in the room the board meeting is taking
>> place fairly quickly and secondly, if there are any objections from
>> anyone else as this is a rather late proposal and I do believe that
>> Clint at least was in channel at the time the initial discussion took
>> place and didn't speak up.
>>
>> Baring an objection and given they are available, then a accept the
>> proposal.
>>
> 
> Thanks Anita. I'm here in the room and will be participating in the
> sit-down.
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Thank you Clint, I see you.

Jeremy has a reply pending. Let's see what he says.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sit down to close gap due to cloud sunset

[Anita Kuno]

On 10/26/2015 11:30 AM, James E. Blair wrote:
> Anita Kuno  writes:
> 
>> The current list i have of folks who should gather is Jim Meyer, Monty
>> Taylor, Jim Blair, Jeremy Stanley, Clark Boylan, Elizabeth Joseph and
>> myself, Anita Kuno.
> 
> As this may relate to infra-cloud, it would be great if perhaps Clint
> and/or Colleen could join us as well.
> 
> -Jim
> 

Thanks for speaking up Jim.

Two things, it being 11:40 and the lunch break is scheduled for 11:45
https://wiki.openstack.org/wiki/Governance/Foundation/26Oct2015BoardMeeting#Board_of_Directors_-_October_26.2C_2015_Meeting
one or both of Clint or Colleen need to be present when we have the
opportunity to meet. Secondly, I believe Clint at least was aware of the
conversation when the meeting was proposed and didn't speak up about
attending.

Barring an objection and given they are available, I accept the proposal
to include one or both.

Thanks Jim,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sit down to close gap due to cloud sunset

[Anita Kuno]

On 10/26/2015 11:30 AM, James E. Blair wrote:
> Anita Kuno  writes:
> 
>> The current list i have of folks who should gather is Jim Meyer, Monty
>> Taylor, Jim Blair, Jeremy Stanley, Clark Boylan, Elizabeth Joseph and
>> myself, Anita Kuno.
> 
> As this may relate to infra-cloud, it would be great if perhaps Clint
> and/or Colleen could join us as well.
> 
> -Jim
> 

Thanks for speaking up Jim.

Well two things, it being 11:35am and the board working lunch is
scheduled to begin at 11:45am
https://wiki.openstack.org/wiki/Governance/Foundation/26Oct2015BoardMeeting#Board_of_Directors_-_October_26.2C_2015_Meeting
(the board is running late, but the point is that we have to take the
chance to gather when it presents itself) one or both of Clint and
Colleen would need to be present in the room the board meeting is taking
place fairly quickly and secondly, if there are any objections from
anyone else as this is a rather late proposal and I do believe that
Clint at least was in channel at the time the initial discussion took
place and didn't speak up.

Baring an objection and given they are available, then a accept the
proposal.

Thank you Jim,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Sit down to close gap due to cloud sunset

[Anita Kuno]

On 10/26/2015 07:04 AM, Joshua Hesketh wrote:
> Hey,
> 
> I'd love to be able to be there for this conversation, but sadly I'm
> travelling today. Hopefully we can touch base and catch up afterwards.
> 
> Cheers,
> Josh

Thanks for sharing your schedule, Josh. Yes we had to move quickly to
find a time so we could start the conversation. Today's meeting won't be
the end, just the beginning. As agreements and understandings develop
they will be shared so that those who are able can volunteer to support
the direction.

Safe travels Josh. See you soon,
Anita.

> 
> On Thu, Oct 22, 2015 at 9:46 AM, Anita Kuno  wrote:
> 
>> This post is for organization and archival purposes. Posting opinions of
>> a company's decision about their business strategy is off topic.
>>
>> HP public cloud is going away as of 31 Jan 2016:
>>
>> http://h30499.www3.hp.com/t5/Grounded-in-the-Cloud/A-new-model-to-deliver-public-cloud/ba-p/6804409#.VifwJJcnFz3
>>
>> Jim Meyer from HP would like to do what he can to close the gap with
>> infra as a result of this decision.
>>
>> In irc, it was decided to see if we could find a time to discuss this
>> (Jim Meyer and infra developers who understand infra testing use of HP
>> cloud).
>>
>> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-10-21.log.html#t2015-10-21T20:22:45
>>
>> The current list i have of folks who should gather is Jim Meyer, Monty
>> Taylor, Jim Blair, Jeremy Stanley, Clark Boylan, Elizabeth Joseph and
>> myself, Anita Kuno.
>>
>> Given that this is very short notice to organize a time to talk and that
>> Jeremy and Clark arrive in Tokyo on Sunday night, as well as that it
>> appears all of the above will be at the tc/board meeting on the Monday
>> (I'm not positive about Elizabeth, can you share your plans Lyz?), the
>> current plan is to try to find 15 or 20 minutes during lunch break to
>> discuss this and create an agreement about next steps and a follow up plan.
>>
>> I am informed the only room open during the Monday is the board room so
>> we might have to make due with a hallway, lobby space, restaurant, or
>> perhaps a corner of the room the board is meeting in. We might play this
>> one by ear as I am expecting we will all be able to see each other
>> during the Monday.
>>
>> If you are reading this email and would like to donate public cloud
>> resources, here is our documentation, please follow up with a thread to
>> the infra list that is not a child of this post. Please start your own
>> thread.
>> http://docs.openstack.org/infra/system-config/contribute-cloud.html
>>
>> If this development spurs you to want to discuss infra's relationship
>> with companies who host public clouds, the Friday meetup at summit would
>> be a good place to have that conversation. Doing so on this thread would
>> again be considered off topic.
>>
>> The infra team is very grateful and appreciative of the companies that
>> take the time, trouble and take on the considerable work load to make a
>> commitment to OpenStack's development and support it. We are grateful
>> for our past relationship and we also acknowledge the speed with which
>> Jim Meyer made contact with the infra team on irc to offer his support
>> to find a way through this situation.
>>
>> Conversations that imply that the infra team is not grateful to our host
>> cloud companies is not a reflection of the perspective of infra.
>>
>> Thank you to those who support OpenStack development and allow this
>> conversation to proceed.
>>
>> Anita.
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Sit down to close gap due to cloud sunset

[Anita Kuno]

This post is for organization and archival purposes. Posting opinions of
a company's decision about their business strategy is off topic.

HP public cloud is going away as of 31 Jan 2016:
http://h30499.www3.hp.com/t5/Grounded-in-the-Cloud/A-new-model-to-deliver-public-cloud/ba-p/6804409#.VifwJJcnFz3

Jim Meyer from HP would like to do what he can to close the gap with
infra as a result of this decision.

In irc, it was decided to see if we could find a time to discuss this
(Jim Meyer and infra developers who understand infra testing use of HP
cloud).
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-10-21.log.html#t2015-10-21T20:22:45

The current list i have of folks who should gather is Jim Meyer, Monty
Taylor, Jim Blair, Jeremy Stanley, Clark Boylan, Elizabeth Joseph and
myself, Anita Kuno.

Given that this is very short notice to organize a time to talk and that
Jeremy and Clark arrive in Tokyo on Sunday night, as well as that it
appears all of the above will be at the tc/board meeting on the Monday
(I'm not positive about Elizabeth, can you share your plans Lyz?), the
current plan is to try to find 15 or 20 minutes during lunch break to
discuss this and create an agreement about next steps and a follow up plan.

I am informed the only room open during the Monday is the board room so
we might have to make due with a hallway, lobby space, restaurant, or
perhaps a corner of the room the board is meeting in. We might play this
one by ear as I am expecting we will all be able to see each other
during the Monday.

If you are reading this email and would like to donate public cloud
resources, here is our documentation, please follow up with a thread to
the infra list that is not a child of this post. Please start your own
thread. http://docs.openstack.org/infra/system-config/contribute-cloud.html

If this development spurs you to want to discuss infra's relationship
with companies who host public clouds, the Friday meetup at summit would
be a good place to have that conversation. Doing so on this thread would
again be considered off topic.

The infra team is very grateful and appreciative of the companies that
take the time, trouble and take on the considerable work load to make a
commitment to OpenStack's development and support it. We are grateful
for our past relationship and we also acknowledge the speed with which
Jim Meyer made contact with the infra team on irc to offer his support
to find a way through this situation.

Conversations that imply that the infra team is not grateful to our host
cloud companies is not a reflection of the perspective of infra.

Thank you to those who support OpenStack development and allow this
conversation to proceed.

Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] new-project swauth

[Anita Kuno]

On 10/21/2015 11:28 AM, Lisak, Peter wrote:
> Hello Infra team,
> I'm a developer from Seznam.cz company 
> (http://stackalytics.com/report/companies/seznam.cz) and have started to 
> contribute to openstack/swift recently.
> 
> And reason I am writting to you:
> I would like to add swauth project (https://github.com/gholt/swauth) to 
> offical OpenStack projects. I know there is Keystone as the recommended 
> complex auth solution for the OpenStack family. But swauth is useful wsgi 
> middleware especially for smaller installation and development.
> 
> We (as Seznam.cz company) have permission from swauth author 
> (https://github.com/gholt) to take it over and continue in 
> development/extending/fixing issues. So I will appreciate if swauth could 
> become an official OpenStack project and use gerrit for code review, 
> autotests and other great features to keep it "alive and health".
> 
> Will you be OK with it?
> 
> I want to know your opinion before create the project 
> (http://docs.openstack.org/infra/manual/creators.html).
> 
> Thanks for reply.
> 
> 
> --
> Peter Lisák
> peter.li...@firma.seznam.cz
> 
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Hello Peter,

The infrastructure team maintains the tooling for developers to develop
projects. The body that has input on the officialness of any given
project is the Technical Committee:
http://www.openstack.org/foundation/tech-committee/

It might be worth some of your time to peruse this site:
http://governance.openstack.org/
particularly here:
http://governance.openstack.org/reference/new-projects-requirements.html

Also as something to consider, we are just about to head to Tokyo (some
of us are there already) next week for summit:
https://www.openstack.org/summit/

Trends have shown weeks during summit are remarkably slow for email
traffic, so keep that in mind should you kick off an email discussion
wtih the tc right now.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Zuul comments to Gerrit

[Anita Kuno]

On 10/21/2015 10:58 AM, Francesco Santoro wrote:
> Hi Anita,
> thanks for your answer.
> 
> Since we noticed that our CI posted comments with no logs we stopped
> commenting on patches.

Oh how heartening, thank you. Your level of responsibility regarding
your third party ci's effect on the community makes me happy for the
day. Thank you, Francesco!

> 
> We were thinking to backport the patch mentioned by Jeremy in order to
> avoid waiting for the next zuul release.

That certainly is an option, yes.

> The idea is to correctly test the feature on the openstack-dev/ci-sandbox
> before starting commenting on other projects.
> What do you think?

Oh my goodness, two wonderful things you acknowledge in your email.
Thank you so much. I look forward to meeting you some day and shaking
your hand. Thank you Francesco. Yes, the ci-sandbox repo is the place to
test third party ci operations. My irc nickname is anteaya, if you want
me to look at any of your output while you are testing do ping me in
#openstack-infra.

Thank you so much, Francesco,
Anita.

> 
> Best regards,
> Francesco
> 
> On Wed, Oct 21, 2015 at 4:04 PM, Anita Kuno  wrote:
> 
>> On 10/21/2015 09:17 AM, Jeremy Stanley wrote:
>>> On 2015-10-21 13:36:41 +0200 (+0200), Francesco Santoro wrote:
>>> [...]
>>>> This setup is correctly working but zuul publishes comments also on
>>>> other patches that don't trigger any job.
>>> [...]
>>>
>>> It's because file and branch filters affect which jobs run, but
>>> comments are tied to whether pipelines are triggered (not to
>>> individual jobs).
>>>
>>> What you probably want is https://review.openstack.org/188383 which
>>> will cause Zuul not to report for a pipeline at all if it has no
>>> matching jobs for a change triggering it. This merged to master a
>>> few weeks after 2.1.0 was released so isn't in an officially
>>> released version yet. You could try running from the tip of the
>>> master branch to get this improvement, or backport the patch to your
>>> installed version, or wait for the next release.
>>>
>>
>> Please note that should you choose to wait for the next release, having
>> your third party ci system post comments to gerrit that contain no logs
>> is contrary to the requirements of third party ci systems:
>> http://docs.openstack.org/infra/system-config/third_party.html#requirements
>>
>> Jeremy was answering your technical inquiry about zuul and its versions.
>> I am addressing the expectations of every third party ci operator. You
>> are responsible for knowing and adhering to requirements.
>>
>> Thank you,
>> Anita.
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Zuul comments to Gerrit

[Anita Kuno]

On 10/21/2015 09:17 AM, Jeremy Stanley wrote:
> On 2015-10-21 13:36:41 +0200 (+0200), Francesco Santoro wrote:
> [...]
>> This setup is correctly working but zuul publishes comments also on
>> other patches that don't trigger any job.
> [...]
> 
> It's because file and branch filters affect which jobs run, but
> comments are tied to whether pipelines are triggered (not to
> individual jobs).
> 
> What you probably want is https://review.openstack.org/188383 which
> will cause Zuul not to report for a pipeline at all if it has no
> matching jobs for a change triggering it. This merged to master a
> few weeks after 2.1.0 was released so isn't in an officially
> released version yet. You could try running from the tip of the
> master branch to get this improvement, or backport the patch to your
> installed version, or wait for the next release.
> 

Please note that should you choose to wait for the next release, having
your third party ci system post comments to gerrit that contain no logs
is contrary to the requirements of third party ci systems:
http://docs.openstack.org/infra/system-config/third_party.html#requirements

Jeremy was answering your technical inquiry about zuul and its versions.
I am addressing the expectations of every third party ci operator. You
are responsible for knowing and adhering to requirements.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] about move of stackforge - compass-install

[Anita Kuno]

On 10/20/2015 07:11 PM, Weidong.Shao wrote:
> Anita, Monty, and the infra-team:
> 
> When I filled out the wiki regarding moving vs deprecating Compass related 
> repos, I made a mistake on compass-install.
> Now, is it still possible to make compass-install to openstack? We need this 
> for the installation of Compass.
> 
> Thanks,
> Weidong
> 
> 

Somehow this didn't get posted to the openstack-infra mailing list, but
I will reply including that list and hopefully it will post successfully.

Okay so this also happened to networking-bigswitch so the patches that
were offered to fix this were as follows:

Someone on the infra team will have to manually change the gerrit
permissions on the repo before a patch to compass-install following this
pattern can merge:
https://review.openstack.org/#/c/237720/

This patch reverts the removal of contents for the repo:
https://review.openstack.org/#/c/237741/

This patch will allow the project to be moved to the openstack/
namespace as active projects are no longer in stackforge:
https://review.openstack.org/#/c/237753/ This patch is also linked here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames

In future should posts to the mailing list state activity is happening
to repos, please read the posts. Further if you receive an email about
your repo please read the email. If you are uncertain about the
information contained in the email and what it portends for your repo,
please ask. You can ask by sending an email to the openstack-infra
mailing list or by asking in the #openstack-infra irc channel on freenode.

The mass rename was a lot of work, changing repos that have been retired
is also a lot of work. The repo won't be moved from the stackforge
namespace until after we return from summit and then decide on another
gerrit downtime window to fix this.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Please add RedHat RDO CI to the "Third Party CI mail filter list"

[Anita Kuno]

On 10/15/2015 10:46 AM, Attila Darazs wrote:
> Hello Anita,
> 
> I'm in the process of setting up a new CI account and I'm going through
> the checklist
> (http://docs.openstack.org/infra/system-config/third_party.html#requirements)
> 
> The account's name is "RedHat RDO CI" with the email address of
> "rdo-ci-adm...@redhat.com".
> 
> We intend to CI some TripleO related projects on CentOS to begin with,
> later we might expand our testing to have a more general "works with
> RDO" level. We still need some time to get going.
> 
> I hope it's all right I wrote to you directly, you seem to post the most
> to third-party-annou...@lists.openstack.org
> 
> Best regards,
> Attila
> 

Please do not email me personally in future about third party matters,
ensure communication is somewhere that is archived, either a mailing
list, logged irc channel or a third party meeting (which takes place on
irc).

If you are unable to reach any of the individuals with the ability to
add your email to the Third Party CI mail filter list via irc either in
the #openstack-dev channel or a third party meeting then posting to the
infra mailing list is fine, but please try to reach one of us via irc
first: https://review.openstack.org/#/admin/groups/440,members

Your email has been added to the filter list.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [infra] Infra Design Summit Schedule

[Anita Kuno]

On 10/14/2015 07:13 PM, Jeremy Stanley wrote:
> Based on feedback from our last meeting and the discussion and
> subsequent voting in our session ideas pad, I've taken a first pass
> at scheduling:
> 
> http://mitakadesignsummit.sched.org/type/Infrastructure
> 
> I did the best I could to avoid obvious conflicts where necessary
> participants were likely to be involved in other summit tracks or
> conference talks, but due to the compressed nature of this round
> there's some unavoidable overlap (notably with QA, Docs, Ansible,
> Oslo, TripleO, and Ironic).
> 
> Also, since it ended up making more sense to collapse the Storyboard
> and Maniphest workroom sessions into the Task Tracking fishbowl
> session (individually they had fewer votes, and otherwise we either
> had to conflict with QA or do the corresponding workrooms before the
> fishbowl), we really only had three workroom topics so I've proposed
> spending our back-to-back Wednesday sessions on the most popular of
> the three: Masterless Puppet. I have confidence you'll let me know
> if this is insane, and in that case provide alternative suggestions!
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Thank you, this looks good to me.

Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] adding CI job for ovs native interface

[Anita Kuno]

On 10/08/2015 07:06 PM, fumihiko kakuma wrote:
> Hi,
> 
> Thank you for reply and adding CC.

You're welcome.

> 
> On Thu, 8 Oct 2015 11:25:22 -0400
> Anita Kuno  wrote:
> 
>> On 10/08/2015 08:06 AM, fumihiko kakuma wrote:
>>> Hello Anita,
>>>
>>> I work in ryu team in neutron. 
>>>
>>> We added a interface using ryu library to the ovs mechanism
>>> driver in liberty(it is called native interface).
>>> We want to run CI for it to verify behavior of the native interface.
>>> And I pushed the change to project-config to add a job for
>>> the ovs native interface.
>>> But it is not checked for several days.
>>>
>>> Could you infra team check the following change ?
>>>
>>> https://review.openstack.org/#/c/221143/
>>>
>>>
>>> Regards,
>>>
>>
>> Hello fumihiko:
>>
>> I future it is best to email to a mailing list rather than me personally.
>>
> 
> I understood it.
> I'm sorry for having sent an email personally.

That's okay, not to worry.

> 
>> Our reviewers work hard to review as many patches as they can in a day,
>> I am confident someone will review your patch as soon as they are able.
>>
> 
> I understand circumstances well.

Oh thank you, I'm grateful for your understanding.

Thank you,
Anita.

> 
>> Thank you,
>> Anita.
> 
> Thank you,
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] adding CI job for ovs native interface

[Anita Kuno]

On 10/08/2015 08:06 AM, fumihiko kakuma wrote:
> Hello Anita,
> 
> I work in ryu team in neutron. 
> 
> We added a interface using ryu library to the ovs mechanism
> driver in liberty(it is called native interface).
> We want to run CI for it to verify behavior of the native interface.
> And I pushed the change to project-config to add a job for
> the ovs native interface.
> But it is not checked for several days.
> 
> Could you infra team check the following change ?
> 
> https://review.openstack.org/#/c/221143/
> 
> 
> Regards,
> 

Hello fumihiko:

I future it is best to email to a mailing list rather than me personally.

Our reviewers work hard to review as many patches as they can in a day,
I am confident someone will review your patch as soon as they are able.

Thank you,
Anita.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Action required: stackforge/openvz-nova-driver project move

[Anita Kuno]

On 10/07/2015 06:27 PM, Michael Basnight wrote:
> I don't care about this. Does anyone else? Hell Paul doesn't even have that
> email addy anymore. Really only joe would care... Maybe...

hubcap!

> 
> On Wed, Oct 7, 2015 at 5:10 PM OpenStack Infrastructure Team <
> openstack-infra@lists.openstack.org> wrote:
> 
>> You appear to be associated with the stackforge/openvz-nova-driver project.
>>
>> The stackforge/ git repository namespace is being retired[1], and all
>> projects within need to move to the openstack/ namespace or, in the
>> case of inactive projects, identified as such and made read-only.
>>
>> For more background information, see this mailing list post and TC
>> resolution:
>>
>>
>> http://lists.openstack.org/pipermail/openstack-dev/2015-August/072140.html
>>
>> http://governance.openstack.org/resolutions/20150615-stackforge-retirement.html
>>
>> To ensure we have correctly identified all of the projects, we have
>> created a wiki page listing the projects that should be moved and the
>> projects that should be retired.  You may find it here:
>>
>>   https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement
>>
>> Your project is currently scheduled to become read only as of October
>> 17th.  Should you wish to continue active development on your project
>> please ensure the title of your project appears under "Active Projects
>> to Move" as soon as you recieve this email.  If you wish your project
>> to become read only please do nothing.
>>
>> Thank you for attending to this promptly,
>>
>> The OpenStack Infrastructure Team
>>
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [infra][nova][all] Pillow breaking gate?

[Anita Kuno]

On 10/01/2015 06:48 PM, Kevin L. Mitchell wrote:
> It looks like Pillow (pulled in by blockdiag, pulled in by
> sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably
> others) had a 3.0.0 release today, and now the gate is breaking because
> libjpeg isn't available in the image…thoughts on how best to address
> this problem?
> 

This patch is approved: https://review.openstack.org/#/c/230167/
It pins Pillow in global requirements to <3.0.0.

Infra is rebuilding images to include the necessary header.

Thanks Kevin,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Help with tagging releases for networking sub-projects

[Anita Kuno]

On 09/30/2015 11:32 AM, Kyle Mestery wrote:
> Hi infra folks!
> 
> I'm sending this email because I'm having trouble tagging and releasing
> some networking sub-projects to PyPi. For some, I've had success. See [1]
> as an example of one where I tagged the 1.0.0 release of networking-onos
> and it pushed to PyPi OK. For another, Octavia, I've never been able to get
> a PyPi release to happen. If you look [2], it's not there, just a stub
> version the Octavia folks put up. For Octavia, they had some issues with
> their PyPi project when I pushed 0.5.0 [3], so I pushed a 0.5.1 [4] after
> they addressed that but it still never showed up on PyPi. I've run into a
> similar problem with networking-ale-omniswitch. I wanted to release 1.0.0,
> but again, the push of the tag to gerrit shows up fine in git [5] but not
> on PyPi [6].
> 
> Any idea why some of these seem to work and others don't?
> 
> Thanks for your help!
> Kyle
> 
> [1] https://pypi.python.org/pypi/networking-onos/1.0.0
> [2] https://pypi.python.org/pypi/octavia/0.0.1.dev384
> [3] http://git.openstack.org/cgit/openstack/octavia/tag/?id=0.5.0
> [4] http://git.openstack.org/cgit/openstack/octavia/tag/?id=0.5.1
> [5]
> http://git.openstack.org/cgit/openstack/networking-ale-omniswitch/tag/?id=1.0.0
> [6] https://pypi.python.org/pypi/networking-ale-omniswitch
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

For you as a member of the neutron-release gerrit group to successfully
push a tag and have it appear on pypi, at least 3 things need to be in
place:

1) the neutron release gerrit group needs to have tagging permissions on
the repo. This is accomplished with the following stanza in the gerrit
acl file for the repo:

[access "refs/tags/*"]
pushSignedTag = group neutron-release

2) the project on pypi has to name openstackci as an owner of the pypi
project:

 Package Index Owner: openstackci, 

This one does: https://pypi.python.org/pypi/networking-onos/1.0.0

This one does not:
https://pypi.python.org/pypi/networking-ale-omniswitch/2015.1.2

3) the project in project-config has to have the publish-to-pypi job
configured to run on the repo:

This one does:
http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n2691

This one does not:
http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/layout.yaml#n2923

Once the projects you need to tag have all three requirements in place
the tagging should work. If it does not please return with examples and
we will continue.

Thanks Kyle,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [openstack-dev] Infra needs Gerrit developers

[Anita Kuno]

On 09/30/2015 09:26 AM, Remo Mattei wrote:
> Hello what are your requirements, I would not mind to help if my skills is 
> what you need. 
> 
> Ciao

Hello Remo:

Our requirements are a desire to help. Now if you happen to be familiar
with gerrit, the openstack workflow, java and debugging threading
issues, so much the better but our largest requirement is the desire to
help.

Thank you for asking. It would be great to meet you in the
#openstack-infra irc channel on freenode when you have a minute.

Thank you,
Anita (anteaya on irc)

> 
>> From: Zaro mailto:zaro0...@gmail.com>>
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>> > >
>> Date: Tuesday, September 29, 2015 at 5:30 PM
>> To: OpenStack Development Mailing List > >
>> Subject: [openstack-dev] Infra needs Gerrit developers
>>
>> Hello All,
>>
>> I believe you are all familiar with Gerrit.  Our community relies on it 
>> quite heavily and it is one of the most important applications in our CI 
>> infrastructure. I work on the OpenStack-infra team and I've been hacking on 
>> Gerrit for a while. I'm the infra team's sole Gerrit developer. I also test 
>> all our Gerrit upgrades prior to infra upgrading Gerrit.  There are many 
>> Gerrit feature and bug fix requests coming from the OpenStack community 
>> however due to limited resources it has been a challenge to meet those 
>> requests.
>>
>> I've been fielding some of those requests and trying to make Gerrit better 
>> for OpenStack.  I was wondering whether there are any other folks in our 
>> community who might also like to hack on a large scale java application 
>> that's being used by many corporations and open source projects in the 
>> world.  If so this is an opportunity for you to contribute.  I'm hoping to 
>> get more OpenStackers involved with the Gerrit community so we can 
>> collectively make OpenStack better.  If you would like to get involved let 
>> the openstack-infra folks know[1] and we will try help get you going. 
>>
>> For instance our last attempt to upgrading Gerrit failed due to a bug[2] 
>> that makes repos unusable on a diff timeout.   This bug is still not fixed 
>> so a nice way to contribute is to help us fix things like this so we can 
>> continue to use never versions of Gerrit.
>>
>> [1] in #openstack-infra or on openstack-infra@lists.openstack.org 
>> 
>> [2] https://code.google.com/p/gerrit/issues/detail?id=3424 
>>  
>>
>>
>> Thank You.
>> - Khai (AKA zaro)
>> !DSPAM:1,560bdfd7107146203035935!
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>>
>> !DSPAM:1,560bdfd7107146203035935!
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [openstack-dev] Infra needs Gerrit developers

[Anita Kuno]

On 09/30/2015 09:04 AM, Dimitry Ushakov wrote:
> Good morning,
> 
> I would definitely love to get involved after October.  I also have a few 
> people in mind who'd also love to help out.  Who should I chat with for more 
> details/setup?
> 
> Thanks,
> Dimitry

Welcome Dimitry:

You and anyone else you care to bring along can find us in the
#openstack-infra irc channel anytime.

Zaro is Khai's irc nick and is mostly available on pacific time. Others
are available to help and support in other time zones. Do drop by
anytime and say hello.

Thanks for your response,
Anita. (anteaya on irc)

> 
> From: Zaro mailto:zaro0...@gmail.com>>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
> mailto:openstack-...@lists.openstack.org>>
> Date: Tuesday, September 29, 2015 at 5:30 PM
> To: OpenStack Development Mailing List 
> mailto:openstack-...@lists.openstack.org>>
> Subject: [openstack-dev] Infra needs Gerrit developers
> 
> Hello All,
> 
> I believe you are all familiar with Gerrit.  Our community relies on it quite 
> heavily and it is one of the most important applications in our CI 
> infrastructure. I work on the OpenStack-infra team and I've been hacking on 
> Gerrit for a while. I'm the infra team's sole Gerrit developer. I also test 
> all our Gerrit upgrades prior to infra upgrading Gerrit.  There are many 
> Gerrit feature and bug fix requests coming from the OpenStack community 
> however due to limited resources it has been a challenge to meet those 
> requests.
> 
> I've been fielding some of those requests and trying to make Gerrit better 
> for OpenStack.  I was wondering whether there are any other folks in our 
> community who might also like to hack on a large scale java application 
> that's being used by many corporations and open source projects in the world. 
>  If so this is an opportunity for you to contribute.  I'm hoping to get more 
> OpenStackers involved with the Gerrit community so we can collectively make 
> OpenStack better.  If you would like to get involved let the openstack-infra 
> folks know[1] and we will try help get you going.
> 
> For instance our last attempt to upgrading Gerrit failed due to a bug[2] that 
> makes repos unusable on a diff timeout.   This bug is still not fixed so a 
> nice way to contribute is to help us fix things like this so we can continue 
> to use never versions of Gerrit.
> 
> [1] in #openstack-infra or on 
> openstack-infra@lists.openstack.org
> [2] https://code.google.com/p/gerrit/issues/detail?id=3424
> 
> 
> Thank You.
> - Khai (AKA zaro)
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Action required: stackforge/cookbook-pacemaker project move

[Anita Kuno]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/25/2015 06:29 PM, Samuel Cassiba wrote:
> Added it to the 'Inactive' list.

Thank you, that is the action we are looking for.

Anita.

> 
> On Fri, Sep 25, 2015 at 3:06 PM, JJ Asghar  wrote:
> 
>> 
> 
> On 9/25/15 4:57 PM, OpenStack Infrastructure Team wrote:
 You appear to be associated with the
 stackforge/cookbook-pacemaker
> project.
 
 The stackforge/ git repository namespace is being retired[1],
 and all projects within need to move to the openstack/
 namespace or, in the case of inactive projects, identified as
 such and made read-only.
 
> I'm pretty sure that the cookbook-pacemaker project isn't relevant 
> anymore. Please make it read-only.
> 
> Thanks!
> 
> Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2
> 
>> 
>> 
> 
> 
> 
> ___ OpenStack-Infra
> mailing list OpenStack-Infra@lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWBdtWAAoJELmKyZugNFU0Ui8H/RuQGSaSFIo5CJIRzaKVUhv0
buypHHis39bkEQl4gXi+s3cF9KP7LYiU2ZbhmTRW3+WpAR1p7Kb7+rhmsoW05d+q
RJzGFWl/5tKMta4wHIOAKFKE5Y7aQ1FX+iiiF1IyyjL19rnBJ9nMXe6M1ngY14zR
MzVBuzi9xgOxHHOUw2m/bfy1mxMRct1Km5FfJG3ipM0cRoPYtvVIHfkpSxB8HEst
GrUCsKuE8rLVmalksM9DtSs7a1RTpn3kkMlIrHM1geGC3sb/Q5ry/f0HauBrQSUx
6TJrfkBNbVtG0Kd3+TbcQyp3T53ELyfD22ClA8XhbUejfwb66Xc7B+p9UHpqa7I=
=PAqZ
-END PGP SIGNATURE-

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerrit downtime on Friday 2015-09-11 at 23:00 UTC

[Anita Kuno]

On 08/27/2015 12:51 PM, James E. Blair wrote:
> On Friday, September 11 at 23:00 UTC Gerrit will be unavailable for
> about 30 minutes while we rename some projects.
> 
> Existing reviews, project watches, etc, should all be carried
> over. Currently, we plan on renaming the following projects:
> 
>   stackforge/os-ansible-deployment -> openstack/openstack-ansible
>   stackforge/os-ansible-specs -> openstack/openstack-ansible-specs
> 
>   stackforge/solum -> openstack/solum
>   stackforge/python-solumclient -> openstack/python-solumclient
>   stackforge/solum-specs -> openstack/solum-specs
>   stackforge/solum-dashboard -> openstack/solum-dashboard
>   stackforge/solum-infra-guestagent -> openstack/solum-infra-guestagent
> 
>   stackforge/magnetodb -> openstack/magnetodb
>   stackforge/python-magnetodbclient -> openstack/python-magnetodbclient
>   stackforge/magnetodb-specs -> openstack/magnetodb-specs
> 
>   stackforge/kolla -> openstack/kolla
>   stackforge/neutron-powervm -> openstack/networking-powervm
> 
> This list is subject to change.
> 
> The projects in this list have recently become official OpenStack
> projects and many of them have been waiting patiently for some time to
> be moved from stackforge/ to openstack/.  This is likely to be the last
> of the so-called "big-tent" moves as we plan on retiring the stackforge/
> namespace and moving most of the remaining projects into openstack/ [1].
> 
> If you have any questions about the maintenance, please reply here or
> contact us in #openstack-infra on Freenode.
> 
> -Jim
> 
> [1] http://lists.openstack.org/pipermail/openstack-dev/2015-August/072140.html
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 

Reminder that gerrit downtime starts in about 8 hours.

stackforge/refstack -> openstack/refstack
stackforge/refstack-client -> openstack/refstack-client

will also be added to the rename list.

If you are an author of any of these rename patches it never hurts to be
standing by in the #openstack-infra irc channel in case of any last
minute questions.

For core reviewers of project-config, it would be great if you could
stop approving project-config changes at 2000 utc ensuring that last
minute rebases are avoided during the rename workflow. Thanks for your
understanding.

As always, if you have any questions we are available in
#openstack-infra to do our best to answer them.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Compass will move to the /openstack namespace in October

[Anita Kuno]

On 09/09/2015 08:59 PM, Weidong.Shao wrote:
> Anita, 
> 
> Regarding the CL, we still intend to enter the program after we clear some of 
> the questions from the review. 
> Shall I abandon the CL for now and re-apply in the future?
> 
> Thanks, 
> Weidong

As discussed in the infra channel, the namespace will no longer be
attached to the governance repo.

If you would like to be included in the governance repo, by all means
offer a patch and apply to the tc.

All remaining projects in stackforge will be moved to the openstack
namespace in October:
http://lists.openstack.org/pipermail/openstack-dev/2015-August/072140.html
https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement

Please abandon your patch, thank you,
Anita.

> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Wednesday, September 09, 2015 1:34 PM
> To: Jerry Zhao; Weidong.Shao; openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] Compass will move to the /openstack namespace 
> in October
> 
> On 09/09/2015 04:23 PM, Jerry Zhao wrote:
>> Hi Anita
>> I already asked Weidong to list the compass repos in the retirement 
>> wiki page about two weeks ago.
>> Per I just checked, there are duplicates listed now.
>> I am not sure if it will confuse the migration script if any.
>> Please go ahead and remove the duplicates.
>> Thanks!
> 
> Oh okay great, since that patch was still open and listed on the project 
> infrastructure agenda page under renames I didn't check first to see if there 
> were duplicates.
> 
> I will remove the duplicates.
> 
> Thank you.
> 
> Can the author abandon the patch please?
> 
> Thank you,
> Anita.
> 
>>
>> On 09/09/2015 11:54 AM, Anita Kuno wrote:
>>> Hello:
>>>
>>> Your request to move the compass project (4 repos) to the openstack 
>>> namespace in September will be done in October.
>>>
>>> The September rename will be limited to those projects currently 
>>> listed in the governance/projects.yaml file:
>>> http://git.openstack.org/cgit/openstack/governance/tree/reference/pro
>>> jects.yaml
>>>
>>>
>>> Compass is not listed so I have added it to the Stackforge Retirement
>>> wikipage:
>>> https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement
>>>
>>> Please confirm you see compass' repos listed under 'Active Projects 
>>> to Move'.
>>>
>>> You will not need a patch to move your repos from stackforge to 
>>> openstack in October so please abandon:
>>> https://review.openstack.org/#/c/196916/
>>>
>>> The October rename does not affect any application for your 
>>> project(s) to be listed in the governance repo. That is a separate issue.
>>>
>>> If you have any questions you are welcome to reply to this email or 
>>> find me on irc, the #openstack-infra channel is best and my irc 
>>> nickname is anteaya.
>>>
>>> Thank you,
>>> Anita.
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Compass will move to the /openstack namespace in October

[Anita Kuno]

On 09/09/2015 09:09 PM, Weidong.Shao wrote:
> Anita, 
> 
> per discussion on IRC, I have abandoned the CL. 
> 
> thanks, 
> Weidong

Wonderful, thank you,
Anita.

> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Wednesday, September 09, 2015 1:34 PM
> To: Jerry Zhao; Weidong.Shao; openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] Compass will move to the /openstack namespace 
> in October
> 
> On 09/09/2015 04:23 PM, Jerry Zhao wrote:
>> Hi Anita
>> I already asked Weidong to list the compass repos in the retirement 
>> wiki page about two weeks ago.
>> Per I just checked, there are duplicates listed now.
>> I am not sure if it will confuse the migration script if any.
>> Please go ahead and remove the duplicates.
>> Thanks!
> 
> Oh okay great, since that patch was still open and listed on the project 
> infrastructure agenda page under renames I didn't check first to see if there 
> were duplicates.
> 
> I will remove the duplicates.
> 
> Thank you.
> 
> Can the author abandon the patch please?
> 
> Thank you,
> Anita.
> 
>>
>> On 09/09/2015 11:54 AM, Anita Kuno wrote:
>>> Hello:
>>>
>>> Your request to move the compass project (4 repos) to the openstack 
>>> namespace in September will be done in October.
>>>
>>> The September rename will be limited to those projects currently 
>>> listed in the governance/projects.yaml file:
>>> http://git.openstack.org/cgit/openstack/governance/tree/reference/pro
>>> jects.yaml
>>>
>>>
>>> Compass is not listed so I have added it to the Stackforge Retirement
>>> wikipage:
>>> https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement
>>>
>>> Please confirm you see compass' repos listed under 'Active Projects 
>>> to Move'.
>>>
>>> You will not need a patch to move your repos from stackforge to 
>>> openstack in October so please abandon:
>>> https://review.openstack.org/#/c/196916/
>>>
>>> The October rename does not affect any application for your 
>>> project(s) to be listed in the governance repo. That is a separate issue.
>>>
>>> If you have any questions you are welcome to reply to this email or 
>>> find me on irc, the #openstack-infra channel is best and my irc 
>>> nickname is anteaya.
>>>
>>> Thank you,
>>> Anita.
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Compass will move to the /openstack namespace in October

[Anita Kuno]

On 09/09/2015 04:23 PM, Jerry Zhao wrote:
> Hi Anita
> I already asked Weidong to list the compass repos in the retirement wiki
> page about two weeks ago.
> Per I just checked, there are duplicates listed now.
> I am not sure if it will confuse the migration script if any.
> Please go ahead and remove the duplicates.
> Thanks!

Oh okay great, since that patch was still open and listed on the project
infrastructure agenda page under renames I didn't check first to see if
there were duplicates.

I will remove the duplicates.

Thank you.

Can the author abandon the patch please?

Thank you,
Anita.

> 
> On 09/09/2015 11:54 AM, Anita Kuno wrote:
>> Hello:
>>
>> Your request to move the compass project (4 repos) to the openstack
>> namespace in September will be done in October.
>>
>> The September rename will be limited to those projects currently listed
>> in the governance/projects.yaml file:
>> http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
>>
>>
>> Compass is not listed so I have added it to the Stackforge Retirement
>> wikipage:
>> https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement
>>
>> Please confirm you see compass' repos listed under 'Active Projects to
>> Move'.
>>
>> You will not need a patch to move your repos from stackforge to
>> openstack in October so please abandon:
>> https://review.openstack.org/#/c/196916/
>>
>> The October rename does not affect any application for your project(s)
>> to be listed in the governance repo. That is a separate issue.
>>
>> If you have any questions you are welcome to reply to this email or find
>> me on irc, the #openstack-infra channel is best and my irc nickname is
>> anteaya.
>>
>> Thank you,
>> Anita.
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Compass will move to the /openstack namespace in October

[Anita Kuno]

Hello:

Your request to move the compass project (4 repos) to the openstack
namespace in September will be done in October.

The September rename will be limited to those projects currently listed
in the governance/projects.yaml file:
http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

Compass is not listed so I have added it to the Stackforge Retirement
wikipage:
https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement

Please confirm you see compass' repos listed under 'Active Projects to
Move'.

You will not need a patch to move your repos from stackforge to
openstack in October so please abandon:
https://review.openstack.org/#/c/196916/

The October rename does not affect any application for your project(s)
to be listed in the governance repo. That is a separate issue.

If you have any questions you are welcome to reply to this email or find
me on irc, the #openstack-infra channel is best and my irc nickname is
anteaya.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Request to add members to swift-ceph-backend-core

[Anita Kuno]

On 09/04/2015 07:38 AM, Christian Schwede wrote:
> Hello OpenStack-Infra team,
> 
> could you please add the following members to the group
> swift-ceph-backend-core:
> 
> Thiago da Silva 
> Chmouel Boudjnah 
> Sebastien Han 
> Christian Schwede 
> 
> If you have any questions, please let me know.
> 
> Thank you very much in advance!
> 
> Christian Schwede
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
This project was created last June with this patch:
https://review.openstack.org/#/c/93102/

When alerted to needing to add members to a gerrit group we add the
author of the original patch.

Christian Schwede is a member of both:
https://review.openstack.org/#/admin/groups/372,members
and
https://review.openstack.org/#/admin/groups/373,members
and can add additional members as he sees fit.

We encourage release teams to be as small as possible, usually just one
person, unless that person is stepping aside then they add their
successor who removes the original member retaining the optimum number
of one for a -release team.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Change of Public Key

[Anita Kuno]

On 07/17/2015 12:55 PM, Xicheng Chang wrote:
> Hi Lyz,
> 
> The "third party testing doc" recommends that 3rd party CI accounts should
> be added to the Third Party CI mail filter list
>  by contacting
> coordinators. Is there a group email address for those coordinators or
> should I just send an email to all of them?
> 
> 
> Thanks,
> Xicheng

Hi Xicheng:

Anyone on this list can help you if you provide the name of the gerrit
ci account: https://review.openstack.org/#/admin/groups/440,members

I am on this list and can help you if you provide the name of the gerrit
ci account.

I can't speak for the others on this list but for something like this I
prefer if someone talks to me on irc.

Thanks,
Anita.
irc nick: anteaya

> 
> On Wed, Jul 15, 2015 at 8:48 PM, Elizabeth K. Joseph 
> wrote:
> 
>> On Wed, Jul 15, 2015 at 8:39 PM, Jerry Zhao  wrote:
>>> Hi
>>> I am afraid this account was created long ago through email request
>> instead of the procedure mentioned in the doc, so I don't have the password
>> to login Gerrit with.
>>
>> I see. Since we switched to self-service accounts the only process we
>> have for editing information is for you to create a new CI account
>> using the self-service process I linked to in the last email. You'll
>> want to go ahead and do that and update your system to use the new
>> account.
>>
>> Let us know when you've done this so we can then take care of cleaning
>> up the old account.
>>
>> --
>> Elizabeth Krumbach Joseph || Lyz || pleia2
>>
> 
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Fwd: IBM DB2 CI spam alot

[Anita Kuno]

On 06/11/2015 10:14 AM, Sean Dague wrote:
> On 06/11/2015 10:02 AM, Anita Kuno wrote:
>> On 06/11/2015 05:09 AM, yan fengxi wrote:
>>> Hi, everyone. The annoying problem is now resolved. But I found the DB2 CI
>>> account was already disabled.
>>> We need to get it enabled, so that we could test if our solution works, and
>>> we will not publish any results to community until then.
>>>
>>> @*Anita Kuno, would you please help on this?*
>>
>> If Sean agrees this is satisfactory, then yes, I can support your system
>> being re-enabled.
> 
> Yes, sounds fine.

Thank you, Sean.

Yan Fengxi, your gerrit account is re-enabled. I suggest following up
with Sean on irc (sdague) after you begin commenting again to ensure
what you are posting is inline with expectations.

Thank you,
Anita.

> 
>>
>> Thank you,
>> Anita.
>>>
>>>
>>> -- Forwarded message --
>>> From: yan fengxi 
>>> Date: Thu, Jun 11, 2015 at 2:01 PM
>>> Subject: IBM DB2 CI spam alot
>>> To: s...@dague.net
>>> Cc: openstack-infra@lists.openstack.org, yanfen...@cn.ibm.com,
>>> good...@gmail.com
>>>
>>>
>>> Hi, Sean, I am the DB2 CI maintainer "yanfengxi". Thanks for reminding us
>>> this problem. It is indeed annoying to see merge failures.
>>> Now our team is trying to resolv this problem, by stopping to publish this
>>> kind of failures. Before it's resolved, our DB2 CI will not publish result
>>> to community.
>>>
>>> Actually, not long ago, we met merge failure errors. We configured our zuul
>>> to stop publishing "Merge failure" errors on specific patch. But we were
>>> not aware that patches that depends on the failed patch will also publish
>>> merge failures.
>>>
>>> Cheers
>>> Feng Xi Yan(yanfen...@cn.ibm.com)
>>>
>>> On Thu, Jun 11, 2015 at 5:26 AM, Sean Dague >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>>
>>> wrote:
>>>> * The IBM DB2 CI seems to be running a Zuul, and seems to be reporting
>>> *>* back on merge conflicts a lot in completely unhelpful ways -
>>> *>* https://review.openstack.org/#/c/188148/
>>> <https://review.openstack.org/#/c/188148/>
>>> *>>* It seems like no 3rd party CI should be sending merge conflict messages
>>> *>* to gerrit. This is my formal complaint on that front, and I'd like the
>>> *>* CI system turned off if it's not fixed in the near term.
>>> *>>* -Sean
>>> *>>* --
>>> *>* Sean Dague
>>> *>* http://dague.net <http://dague.net/>
>>> *>>* ___
>>> *>* OpenStack-Infra mailing list
>>> *>* OpenStack-Infra at lists.openstack.org
>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>
>>> *>* http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>*
>>>
>>
> 
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Fwd: IBM DB2 CI spam alot

[Anita Kuno]

On 06/11/2015 05:09 AM, yan fengxi wrote:
> Hi, everyone. The annoying problem is now resolved. But I found the DB2 CI
> account was already disabled.
> We need to get it enabled, so that we could test if our solution works, and
> we will not publish any results to community until then.
> 
> @*Anita Kuno, would you please help on this?*

If Sean agrees this is satisfactory, then yes, I can support your system
being re-enabled.

Thank you,
Anita.
> 
> 
> -- Forwarded message --
> From: yan fengxi 
> Date: Thu, Jun 11, 2015 at 2:01 PM
> Subject: IBM DB2 CI spam alot
> To: s...@dague.net
> Cc: openstack-infra@lists.openstack.org, yanfen...@cn.ibm.com,
> good...@gmail.com
> 
> 
> Hi, Sean, I am the DB2 CI maintainer "yanfengxi". Thanks for reminding us
> this problem. It is indeed annoying to see merge failures.
> Now our team is trying to resolv this problem, by stopping to publish this
> kind of failures. Before it's resolved, our DB2 CI will not publish result
> to community.
> 
> Actually, not long ago, we met merge failure errors. We configured our zuul
> to stop publishing "Merge failure" errors on specific patch. But we were
> not aware that patches that depends on the failed patch will also publish
> merge failures.
> 
> Cheers
> Feng Xi Yan(yanfen...@cn.ibm.com)
> 
> On Thu, Jun 11, 2015 at 5:26 AM, Sean Dague  <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>>
> wrote:
>> * The IBM DB2 CI seems to be running a Zuul, and seems to be reporting
> *>* back on merge conflicts a lot in completely unhelpful ways -
> *>* https://review.openstack.org/#/c/188148/
> <https://review.openstack.org/#/c/188148/>
> *>>* It seems like no 3rd party CI should be sending merge conflict messages
> *>* to gerrit. This is my formal complaint on that front, and I'd like the
> *>* CI system turned off if it's not fixed in the near term.
> *>>* -Sean
> *>>* --
> *>* Sean Dague
> *>* http://dague.net <http://dague.net/>
> *>>* ___
> *>* OpenStack-Infra mailing list
> *>* OpenStack-Infra at lists.openstack.org
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>
> *>* http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>*
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] IBM DB2 CI is disabled was IBM DB2 CI spam alot

[Anita Kuno]

On 06/10/2015 03:26 PM, Sean Dague wrote:
> The IBM DB2 CI seems to be running a Zuul, and seems to be reporting
> back on merge conflicts a lot in completely unhelpful ways -
> https://review.openstack.org/#/c/188148/
> 
> It seems like no 3rd party CI should be sending merge conflict messages
> to gerrit. This is my formal complaint on that front, and I'd like the
> CI system turned off if it's not fixed in the near term.
> 
>   -Sean
> 

Thank you, Sean, this account is currently disabled.

I agree that CI systems should only be posting useful information and
nothing else. I am reluctant to make yet another rule stating as such
since some folks don't follow the ones we have already and some projects
have just thrown their hands up in terms of prodding peers to comply.

I am quite happy to exercise "infra discretion" at any time and would
consider this case to fall under that heading.

IMB DB2 CI operators, please address your system and oversee its
commenting. If you are uncertain what kind of comments are helpful I
encourage you to be in regular contact with the developers of the
project you are commenting on and listen to what they find helpful in
comments.

Thank you,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Your Gerrit Account has been temporarily disabled

[Anita Kuno]

On 06/04/2015 05:07 PM, Auld, Will wrote:
> Hi Anita,
> 
> I am just figuring out how to use Gerrit..., the whole tool chain really. In 
> the past I was trying to use the tool chain from windows but the docs I was 
> using had missing pieces so I decided to first figure it out with Linux. 
> Yesterday, I made a lot of progress along those lines and was able to submit 
> some changes to the sandbox system successfully. Today, I was doing some 
> defcore reviews which seemed to work OK, though I still feel like I don't 
> know what I am doing. The review work is through the web interface while the 
> sandbox submissions were through an Ubuntu guest VM. 
> 
> Thanks,
> 
> Will

This email was meant for Waldemar Znoinski. The -infra list was cc'd as
a way of archiving the conversation.

Thank you,
Anita.

> 
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: Thursday, June 04, 2015 12:15 PM
>> To: Znoinski, Waldemar
>> Cc: openstack-infra@lists.openstack.org
>> Subject: [OpenStack-Infra] Your Gerrit Account has been temporarily disabled
>>
>> Hi:
>>
>> We had an issue today with Gerrit being unable to broadcast stream events due
>> to stuck threads. we were having issues with this in the past but they 
>> cleared up
>> after we discovered that one of our third party ci operators had a script 
>> running
>> to keep ssh connections open. Today was the first time since we had the third
>> party ci operator turn off there script that we had an issue.
>>
>> Jeremy looked and discovered that there were a number of threads associated
>> with your personal gerrit account and in an attempt to get things moving 
>> again
>> disabled your personal gerrit account.
>>
>> Were you running any script or automated tool to do with ssh connections out
>> of your personal gerrit account? Can you think of anything unusual that 
>> might be
>> associated with your account? We are interested to hear from you.
>>
>> Once we get this cleared up we will re-enable your account. It is entirely 
>> possible
>> you did something you consider harmless and gerrit responded unexpectedly.
>> We appreciate your help.
>>
>> Also as a note, if testing anything that pertains to a ci system, that 
>> activity is
>> best done via a ci account, not a personal gerrit account.
>>
>> Thanks,
>> Anita.
>>
>> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-
>> infra.2015-06-04.log.html#t2015-06-04T18:24:26
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Your Gerrit Account has been temporarily disabled

[Anita Kuno]

Hi:

We had an issue today with Gerrit being unable to broadcast stream
events due to stuck threads. we were having issues with this in the past
but they cleared up after we discovered that one of our third party ci
operators had a script running to keep ssh connections open. Today was
the first time since we had the third party ci operator turn off there
script that we had an issue.

Jeremy looked and discovered that there were a number of threads
associated with your personal gerrit account and in an attempt to get
things moving again disabled your personal gerrit account.

Were you running any script or automated tool to do with ssh connections
out of your personal gerrit account? Can you think of anything unusual
that might be associated with your account? We are interested to hear
from you.

Once we get this cleared up we will re-enable your account. It is
entirely possible you did something you consider harmless and gerrit
responded unexpectedly. We appreciate your help.

Also as a note, if testing anything that pertains to a ci system, that
activity is best done via a ci account, not a personal gerrit account.

Thanks,
Anita.

http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-06-04.log.html#t2015-06-04T18:24:26

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] PuppetBoard

[Anita Kuno]

On 04/27/2015 02:33 PM, Elizabeth K. Joseph wrote:
> On Sun, Apr 26, 2015 at 5:08 PM, Spencer Krum  wrote:
>> Hi All,
>>
>> The primary maintainer of puppetboard is stepping aside:
>> https://github.com/puppet-community/puppetboard/issues/132. We use
>> puppetboard to display facts from machines and reports of puppet runs. We
>> can expect to continue to have this need into puppet 4 and puppet apply. I
>> like the idea of infra trying to help this project (we've already landed a
>> couple features) but I know we have to be strategic in where we put our
>> efforts. There is nothing wrong with our current installation (in fact it
>> could use an upgrade, it is almost a year out of date).
>>
>> There are at least two open source options if we wanted to look at
>> switching: Puppet-explorer: https://github.com/spotify/puppetexplorer and
>> Panopuppet: https://github.com/propyless/panopuppet
> 
> As a data point, prior to puppetboard, we used Puppet Dashboard, a
> fork of which we considered:
> https://github.com/sodabrew/puppet-dashboard
> 
> At the recent PuppetCampSF, author sodabrew did a talk on his plans
> for version 2, following a have-kids hiatus on the project. He's not
> planning on making distro-based packages (his expertise and time is
> better spent on project dev), but it may be worth considering again
> anyway.
> 
> Refresher, this is the bug report from the last time we did this,
> includes what we evaluated then:
> https://bugs.launchpad.net/openstack-ci/+bug/1218631
> 
> It would be awesome if we didn't have to do this every year :\
> 
I'll also note that both puppetexplorer and panopuppet essentially have
one active developer apiece right now.

Not that that helps sway one way or the other.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerrit downtime on Friday 2015-04-17 at 22:00 UTC

[Anita Kuno]

On 04/14/2015 06:06 PM, Boris Pavlovic wrote:
> Anita,
> 
> Thank you.
> I added patch to that list.
> 
> Best regards,
> Boris Pavlovic
Thank you, Boris.

Just be responsive to reviews on the patch and it would help if someone
from the team was available during that time to answer any last minute
questions that may arise.

Thanks,
Anita.
> 
> On Wed, Apr 15, 2015 at 1:02 AM, Anita Kuno  wrote:
> 
>> On 04/14/2015 05:59 PM, Boris Pavlovic wrote:
>>> James,
>>>
>>> What about  stackforge/rally -> openstack/rally ?
>>>
>>> Best regards,
>>> Boris Pavlovic
>> Was the patch for the rename listed here?
>>
>> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames
>>
>> This is where we collect our rename patches to schedule them.
>>
>> If you have the patch ready and list it in the above slot in the
>> wikipage we can do the rename with the others in the same maintenance
>> window.
>>
>> Thanks,
>> Anita.
>>>
>>> On Wed, Apr 15, 2015 at 12:57 AM, James E. Blair 
>>> wrote:
>>>
>>>> On Friday, April 17 at 22:00 UTC Gerrit will be unavailable for about 2
>>>> hours while we rename some projects and perform some database
>>>> maintenance.
>>>>
>>>> Existing reviews, project watches, etc, should all be carried
>>>> over. Currently, we plan on renaming the following projects:
>>>>
>>>>   stackforge/murano  -> openstack/murano
>>>>   stackforge/murano-agent-> openstack/murano-agent
>>>>   stackforge/murano-apps -> openstack/murano-apps
>>>>   stackforge/murano-dashboard-> openstack/murano-dashboard
>>>>   stackforge/murano-deployment   -> openstack/murano-deployment
>>>>   stackforge/murano-specs-> openstack/murano-specs
>>>>   stackforge/python-muranoclient -> openstack/python-muranoclient
>>>>   stackforge/murano-docs -> stackforge-attic/murano-docs
>>>>
>>>>   stackforge/congress  -> openstack/congress
>>>>   stackforge/congress-specs-> openstack/congress-specs
>>>>   stackforge/python-congressclient -> openstack/python-congressclient
>>>>
>>>>   stackforge/tuskar-ui-extras -> stackforge-attic/tuskar-ui-extras
>>>>
>>>> We also plan to transform some database fields in order to support
>>>> Unicode comments.
>>>>
>>>> If you have any questions about the maintenance, please reply here or
>>>> contact us in #openstack-infra on Freenode.
>>>>
>>>> -Jim
>>>>
>>>> ___
>>>> OpenStack-Infra mailing list
>>>> OpenStack-Infra@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Gerrit downtime on Friday 2015-04-17 at 22:00 UTC

[Anita Kuno]

On 04/14/2015 05:59 PM, Boris Pavlovic wrote:
> James,
> 
> What about  stackforge/rally -> openstack/rally ?
> 
> Best regards,
> Boris Pavlovic
Was the patch for the rename listed here?
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames

This is where we collect our rename patches to schedule them.

If you have the patch ready and list it in the above slot in the
wikipage we can do the rename with the others in the same maintenance
window.

Thanks,
Anita.
> 
> On Wed, Apr 15, 2015 at 12:57 AM, James E. Blair 
> wrote:
> 
>> On Friday, April 17 at 22:00 UTC Gerrit will be unavailable for about 2
>> hours while we rename some projects and perform some database
>> maintenance.
>>
>> Existing reviews, project watches, etc, should all be carried
>> over. Currently, we plan on renaming the following projects:
>>
>>   stackforge/murano  -> openstack/murano
>>   stackforge/murano-agent-> openstack/murano-agent
>>   stackforge/murano-apps -> openstack/murano-apps
>>   stackforge/murano-dashboard-> openstack/murano-dashboard
>>   stackforge/murano-deployment   -> openstack/murano-deployment
>>   stackforge/murano-specs-> openstack/murano-specs
>>   stackforge/python-muranoclient -> openstack/python-muranoclient
>>   stackforge/murano-docs -> stackforge-attic/murano-docs
>>
>>   stackforge/congress  -> openstack/congress
>>   stackforge/congress-specs-> openstack/congress-specs
>>   stackforge/python-congressclient -> openstack/python-congressclient
>>
>>   stackforge/tuskar-ui-extras -> stackforge-attic/tuskar-ui-extras
>>
>> We also plan to transform some database fields in order to support
>> Unicode comments.
>>
>> If you have any questions about the maintenance, please reply here or
>> contact us in #openstack-infra on Freenode.
>>
>> -Jim
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Discussion about scalable election tools

[Anita Kuno]

Problem Statement: OpenStack is growing, the election tools we use for
gathering nominations and communicating status of nominations, the
current workflow can be found on this wikipage:
https://wiki.openstack.org/wiki/Election_Officiating_Guidelines is
unable to be accessed by election officials and the electorate in a
clear way. The process we use for actually conducting the polls is fine.
We need to discuss and agree on a new workflow for posting
self-nominations and platforms for elections.

Does anyone have  input on tools that we might use to meet these
requirements for self nomination and platform management in elections?
Requirements:
* archivable
* public
* unable to be edited once posted
* clear differentiation between governed and ungoverned elections
* candidates can self-nominate
* low barrier to entry for tools, candidates shouldn't be restricted due
to lack of knowledge of tools

Reference:
* Current voting workflow:
https://wiki.openstack.org/wiki/Election_Officiating_Guidelines
* Condorcet: http://civs.cs.cornell.edu/

Thank you in advance for sharing your thoughts,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Update "Intel PCI CI" account information

[Anita Kuno]

On 03/25/2015 01:46 AM, Jiang, YuX Y wrote:
> Hi infra,
>  I want to update the email address of CI account - "Intel PCI CI".
>  Please help me to disable the old "Intel PCI CI" account. Thanks a 
> lot!
> 
> The old information of that account are below:
> Username: intelotccloud
> Full Name: Intel PCI CI
> Email address: otc_cl...@163.com
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
At your request, this account is now disabled.

Thank you for helping us to clean up and disable inactive accounts.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Biting the bullet on issue tracking

[Anita Kuno]

On 03/23/2015 07:28 PM, Michael Krotscheck wrote:
> Hey everyone!
> 
> It's quite rough to realize that the thing you've been advocating, working
> on, and desperately trying to recruit contributors for is DoA, and that's
> what I've been struggling with for the past few weeks. Even so, I was part
> and parcel to coming up with Monty's recommendation, so this wasn't a
> surprise.
> 
> Don't get me wrong: I love the project. I love the team, I love our
> technological vision, I love all these things. There are features that I
> feel are unique - Federation, process-agnosticism, clean api/ui separation,
> etc. - and given the opportunity (and proper resources) I would love to
> continue working on it. However for all the excitement that I've received
> over the past year, very little has solidified into any kind of concrete
> contribution. It was time to call the bluff.
> 
> And yet... StoryBoard has been a fantastic test bed for JavaScript as a
> first class citizen in OpenStack, and I'm going to continue moving that
> forward. There are some missing parts of our infrastructure, some of our
> existing tools need to be refined and documented, and there are some sticky
> policy items that need to be proposed to the TC. I see no reason not to
> continue supporting StoryBoard as that test bed, especially since the
> infrastructure team is still using it. Once a reasonable sunset has been
> reached (assuming new contributors don't magically materialize), my plan is
> to dive into the other UI components in OpenStack.
> 
> A very special thank you Yolanda Robla-Mota, Mike Heald, Riccardo Cruz,
> Nikita Konovalov, Aleksey Ripinien, Tom Pollard, and all the others who
> have contributed over the past year. Y'all are awesome.
> 
> Michael
Nicely said, Michael. I expected this decision was a collaborative
effort. It is nice to have your confirmation.

You and the rest of the team certainly have worked hard and have
accomplished a lot with what you had available. Kudos to all of you for
your hard work and dedication to your task.

Thanks for letting us know the status of the project,
Anita.
> 
> On Mon, Mar 23, 2015 at 4:03 PM Monty Taylor  wrote:
> 
>> Hi everybody,
>>
>> First, some background:
>>
>> A year and a half ago, Infra started down the road of of writing a
>> replacement for the pieces of Launchpad that OpenStack continues to use.
>> There were several reasons, but notable amongst them are:
>>
>> - Desire to use the forthcoming openstackid OpenID/Oauth as an SSO
>> - Delay in long-standing bugs that affect OpenStack getting fixed
>>
>> The existing open source offerings that we investigated did not have
>> adequate feature parity in the key data model areas that made Launchpad
>> particularly compelling as a choice for us, and adding what we needed to
>> the existing offerings would amount to substantial rewrites ... so we
>> decided that we had no real choice but to write our own.
>>
>> Where we're at
>>
>> We've gotten far enough to get Infra moved on to storyboard, but the
>> project has never really gotten resourced to the level it needs to be to
>> truly responsive to the needs of our community. We're making good
>> progress towards meeting the initial set of goals we set, but in the
>> mean time several new requests have come in - such as from the UX team
>> and the Product Management Working Group - that we cannot meet today and
>> which at our current rate I do not believe we would be able to meet in a
>> reasonable timeframe.
>>
>> At the same time, the state of the art around us has improved since we
>> started. A year and a half ago, I was able to very honestly say that we
>> needed to work on this effort because we simply had no other choice.
>> That is no longer true. Existing Open Source offerings not only can
>> represent a large portion of our data needs, but additionally can
>> support the additional features that have been requested by our
>> community today out of the box.
>>
>> The combination of the two of those makes the likelihood of us being
>> able to convince people to pony up more resources seem more and more far
>> fetched. I could be wrong, of course - it's possible that in response to
>> this someone will start jumping up and down and commit engineers to the
>> effort ... but I'm not holding my breath.
>>
>> Biting the bullet
>>
>> I think we should get out of the business of writing our own bug tracker.
>>
>> It's not an easy thing to say, and I don't say it lightly. There are
>> things that storyboard models well that continue to be things that
>> simply are not modeled elsewhere. However, I think it's important to
>> know when good enough will do, and I think it's important to be able to
>> step up and say that we tried valiantly, and everyone involved did a
>> great job, and yet the world has moved on and writing a bug tracker is
>> not, at the end of the day, what we're all here to do.
>>
>> We're looking at what our options are, and Thierry is examining them to
>> see ho

Re: [OpenStack-Infra] PTL election season?

[Anita Kuno]

On 03/12/2015 07:29 PM, Tony Breeds wrote:
> On Thu, Mar 12, 2015 at 11:00:07PM +, Jeremy Stanley wrote:
> 
>> I'm not sure why this is an -infra ML topic, but from what I've
>> seen those have all been unofficial projects which are trying to
>> apply for official status with the TC under the new "big tent"
>> model and as such need to meet the requirement of having an
>> elected PTL.
> 
> Thanks.
> 
> Sorry if this wasn't an appropriate venue.
> 
> Yours Tony.
> 
> 
> 
> ___ OpenStack-Infra
> mailing list OpenStack-Infra@lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
> 
Tony pm'd me and I asked him to post in -infra, meaning the infra irc
channel and he interpreted this as the infra mailing list.

Also the flurry of elections is based on an interpretation of what is
required, not what is required.

The requirement is: The leadership is chosen by the contributors to
the project
http://git.openstack.org/cgit/openstack/governance/tree/reference/new-projects-requirements.rst#n30
which can take many forms. They are just all heading to the -dev list.

Thanks for asking Tony,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Microsoft Hyper-V CI is Offline Until Friday 8 pm EST

[Anita Kuno]

On 03/02/2015 01:07 PM, Hashir Abdi wrote:
> We are replacing our older Network Switching Infrastructure in order to 
> stabilize issues recently seen on our CI.
> 
> This Effort is scheduled to complete by this Friday, the 6th of February and 
> we intend to be back online by  8 pm EST the same day.
> 
> Regards
> 
> Hashir Abdi
> Principal Software Engineering Manager
> Microsoft
> 
> 
> 
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
As I told alexpilotti online the expected place to inform others of
changes to your system status is on your system status wikipage, not the
mailing list: https://wiki.openstack.org/wiki/ThirdPartySystems/Hyper-V_CI

I still don't see the wikipage updated.

2015-03-02T17:47:21   anteaya: theoretically somebody
should have sent an email to the ML, stating that we were under
maintenance until Friday
2015-03-02T17:47:55   alexpilotti: or updated your third party
systems individual page"
ttps://wiki.openstack.org/wiki/ThirdPartySystems/Hyper-V_CI
2015-03-02T17:48:11   which is what I would have asked you do
to if you tried posting to the mailing list

http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2015-03-02.log

Status updates for systems belong on your system wikipage _not_ any of
the mailing lists.

Thank you for paying attention to this in future.

Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [openstack-dev] [infra] --verified option in gerrit

[Anita Kuno]

On 03/02/2015 11:41 AM, Clark Boylan wrote:
> On Sun, Mar 1, 2015, at 10:28 AM, Fawad Khaliq wrote:
>> Infra folks,
>>
>> Any input/help here?
>>
>> Thanks,
>> Fawad Khaliq
>>
>>
>> On Tue, Feb 17, 2015 at 3:46 PM, Fawad Khaliq  wrote:
>>
>>> Folks,
>>>
>>> I am seeing a behavior where the following command fails [1] to update
>>> "verified" on OpenStack Gerrit:
>>>
>>> ssh -p 29418 thirdpart...@review.openstack.org gerrit review --verified 1
>>> 2,1
>>>
>>> Have we configured Gerrit verified label [1] on OpenStack Gerrit servers?.
>>> This used to work but recently, something has changed. If not, can we
>>> please enable it. This is needed by PLUMgrid CI.
>>>
>>> Thanks for the help!
>>>
>>> [1] https://review.openstack.org/#/c/156529/
>>> [2]
>>> https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_Verified
>>>
> In your example command the change listed is change 2 which does not
> appear to be publicly visible, your account would not be able to vote
> verified on that change. The other change listed, 156529, is a neutron
> change, the accounts that can vote in the verified column for neutron
> are listed in the neutron-ci group [0]. This group is owned and managed
> by the neutron-release [1] group.
> 
> If this was working for you at one time but isn't anymore it is possible
> that you were a member of the neutron-ci group then you were removed for
> some reason. I would check with the neutron-release group.
> 
> [0] https://review.openstack.org/#/admin/groups/510,members
> [1] https://review.openstack.org/#/admin/groups/150,members
> 
> Hope this helps,
> Clark
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Yes Plumgrid CI was moved to non-voting on Neutron patches a couple of
weeks ago.

Edgar and Kyle will know the details.

I had asked that an email be posted to the third party announce list
when the status changed, but I guess that didnt' happen and I didn't
follow up on that.

So yes, communicating with Neutron is your next step.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [infra] Infra cloud: infra running a cloud for nodepool

[Anita Kuno]

On 02/24/2015 05:34 PM, Chmouel Boudjnah wrote:
> cor...@inaugust.com (James E. Blair) writes:
> 
>> A group of folks from HP is interested in starting an effort to run a
>> cloud as part of the Infrastructure program with the purpose of
>> providing resources to nodepool for OpenStack testing.  HP is supplying
>> two racks of machines, and we will operate each as an independent cloud.
>> I think this is a really good idea, and will do a lot for OpenStack.
>>
>> Here's what we would get out of it:
> 
> Pretty cool! thanks to HP for providing this. If that's possible (with
> HP and if the infra wants to allow that) it would be nice to allow a dev
> to login into the failing vm for investigation.
> 
> Cheers,
> Chmouel
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Chmouel:

We can do that now, if the request meets certain criteria:

We need to know or be shown you have exhausted all ability to reproduce
the error locally. We had a request to hold a vm for someone last week,
it turns out they didn't know how to read the logs.

We need the id number of the node, line 3 of the console output of the
job in question. We actually did this today for Kyle Mestery:
2015-02-24T20:52:52   fungi clarkb: Any chance you can save the
VM from this job (https://review.openstack.org/#/c/158076/) for me? I'm
trying to debug a gate issue with ODL in the gate and live debug would
be immensly helpful.
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-02-24.log

We need this to be an extreme circumstance only, not "I'm too lazy to
look at the logs that are currently provided". Not saying you do that
Chmouel but for other readers.

If folks need help finding errors in the logs, do ask in #openstack-dev
or #openstack-infra, it is easier for us to help you learn to read what
is already publicly available than to hold a node for you.

Thanks,
Anita.


___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Cross-Repo Dependencies in Zuul

[Anita Kuno]

On 02/12/2015 03:42 AM, Antoine Musso wrote:
> Le 10/02/2015 23:26, James E. Blair a écrit :
>> We have added support for cross-repo dependencies (CRD) in Zuul.
> 
> 
> Hello James and Infra,
> 
> Congratulations for this nice feature, that is a great addition to
> Gerrit workflow.
> 
> You might want to copy paste James nice email to Zuul documentation so
> it does not get lost in the attic of this mailing list.   Will most
> probably help third parties figuring out how it works.
> 
> Thanks again!
> 
Anyone can beat us to it, copy/paste away. Then we can refine via review.

Thanks,
Anita.

___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra