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] 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] 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] 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] 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] 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] 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] 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

[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] 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

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] 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] Infra mid-cycle meetup

[Anita Kuno]

I'd like to attend.

Since I currently seem to be spending my time spreading the gospel of
infra, I would like to ensure that I am conveying accurate information
as well as guidance and direction for those folks/projects who what more
infra in their work but don't yet know how.

That is my current goal, which may change subject to circumstances and
how I happen to feel at the time.

Thanks Jim,
Anita.

On 12/02/2013 11:21 AM, James E. Blair wrote:
> Hi,
> 
> The subject of a mid-cycle meetup for the infrastructure team has come
> up a few times recently, so I wanted to get an idea of who might be
> interested and what we want to get out of it.
> 
> If you are interested in spending a few days focusing on OpenStack
> project infrastructure, would you please reply (privately is fine) with
> your area of interest.  Some ideas:
> 
> * You want to sit in a room and hack with other infra folks on large
>   projects we have undertaken this cycle.
> 
> * You want to become a core infra team member and would like to get up
>   to speed.
> 
> * You are running an internal CI system and want to become familiar with
>   our tools.
> 
> * You are running an internal CI system and want to figure out how to
>   contribute upstream.
> 
> Feel free to add any others.
> 
> After collecting this feedback, we'll be better able to determine if
> it's worth getting together and how to structure a meeting to be most
> effective.
> 
> Thanks,
> 
> 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

Re: [OpenStack-Infra] Radware's service account request for third party testing

[Anita Kuno]

On 01/16/2014 03:09 PM, Jeremy Stanley wrote:
> On 2014-01-16 19:42:44 + (+), Izik Penso wrote:
>> True, I'll let you know when it all fixed.
> 
> I also just noticed that the contact address you have specified for
> that service account is undeliverable from the Internet. My attempt
> to contact it was bounced with the error:
> 
> Radware 3rd Party Testing (openstack3rdpartytest...@radware.com)
> Your message can't be delivered because delivery to this address
> is restricted.
> 
> So that makes it a somewhat ineffective contact address.
> 
I just tested this email (openstack3rdpartytest...@radware.com) from my
laptop, thunderbird client, gmail backend and it worked for me.

Thanks,
Anita.

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

[OpenStack-Infra] Please turn off verification voting for Big Switch CI

[Anita Kuno]

Please turn off verification voting for Big Switch CI.

It is voting -1 on patches which is raising questions from developers.
[0][1]

We are moving in the direction of requiring 3rd party testing systems to
only vote +1 when tests pass and removing -1 voting entirely.

You do yourself a big favour if you make this change voluntarily.

We need a response from you that -1 voting is turned off for your system
within 4 hours from the time this email is sent. If we don't get your
response that you have turned off -1 voting for your system, we reserve
the right to turn off verification voting for your system within gerrit.

Please respond promptly.

Thank you,
Anita.

[0] https://review.openstack.org/#/c/63558/
[1] https://review.openstack.org/#/c/66453/

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

Re: [OpenStack-Infra] Please turn off verification voting for Big Switch CI

[Anita Kuno]

Thank you for your prompt response.

Please confirm once -1 voting has been turned off for your system.

Thank you,
Anita.

On 01/17/2014 04:11 PM, Sumit Naiksatam wrote:
> Thanks for the heads up. We will turn off the negative vote. Just a
> clarification, the current negative votes are not incorrect, we are
> hitting  existing race conditions for which bugs exist. This should have
> been clear from the tempest test run log, however this file was not getting
> copied over correctly and hence was not visible in the logs that we have
> made publicly available.
> On Jan 17, 2014 1:03 PM, "Anita Kuno"  wrote:
> 
>> Please turn off verification voting for Big Switch CI.
>>
>> It is voting -1 on patches which is raising questions from developers.
>> [0][1]
>>
>> We are moving in the direction of requiring 3rd party testing systems to
>> only vote +1 when tests pass and removing -1 voting entirely.
>>
>> You do yourself a big favour if you make this change voluntarily.
>>
>> We need a response from you that -1 voting is turned off for your system
>> within 4 hours from the time this email is sent. If we don't get your
>> response that you have turned off -1 voting for your system, we reserve
>> the right to turn off verification voting for your system within gerrit.
>>
>> Please respond promptly.
>>
>> Thank you,
>> Anita.
>>
>> [0] https://review.openstack.org/#/c/63558/
>> [1] https://review.openstack.org/#/c/66453/
>>
> 


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

Re: [OpenStack-Infra] Please turn off verification voting for Big Switch CI

[Anita Kuno]

Wonderful. Thank you for the confirmation and the prompt reply.

I am also talking with Sumit on irc which is helpful as well.

Thank you,
Anita.

On 01/17/2014 05:02 PM, Kevin Benton wrote:
> -1 voting has been disabled.
> 
> Thanks,
> Kevin Benton
> 
> 
> On Fri, Jan 17, 2014 at 1:15 PM, Anita Kuno  wrote:
> 
>> Thank you for your prompt response.
>>
>> Please confirm once -1 voting has been turned off for your system.
>>
>> Thank you,
>> Anita.
>>
>> On 01/17/2014 04:11 PM, Sumit Naiksatam wrote:
>>> Thanks for the heads up. We will turn off the negative vote. Just a
>>> clarification, the current negative votes are not incorrect, we are
>>> hitting  existing race conditions for which bugs exist. This should have
>>> been clear from the tempest test run log, however this file was not
>> getting
>>> copied over correctly and hence was not visible in the logs that we have
>>> made publicly available.
>>> On Jan 17, 2014 1:03 PM, "Anita Kuno"  wrote:
>>>
>>>> Please turn off verification voting for Big Switch CI.
>>>>
>>>> It is voting -1 on patches which is raising questions from developers.
>>>> [0][1]
>>>>
>>>> We are moving in the direction of requiring 3rd party testing systems to
>>>> only vote +1 when tests pass and removing -1 voting entirely.
>>>>
>>>> You do yourself a big favour if you make this change voluntarily.
>>>>
>>>> We need a response from you that -1 voting is turned off for your system
>>>> within 4 hours from the time this email is sent. If we don't get your
>>>> response that you have turned off -1 voting for your system, we reserve
>>>> the right to turn off verification voting for your system within gerrit.
>>>>
>>>> Please respond promptly.
>>>>
>>>> Thank you,
>>>> Anita.
>>>>
>>>> [0] https://review.openstack.org/#/c/63558/
>>>> [1] https://review.openstack.org/#/c/66453/
>>>>
>>>
>>
>>
> 


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

[OpenStack-Infra] Please adjust your system - one comment per event

[Anita Kuno]

Your 3rd party testing system is currently commenting twice per event:

https://review.openstack.org/#/c/61183/

Please adjust your system, one comment per event is the expectation.

Please confirm once you have received this email and confirm again once
the adjustment has been made.

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] [bsn-openstack-ci] Please adjust your system - one comment per event

[Anita Kuno]

Thank you, Kevin.

Given the current state of 3rd party testing, I think it is important we
track data somewhere and the openstack-infra mailing list seems to be
the default.

Thanks,
Anita.

On 01/22/2014 08:33 PM, Kevin Benton wrote:
> Hi Anita,
> 
> If Sumit didn't already contact you, the double-commenting should be fixed.
> 
> Thanks,
> Kevin Benton
> 
> 
> On Wed, Jan 22, 2014 at 5:23 AM, Anita Kuno  wrote:
> 
>> Your 3rd party testing system is currently commenting twice per event:
>>
>> https://review.openstack.org/#/c/61183/
>>
>> Please adjust your system, one comment per event is the expectation.
>>
>> Please confirm once you have received this email and confirm again once
>> the adjustment has been made.
>>
>> 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] [Neutron][third-party-testing] Third Party Test setup and details

[Anita Kuno]

On 02/25/2014 05:08 PM, Sukhdev Kapur wrote:
> Fellow developers,
> 
> I just put together a wiki describing the Arista Third Party Setup.
> In the attached document we provide a link to the modified Gerrit Plugin to
> handle the regex matching for the "Comment Added" event so that
> "recheck/reverify no bug/" can be handled.
> 
> https://wiki.openstack.org/wiki/Arista-third-party-testing
> 
> Have a look. Your feedback/comments will be appreciated.
> 
> regards..
> -Sukhdev
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Sukhdev:

Thanks so much for putting this together.

The text in the wiki page is basically a link to a google document. Is
it possible to put the text of the google document in the wiki page? I
think it would be a lot more useful to users to do so.

Thanks,
Anita.

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

Re: [OpenStack-Infra] [Neutron][third-party-testing] Third Party Test setup and details

[Anita Kuno]

On 02/25/2014 08:21 PM, Sukhdev Kapur wrote:
> Hi Anita,
> 
> I started writing in the wiki and realized it was quite painful to draw and
> edit in wiki. So, I switched to the document :-)
> 
> If others also feel that it is better to move the text to wiki, I can spend
> some time moving it to the wiki. Now that I have most of the material, I
> guess it may not be that bad.
> 
> Do you really feel it will be better to do that though?
Yes I do. For a project as large as OpenStack we need to do the best we
can to use as much standardized tooling as possible.

Wikis and docs are expected ways to consume information, using google
docs is not.

Do your best and if you have issues transferring the material ping me on
irc and I will do the best I can to help you so that you are satisfied
with the result.

Thanks Sukhdev,
Anita.
> 
> 
> regards..
> -Sukhdev
> 
> 
> 
> 
> On Tue, Feb 25, 2014 at 2:43 PM, Anita Kuno  wrote:
> 
>> On 02/25/2014 05:08 PM, Sukhdev Kapur wrote:
>>> Fellow developers,
>>>
>>> I just put together a wiki describing the Arista Third Party Setup.
>>> In the attached document we provide a link to the modified Gerrit Plugin
>> to
>>> handle the regex matching for the "Comment Added" event so that
>>> "recheck/reverify no bug/" can be handled.
>>>
>>> https://wiki.openstack.org/wiki/Arista-third-party-testing
>>>
>>> Have a look. Your feedback/comments will be appreciated.
>>>
>>> regards..
>>> -Sukhdev
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Hi Sukhdev:
>>
>> Thanks so much for putting this together.
>>
>> The text in the wiki page is basically a link to a google document. Is
>> it possible to put the text of the google document in the wiki page? I
>> think it would be a lot more useful to users to do so.
>>
>> Thanks,
>> 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] Incorrect 3rd party vote, please correct

[Anita Kuno]

On 03/01/2014 05:59 PM, Michael Still wrote:
> Can you just do a recheck?
> 
> Michael
There is a problem with the ci, which Neutron Ryu has acknowledged but
has not fixed. [0]

Unfortunately they are still voting. Voting should be turned off while
ci systems are fixing issues and then they can turn them back on once
issues are addressed.

If they decide to leave broken ci systems voting, infra can turn the
voting off and then the 3rd party testing ci system needs to apply at a
project team meeting to have voting re-instated.

Right now they are still voting and still broken. [1]

I am in #openstack-infra now discussing having their voting turned off.

Thanks,
Anita.

[0]
http://lists.openstack.org/pipermail/openstack-infra/2014-March/000928.html

[1] http://180.37.183.32/jenkins/job/ryuplugin-tempest/9/console

> 
> On Sat, Mar 1, 2014 at 10:44 AM, Mohammad Banikazemi  wrote:
>> Please remove your -1 from the review posted on
>> https://review.openstack.org/#/c/66453/ for the latest patchset.
>>
>> From the cosole log posted in your review I see  the following:
>> [Call Trace]
>> ./stack.sh:1102:start_glance
>> /var/lib/jenkins/jobs/ofagent-tempest/workspace/devstack/lib/glance:210:die
>> [ERROR]
>> /var/lib/jenkins/jobs/ofagent-tempest/workspace/devstack/lib/glance:210
>> g-api did not start
>> which does not seem related to Neutron and our patch.
>>
>> Please respond as soon as you can so the review process can resume on this
>> patch.
>>
>> Thank you,
>>
>> Mohammad
>>
>>
>> ___
>> 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] duplicated account in gerrit!

[Anita Kuno]

On 03/05/2014 06:16 AM, Lahoucine Benlahmr wrote:
> Hi everyone,
> 
> I'have deleted my old account "lahoucine " but
> it's still visible in gerrit.
> 
> My current account "Lahoucine BENLAHMR " is shown
> duplicated and  is unselectable when trying to add it as reviewer to a
> change.
> 
> Any one knows how I can definitly remove my old account "lahoucine <
> ben.lahouc...@gmail.com>",
> And  how to makes my current account  "Lahoucine BENLAHMR <
> lahouc...@benlahmr.com>" works (resolve deplucation) ?
> 
> Thank you for your answers.
> 
> 
> Lahoucine BENLAHMR
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Lahoucine:

Yes deleting anything from gerrit was never the intention of gerrit.

My suggestion is to come into #openstack-infra irc channel on freenode
and ask for fungi to give you a hand. Today is not a great day for this
request as it is feature freeze day, but you are welcome anytime.

When you come, please post the gerrit id that you have with your current
gerrit account which you can find when you sign into gerrit and select
settings.

Fungi will have to look at the database manually and clean it up, there
is no gui for this sort if situation.

Fungi usually handles gerrit db cleanup though others can as well.

Thank you,
Anita.

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

[OpenStack-Infra] Freescale CI is allowed one comment per patchset - please acknowledge

[Anita Kuno]

Hello Trinath:

All 3rd party ci systems are allowed one comment per patchset.

Right now Freescale CI is commenting more than once per patchset:
https://review.openstack.org/#/c/73575/

I count 8 Freescale CI comments on patchset 21 for patch 73575. This
creates noise for developers.

Please post one comment per patchset (or recheck) which is posted after
your testing is completed with your test results, link to the test logs
and contact information for your system.

If you cannot make this change immediately, please shut down commenting
on your system until you can make the change.

Remember you can vote on the sandbox repo:
http://git.openstack.org/cgit/openstack-dev/sandbox/ as much as you want
to ensure your system is configured in the way you are requested. You
can post links to your system comments in the sandbox repo in the irc
channel (#openstack-neutron on freenode) to ensure your system is
compliant with this request.

Please contact me on irc if you are unclear in what you are being asked
to do. 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] Freescale CI is allowed one comment per patchset - please acknowledge

[Anita Kuno]

On 03/05/2014 09:10 PM, trinath.soman...@freescale.com wrote:
> Hi Anita-
> 
> Its that one patch which got many comments. Rest all patches got a single 
> comment.
> 
> Let me check on what might have happened.
> 
> Will review the system on this ..
> 
> Thank you for the email.
> 
> --
> Trinath
Thank you, Trianth.

Please review other recent patches your system has reviewed as well.

Please post your findings from your investigation into this patch.

Thank you,
Anita.
> 
> ____
> From: Anita Kuno 
> Sent: Thursday, March 06, 2014 3:59 AM
> To: Somanchi Trinath-B39208; openstack-infra@lists.openstack.org; Mark McClain
> Subject: Freescale CI is allowed one comment per patchset - please acknowledge
> 
> Hello Trinath:
> 
> All 3rd party ci systems are allowed one comment per patchset.
> 
> Right now Freescale CI is commenting more than once per patchset:
> https://review.openstack.org/#/c/73575/
> 
> I count 8 Freescale CI comments on patchset 21 for patch 73575. This
> creates noise for developers.
> 
> Please post one comment per patchset (or recheck) which is posted after
> your testing is completed with your test results, link to the test logs
> and contact information for your system.
> 
> If you cannot make this change immediately, please shut down commenting
> on your system until you can make the change.
> 
> Remember you can vote on the sandbox repo:
> http://git.openstack.org/cgit/openstack-dev/sandbox/ as much as you want
> to ensure your system is configured in the way you are requested. You
> can post links to your system comments in the sandbox repo in the irc
> channel (#openstack-neutron on freenode) to ensure your system is
> compliant with this request.
> 
> Please contact me on irc if you are unclear in what you are being asked
> to do. 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] Freescale CI is allowed one comment per patchset - please acknowledge

[Anita Kuno]

On 03/06/2014 01:23 AM, Michael Still wrote:
> Anita,
> 
> here's a report of recent (last seven days) Freescale CI votes. It
> doesn't include the review revision that caused your initial concern,
> because that revision lasted less than the required three hours for my
> reporting. I hope it helps regardless.
> 
> http://www.rcbops.com/gerrit/reports/Freescale_CI-cireport.html
> 
> Cheers,
> Michael
You're just awesome.

Thanks will go over it during morning tea.
> 
> On Thu, Mar 6, 2014 at 1:21 PM, Anita Kuno  wrote:
>> On 03/05/2014 09:10 PM, trinath.soman...@freescale.com wrote:
>>> Hi Anita-
>>>
>>> Its that one patch which got many comments. Rest all patches got a single 
>>> comment.
>>>
>>> Let me check on what might have happened.
>>>
>>> Will review the system on this ..
>>>
>>> Thank you for the email.
>>>
>>> --
>>> Trinath
>> Thank you, Trianth.
>>
>> Please review other recent patches your system has reviewed as well.
>>
>> Please post your findings from your investigation into this patch.
>>
>> Thank you,
>> Anita.
>>>
>>> 
>>> From: Anita Kuno 
>>> Sent: Thursday, March 06, 2014 3:59 AM
>>> To: Somanchi Trinath-B39208; openstack-infra@lists.openstack.org; Mark 
>>> McClain
>>> Subject: Freescale CI is allowed one comment per patchset - please 
>>> acknowledge
>>>
>>> Hello Trinath:
>>>
>>> All 3rd party ci systems are allowed one comment per patchset.
>>>
>>> Right now Freescale CI is commenting more than once per patchset:
>>> https://review.openstack.org/#/c/73575/
>>>
>>> I count 8 Freescale CI comments on patchset 21 for patch 73575. This
>>> creates noise for developers.
>>>
>>> Please post one comment per patchset (or recheck) which is posted after
>>> your testing is completed with your test results, link to the test logs
>>> and contact information for your system.
>>>
>>> If you cannot make this change immediately, please shut down commenting
>>> on your system until you can make the change.
>>>
>>> Remember you can vote on the sandbox repo:
>>> http://git.openstack.org/cgit/openstack-dev/sandbox/ as much as you want
>>> to ensure your system is configured in the way you are requested. You
>>> can post links to your system comments in the sandbox repo in the irc
>>> channel (#openstack-neutron on freenode) to ensure your system is
>>> compliant with this request.
>>>
>>> Please contact me on irc if you are unclear in what you are being asked
>>> to do. 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] Freescale CI is allowed one comment per patchset - please acknowledge

[Anita Kuno]

On 03/06/2014 01:29 AM, trinath.soman...@freescale.com wrote:
> Hi Michael-
> 
> Thank you for the comment.
> 
> Do we need to improve our CI, further ..? Can post your suggestions/comments 
> on the same.
> 
> 
> 
> --
> Trinath Somanchi - B39208
> trinath.soman...@freescale.com | extn: 4048
> 
> 
> -Original Message-
> From: mikalst...@gmail.com [mailto:mikalst...@gmail.com] On Behalf Of Michael 
> Still
> Sent: Thursday, March 06, 2014 11:53 AM
> To: Anita Kuno
> Cc: Somanchi Trinath-B39208; openstack-infra@lists.openstack.org; Mark McClain
> Subject: Re: [OpenStack-Infra] Freescale CI is allowed one comment per 
> patchset - please acknowledge
> 
> Anita,
> 
> here's a report of recent (last seven days) Freescale CI votes. It doesn't 
> include the review revision that caused your initial concern, because that 
> revision lasted less than the required three hours for my reporting. I hope 
> it helps regardless.
> 
> http://www.rcbops.com/gerrit/reports/Freescale_CI-cireport.html
> 
> Cheers,
> Michael
Okay, let's go through this report:
Starting with this series of patches:

68142: patchset 17 - 1 comment, 1.5 hours ago
   patchset 16 - 2 comments, 2.5 hours ago
   patchset 15 - 2 comments, March 5

70700: patchset 4 - 2 comments, March 5

74156: patchset 18 - 4 comments, March 5,
   patchset 17 - 8 comments, March 5

75253: patchset 11 - 2 comments, March 5,
   patchset 10 - 2 comments, March 5,
   patchset 9 - 2 comments, March 5

75861: patchset 17 - 2 comments, March 5

76670: patchset 6 - 2 comments, March 5
   patchset 5 - 2 comments, March 5

I think that is enough to demonstrate that this statement is not a true
reflection of the status of your system when I emailed you:
"Its that one patch which got many comments. Rest all patches got a
single comment."

Please provide factual information about the status of your system in
future.

Also as can be seen by the only single comment on a patchset of the
patchsets I examined (patchset 68142, 17), it is possible that you are
now commenting only once per patchset as of an hour or so ago.

Please continue to monitor the activity of your system and adjust it
accordingly.

Thank you, Trianth,
Anita.


> 
> On Thu, Mar 6, 2014 at 1:21 PM, Anita Kuno  wrote:
>> On 03/05/2014 09:10 PM, trinath.soman...@freescale.com wrote:
>>> Hi Anita-
>>>
>>> Its that one patch which got many comments. Rest all patches got a single 
>>> comment.
>>>
>>> Let me check on what might have happened.
>>>
>>> Will review the system on this ..
>>>
>>> Thank you for the email.
>>>
>>> --
>>> Trinath
>> Thank you, Trianth.
>>
>> Please review other recent patches your system has reviewed as well.
>>
>> Please post your findings from your investigation into this patch.
>>
>> Thank you,
>> Anita.
>>>
>>> 
>>> From: Anita Kuno 
>>> Sent: Thursday, March 06, 2014 3:59 AM
>>> To: Somanchi Trinath-B39208; openstack-infra@lists.openstack.org; 
>>> Mark McClain
>>> Subject: Freescale CI is allowed one comment per patchset - please 
>>> acknowledge
>>>
>>> Hello Trinath:
>>>
>>> All 3rd party ci systems are allowed one comment per patchset.
>>>
>>> Right now Freescale CI is commenting more than once per patchset:
>>> https://review.openstack.org/#/c/73575/
>>>
>>> I count 8 Freescale CI comments on patchset 21 for patch 73575. This 
>>> creates noise for developers.
>>>
>>> Please post one comment per patchset (or recheck) which is posted 
>>> after your testing is completed with your test results, link to the 
>>> test logs and contact information for your system.
>>>
>>> If you cannot make this change immediately, please shut down 
>>> commenting on your system until you can make the change.
>>>
>>> Remember you can vote on the sandbox repo:
>>> http://git.openstack.org/cgit/openstack-dev/sandbox/ as much as you 
>>> want to ensure your system is configured in the way you are 
>>> requested. You can post links to your system comments in the sandbox 
>>> repo in the irc channel (#openstack-neutron on freenode) to ensure 
>>> your system is compliant with this request.
>>>
>>> Please contact me on irc if you are unclear in what you are being 
>>> asked to do. 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
> 
> 
> 
> --
> Rackspace Australia
> 
> 


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

Re: [OpenStack-Infra] Radware's service account request for third party testing

[Anita Kuno]

On 03/25/2014 08:52 AM, Mark McClain wrote:
> 
> On Mar 23, 2014, at 9:15 AM, Izik Penso  wrote:
> 
>> Hi Jeremy,
>>
>> Could you please reenable Radware's 3rd party testing account.
>>
>> Thanks,
>> Izik Penso.
> 
> I haven’t seen any recent comments from the Radware test system.  If we’re 
> blocking commenting, might make sense to reenable commenting to see if 
> they’re compliant but not allow voting.
> 
> mark
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Radware's 3rd party testing account has always retained the ability to
post comments.

Thanks,
Anita.

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

[OpenStack-Infra] Please address your 3rd party ci system

[Anita Kuno]

https://review.openstack.org/#/c/87775/

Your system seems to be commenting in error. One comment per patchset
please.

If you can't fix this immediately, please take your system offline until
you can address this issue.

Please reply as soon as you receive this email.

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 address your 3rd party ci system

[Anita Kuno]

On 04/23/2014 01:25 PM, Rafael Folco wrote:
> I just disabled our CI until we resolve this issue.
> We just migrated our CI system to a new cloud environment and something is
> not working properly. I have seen SSL issues, so probably need to renew SSL
> for the new VMs.
> Sorry for the inconvenience.
> 
Thanks for the quick response, Rafael.

We appreciate your attention to this.

Anita.
> 
> On Wed, Apr 23, 2014 at 2:07 PM, Anita Kuno  wrote:
> 
>> https://review.openstack.org/#/c/87775/
>>
>> Your system seems to be commenting in error. One comment per patchset
>> please.
>>
>> If you can't fix this immediately, please take your system offline until
>> you can address this issue.
>>
>> Please reply as soon as you receive this email.
>>
>> 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] Urgent: Problem with Gerrit JS?

[Anita Kuno]

On 04/30/2014 11:55 AM, Kevin L. Mitchell wrote:
> I'm trying to review https://review.openstack.org/#/c/44715/8 and when I
> go to look at the nova/tests/db/test_db_api.py by clicking on that link
> under "File Path" in the review table, I get an "Unresponsive script"
> warning from my browser; clicking on the "Continue" option in the
> warning pop-up does not help.
I confirm.

> I've also tried the "Side-by-Side" and
> "Unified" links from that table, even the "All Side-by-Side" and "All
> Unified" links.


> The same problem also occurs if I try to get there by
> clicking the "next" link while looking at the commit message.
I confirm.

>  I have
> tried restarting my browser, but the same thing still happens.  I'm also
> having the issue trying to look at the same file in patch set 7, which I
> had previously reviewed.
> 
> This is happening with Firefox 28.0 running on a Fedora 19 x86_64
> system.
> 
> The script that's being referenced is:
> 
> 
> https://review.openstack.org/gerrit_ui/89B6B1C2255AB537598BF6FC8F36BB0D.cache.html:164
I confirm.

> 
> My "Change View" setting is "Server Default (Old Screen)".
> 
> Any ideas?  The change is a +14-12, and I can't seem to look at the file
> in *any* patch set on this review anymore.
> 
> Further investigation shows that the same problem occurs with the same
> file in https://review.openstack.org/#/c/44714 and
> https://review.openstack.org/#/c/44716/ so it seems to be a problem
> specific to the test_db_api.py file itself.
> 
Are you able to file a bug with this information? It will help us track
progress on this easier than an email thread. If you reply with a link I
will confirm the bug.

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] Urgent: Problem with Gerrit JS?

[Anita Kuno]

On 04/30/2014 12:34 PM, Kevin L. Mitchell wrote:
> On Wed, 2014-04-30 at 12:14 -0400, Anita Kuno wrote:
>> Are you able to file a bug with this information? It will help us track
>> progress on this easier than an email thread. If you reply with a link I
>> will confirm the bug.
> 
> Sure, I just wasn't sure where to file the bug :)  Best filed at
> https://launchpad.net/openstack-ci ?
> 
Well Khai thinks this might belong upstream. Why not file it at
openstack-ci and if this is upstream we can mark the bug invalid and
make a recommendation or file it ourselves.

Would that work for you, Kevin?

Thanks,
Anita.

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

Re: [OpenStack-Infra] Urgent: Problem with Gerrit JS?

[Anita Kuno]

On 04/30/2014 12:54 PM, Kevin L. Mitchell wrote:
> On Wed, 2014-04-30 at 12:47 -0400, Anita Kuno wrote:
>> On 04/30/2014 12:34 PM, Kevin L. Mitchell wrote:
>>> On Wed, 2014-04-30 at 12:14 -0400, Anita Kuno wrote:
>>>> Are you able to file a bug with this information? It will help us track
>>>> progress on this easier than an email thread. If you reply with a link I
>>>> will confirm the bug.
>>>
>>> Sure, I just wasn't sure where to file the bug :)  Best filed at
>>> https://launchpad.net/openstack-ci ?
>>>
>> Well Khai thinks this might belong upstream. Why not file it at
>> openstack-ci and if this is upstream we can mark the bug invalid and
>> make a recommendation or file it ourselves.
>>
>> Would that work for you, Kevin?
> 
> Just wanted to confirm I had selected the correct local tracker.
> Anyway, reported as:
> 
> https://bugs.launchpad.net/openstack-ci/+bug/1314713
> 
Thank you, I have moved to the bug report.

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

Re: [OpenStack-Infra] Review guidelines for new specs repos

[Anita Kuno]

On 05/20/2014 07:24 PM, James E. Blair wrote:
> Hi,
> 
> At the project meeting today, I cornered the PTLs and got consensus that
> we should be using PROGRAM-specs as the name for the specs repos.  Eg,
> "compute-specs" instead of "nova-specs".  This is to better support
> programs with multiple projects (such as client and server projects).
> Short names (object instead of object-storage) are fine.
> 
> If you review patches to create new specs repos, please keep that in
> mind.  Also, we'll be scheduling renames of some existing specs repos
> when convenient.
> 
> -Jim
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Will do.

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

Re: [OpenStack-Infra] IRC channels

[Anita Kuno]

On 05/22/2014 07:03 PM, Birdsall, Dave wrote:
> Hi,
> 
> I'm involved with a nascent open source effort that is using a clone of the 
> Open Stack infrastructure.
> 
> I've read and played with the Open Stack IRC enough that I think I understand 
> how end users will access IRC. 
> 
> My question concerns IRC channels. Refer to 
> https://wiki.openstack.org/wiki/IRC. That page says, "If you want to start a 
> new IRC channel, please consult with the InfrastructureTeam in 
> #openstack-infra or at openstack-infra@lists.openstack.org to ensure it gets 
> registered appropriately."
> 
> So, what exactly do the infrastructure folks do when creating an IRC channel?
> 
> Thanks in advance for your help,
> 
> Dave
> 
> 
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Dave:

Well first of all we chat a bit to understand the scope of your
direction. We want to understand what you are doing in case there is
already a good channel in place for you do proceed. Sometimes it is best
to work with folks who are already in that space if that exists, it
helps you reach your goals faster.

Some projects are best discussed in the #openstack-infra channel. It
helps us to be aware of obstacles and ensure the project is headed in a
successful direction.

This page might have some information that is helpful for you:
http://ci.openstack.org/irc.html

Do stop into #openstack-infra and say hello. I look forward to chatting
with you there, my nick is anteaya.

Thanks Dave,
Anita.

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

Re: [OpenStack-Infra] Zanata demo server

[Anita Kuno]

On 05/26/2014 07:10 PM, Carlos Munoz wrote:
> Hi All,
> 
> My name is Carlos Munoz and I am the team supervisor for the Zanata
> (zanata.org) team in Brisbane, Australia. After attending OpenStack
> summit in Atlanta a few weeks back, it was decided that a trial Zanata
> server should be set up for evaluation purposes.
> 
> Daisy suggested I introduced myself to the list just to make sure that
> you have everything you need to make the installation successful. Please
> don't hesitate to contact me with any questions or concerns, and I'll
> make sure that either myself or someone from the Zanata team provides an
> answer.
> 
> Regards,
> 
Hi Carlos:

Welcome and thanks for the introduction.

If you are able to join us on irc, freenode network #openstack-infra,
that is where we spend the majority of our time. Email works as well.

Thanks,
Anita.

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

Re: [OpenStack-Infra] Update to OpenDaylight Jenkins user

[Anita Kuno]

On 06/04/2014 05:31 PM, Andrew Grimberg wrote:
> I received a request from one of my OpenDaylight / OpenStack devs
> (Kyle Mestery) informing me that we're being asked to update the
> display name of our CI system (currently it's 'OpenDaylight
> Jenkins').
> 
> When I had originally requested a stream access [1] account I had 
> provided just a preferred username (odl-jenkins), email address 
> (odl-openst...@opendaylight.org) & SSH pubkey.
> 
> Unfortunately my local records were not clear and I couldn't
> remember what exactly I had done and forgot that a user hadn't been
> created directly in LaunchPad and so I went and did that and I've
> also attached the same email address. Of course, logging in to
> Gerrit using that account won't allow me to configure that account
> to have the uid of odl-jenkins. Could I get some help to merge the
> two gerrit accounts that now exist?
> 
> The first one is identified as a full name of 'OpenDaylight
> Jenkins', email address: odl-openst...@opendaylight.org and has an
> SSH pubkey of 'ssh-rsa B3NzaC1yc2EBIwAAAQEAztcqByxj 
> +6H3Vb78ZZN8FTbritMUBssYGxNdjdbhYJk60hQq/D4adWf4RAf3F6FGKhWCZAqPMdHFyZNjHsWUJJZGs68B0fA/jnlU1CQTeD3cf2olgXYE8X/h1c1LW1iPYndFm8JSmz3b8FigIcMEekTxlQzLOtToWoUPiLkrG/esk1lUd2FUapEay03iId9cERSTBtiAGVzw5K5E5HYotzriQnugcOkTxQilbXNBbg+m1YshC7wFlGHpOQHTtG+BhznXtmlFRXQTcOiwtp5f9PJgIyzeOMNN45i/Dbl4lAQpTqf/OklMh4CSK+LaHlJ1MgaKfb5Qk3NXdGTsKhOGvQ==
> odl-jenk...@opendaylight.org'
> 
> This account is in the 'Voting Third-Party CI' group. As there is
> no LaunchPad ID attached to it I can't get in to modify the display
> / full name.
> 
> The newly created account is account_id 11779
> 
> With a Full Name of 'OpenDaylight CI' (what I've been asked to
> change the display name to), email address of
> odl-openst...@opendaylight.org, same SSH pubkey. This account has a
> launchpad identity associated with it.
> 
> If I could get the accounts merged that would be helpful so that I
> can manage the display name as requested.
> 
> [1] 
> http://lists.openstack.org/pipermail/openstack-infra/2014-February/000803.html
>
>  Thanks, -Andy-
> 
> 
> 
> ___ OpenStack-Infra
> mailing list OpenStack-Infra@lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
> 
Hi Andy:

I had talked to Kyle earlier. You aren't being asked to do anything.

We are working through a naming standardization process and I just was
informing Kyle the name would be changing.

>From OpenDaylight Jenkins to OpenDaylight CI.

We have over 55 automated Gerrit accounts and the use of OpenStack,
test, testing, Jenkins, Tempest and user (which occurs in some account
names) is confusing to devs. We are removing those and using CI for
voting accounts and Bot for accounts which never will vote.

Thanks for the quick response and sorry for the confusion.

Anita.
anteaya on irc

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

Re: [OpenStack-Infra] Brocade: Rogue 3rd-party CI system

[Anita Kuno]

On 06/12/2014 01:40 PM, Steven Weston wrote:
> Hi Rob,
> 
>   Thank you for alerting us to the issue.  Fortunately, we were able to take 
> the Zuul server offline immediately and resolve the issue within half an 
> hour.  I have included a link to the IRC logs, here: 
> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-12.log
And here is the timestamp for the above log url: 2014-06-12T08:52:57


> 
>   If there are any further problems, please don’t hesitate to contact us, or 
> feel free to ping me in IRC.
> 
> Steve Weston
> OpenStack Software Engineer
> Brocade
> 
> -Original Message-
> From: Robert Collins [mailto:robe...@robertcollins.net] 
> Sent: Thursday, June 12, 2014 1:48 AM
> To: DL-GRP-VYATTA-OSS; 
> Subject: Brocade: Rogue 3rd-party CI system
> 
> Hi, your 3rd-party zuul is mis-configured:
>  - its reporting on test starting (which isn't needed for third party systems 
> AFAIK)
>  - its claiming that its running at the master zuul location (its not!)
>  - its running on everything rather than your area of interest (as far as I 
> can tell)
> 
> could you please disable gerrit reporting until you've got it bedded in? Jay 
> Pipes wrote a good guide for doing 3rd-party CI properly...
> 
> -Rob
> 
> --
> Robert Collins 
> Distinguished Technologist
> HP Converged Cloud
> ___
> 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 Service Account Change Request For openstack_ger...@brocade.com

[Anita Kuno]

On 06/12/2014 03:44 PM, Steven Weston wrote:
> Sorry for the confusion, I have just been informed that Shiv Harris is using 
> that key.  Could we request, instead, that the ssh key be updated for 
> brocade_jenkins (email shivha...@gmail.com) instead?
> 
> Thanks,
> Steve Weston
> OpenStack Software Engineer
> Brocade
> 
> 
> From: Steven Weston 
> (swes...@brocade.com)
> Sent: Thursday, June 12, 2014 12:39 PM
> To: OpenStack Infra Mailing List 
> (openstack-infra@lists.openstack.org)
> Cc: DL-GRP-ENG-OpenStack-CI 
> (dl-grp-eng-openstack...@brocade.com)
> Subject: Gerrit Service Account Change Request For 
> openstack_ger...@brocade.com
> 
> Brocade would like to request that the Gerrit Service Account for 
> openstack_ger...@brocade.com be updated 
> with the following public ssh key:
> 
> ssh-rsa 
> B3NzaC1yc2EDAQABgQC0ErovwEXzR9Z/BEM8Tou07EtZrhFY1SNvbgemtO2b+CYwAEpjBaW7y9MHsuILTTDV20FOtZJPNRhfC4LTzwOefFH0EV6da930H4iGUZ1hIecMfkw3M2XW3d6GtV4PteRrMfAqYs+hcfWEESpzrGFtZ9zUf4sgb/NV7YdTy7UFnw==
>  brocade-bna-ci
> 
> The key is also attached to the email.
> 
> Please note that we would not like the account name, username, or email 
> address updated at this time.
> 
> Thank You!
> 
> Steve Weston
> OpenStack Software Engineer
> Brocade
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
So to confirm:

the ssh key you are including with this email is to be used with
brocade_jenkins (email shivha...@gmail.com).

Is that an accurate statement?

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

Re: [OpenStack-Infra] moving Activity Board fully under openstack-ci

[Anita Kuno]

On 06/15/2014 06:46 PM, Monty Taylor wrote:
> On 06/09/2014 12:15 AM, Jesus M. Gonzalez-Barahona wrote:
>> On Tue, 2014-06-03 at 20:39 +, Stangel, Dan wrote:
>>> Stef,
>>>
>>> On Mon, 2014-06-02 at 14:31 -0700, Stefano Maffulli wrote:
 ...
 The question for OpenStack-CI is then: in the next weeks/months, is
 there going to be someone free, from the CI team or someone willing to
 join it (Dan?), to help Bitergia's team get their tools on our
 infrastructure?
>>>
>>> My impression from the recent "Replace Launchpad OpenID authentication"
>>> design summit session (see https://etherpad.openstack.org/p/juno-openid)
>>> was that infra would prefer that the Foundation create new blueprints to
>>> track and respond to these kinds of requests for resources / integration
>>> work.
>>>
>>> Speaking for myself at least, I'm neither an expert in the "OpenStack-CI
>>> way", nor the *grimoire toolset.  I would love to help any way I can,
>>> but leading the effort is probably not for me to do.
>>>
>>> Dan
>>
>> Oooops. I had missed this message. Sorry. Thanks for your offer of help.
>>
>> Then, do you all think it would better we write that blueprint, or we
>> just go on through email, as we started in this thread with Monty
>> Taylor?
> 
> It would probably be a good exercise to write a blueprint and a spec in
> the infra-specs repo. Honestly, if everything happened and I wasn't even
> involved personally, that would be neat! :)

Yeah, don't pin your progress on Monty. He is a great guy and I wish I
could see more of him, but your safest bet is to use the infra-specs
repo and do consider joining us on irc, freenode server,
#openstack-infra to keep things moving along.

Thanks,
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] [3rd Party] Log retention with 3rd party testing

[Anita Kuno]

On 06/17/2014 12:59 AM, trinath.soman...@freescale.com wrote:
> Hi Stackers-
> 
> I have a doubt on what is the timeline for log retention. From the discussion 
> (irc), I learnt that time for log retention is ONE month.
> 
> I have two scenarios to deal with.
> 
> [1] A change takes two months or more to get merged into the master branch.
> 
>  Here, if CI's, delete the logs of the last month, the owner/reviewer may 
> not be able to check the old logs.
> 
> [2] A change is good and merged into the master branch.
> 
>  Here, if in future this change creates a BUG, a research on the CI logs 
> might be a helpful to resolve this.
> 
> To retain all the logs forever will be an storage issue.
> 
> Kindly help me with you suggestions to resolve this.
> 
> Thanks in advance.
> 
> 
> --
> Trinath Somanchi - B39208
> trinath.soman...@freescale.com | extn: 4048
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Trianth:

You posted this exact same post last week:
http://lists.openstack.org/pipermail/openstack-dev/2014-June/037666.html

Have you read all of How to Ask Questions the Smart Way?
http://www.catb.org/esr/faqs/smart-questions.html

Sometimes others don't feel the same way that you do about an issue, or
maybe they do but not as the same time as you do. Sometimes you need to
accept that others don't wish to talk about the same topics as yourself
when you want to. You could take the time to read what others are
saying, talk to other people, ask them "What is important to you?" and
actually _listen_ to what they have to say. You might learn something.
You also might learn, by caring what someone else has to say, that you
find some people are willing to care what you have to say on a topic. It
doesn't mean they will agree, but by making connections and listening to
others, others may listen to you.

Please don't continue to post the same topic to the mailing list, once
is enough. If people are interested, they will talk to you about it. If
they aren't, well sometimes you have to accept that they aren't.

Thanks for your continued enthusiasm in the third-party space, Trianth.
I appreciate it,
Anita.

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

Re: [OpenStack-Infra] Add Datera service account

[Anita Kuno]

On 06/18/2014 04:21 PM, Mike Perez wrote:
> Hello,
> 
> I would like to have a service account added please.
> 
> Pub key:
> ssh-rsa
> B3NzaC1yc2EDAQABgQCwIZcZ7jwJA3Fo071bvL7rPfKX4zv2t04mf4Xw9jhfgijQjd7WfWxYguLCuEf2ymB8yrn0XKfBV1XqbEhe9V33kPVzcGk0+omDb5BeY7lIgXVAloWHshx7D8UwwFLWUa/RREqaVow+zx5U3Rlg6OK5MyQRBAxeCtTczgPxOB8m3Q==
> 
> username: datera-storage-ci
> Fullname: Datera Storage CI
> email: datera-openstack...@datera.io
> 
> --
> Mike Perez
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Storage is a poor word choice. There will be too many accounts with
storage in the name.

What is the name of your proprietary product you are testing?

so datera-{name of proprietary thing}-ci

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

Re: [OpenStack-Infra] Add Datera service account

[Anita Kuno]

On 06/18/2014 05:03 PM, Mike Perez wrote:
> On 16:46 Wed 18 Jun , Anita Kuno wrote:
>> On 06/18/2014 04:21 PM, Mike Perez wrote:
>>> Hello,
>>>
>>> I would like to have a service account added please.
>>>
>>> Pub key:
>>> ssh-rsa
>>> B3NzaC1yc2EDAQABgQCwIZcZ7jwJA3Fo071bvL7rPfKX4zv2t04mf4Xw9jhfgijQjd7WfWxYguLCuEf2ymB8yrn0XKfBV1XqbEhe9V33kPVzcGk0+omDb5BeY7lIgXVAloWHshx7D8UwwFLWUa/RREqaVow+zx5U3Rlg6OK5MyQRBAxeCtTczgPxOB8m3Q==
>>>
>>> username: datera-storage-ci
>>> Fullname: Datera Storage CI
>>> email: datera-openstack...@datera.io
>>>
>>> --
>>> Mike Perez
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Storage is a poor word choice. There will be too many accounts with
>> storage in the name.
>>
>> What is the name of your proprietary product you are testing?
>>
>> so datera-{name of proprietary thing}-ci
> 
> This is testing for a Cinder driver. datera-block-storage-ci is what comes to
> mind, but that does contain storage in the name.
> 
We can go with datera-ci if this is the only ci system datera will ever
need.

The more we have openstack program names in the account name, the harder
it is for the developers.

The name ideally should answer the question of why you are testing using
a third party ci rather than putting your tests in the cinder gate.

What is the name of your cinder driver?

Perhaps datera-{name of datera cinder driver}-ci?

Anita.

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

Re: [OpenStack-Infra] Add Datera service account

[Anita Kuno]

On 06/18/2014 05:11 PM, Mike Perez wrote:
> On 17:08 Wed 18 Jun , Anita Kuno wrote:
>> On 06/18/2014 05:03 PM, Mike Perez wrote:
>>> On 16:46 Wed 18 Jun , Anita Kuno wrote:
>>>> On 06/18/2014 04:21 PM, Mike Perez wrote:
>>>>> Hello,
>>>>>
>>>>> I would like to have a service account added please.
>>>>>
>>>>> Pub key:
>>>>> ssh-rsa
>>>>> B3NzaC1yc2EDAQABgQCwIZcZ7jwJA3Fo071bvL7rPfKX4zv2t04mf4Xw9jhfgijQjd7WfWxYguLCuEf2ymB8yrn0XKfBV1XqbEhe9V33kPVzcGk0+omDb5BeY7lIgXVAloWHshx7D8UwwFLWUa/RREqaVow+zx5U3Rlg6OK5MyQRBAxeCtTczgPxOB8m3Q==
>>>>>
>>>>> username: datera-storage-ci
>>>>> Fullname: Datera Storage CI
>>>>> email: datera-openstack...@datera.io
>>>>>
>>>>> --
>>>>> Mike Perez
>>>>>
>>>>> ___
>>>>> OpenStack-Infra mailing list
>>>>> OpenStack-Infra@lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>>
>>>> Storage is a poor word choice. There will be too many accounts with
>>>> storage in the name.
>>>>
>>>> What is the name of your proprietary product you are testing?
>>>>
>>>> so datera-{name of proprietary thing}-ci
>>>
>>> This is testing for a Cinder driver. datera-block-storage-ci is what comes 
>>> to
>>> mind, but that does contain storage in the name.
>>>
>> We can go with datera-ci if this is the only ci system datera will ever
>> need.
>>
>> The more we have openstack program names in the account name, the harder
>> it is for the developers.
>>
>> The name ideally should answer the question of why you are testing using
>> a third party ci rather than putting your tests in the cinder gate.
>>
>> What is the name of your cinder driver?
>>
>> Perhaps datera-{name of datera cinder driver}-ci?
>>
>> Anita.
> 
> It's called Datera.
> 
> datera-datera-ci wouldn't be ideal.
> 
Let's go with datera-ci then.

That is perfectly feasible from our end.

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

Re: [OpenStack-Infra] Add Datera service account

[Anita Kuno]

On 06/18/2014 05:18 PM, Mike Perez wrote:
> On 17:14 Wed 18 Jun , Anita Kuno wrote:
>> On 06/18/2014 05:11 PM, Mike Perez wrote:
>>> On 17:08 Wed 18 Jun , Anita Kuno wrote:
>>>> On 06/18/2014 05:03 PM, Mike Perez wrote:
>>>>> On 16:46 Wed 18 Jun , Anita Kuno wrote:
>>>>>> On 06/18/2014 04:21 PM, Mike Perez wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I would like to have a service account added please.
>>>>>>>
>>>>>>> Pub key:
>>>>>>> ssh-rsa
>>>>>>> B3NzaC1yc2EDAQABgQCwIZcZ7jwJA3Fo071bvL7rPfKX4zv2t04mf4Xw9jhfgijQjd7WfWxYguLCuEf2ymB8yrn0XKfBV1XqbEhe9V33kPVzcGk0+omDb5BeY7lIgXVAloWHshx7D8UwwFLWUa/RREqaVow+zx5U3Rlg6OK5MyQRBAxeCtTczgPxOB8m3Q==
>>>>>>>
>>>>>>> username: datera-storage-ci
>>>>>>> Fullname: Datera Storage CI
>>>>>>> email: datera-openstack...@datera.io
>>>>>>>
>>>>>>> --
>>>>>>> Mike Perez
>>>>>>>
>>>>>>> ___
>>>>>>> OpenStack-Infra mailing list
>>>>>>> OpenStack-Infra@lists.openstack.org
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>>>>
>>>>>> Storage is a poor word choice. There will be too many accounts with
>>>>>> storage in the name.
>>>>>>
>>>>>> What is the name of your proprietary product you are testing?
>>>>>>
>>>>>> so datera-{name of proprietary thing}-ci
>>>>>
>>>>> This is testing for a Cinder driver. datera-block-storage-ci is what 
>>>>> comes to
>>>>> mind, but that does contain storage in the name.
>>>>>
>>>> We can go with datera-ci if this is the only ci system datera will ever
>>>> need.
>>>>
>>>> The more we have openstack program names in the account name, the harder
>>>> it is for the developers.
>>>>
>>>> The name ideally should answer the question of why you are testing using
>>>> a third party ci rather than putting your tests in the cinder gate.
>>>>
>>>> What is the name of your cinder driver?
>>>>
>>>> Perhaps datera-{name of datera cinder driver}-ci?
>>>>
>>>> Anita.
>>>
>>> It's called Datera.
>>>
>>> datera-datera-ci wouldn't be ideal.
>>>
>> Let's go with datera-ci then.
>>
>> That is perfectly feasible from our end.
> 
> Works for me. Thanks for the help Anita!
> 
Great thanks.

So when someone with permissions next takes a pass at account creation:

username: datera-ci
Full Name: Datera CI

Email and ssh key as posted in original email.

Thanks Mike.

I'm anteaya on irc, I'll probably be point person for a lot of third
party CI questions. Do join us for the third party meetings:
https://wiki.openstack.org/wiki/Meetings/ThirdParty

Anita.

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

[OpenStack-Infra] Hosting your CI logs at dropbox is not acceptable

[Anita Kuno]

Hello:

Your system, Radware 3rd Party Testing, has logs hosted at a dropbox
account. This is not acceptable.

Further, your logs are a tarball which must be downloaded. This also is
unacceptable.

https://review.openstack.org/#/c/98899/

Your logs must be hosted on a secure server that allows the logs to be
accessible via a browser. Firefox and chrome must be supported, at the
very least.

Please respond to this email as soon as you receive it to acknowledge
its receipt. Please disable your system until you can make the required
changes.

It is preferred if someone is available on irc to field questions about
your account. Please have that person make contact with me on irc, my
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] Hosting your CI logs at dropbox is not acceptable

[Anita Kuno]

On 06/19/2014 10:08 AM, Anita Kuno wrote:
> Hello:
> 
> Your system, Radware 3rd Party Testing, has logs hosted at a dropbox
> account. This is not acceptable.
> 
> Further, your logs are a tarball which must be downloaded. This also is
> unacceptable.
> 
> https://review.openstack.org/#/c/98899/
> 
> Your logs must be hosted on a secure server that allows the logs to be
> accessible via a browser. Firefox and chrome must be supported, at the
> very least.
> 
> Please respond to this email as soon as you receive it to acknowledge
> its receipt. Please disable your system until you can make the required
> changes.
> 
> It is preferred if someone is available on irc to field questions about
> your account. Please have that person make contact with me on irc, my
> nickname is anteaya.
> 
> Thank you,
> Anita.
> 
This email generated a fast response in irc:
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-19.log
timestamp 2014-06-19T14:23:54

by IzikPenso

Izik decided to disable the system to fix the log situation.

Thank you for the quick response, Izik,
Anita.

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

[OpenStack-Infra] power kvm ci posting invalid urls in test results

[Anita Kuno]

Hello:

I have had a report about the current status of power kvm ci.

sdague | anteaya / krtaylor: the powerkvm ci seems to be posting invalid
urls in test results. That should either be fixed, or it should be
turned off.
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-20.log
timestamp 2014-06-20T12:55:59

Please respond to this email as soon as you receive 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] Introducing Richard Jones

[Anita Kuno]

On 06/22/2014 07:38 PM, Monty Taylor wrote:
> I'm going to molest you
No, no you aren't. Not in any way shape or form. I will stop you.

Welcome Richard.

Anita.
> 
> On Jun 22, 2014 7:23 PM, Michael Still  wrote:
>>
>> Hey peoples, 
>>
>> So, I've had a bit of a win and hired the primary author of pypi to 
>> work on OpenStack stuff for Rackspace Australia. His first day is 
>> today. 
>>
>> I know we've had some pain with pypi in the past, but I think they're 
>> mostly resolved now. Regardless, I want you to know that Richard is 
>> around as a resource if you need him. 
>>
>> Cheers, 
>> Michael 
>>
>> -- 
>> Rackspace Australia 
>>
>> ___ 
>> 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] Hosting your CI logs at dropbox is not acceptable

[Anita Kuno]

On 06/22/2014 07:10 AM, Avishay Balderman wrote:
> Hi Anita
> Can you please point us to the specification explaining how the 3rd party 
> test results should be hosted?
> 
> What is the main feature for the hosting?
> As far as we understand the files should be visible via browser (Chrome,FF).
> 
> Anything else?
> 
> Thanks
> 
> Avishay
> 
Hi Avishay:

In opensource we have less of an emphasis on specifications and more of
an emphasis on discussion. Yes I can point you to at least one
discussion so far on log hosting and invite you and members of your
group to more discussions on the topic.
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-19.log
timestamp 2014-06-19T13:49:43

Currently we have this documentation around third party testing
requirements: http://ci.openstack.org/third_party.html
Also in light of recent discussions there are two patches in review for
changes to that document: https://review.openstack.org/#/c/101013/ and
https://review.openstack.org/#/c/101227/

We also have a weekly third party meeting that takes place on Mondays at
1800 utc in the #openstack-meeting channel on the freenode network where
we discuss current practices, any questions, identify issues and work to
address them as well as share information among openstack programs and
third party ci systems: https://wiki.openstack.org/wiki/Meetings/ThirdParty

Opensource is a living entity and the more you participate in the
discussions that result in documentation, the more you have a say in
what happens and the better informed you are.

The main feature for the hosting is that it most closely matches the
workflow that the developers already use with gerrit. The more familiar
you are with gerrit, the easier it is to get hosting right. Now we will
create and amend documents as we need to to refine communication around
hosting of logs (as well as all other aspects of third party ci) but the
docs will only ever be looking to address behaviour that we never
imagined anyone would do (or omit) in the first place. I strongly
encourage you to participate in the third party meetings as well as in
the irc channel for the project you are testing to talk with the
developers who are getting the comments from your system on their
patches and hear from them what you system needs to do to make them happy.

Also if I email you in future and cc the openstack-infra mailing list,
please cc the openstack-infra mailing list in your reply. I have done so
in my reply.

Thanks Avishay, I hope to see you or another representative of your
third party ci account in the third party meeting in a few hours,
Anita.

> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Thursday, June 19, 2014 6:39 PM
> To: OpenStack3RDPartyTesting; openstack-infra@lists.openstack.org
> Subject: Re: Hosting your CI logs at dropbox is not acceptable
> 
> On 06/19/2014 10:08 AM, Anita Kuno wrote:
>> Hello:
>>
>> Your system, Radware 3rd Party Testing, has logs hosted at a dropbox 
>> account. This is not acceptable.
>>
>> Further, your logs are a tarball which must be downloaded. This also 
>> is unacceptable.
>>
>> https://review.openstack.org/#/c/98899/
>>
>> Your logs must be hosted on a secure server that allows the logs to be 
>> accessible via a browser. Firefox and chrome must be supported, at the 
>> very least.
>>
>> Please respond to this email as soon as you receive it to acknowledge 
>> its receipt. Please disable your system until you can make the 
>> required changes.
>>
>> It is preferred if someone is available on irc to field questions 
>> about your account. Please have that person make contact with me on 
>> irc, my nickname is anteaya.
>>
>> Thank you,
>> Anita.
>>
> This email generated a fast response in irc:
> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-19.log
> timestamp 2014-06-19T14:23:54
> 
> by IzikPenso
> 
> Izik decided to disable the system to fix the log situation.
> 
> Thank you for the quick response, Izik,
> Anita.
> 


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

Re: [OpenStack-Infra] Hosting your CI logs at dropbox is not acceptable

[Anita Kuno]

On 06/23/2014 10:35 AM, Avishay Balderman wrote:
> Hi
> Thanks for your detailed answer.
> Is the following  link  "valid" for logs hosting?
> (download is not needed, works fine under Chrome and FF)
> 
> https://www.dropbox.com/sh/wl2i5kbofvpbgm9/AADj8qye3nU05Y2ZKNwRQNIWa
> 
> Thanks
> 
> Avishay
Well it isn't open source for starters, and so far while it isn't a
requirment, use of non open source options is discouraged.

Secondly, go to the link yourself and click. See long you you have to
wait until the log file is served, then do the same for the second file.
Now imagine 30 files, some of which you have to go back and look at a
second time. Now imagine a patch where the developer has 5 or more
systems reporting on a given patch (some patches have more but lets go
with 5). All the log hosting systems meet the letter of the requirements
but all are in a different format. The developer has to spend at least
an hour going through 6 different sets of logs (including the OpenStack
set) for one patchset to see where there is a problem. They are going to
get frustrated because this takes too much of their time to figure out
what the problem is. The system that takes so long to render logs is
going to get a complaint, I field the complaint and act on the behalf of
the developer. Then I have to make up a new rule so that third party ci
systems more closely match our system (which the devlopers are used to)
but without saying "do what we do".

So in short, I prefer open source solutions and I would get frustrated
waiting for the log files to render.

Thanks Avishay,
Anita.
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Monday, June 23, 2014 5:16 PM
> To: Avishay Balderman
> Cc: Samuel Bercovici; Izik Penso; openstack-infra@lists.openstack.org
> Subject: Re: Hosting your CI logs at dropbox is not acceptable
> 
> On 06/22/2014 07:10 AM, Avishay Balderman wrote:
>> Hi Anita
>> Can you please point us to the specification explaining how the 3rd party 
>> test results should be hosted?
>>
>> What is the main feature for the hosting?
>> As far as we understand the files should be visible via browser (Chrome,FF).
>>
>> Anything else?
>>
>> Thanks
>>
>> Avishay
>>
> Hi Avishay:
> 
> In opensource we have less of an emphasis on specifications and more of an 
> emphasis on discussion. Yes I can point you to at least one discussion so far 
> on log hosting and invite you and members of your group to more discussions 
> on the topic.
> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-19.log
> timestamp 2014-06-19T13:49:43
> 
> Currently we have this documentation around third party testing
> requirements: http://ci.openstack.org/third_party.html
> Also in light of recent discussions there are two patches in review for 
> changes to that document: https://review.openstack.org/#/c/101013/ and 
> https://review.openstack.org/#/c/101227/
> 
> We also have a weekly third party meeting that takes place on Mondays at
> 1800 utc in the #openstack-meeting channel on the freenode network where we 
> discuss current practices, any questions, identify issues and work to address 
> them as well as share information among openstack programs and third party ci 
> systems: https://wiki.openstack.org/wiki/Meetings/ThirdParty
> 
> Opensource is a living entity and the more you participate in the discussions 
> that result in documentation, the more you have a say in what happens and the 
> better informed you are.
> 
> The main feature for the hosting is that it most closely matches the workflow 
> that the developers already use with gerrit. The more familiar you are with 
> gerrit, the easier it is to get hosting right. Now we will create and amend 
> documents as we need to to refine communication around hosting of logs (as 
> well as all other aspects of third party ci) but the docs will only ever be 
> looking to address behaviour that we never imagined anyone would do (or omit) 
> in the first place. I strongly encourage you to participate in the third 
> party meetings as well as in the irc channel for the project you are testing 
> to talk with the developers who are getting the comments from your system on 
> their patches and hear from them what you system needs to do to make them 
> happy.
> 
> Also if I email you in future and cc the openstack-infra mailing list, please 
> cc the openstack-infra mailing list in your reply. I have done so in my reply.
> 
> Thanks Avishay, I hope to see you or another representative of your third 
> party ci account in the third party meeting in a few hours, Anita.
> 
>>
>> -Original Message-
>> From: An

Re: [OpenStack-Infra] Hosting your CI logs at dropbox is not acceptable

[Anita Kuno]

On 06/23/2014 10:59 AM, Samuel Bercovici wrote:
> Hi Anita,
> 
> When you mention opens source solution, please point to an available open 
> source hosting that we can use to push the log files into?
> The alternative would be to put the 3rd party testing CI system behind a 
> public IP and this will most likely going to take time.
> 
> Regards,
>   -Sam.
Hi Sam:

Well if you attend the third party meeting in #openstack-meeting at 1800
utc you can chat with other third party ci folks and find out how they
host their logs. Getting to know other third party ci maintainers and
sharing information with them will probably help you a lot in this and
other matters.

If I am asked to point to an available open source hosting solution, I
would suggest a secure server running apache, which is what most systems
use for their logs (as far as I know).

Thanks Sam,
Anita.
> 
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Monday, June 23, 2014 5:51 PM
> To: Avishay Balderman
> Cc: Samuel Bercovici; Izik Penso; openstack-infra@lists.openstack.org
> Subject: Re: Hosting your CI logs at dropbox is not acceptable
> 
> On 06/23/2014 10:35 AM, Avishay Balderman wrote:
>> Hi
>> Thanks for your detailed answer.
>> Is the following  link  "valid" for logs hosting?
>> (download is not needed, works fine under Chrome and FF)
>>
>> https://www.dropbox.com/sh/wl2i5kbofvpbgm9/AADj8qye3nU05Y2ZKNwRQNIWa
>>
>> Thanks
>>
>> Avishay
> Well it isn't open source for starters, and so far while it isn't a 
> requirment, use of non open source options is discouraged.
> 
> Secondly, go to the link yourself and click. See long you you have to wait 
> until the log file is served, then do the same for the second file.
> Now imagine 30 files, some of which you have to go back and look at a second 
> time. Now imagine a patch where the developer has 5 or more systems reporting 
> on a given patch (some patches have more but lets go with 5). All the log 
> hosting systems meet the letter of the requirements but all are in a 
> different format. The developer has to spend at least an hour going through 6 
> different sets of logs (including the OpenStack
> set) for one patchset to see where there is a problem. They are going to get 
> frustrated because this takes too much of their time to figure out what the 
> problem is. The system that takes so long to render logs is going to get a 
> complaint, I field the complaint and act on the behalf of the developer. Then 
> I have to make up a new rule so that third party ci systems more closely 
> match our system (which the devlopers are used to) but without saying "do 
> what we do".
> 
> So in short, I prefer open source solutions and I would get frustrated 
> waiting for the log files to render.
> 
> Thanks Avishay,
> Anita.
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: Monday, June 23, 2014 5:16 PM
>> To: Avishay Balderman
>> Cc: Samuel Bercovici; Izik Penso; openstack-infra@lists.openstack.org
>> Subject: Re: Hosting your CI logs at dropbox is not acceptable
>>
>> On 06/22/2014 07:10 AM, Avishay Balderman wrote:
>>> Hi Anita
>>> Can you please point us to the specification explaining how the 3rd party 
>>> test results should be hosted?
>>>
>>> What is the main feature for the hosting?
>>> As far as we understand the files should be visible via browser (Chrome,FF).
>>>
>>> Anything else?
>>>
>>> Thanks
>>>
>>> Avishay
>>>
>> Hi Avishay:
>>
>> In opensource we have less of an emphasis on specifications and more of an 
>> emphasis on discussion. Yes I can point you to at least one discussion so 
>> far on log hosting and invite you and members of your group to more 
>> discussions on the topic.
>> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack
>> -infra.2014-06-19.log
>> timestamp 2014-06-19T13:49:43
>>
>> Currently we have this documentation around third party testing
>> requirements: http://ci.openstack.org/third_party.html
>> Also in light of recent discussions there are two patches in review 
>> for changes to that document: https://review.openstack.org/#/c/101013/ 
>> and https://review.openstack.org/#/c/101227/
>>
>> We also have a weekly third party meeting that takes place on Mondays 
>> at
>> 1800 utc in the #openstack-meeting channel on the freenode network 
>> where we discuss current practices, any questions, identify issues and 
>> work to address them as well as sh

Re: [OpenStack-Infra] Requesting a Service Account

[Anita Kuno]

On 06/25/2014 11:48 AM, David Pineau wrote:
> Hello,
> 
> I currently work on Cinder for my company, Scality. We plan to work on other 
> parts of openstack in the near future too, and as such, we are currently 
> setting up a Third-party CI system, that would validate and vote for each 
> project that requires (or supports) it.
> 
> It seems I was misled by the documentation and created a user account instead 
> of a service account, named "scal-ci" with the ID 12123. I discussed it with 
> anteaya before writing this message, so fungi (Jeremy Stanley) has the 
> removal of that erroneous account on his todo list.
> 
> So here I am requestion a service account:
> Username: scality-ci
> E-Mail: openstack...@scality.com
> Name: Scality CI
> Ssh key:
> ssh-rsa 
> B3NzaC1yc2EDAQABgQDOoIUeA/EAhn0He8PUSQc038iSukahiDpHYB0lrWQQCqYrd8WJ0YJufl7cP8gi3nCAGn4Box5q36rO4UkI6ygs0SZJhmT1s9ASpezCCe3PkLZfQkqZC1Gb6FCpU5e/cKa6iaVBGbCjWleqfVwXQkSlF9GuFjyVp5glMF3IhWp7qw==
>  s...@ns3317586.ip-5-135-165.eu
> 
> Thanks you !
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Please note:

2014-06-27T19:25:24   joa: also, i did already set that old
account inactive and nulled out the login and e-mail address for it
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-27.log

So there should be no gerrit impediments when this account is created.

Thanks,
Anita.

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

Re: [OpenStack-Infra] Requesting a Service Account

[Anita Kuno]

On 07/02/2014 09:15 AM, Subramani Ramanathan wrote:
> Hello,
> 
> I would like to have a service account with the following information.
> 
> Account Information:-
> 1. SSH Key
> 
> ssh-rsa 
> B3NzaC1yc2EBIwAAAQEA4vxKNGuQ/xgIKwDyGPp3cK0ntUQ5ZDG3RzZ93ScoSwxLQuROrV3IU/tUXTHsGuDU3UGuyb8zutFGpq0C2XqBnoHJYs1j1RWH6wBbBux6OoW5BNi/x4cR3hQ5HBEZ9VSPZD7OK95s98vTcpI6nWR3Dn2L/GG6R9Tx6avgRyp0cgVcfjlymOvCi8EgHbNLkDUu2IF2RqlYnCdjSltuEfCm+FK0ecFEbMkStlkxZCjoFDP7uVf/4aQYmiYwghDcAdxFPSMp9LaKwKiie+k8pHln6Wd23bJkELsqHMWJKzIr3GueZjJqmRE6RbjzAhw5+9Jk7VesAp2GEf1b1kRBA4dSiQ==
>  ib-ipam-bot@ib-jenkins-master
> 
> 2. SSH Username
> 
> ib-ipam-bot
> 
> 3. Display name
> 
> IB IPAM Bot
> 
> 4. Contact E-mail
> 
> sramanat...@infoblox.com
> 
> Thanks,
> Subramani.
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Subramani:

Can you explain what it is your bot is intended to do?

Thanks,
Anita.

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

Re: [OpenStack-Infra] Current options for getting Zanata going

[Anita Kuno]

On 07/01/2014 01:10 PM, Elizabeth K. Joseph wrote:
> Hi everyone,
> 
> I met with Carlos of Zanata last week to chat about progress on
> getting a VM up to demo it, some take-aways that we should chat about:
> 
> 1. I was finally able to get a demo up of the pre-configured JBoss AS
> 7 version and they've updated http://zanata.org/download/ to reflect
> parts where I got stuck
> 
> Unfortunately they say right on that page that "that this is not the
> supported configuration" since it's pretty much a pre-packaged version
> pinned to AS7, and AS7 is an older, community-based version of JBoss
> that doesn't guarantee security updates. They target the enterprise
> version for use with Zanata.
> 
> Now, even getting this demo running is a very manual process and
> probably not worth puppetizing since it's not a long term solution,
> it's just a demo. The question here is - do we want to move forward
> with deploying this kind of demo site for the translators to test, or
> do we want to have a properly installed, puppetized version running?
> 
> Which leads me to...
> 
> 2. The community-based (no enterprise license) version of their
> Enterprise JBoss is called WildFly (wildfly.org) and doesn't quite run
> Zanata yet
> 
> There are some technical blockers to getting Zanata running on this,
> but there's at least one person who is working on it, and with our
> help might be able to get all the way there with full support. This is
> an investment of time for us, but if it is a great translations
> platform that the translators want to use, it may be worth it. OTOH,
> Pootle already works.
> 
> 3. Finally, there is the option of working with Red Hat to get a
> donated license for their Enterprise JBoss version for use by
> OpenStack, at the loss of having that part of our infrastructure being
> "less free" than other parts due to requirement of Enterprise
> licensing.
> 
Hey Lyz,

First of all, great work on all of this, putting in the time to research
all the options and getting a demo running.

I'd like to look at this in terms of the end goal, translations. That is
the end goal, yes?

Is one tool any better than the other (zanta and pootle are the two
options, yes?) at doing translating? Is the end product substantially
better using one tool than 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] Requesting a Service Account

[Anita Kuno]

On 07/02/2014 11:17 AM, Subramani Ramanathan wrote:
> Hi Anita,
> 
> We are creating CI environment for Neutron third party integration testing. 
> May be I should have mentioned 'ib-ipam-ci' instead of 'bot'.
> 
> Thanks,
> Subramani.
Hello Subramani:

Thank you for your prompt reply.

Yes, if you are testing Neutron, your account will need to be a CI
account not a Bot account. Thank you for catching that.

Username: ib-ipam-ci
Full Name: IB IPAM CI

Thank you,
Anita.
> ____
> From: Anita Kuno [ante...@anteaya.info]
> Sent: Wednesday, July 02, 2014 7:49 AM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] Requesting a Service Account
> 
> On 07/02/2014 09:15 AM, Subramani Ramanathan wrote:
>> Hello,
>>
>> I would like to have a service account with the following information.
>>
>> Account Information:-
>> 1. SSH Key
>>
>> ssh-rsa 
>> B3NzaC1yc2EBIwAAAQEA4vxKNGuQ/xgIKwDyGPp3cK0ntUQ5ZDG3RzZ93ScoSwxLQuROrV3IU/tUXTHsGuDU3UGuyb8zutFGpq0C2XqBnoHJYs1j1RWH6wBbBux6OoW5BNi/x4cR3hQ5HBEZ9VSPZD7OK95s98vTcpI6nWR3Dn2L/GG6R9Tx6avgRyp0cgVcfjlymOvCi8EgHbNLkDUu2IF2RqlYnCdjSltuEfCm+FK0ecFEbMkStlkxZCjoFDP7uVf/4aQYmiYwghDcAdxFPSMp9LaKwKiie+k8pHln6Wd23bJkELsqHMWJKzIr3GueZjJqmRE6RbjzAhw5+9Jk7VesAp2GEf1b1kRBA4dSiQ==
>>  ib-ipam-bot@ib-jenkins-master
>>
>> 2. SSH Username
>>
>> ib-ipam-bot
>>
>> 3. Display name
>>
>> IB IPAM Bot
>>
>> 4. Contact E-mail
>>
>> sramanat...@infoblox.com
>>
>> Thanks,
>> Subramani.
>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> Hi Subramani:
> 
> Can you explain what it is your bot is intended to do?
> 
> Thanks,
> 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] Requesting a Service Account

[Anita Kuno]

On 07/02/2014 11:33 AM, Subramani Ramanathan wrote:
> Thank You Anita for clarifying it. 
> 
> Below account information should be fine:-
> 
> Username: ib-ipam-ci
> Full Name: IB IPAM CI
> 
> Thanks,
> Subramani.
Great thanks.

Sergey is taking care of new account creation and he usually clears the
list about once a week. I'm not sure if he has looked at it this week or
not.

Anita.
> 
> ________
> From: Anita Kuno [ante...@anteaya.info]
> Sent: Wednesday, July 02, 2014 8:23 AM
> To: Subramani Ramanathan; openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] Requesting a Service Account
> 
> On 07/02/2014 11:17 AM, Subramani Ramanathan wrote:
>> Hi Anita,
>>
>> We are creating CI environment for Neutron third party integration testing. 
>> May be I should have mentioned 'ib-ipam-ci' instead of 'bot'.
>>
>> Thanks,
>> Subramani.
> Hello Subramani:
> 
> Thank you for your prompt reply.
> 
> Yes, if you are testing Neutron, your account will need to be a CI
> account not a Bot account. Thank you for catching that.
> 
> Username: ib-ipam-ci
> Full Name: IB IPAM CI
> 
> Thank you,
> Anita.
>> 
>> From: Anita Kuno [ante...@anteaya.info]
>> Sent: Wednesday, July 02, 2014 7:49 AM
>> To: openstack-infra@lists.openstack.org
>> Subject: Re: [OpenStack-Infra] Requesting a Service Account
>>
>> On 07/02/2014 09:15 AM, Subramani Ramanathan wrote:
>>> Hello,
>>>
>>> I would like to have a service account with the following information.
>>>
>>> Account Information:-
>>> 1. SSH Key
>>>
>>> ssh-rsa 
>>> B3NzaC1yc2EBIwAAAQEA4vxKNGuQ/xgIKwDyGPp3cK0ntUQ5ZDG3RzZ93ScoSwxLQuROrV3IU/tUXTHsGuDU3UGuyb8zutFGpq0C2XqBnoHJYs1j1RWH6wBbBux6OoW5BNi/x4cR3hQ5HBEZ9VSPZD7OK95s98vTcpI6nWR3Dn2L/GG6R9Tx6avgRyp0cgVcfjlymOvCi8EgHbNLkDUu2IF2RqlYnCdjSltuEfCm+FK0ecFEbMkStlkxZCjoFDP7uVf/4aQYmiYwghDcAdxFPSMp9LaKwKiie+k8pHln6Wd23bJkELsqHMWJKzIr3GueZjJqmRE6RbjzAhw5+9Jk7VesAp2GEf1b1kRBA4dSiQ==
>>>  ib-ipam-bot@ib-jenkins-master
>>>
>>> 2. SSH Username
>>>
>>> ib-ipam-bot
>>>
>>> 3. Display name
>>>
>>> IB IPAM Bot
>>>
>>> 4. Contact E-mail
>>>
>>> sramanat...@infoblox.com
>>>
>>> Thanks,
>>> Subramani.
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Hi Subramani:
>>
>> Can you explain what it is your bot is intended to do?
>>
>> Thanks,
>> 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] Current options for getting Zanata going

[Anita Kuno]

On 07/02/2014 12:25 PM, Elizabeth K. Joseph wrote:
> On Wed, Jul 2, 2014 at 8:04 AM, Anita Kuno  wrote:
>> I'd like to look at this in terms of the end goal, translations. That is
>> the end goal, yes?
>>
>> Is one tool any better than the other (zanta and pootle are the two
>> options, yes?) at doing translating? Is the end product substantially
>> better using one tool than the other?
> 
> Right, Zanata and Pootle are the two leading options. The translations
> team seemed to prefer Zanata so we said we'd work to get a demo going
> for them so they could try it themselves, just like we have for
> Pootle.
> 
> On our end maintainability is the major consideration, since we don't
> want to deploy a solution that will be disruptive to translators
> (during upgrades, etc) or insecure.
> 
Can we get an item on next week's infra agenda and have some of the
folks doing the translation work attend and offer their opinion?

It seems we might be at a point of weighing costs of setup and
maintenance time versus advantages of use.

Thanks,
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] [QA][Infra] Mid-Cycle Meet-up Registration Closed

[Anita Kuno]

On 07/02/2014 02:08 PM, Matthew Treinish wrote:
> 
> On Mon, Jun 09, 2014 at 02:08:58PM -0400, Matthew Treinish wrote:
>> On Thu, May 29, 2014 at 12:07:07PM -0400, Matthew Treinish 
>> wrote:
>>> 
>>> Hi Everyone,
>>> 
>>> So we'd like to announce to everyone that we're going to be 
>>> doing a combined Infra and QA program mid-cycle meet-up. It 
>>> will be the week of July 14th in Darmstadt, Germany at
>>> Deutsche Telekom who has graciously offered to sponsor the
>>> event. The plan is to use the week as both a time for face to
>>> face collaboration for both programs respectively as well as
>>> having a couple days of bootstrapping for new
>>> users/contributors. The intent was that this would be useful
>>> for people who are interested in contributing to either Infra
>>> or QA, and those who are running third party CI systems.
>>> 
>>> The current break down for the week that we're looking at is:
>>> 
>>> July 14th: Infra July 15th: Infra July 16th: Bootstrapping for 
>>> new users July 17th: More bootstrapping July 18th: QA
>>> 
>>> We still have to work out more details, and will follow up
>>> once we have them. But, we thought it would be better to
>>> announce the event earlier so people can start to plan travel
>>> if they need it.
>>> 
>>> 
>>> Thanks,
>>> 
>>> Matt Treinish Jim Blair
>> 
>> 
>> Just a quick follow-up, the agenda has changed slightly based on 
>> room availability since I first sent out the announcement. You 
>> can find up-to-date information on the meet-up wiki page:
>> 
>> https://wiki.openstack.org/wiki/Qa_Infra_Meetup_2014
>> 
>> Once we work out a detailed agenda of discussion topics/work 
>> items for the 3 discussion days I'll update the wiki page.
>> 
>> Also, if you're intending to attend please put your name on the 
>> wiki page's registration section.
>> 
>> Thanks,
>> 
>> Matt Treinish
> 
> Hi Everyone,
> 
> Just a quick update, we have to close registration for the
> Infra/QA mid-cycle meet-up. Based on the number of people who have
> signed up on the wiki page [1] we are basically at the maximum
> capacity for the rooms we reserved. So if you had intended to come
> but didn't sign up on the wiki unfortunately there isn't any space
> left.
> 
> Thanks,
> 
> Matt Treinish
> 
> [1] 
> https://wiki.openstack.org/wiki/Qa_Infra_Meetup_2014#Registration
> 
> 
> 
> ___ OpenStack-Infra 
> mailing list OpenStack-Infra@lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
> 
Hi Matt:

I was just talking with Kevin Taylor this morning who was trying to
find out if he could get approval to attend. Would there still be
space for him if we squeezed in?

Let me know, thanks for organizing this Matt,
Anita.

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

[OpenStack-Infra] hyperv-ci logs force me to download

[Anita Kuno]

Hello:

Your ci logs linked in your comment on this patch set include files that
force me to download.
https://review.openstack.org/#/c/61183/

All log files must be browsable. Please address your log files.

Thank you,
Anita.

reference: https://review.openstack.org/#/c/101227/

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

Re: [OpenStack-Infra] Current options for getting Zanata going

[Anita Kuno]

On 07/02/2014 10:07 PM, Ying Chun Guo wrote:
> Hello, Elizabeth
> 
> I could try to be infrastructure meeting.
> When is the next infrastructure meeting?
Infra meets on Tuesdays:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting
> 
> Now we cannot create new projects in Transifex.
> See: https://bugs.launchpad.net/openstack-i18n/+bug/608725/comments/6
> It's a big issue for us.
> Transifex supporting team is helping, but the response time is not that
> quick.
> 
> We do need to have another candidate to take place Transifex.
> 
> I notice the key issue with Zanata is the JBoss version and license.
> How about we use a Redhat donated enterprise version ?
> 
> Best regards
> Ying Chun Guo (Daisy)
> 
> 
> Anita Kuno  wrote on 2014/07/03 00:37:54:
> 
>> Anita Kuno 
>> 2014/07/03 00:37
>>
>> To
>>
>> openstack-infra@lists.openstack.org,
>>
>> cc
>>
>> Subject
>>
>> Re: [OpenStack-Infra] Current options for getting Zanata going
>>
>> On 07/02/2014 12:25 PM, Elizabeth K. Joseph wrote:
>>> On Wed, Jul 2, 2014 at 8:04 AM, Anita Kuno 
> wrote:
>>>> I'd like to look at this in terms of the end goal, translations. That
> is
>>>> the end goal, yes?
>>>>
>>>> Is one tool any better than the other (zanta and pootle are the two
>>>> options, yes?) at doing translating? Is the end product substantially
>>>> better using one tool than the other?
>>>
>>> Right, Zanata and Pootle are the two leading options. The translations
>>> team seemed to prefer Zanata so we said we'd work to get a demo going
>>> for them so they could try it themselves, just like we have for
>>> Pootle.
>>>
>>> On our end maintainability is the major consideration, since we don't
>>> want to deploy a solution that will be disruptive to translators
>>> (during upgrades, etc) or insecure.
>>>
>> Can we get an item on next week's infra agenda and have some of the
>> folks doing the translation work attend and offer their opinion?
>>
>> It seems we might be at a point of weighing costs of setup and
>> maintenance time versus advantages of use.
>>
>> Thanks,
>> 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] [openstack-dev] [neutron][third-party-ci] Midokura CI Bot results migration

[Anita Kuno]

On 07/03/2014 07:54 AM, Lucas Eznarriaga wrote:
> Hi,
> 
> Due to maintenance reasons, our CI results server has been moved to a new
> machine.
> As we didn't use a dns name before, previous links posted on the
> review.openstack.org will appear as broken but they're still available
> changing the previous hardcoded ip: 119.15.112.63 by the new dns name:
> 3rdparty-logs.midokura.com
> 
> Sorry for the inconvenience,
> Best regards,
> 
> Lucas
> Midokura
> 
> 
> 
> ___
> OpenStack-dev mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
Hello Lucas:

Thank you for being proactive and informing everyone of the backwards
incompatible url.

Given that you had previously hardcoded the ip address into your urls,
are you willing to offer a patch to
http://ci.openstack.org/third_party.html found here:
http://git.openstack.org/cgit/openstack-infra/config/tree/doc/source/third_party.rst
to prevent other third party ci systems from using backward incompatible
urls in future.

Let me know your thoughts. If you are willing but don't know how I can
help you. If you aren't willing, I can do it myself, but I would like to
start helping others offer patches to third party documentation.

Thanks Lucas,
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] [neutron][third-party-ci] Midokura CI Bot results migration

[Anita Kuno]

On 07/03/2014 09:37 AM, Lucas Eznarriaga wrote:
> Hi Anita,
> 
> For sure it will help including this info on the third party documentation
> and I am willing to contribute :)
> I have seen that other third party systems also use a hardcoded IP which
> may lead to the same issue in the future.
Yes, it probably will. Learning by doing requires cleanup after the fact.

> I would patch this sentence:
> Include a public link to all test artifacts to make debugging failed tests
> easier. This should include:
> into
> Include a public link (using a dns name over a hardcoded ip is recommended) to
> all test artifacts to make debugging failed tests easier. This should
> include:
> 
> Does it sound good to you?
> 
> Best regards,
> Lucas
> 
Thanks Lucas, I am grateful for your willingness to help.

Your suggestion sounds like a great start. Let's get it up in a patch
and hear thoughts from others.

Now in Monday's third party meeting, when talking about our
recommendations for logs, Kurt Taylor said he would offer a patch with
our recommendations (as opposed to requirements) but that patch isn't
offered yet, so go ahead with your direction, since once Kurt's patch is
up changing the location of your edit (if a different line is better) is
an easy to do. But let's keep track of what we said (using a patch) so
we don't forget.

Ping me in -infra if you need any help.

Thanks Lucas,
Anita.
> 
> 
> On Thu, Jul 3, 2014 at 2:39 PM, Anita Kuno  wrote:
> 
>> On 07/03/2014 07:54 AM, Lucas Eznarriaga wrote:
>>> Hi,
>>>
>>> Due to maintenance reasons, our CI results server has been moved to a new
>>> machine.
>>> As we didn't use a dns name before, previous links posted on the
>>> review.openstack.org will appear as broken but they're still available
>>> changing the previous hardcoded ip: 119.15.112.63 by the new dns name:
>>> 3rdparty-logs.midokura.com
>>>
>>> Sorry for the inconvenience,
>>> Best regards,
>>>
>>> Lucas
>>> Midokura
>>>
>>>
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> openstack-...@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> Hello Lucas:
>>
>> Thank you for being proactive and informing everyone of the backwards
>> incompatible url.
>>
>> Given that you had previously hardcoded the ip address into your urls,
>> are you willing to offer a patch to
>> http://ci.openstack.org/third_party.html found here:
>>
>> http://git.openstack.org/cgit/openstack-infra/config/tree/doc/source/third_party.rst
>> to prevent other third party ci systems from using backward incompatible
>> urls in future.
>>
>> Let me know your thoughts. If you are willing but don't know how I can
>> help you. If you aren't willing, I can do it myself, but I would like to
>> start helping others offer patches to third party documentation.
>>
>> Thanks Lucas,
>> Anita.
>>
>> ___
>> OpenStack-dev mailing list
>> openstack-...@lists.openstack.org
>> 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] hyperv-ci logs force me to download

[Anita Kuno]

On 07/03/2014 02:47 PM, Octavian Ciuhandu (Cloudbase Solutions SRL) wrote:
> Hi Anita,
> 
> We are currently fixing all links to open in the browser. Will get back very 
> soon with the confirmation that all has been implemented. We will also make 
> sure that even the rootwrap.d folders that are currently as tar.gz will be 
> browsable directly.
> 
> Thank you,
> 
> Octavian.
Thank you Octavian, I appreciate your understanding regarding the logs.

Please keep me informed of your progress.

My thanks,
Anita.
> 
> On 3 Jul 2014, at 04:18, Anita Kuno  wrote:
> 
>> Hello:
>>
>> Your ci logs linked in your comment on this patch set include files that
>> force me to download.
>> https://review.openstack.org/#/c/61183/
>>
>> All log files must be browsable. Please address your log files.
>>
>> Thank you,
>> Anita.
>>
>> reference: https://review.openstack.org/#/c/101227/
> 


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

Re: [OpenStack-Infra] gerrit: error: unpack failed: error Missing unknown

[Anita Kuno]

On 07/05/2014 08:57 AM, Vinay Mahuli wrote:
> Hi,
> 
> I had the a project contrail-controller earlier which was accidentally
> deleted.
> 
> After that, I tried running "manage-projects -dv" which is giving below
> error while adding back the deleted project.
> 
> Now, I don't have anything in /home/gerrit2/review_site/git/Juniper/
> contrail-controller.git
> 
> Can you please give me some inputs to resolve this? The issue is the
> commit 4619766bb3cb0b7a43a6ae25be4f5fcf75e874e3 is not found either in
> "open", "merged" nor "abandoned" states.
> 
> I cannot upgrade the version of gerrit since we have custom changes.
> 
> Manage-projects log:
> 
> ---
> 
> remote: Resolving deltas: 100% (18789/18789)
> 
> error: unpack failed: error Missing unknown
> 4619766bb3cb0b7a43a6ae25be4f5fcf75e874e3
> 
> fatal: Unpack error, check server log
> 
> To ssh://localhost:29418/Juniper/contrail-controller
> 
>  ! [remote rejected] refs/copy/heads/R1.04 -> R1.04 (n/a (unpacker error))
> 
>  ! [remote rejected] refs/copy/heads/R1.05 -> R1.05 (n/a (unpacker error))
> 
>  ! [remote rejected] refs/copy/heads/R1.06 -> R1.06 (n/a (unpacker error))
> 
>  ! [remote rejected] refs/copy/heads/R1.06c1 -> R1.06c1 (n/a (unpacker
> error))
> 
>  ! [remote rejected] refs/copy/heads/config-devel -> config-devel (n/a
> (unpacker error))
> 
>  ! [remote rejected] refs/copy/heads/fix -> fix (n/a (unpacker error))
> 
>  ! [remote rejected] refs/copy/heads/master -> master (n/a (unpacker error))
> 
>  ! [remote rejected] refs/copy/heads/meghb_stoi -> meghb_stoi (n/a
> (unpacker error))
> 
> error: failed to push some refs to '
> ssh://localhost:29418/Juniper/contrail-controller'
> 
> INFO:manage_projects:Return code: 1
> 
> remote: Resolving deltas: 100% (9774/9774)
> 
> error: unpack failed: error Missing unknown
> 4619766bb3cb0b7a43a6ae25be4f5fcf75e874e3
> 
> 
> 
> Gerrit logs:
> 
> ---
> 
> [2014-07-04 07:18:09,081] ERROR com.google.gerrit.sshd.BaseCommand :
> Internal server error (user opencontrail-project-creator account 2) during
> git-receive-pack '/Juniper/contrail-controller'
> 
> com.google.gerrit.sshd.BaseCommand$Failure: fatal: Unpack error, check
> server log
> 
> at com.google.gerrit.sshd.commands.Receive.runImpl(Receive.java:146)
> 
> at
> com.google.gerrit.sshd.AbstractGitCommand.service(AbstractGitCommand.java:103)
> 
> at
> com.google.gerrit.sshd.AbstractGitCommand.access$000(AbstractGitCommand.java:34)
> 
> at
> com.google.gerrit.sshd.AbstractGitCommand$1.run(AbstractGitCommand.java:69)
> 
> at com.google.gerrit.sshd.BaseCommand$TaskThunk.run(BaseCommand.java:403)
> 
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> 
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> 
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> 
> at com.google.gerrit.server.git.WorkQueue$Task.run(WorkQueue.java:333)
> 
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 
> at java.lang.Thread.run(Thread.java:744)
> 
> Caused by: java.io.IOException: Unpack error on project
> "Juniper/contrail-controller":
> 
>   AdvertiseRefsHook:
> com.google.gerrit.server.git.ReceiveCommitsAdvertiseRefsHook@1b4d01d7class
> com.google.gerrit.server.git.ReceiveCommitsAdvertiseRefsHook
> 
> 
> at com.google.gerrit.sshd.commands.Receive.runImpl(Receive.java:145)
> 
> ... 12 more
> 
> Caused by: org.eclipse.jgit.errors.UnpackException: Exception while parsing
> pack stream
> 
> at org.eclipse.jgit.transport.ReceivePack.service(ReceivePack.java:877)
> 
> at org.eclipse.jgit.transport.ReceivePack.receive(ReceivePack.java:768)
> 
> at com.google.gerrit.sshd.commands.Receive.runImpl(Receive.java:95)
> 
> ... 12 more
> 
> Caused by: org.eclipse.jgit.errors.MissingObjectException: Missing unknown
> 4619766bb3cb0b7a43a6ae25be4f5fcf75e874e3
> 
> at org.eclipse.jgit.storage.file.WindowCursor.open(WindowCursor.java:125)
> 
> at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:228)
> 
> at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:811)
> 
> at
> org.eclipse.jgit.transport.ReceivePack.checkConnectivity(ReceivePack.java:1058)
> 
> at org.eclipse.jgit.transport.ReceivePack.service(ReceivePack.java:840)
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Vinay:

I'm a bit foggy here, perhaps you can expand on some details?

Are you saying that you had a project on OpenStack's Gerrit
(review.openstack.org) called contrail-controller which has been deleted?

We don't delete any projects on OpenStack's Gerrit
(review.openstack.org). I

Re: [OpenStack-Infra] develop on upstream or stackforge

[Anita Kuno]

On 07/15/2014 11:47 AM, 金子　雄大 wrote:
> Hi Josh,
> 
> Thank you for your help!
> I'll do as you say.
> Should I delete the upstream part of projects.yaml?
> 
> Regards,
> takehiro
No, deleting the upstream url in projects.yaml is not required.

The system acts on that line during project creation only, subsequent
reads of that file do not result in any further activity on the upstream
url.

Thanks takehiro,
Anita.
> 
> (2014/07/15 18:00), Joshua Hesketh wrote:
>> Hi takehiro,
>>
>> The upstream part of projects.yaml is simply for the initial import. After 
>> that it is expected that stackforge (either from git.openstack.org or 
>> through the stackforge org on github) is the canonical repository. ie, your 
>> other upstream is no longer 'upstream' so to speak.
>>
>> My recommendation would be to remove your old upstream and just use the 
>> stackforge one. The reason being is that you want all new patches to go 
>> through gerrit anyway so there is no real use of another upstream. You could 
>> create a fork or mirror on github elsewhere but you do already have the copy 
>> in the stackforge org.
>>
>> I hope that helps!
>>
>> Cheers,
>> Josh
>> 
>> From: 金子　雄大 [takehiro.kan...@ctc-g.co.jp]
>> Sent: Tuesday, July 15, 2014 11:59 AM
>> To: openstack-infra@lists.openstack.org
>> Subject: [OpenStack-Infra] develop on upstream or stackforge
>>
>> Hi all.
>>
>> I'm working on a stackforge project "rack".
>> We have an upstream repository on github that is different from
>> stackforge one.
>> I pushed my patch to Gerrit and it was merged to our stackforge github,
>> but the change wasn't merged to upstream github.
>> Should I push my patch to upstream github?
>> And the patch is also merged to stackfoge github?
>>
>> Regards,
>> takehiro
>>
>> ___
>> 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] Request help for 3rd party account HP Cinder Ci

[Anita Kuno]

On 07/18/2014 07:14 PM, Asselin, Ramy wrote:
> Hi,
> 
> I'm testing out my 3rd party ci setup. It works fine for sandbox [1], but not 
> for cinder[2].
> 
> Let me know if this is an error on my side or if there's a config issue that 
> needs to be done upstream?
> 
> Here are some of the errors I posted in the IRC channel.
> 
> GitCommandError: 'Error when fetching: fatal: Couldn't find remote ref 
> refs/changes/46/106046/7' returned exit status 2: None
> http://paste.openstack.org/show/86972/
> 2014-07-18 07:21:21,861 ERROR zuul.Gerrit: Cannot get references from 
> https://review.openstack.org/p/openstack/cinder/info/refs?service=git-upload-pack
> 
> 
> The command works when run manually as zuul user [3].
> 
> 
> Thanks,
> Ramy
> 
> P.S. I'm not subscribed to this mailing list. Please reply to: 
> ramy.asse...@hp.com (IRC: asselin), or let me 
> know if I should subscribe.
> 
> [1] https://review.openstack.org/#/c/107503/
> [2] https://review.openstack.org/#/c/74532/
> [3] http://paste.openstack.org/show/87159/
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Ramy:

I don't know the cause of your error, but subscribing to this list would
be a good idea.

Also, adding this to the third party meeting agenda might be an idea. If
you don't get a solution perhaps that is another method to find one, and
if you do find a solution perhaps you can share.

Thanks Ramy,
Anita.

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

Re: [OpenStack-Infra] 3rd Party CI Service Account Request

[Anita Kuno]

On 07/18/2014 04:32 PM, Sean McGinnis wrote:
> Hello,
> 
> I would like to have a service account created for the Dell Storage team. 
> Please let me know if you need any additional information. Thanks!
> 
> Public SSH Key
> ssh-rsa 
> B3NzaC1yc2EDAQABgQDZjZbuehBmIqVDVs5NMZ1tojpU/ShdvrIuQbLltNw/VXUNP04mcEfGUpWL/7jMqnI3ietLA981/EQTSlMRdHSfktqXGz28C5bK8JmYbZ31+fj2teJ6WOGfl74IOJ7Q2l1AolN9l80sDnLIsPqSeoSpiU+uITGQRzrPH2lrbwBx3w==
>  dell-cinder-ci@openstack-cinder-ci
> 
> Requested Username
> dell-cinder-ci
> 
> Display Name
> Dell Cinder CI
> 
> Email
> openstack-cin...@dell.com
> 
> Additional Contact Info
> Primary:
> Sean McGinnis
> sean_mcgin...@dell.com
> IRC: smcginnis
> Alternate:
> Tom Swanson
> tom_swan...@dell.com
> IRC: Swanson
> 
> 
> Sean McGinnis
> Sr. Principal Software Engineer
> Dell | Storage
> office +1 952 294 3355
> sean_mcgin...@dell.com
> Dell Storage, 7625 Smetana Ln, Eden Prairie, MN 55344
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Sean:

Currently we have a patch up around our naming policy and I haven't yet
offered a recent patch to reflect our newly achieved consensus from the
QA/Infra meetup in Germany of our CI naming format.

If you can tell us what product/driver/application(s) are you going to
be running patches against for verification as per the current status of
this patch: https://review.openstack.org/#/c/101013/8 infra will select
a suitable name for your account.

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] [openstack-dev][neutron][third-party] Updated Gerrit plugin for Third party CIs

[Anita Kuno]

On 07/18/2014 06:08 AM, Sukhdev Kapur wrote:
> The upgrade of Gerrit in the upstream had impacted the gerrit triggers for
> "recheck no bug" and "recheck bug " in the downstream CI's that use
> Gerrit plugin with Jenkins.
> 
> We have fixed the issue and have uploaded patch for the fix.
> The following wiki has updated links to the correct patch, along with
> updated steps to use Gerrit plugin along with Jenkins.
> 
> https://wiki.openstack.org/wiki/Arista-third-party-testing
> 
> Hope this helps.
> 
> Any questions/issues, please let us know.
> 
> regards..
> Sukhdev
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Sukhdev:

Thanks for working so persistently with SlickNik to get this situation
solved. This is a great example of teamwork, thank you.

I see that the wikipage still links to a google document. I would really
like to see the contents of the google document brought into the wiki
and the link to the document removed.

Please ask at the third-party meeting or ask me if you need help to
bring the information into the wikipage.

Thanks Sukhdev,
Anita.

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

Re: [OpenStack-Infra] 3rd Party CI Service Account Request

[Anita Kuno]

On 07/19/2014 08:32 AM, Anita Kuno wrote:
> On 07/18/2014 04:32 PM, Sean McGinnis wrote:
>> Hello,
>>
>> I would like to have a service account created for the Dell Storage team. 
>> Please let me know if you need any additional information. Thanks!
>>
>> Public SSH Key
>> ssh-rsa 
>> B3NzaC1yc2EDAQABgQDZjZbuehBmIqVDVs5NMZ1tojpU/ShdvrIuQbLltNw/VXUNP04mcEfGUpWL/7jMqnI3ietLA981/EQTSlMRdHSfktqXGz28C5bK8JmYbZ31+fj2teJ6WOGfl74IOJ7Q2l1AolN9l80sDnLIsPqSeoSpiU+uITGQRzrPH2lrbwBx3w==
>>  dell-cinder-ci@openstack-cinder-ci
>>
>> Requested Username
>> dell-cinder-ci
>>
>> Display Name
>> Dell Cinder CI
>>
>> Email
>> openstack-cin...@dell.com<mailto:openstack-cin...@dell.com>
>>
>> Additional Contact Info
>> Primary:
>> Sean McGinnis
>> sean_mcgin...@dell.com<mailto:sean_mcgin...@dell.com>
>> IRC: smcginnis
>> Alternate:
>> Tom Swanson
>> tom_swan...@dell.com<mailto:tom_swan...@dell.com>
>> IRC: Swanson
>>
>>
>> Sean McGinnis
>> Sr. Principal Software Engineer
>> Dell | Storage
>> office +1 952 294 3355
>> sean_mcgin...@dell.com
>> Dell Storage, 7625 Smetana Ln, Eden Prairie, MN 55344
>>
>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> Hi Sean:
> 
> Currently we have a patch up around our naming policy and I haven't yet
> offered a recent patch to reflect our newly achieved consensus from the
> QA/Infra meetup in Germany of our CI naming format.
> 
> If you can tell us what product/driver/application(s) are you going to
> be running patches against for verification as per the current status of
> this patch: https://review.openstack.org/#/c/101013/8 infra will select
> a suitable name for your account.
> 
> Thank you,
> Anita.
> 
Replying again to put this in Sean's inbox.

Thanks Sean,
Anita.

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

Re: [OpenStack-Infra] 3rd Party CI Service Account Request

[Anita Kuno]

On 07/21/2014 10:00 PM, Sean McGinnis wrote:
> I am working with the group setting up for implementing the Dell Storage 
> Center cinder driver. Our work here will initially be focused on just Storage 
> Center, and just cinder, but eventually we may be pulling in ownership of the 
> existing EqualLogic driver and possibly working on other projects than cinder.
> 
> For our internal management of the ownership of different pieces it would 
> work best for us to have something like:
> 
> dell-[openstackproject]-ci
> 
> If it is preferred to not do it by OpenStack projects then we could do 
> something like dell-storage-ci.
> 
> If we need to have it for a specific product, then we would be looking at 
> dell-storagecenter-ci.
> 
> Thanks!
>
Storage Center is the name of a Dell driver?

Thanks Sean,
Anita.

> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Monday, July 21, 2014 2:12 PM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request
> 
> On 07/19/2014 08:32 AM, Anita Kuno wrote:
>> On 07/18/2014 04:32 PM, Sean McGinnis wrote:
>>> Hello,
>>>
>>> I would like to have a service account created for the Dell Storage team. 
>>> Please let me know if you need any additional information. Thanks!
>>>
>>> Public SSH Key
>>> ssh-rsa 
>>> B3NzaC1yc2EDAQABgQDZjZbuehBmIqVDVs5NMZ1tojpU/ShdvrIuQbLltNw/VXUNP04mcEfGUpWL/7jMqnI3ietLA981/EQTSlMRdHSfktqXGz28C5bK8JmYbZ31+fj2teJ6WOGfl74IOJ7Q2l1AolN9l80sDnLIsPqSeoSpiU+uITGQRzrPH2lrbwBx3w==
>>>  dell-cinder-ci@openstack-cinder-ci
>>>
>>> Requested Username
>>> dell-cinder-ci
>>>
>>> Display Name
>>> Dell Cinder CI
>>>
>>> Email
>>> openstack-cin...@dell.com<mailto:openstack-cin...@dell.com>
>>>
>>> Additional Contact Info
>>> Primary:
>>> Sean McGinnis
>>> sean_mcgin...@dell.com<mailto:sean_mcgin...@dell.com>
>>> IRC: smcginnis
>>> Alternate:
>>> Tom Swanson
>>> tom_swan...@dell.com<mailto:tom_swan...@dell.com>
>>> IRC: Swanson
>>>
>>>
>>> Sean McGinnis
>>> Sr. Principal Software Engineer
>>> Dell | Storage
>>> office +1 952 294 3355
>>> sean_mcgin...@dell.com
>>> Dell Storage, 7625 Smetana Ln, Eden Prairie, MN 55344
>>>
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Hi Sean:
>>
>> Currently we have a patch up around our naming policy and I haven't yet
>> offered a recent patch to reflect our newly achieved consensus from the
>> QA/Infra meetup in Germany of our CI naming format.
>>
>> If you can tell us what product/driver/application(s) are you going to
>> be running patches against for verification as per the current status of
>> this patch: https://review.openstack.org/#/c/101013/8 infra will select
>> a suitable name for your account.
>>
>> Thank you,
>> Anita.
>>
> Replying again to put this in Sean's inbox.
> 
> Thanks Sean,
> 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 mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Style Guide for Infra Manual

[Anita Kuno]

Currently infra-manual doesn't have a style guide. We need one.

There was some great work done at the QA/Infra meetup on infra-manual.
Pavel was offering some style markup for the infra-manual, but since we
don't have a style guide yet, it is difficult to get consistency with
the markup.

Let's collect our thoughts about how we would like style to be used in
the infra-manual. We can then create a style-guide file inside the repo
to direct future patches and reviews.

Who has some thoughts on this?

Thanks all,
Anita.

http://git.openstack.org/cgit/openstack-infra/infra-manual/
http://docs.openstack.org/infra/manual/

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

Re: [OpenStack-Infra] 3rd Party CI Service Account Request

[Anita Kuno]

On 07/21/2014 05:03 PM, Sean McGinnis wrote:
> Yes, it is one we are working on right now. So it is not in there yet, but 
> hopefully soon.
> 
> https://blueprints.launchpad.net/cinder/+spec/dell-storage-center-block-storage-driver
>  
> 
Ah, okay. Linking to the blueprint is helpful, I'm grateful to know the
level of detail the blueprint provides.

Thanks Sean,
Anita.



> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Monday, July 21, 2014 3:12 PM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request
> 
> On 07/21/2014 10:00 PM, Sean McGinnis wrote:
>> I am working with the group setting up for implementing the Dell Storage 
>> Center cinder driver. Our work here will initially be focused on just 
>> Storage Center, and just cinder, but eventually we may be pulling in 
>> ownership of the existing EqualLogic driver and possibly working on other 
>> projects than cinder.
>>
>> For our internal management of the ownership of different pieces it would 
>> work best for us to have something like:
>>
>> dell-[openstackproject]-ci
>>
>> If it is preferred to not do it by OpenStack projects then we could do 
>> something like dell-storage-ci.
>>
>> If we need to have it for a specific product, then we would be looking at 
>> dell-storagecenter-ci.
>>
>> Thanks!
>>
> Storage Center is the name of a Dell driver?
> 
> Thanks Sean,
> Anita.
> 
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info] 
>> Sent: Monday, July 21, 2014 2:12 PM
>> To: openstack-infra@lists.openstack.org
>> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request
>>
>> On 07/19/2014 08:32 AM, Anita Kuno wrote:
>>> On 07/18/2014 04:32 PM, Sean McGinnis wrote:
>>>> Hello,
>>>>
>>>> I would like to have a service account created for the Dell Storage team. 
>>>> Please let me know if you need any additional information. Thanks!
>>>>
>>>> Public SSH Key
>>>> ssh-rsa 
>>>> B3NzaC1yc2EDAQABgQDZjZbuehBmIqVDVs5NMZ1tojpU/ShdvrIuQbLltNw/VXUNP04mcEfGUpWL/7jMqnI3ietLA981/EQTSlMRdHSfktqXGz28C5bK8JmYbZ31+fj2teJ6WOGfl74IOJ7Q2l1AolN9l80sDnLIsPqSeoSpiU+uITGQRzrPH2lrbwBx3w==
>>>>  dell-cinder-ci@openstack-cinder-ci
>>>>
>>>> Requested Username
>>>> dell-cinder-ci
>>>>
>>>> Display Name
>>>> Dell Cinder CI
>>>>
>>>> Email
>>>> openstack-cin...@dell.com<mailto:openstack-cin...@dell.com>
>>>>
>>>> Additional Contact Info
>>>> Primary:
>>>> Sean McGinnis
>>>> sean_mcgin...@dell.com<mailto:sean_mcgin...@dell.com>
>>>> IRC: smcginnis
>>>> Alternate:
>>>> Tom Swanson
>>>> tom_swan...@dell.com<mailto:tom_swan...@dell.com>
>>>> IRC: Swanson
>>>>
>>>>
>>>> Sean McGinnis
>>>> Sr. Principal Software Engineer
>>>> Dell | Storage
>>>> office +1 952 294 3355
>>>> sean_mcgin...@dell.com
>>>> Dell Storage, 7625 Smetana Ln, Eden Prairie, MN 55344
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> OpenStack-Infra mailing list
>>>> OpenStack-Infra@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>
>>> Hi Sean:
>>>
>>> Currently we have a patch up around our naming policy and I haven't yet
>>> offered a recent patch to reflect our newly achieved consensus from the
>>> QA/Infra meetup in Germany of our CI naming format.
>>>
>>> If you can tell us what product/driver/application(s) are you going to
>>> be running patches against for verification as per the current status of
>>> this patch: https://review.openstack.org/#/c/101013/8 infra will select
>>> a suitable name for your account.
>>>
>>> Thank you,
>>> Anita.
>>>
>> Replying again to put this in Sean's inbox.
>>
>> Thanks Sean,
>> 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 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] 3rd Party CI Service Account Request

[Anita Kuno]

On 07/23/2014 12:46 PM, Sean McGinnis wrote:
> Sorry, didn't mean to seem impatient. Just want to make sure I didn't miss 
> anything that would cause the process to be held up on me. 
> 
> Thanks for your help with this!
> 
Yep, no problem.

> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Wednesday, July 23, 2014 11:43 AM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request
> 
> On 07/22/2014 03:17 PM, Sean McGinnis wrote:
>> Hello Anita,
>>
>> Any luck on getting a service account created? Or do you need any more 
>> information to help on the naming? Just let me know.
>>
>> Thanks,
>> Sean
>>
> Well Gerrit changes to allow me to have permissions to create and edit
> accounts just got merged upstream, so hopefully I should be able to help
> you soon.
> 
> Be patient, Sergey might get to your account request first.
> 
> Thanks Sean,
> Anita.
> 


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

Re: [OpenStack-Infra] 3rd Party CI Service Account Request

[Anita Kuno]

On 07/22/2014 03:17 PM, Sean McGinnis wrote:
> Hello Anita,
> 
> Any luck on getting a service account created? Or do you need any more 
> information to help on the naming? Just let me know.
> 
> Thanks,
> Sean
> 
Well Gerrit changes to allow me to have permissions to create and edit
accounts just got merged upstream, so hopefully I should be able to help
you soon.

Be patient, Sergey might get to your account request first.

Thanks Sean,
Anita.

> -Original Message-
> From: Sean McGinnis 
> Sent: Monday, July 21, 2014 4:03 PM
> To: openstack-infra@lists.openstack.org
> Subject: RE: [OpenStack-Infra] 3rd Party CI Service Account Request
> 
> Yes, it is one we are working on right now. So it is not in there yet, but 
> hopefully soon.
> 
> https://blueprints.launchpad.net/cinder/+spec/dell-storage-center-block-storage-driver
>  
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Monday, July 21, 2014 3:12 PM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request
> 
> On 07/21/2014 10:00 PM, Sean McGinnis wrote:
>> I am working with the group setting up for implementing the Dell Storage 
>> Center cinder driver. Our work here will initially be focused on just 
>> Storage Center, and just cinder, but eventually we may be pulling in 
>> ownership of the existing EqualLogic driver and possibly working on other 
>> projects than cinder.
>>
>> For our internal management of the ownership of different pieces it would 
>> work best for us to have something like:
>>
>> dell-[openstackproject]-ci
>>
>> If it is preferred to not do it by OpenStack projects then we could do 
>> something like dell-storage-ci.
>>
>> If we need to have it for a specific product, then we would be looking at 
>> dell-storagecenter-ci.
>>
>> Thanks!
>>
> Storage Center is the name of a Dell driver?
> 
> Thanks Sean,
> Anita.
> 
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info] 
>> Sent: Monday, July 21, 2014 2:12 PM
>> To: openstack-infra@lists.openstack.org
>> Subject: Re: [OpenStack-Infra] 3rd Party CI Service Account Request
>>
>> On 07/19/2014 08:32 AM, Anita Kuno wrote:
>>> On 07/18/2014 04:32 PM, Sean McGinnis wrote:
>>>> Hello,
>>>>
>>>> I would like to have a service account created for the Dell Storage team. 
>>>> Please let me know if you need any additional information. Thanks!
>>>>
>>>> Public SSH Key
>>>> ssh-rsa 
>>>> B3NzaC1yc2EDAQABgQDZjZbuehBmIqVDVs5NMZ1tojpU/ShdvrIuQbLltNw/VXUNP04mcEfGUpWL/7jMqnI3ietLA981/EQTSlMRdHSfktqXGz28C5bK8JmYbZ31+fj2teJ6WOGfl74IOJ7Q2l1AolN9l80sDnLIsPqSeoSpiU+uITGQRzrPH2lrbwBx3w==
>>>>  dell-cinder-ci@openstack-cinder-ci
>>>>
>>>> Requested Username
>>>> dell-cinder-ci
>>>>
>>>> Display Name
>>>> Dell Cinder CI
>>>>
>>>> Email
>>>> openstack-cin...@dell.com<mailto:openstack-cin...@dell.com>
>>>>
>>>> Additional Contact Info
>>>> Primary:
>>>> Sean McGinnis
>>>> sean_mcgin...@dell.com<mailto:sean_mcgin...@dell.com>
>>>> IRC: smcginnis
>>>> Alternate:
>>>> Tom Swanson
>>>> tom_swan...@dell.com<mailto:tom_swan...@dell.com>
>>>> IRC: Swanson
>>>>
>>>>
>>>> Sean McGinnis
>>>> Sr. Principal Software Engineer
>>>> Dell | Storage
>>>> office +1 952 294 3355
>>>> sean_mcgin...@dell.com
>>>> Dell Storage, 7625 Smetana Ln, Eden Prairie, MN 55344
>>>>
>>>>
>>>>
>>>>
>>>> ___
>>>> OpenStack-Infra mailing list
>>>> OpenStack-Infra@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>
>>> Hi Sean:
>>>
>>> Currently we have a patch up around our naming policy and I haven't yet
>>> offered a recent patch to reflect our newly achieved consensus from the
>>> QA/Infra meetup in Germany of our CI naming format.
>>>
>>> If you can tell us what product/driver/application(s) are you going to
>>> be running patches against for verification as per the current status of
>>> this patch: https://review.openstack.org/#/c/101013/8 infra will select
>>> a suitable 

Re: [OpenStack-Infra] Third Party CI System account

[Anita Kuno]

On 07/22/2014 05:15 PM, Wilfredo Ronsini wrote:
> I work in the Flextronics Institute of Technology and I am in the process of 
> setting an OpenStack CI server.
> 
> Please, create a Gerrit user account.
> 
> Preferred username: wronsini
> 
> Best regards,
> Wilfredo Raphael Ronsini Junior
> email: wilfredo...@fit-tecnologia.org.br
> 
> Legal Disclaimer:
> The information contained in this message may be privileged and confidential. 
> It is intended to be read only by the individual or entity to whom it is 
> addressed or by their designee. If the reader of this message is not the 
> intended recipient, you are on notice that any distribution of this message, 
> in any form, is strictly prohibited. If you have received this message in 
> error, please immediately notify the sender and delete or destroy any copy of 
> this message!
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Wilfredo:

The need for a third party ci account from gerrit comes into play if you
are looking to comment on patches with some kind of verification.

What do you plan on verifying?

For instance businesses often want to verify their proprietary code or
hardware will work with each evaluated patch. What might you be verifying?

If you aren't going to be reporting back any verification status, you
can hook into gerrit events with a normal user account using:
ssh -p 29418 @review.openstack.org gerrit stream-events

and you can have your system trigger off of gerrit events and you don't
need to report anything back to the patch you are using as a trigger.

Thanks Wilfredo,
Anita.

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

Re: [OpenStack-Infra] Cloudwatt Spamming: Fwd: Jenkins build is back to normal : iaas-cw_console_master-test #2

[Anita Kuno]

On 07/25/2014 07:13 AM, Sean Dague wrote:
> Cloudwatt seems to have some jenkins environment up and is spamming a
> ton of people with Jenkins messages.
> 
> There is no contact info that looks real here, so I don't know how to
> direct connect them. Can anyone in infra / 3rd party testing reach out
> to them?
> 
>   -Sean
> 
> 
>  Forwarded Message 
> Subject: Jenkins build is back to normal : iaas-cw_console_master-test #2
> Date: Fri, 25 Jul 2014 10:51:58 + (UTC)
> From: r...@i-cisics-.adm.int0.aub.cloudwatt.net
> To: yves-gwenael.bour...@cloudwatt.com, cedric.sou...@cloudwatt.com,
> bere...@b1-systems.de, jpom...@linux.vnet.ibm.com, amitp...@gmail.com,
> crobe...@redhat.com, ericpeter...@hp.com, tsuf...@mirantis.com,
> tqt...@us.ibm.com, lbezd...@redhat.com, mru...@redhat.com,
> pbela...@redhat.com, m...@mattfischer.com, sdrapisa...@gmail.com,
> lawrancej...@gmail.com, jing.liuq...@99cloud.net, tianli...@awcloud.com,
> francois.magi...@objectif-libre.com, julie.gra...@hp.com,
> niu.zgli...@gmail.com, robert.miziel...@epitech.eu, da...@dcaudill.com,
> c...@us.ibm.com, ogaz...@gmail.com, mich...@ebaysf.com,
> openstack-infra@lists.openstack.org, ikolodyaz...@mirantis.com,
> ramis...@redhat.com, pawel.skow...@intel.com, kanagaraj.manic...@hp.com,
> tnova...@redhat.com, and...@tesora.com, veronica.a.mu...@intel.com,
> jpic...@redhat.com, jebl...@openstack.org, david.l...@hp.com,
> kevin.stev...@rackspace.com, richard.haga...@hp.com,
> akriv...@redhat.com, juan.m.o...@intel.com, alex.gay...@gmail.com,
> george.peristera...@enovance.com, gary.w.sm...@hp.com,
> jun11matayo...@gmail.com, santiago.b.baldas...@intel.com,
> liyingjun1...@gmail.com, rev...@openstack.org, tangmeiya...@gmail.com,
> li...@ryanpetrello.com, davide.gue...@hp.com,
> mail.ashishchan...@gmail.com, stpie...@metacloud.com, s...@dague.net,
> absub...@cisco.com, gloria...@hp.com, slick...@gmail.com,
> j...@cs.stanford.edu, r1chardj0...@gmail.com, clay...@oneill.net,
> leandro.i.costant...@intel.com, yongli...@intel.com,
> mot...@da.jp.nec.com, t.v.ovtchinnik...@gmail.com, rob.raym...@hp.com,
> n...@metacloud.com, lin-hua.ch...@hp.com, rodrig...@lsd.ufcg.edu.br,
> david.laps...@metacloud.com, lsm...@redhat.com,
> andres.buras...@intel.com, ala.rezmer...@cloudwatt.com,
> maria.nita...@gmail.com, ihrac...@redhat.com, dragon...@163.com,
> openst...@sheep.art.pl, jom...@redhat.com,
> guillermo.d.cabr...@intel.com, drf...@us.ibm.com,
> dimitri.mazma...@ericsson.com, brianna.pou...@jhuapl.edu,
> robert.miziel...@cloudwatt.com, jamielen...@redhat.com,
> jroov...@cisco.com, maxime.vid...@enovance.com, matt.w...@hp.com,
> masco.kaliyamoor...@enovance.com, na...@ntti3.com, kisp...@gmail.com,
> dk...@redhat.com, emag...@gmail.com
> 
> See
> 
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Replying to put this in the next poster's email inbox.

Anita.

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

Re: [OpenStack-Infra] Cloudwatt Spamming: Fwd: Jenkins build is back to normal : iaas-cw_console_master-test #2

[Anita Kuno]

On 07/25/2014 11:14 AM, Yves-Gwenaël Bourhis wrote:
> Le 25/07/2014 16:07, Anita Kuno a écrit :
>> On 07/25/2014 07:13 AM, Sean Dague wrote:
>>> Cloudwatt seems to have some jenkins environment up and is spamming a
>>> ton of people with Jenkins messages.
>>>
>>> There is no contact info that looks real here, so I don't know how to
>>> direct connect them. Can anyone in infra / 3rd party testing reach out
>>> to them?
>>>
>>> -Sean
> [...]
>> Replying to put this in the next poster's email inbox.
>>
>> Anita.
> 
> Hi all, sorry for the Jenkins Spam, it was my fault.
> 
> So to prevent the same thing to happen to others who would be setting up
> a new Jenkins Job, I will explain how to reproduce my mistake so that
> others "do not" reproduce it :-)
> 
> In Cloudwatt, we have our own fork of horizon (in fact it's horizon with
> our own CSS theme, some django-cms panel added on the side, plus the
> patches me and my team submitted in horizon which are not yet merged
> (because they are still in review)), and we continuously sync with upstream.
> 
> I added a Jenkins Job to automate unittests to have our own CI.
> I configured the Job to send a notification e-mail to individuals who
> have committed changes which lead to a broken build, so that people of
> my team who introduce a bug get notified.
> 
> Now what happened: Our "master" branch was not already synced with
> horizon's upstream version, and if you pull a horizon version which is
> more than 5 days old you'll notice that dependencies pulled by
> "(test-)requirements.txt" will make unittests fail (horizon has had
> recent updates to fix this).
> 
> When you create a new Job in Jenkins, it seems like all the commits are
> considered by Jenkins as new commits for this  particular job, and this
> means that our Jenkins thought "all" the commits in horizon history
> introduced a failing test... and Jenkins has sent an email... to all
> horizon contributers in history!
> 
> As soon as the branch I was testing the upstream merge was committed in
> our master branch (to fix tests), another mail was sent... to the whole
> community...
> This happened because Jenkins saw all commits...(Mummy, I'm famous now,
> I accidentally spamed the whole OpenStack community...)
> 
> To fix this, I removed the Jenkins option to send a mail to all people
> who committed changes, but only to my team.
> 
> Also, if you test a merge in a branch, then commit this merge in master
> with '-ff-only' (to prevent another merge commit), well then... Jenkins
> sees ALL the commits as new... not only the first merge commit.
> 
> 
> So please all accept my apologies for this... I really feel stupid about
> this...
> 
Hi Yves:

We all make mistakes. Thank you for taking the time to detail your
situation, especially the part that resulted in the spam as well as what
you did to ensure you didn't continue to spam.

The decision that sets people apart in open source communities is their
willingness to take responsibility for their actions, including their
mistakes. It is tough to do, especially in public but I'll tell you, you
sure get a lot of respect for doing so.

You have my respect.

Thanks Yves,
Anita.

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

Re: [OpenStack-Infra] Requesting a Service Account for Third Party CI System

[Anita Kuno]

On 07/25/2014 08:36 PM, Rick Chen wrote:
> Hi Sir:
> 
> Please help us to create service account, Thanks.
> 
>  
> 
> 1.  Attached file.
> 
> 2.  A preferred username: prophetstor
> 
> 3.  A human-readable: Prophetstor-CI
> 
> 4.  Email address: prophetstor...@prophetstor.com
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Rick:

We are changing our documentation around requesting a service account,
the patch hasn't been merged yet:
https://review.openstack.org/#/c/101013/11/doc/source/third_party.rst

So Prophetstor is the name of your company, what details can you give me
about what you intend to be verifying with your third party ci account?
It might be a piece of software or hardware or something else.
The more details you can offer, the better. If you have a blueprint or
spec for it, linking to the blueprint or spec in your reply is really
helpful.

Thanks Rick,
Anita.

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

Re: [OpenStack-Infra] Requesting a Service Account for Third Party CI System

[Anita Kuno]

On 07/27/2014 01:07 PM, Rick Chen wrote:
> Hi Anita:
>   Prophetstor is my company name. I plan to verify our cinder volume
> driver.
>   BP:
> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver
>   Please help us to create service account. Thanks.
Great, thanks Rick. Linking the blueprint really helps.

We are working on getting me permissions to create accounts, which is
soon but hasn't happened yet. In the meantime one of my infra colleagues
may get the account created before I do.

Thanks,
Anita.
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Saturday, July 26, 2014 9:08 PM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third Party
> CI System
> 
> On 07/25/2014 08:36 PM, Rick Chen wrote:
>> Hi Sir:
>>
>> Please help us to create service account, Thanks.
>>
>>  
>>
>> 1.  Attached file.
>>
>> 2.  A preferred username: prophetstor
>>
>> 3.  A human-readable: Prophetstor-CI
>>
>> 4.  Email address: prophetstor...@prophetstor.com
>>
>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> Hi Rick:
> 
> We are changing our documentation around requesting a service account, the
> patch hasn't been merged yet:
> https://review.openstack.org/#/c/101013/11/doc/source/third_party.rst
> 
> So Prophetstor is the name of your company, what details can you give me
> about what you intend to be verifying with your third party ci account?
> It might be a piece of software or hardware or something else.
> The more details you can offer, the better. If you have a blueprint or spec
> for it, linking to the blueprint or spec in your reply is really helpful.
> 
> Thanks Rick,
> 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] Style Guide for Infra Manual

[Anita Kuno]

On 07/22/2014 11:08 AM, Andreas Jaeger wrote:
> On 07/22/2014 04:39 PM, Pavel Sedlak wrote:
>> Hi.
>>
>> While the `general conventions`_ seems to cover lot of things,
>> I'm not really convinced it can do work well for our case.
>>
>> First part, writing style, probably could (and should?) be followed here.
>>
>> But rest is not directly applicable, as we are not using DocBook but rst.
> 
> That's why I said, I would be fine splitting it up in two pages - one
> page that handles content we both can use, one that is specific for DocBook.
> 
>> Though of course when there are matching options (like ".. Note::" for
>> marking side notes) I'm for using them as much as possible/feasible
>> (to later simplify for example styling per mass).
>>
>> What I've used in my proposal is not just meta-information markers
>> (code citation, command, program name, ...) but also emphasize most
>> important part of the paragraph/section (in the sense of the information
>> we are trying to transfer to user/reader).
>>
>> For example, see how the final output of my `proposal patch`_ looks
>> like, when `rendered as html`_.
>>
>>
>> I didn't had much time to write down my style-guide proposal yet,
>> but at least I can draft my idea (what i +- followed in the patches):
>>
>> - exact name/quotation of some element in italics
> 
> Coming from a different background, I would say use "code" for these and
> "code" gets then rendered in a special font...
> 
>>   as it differentiates it from surrounding text,
>>   but does not steals focus of the reader (too much)
>>
>>   > look for *Review* button, click *Submit*
>>
>> - core point(s) of transferred idea in bold font
>>   as that should make strong memory-bound to the described topic,
>>   as also allow quick scanning through the text
>>   (try it on those two sections of the proposal change `rendered as html`_
>>read just the section headline a only(!) the text in bold font)
>>   For this there could be suggested general limit, as "please try to
>>   use ~2 highlights per paragraph at most".
> 
> That's something I would not use.
> 
> But I see we're discussing different levels here. Style for me is much
> more than marking content, it includes whom to address ("you can do..."
> vs "we do" ...), spelling, usage of words,...
> 
>>   e.g. in section about contributing to infra-manuals:
>>   > when doing changes you should **follow style guide** and
>>   > submit all your modifications to **gerrit** for **review**
>>
>>
>> I totally agree that this can be subjective and/or sensitive topic.
> 
> It is - but that's why it's important to have one guideline. In the
> documentation team we discuss those and listen to the professional
> editors that are part of our team,
> 
> 
>> But on contrary having long documents structured just by headlines/code 
>> blocks
>> to something like uniform grey paper boxes, does not make me feel
>> like it was written by/for humans. Of course having text in chaotic 'grid'
>> with rainbow-like look is probably worse.
> 
> The sentences itself need to read fine as well ;)
> 
> Andreas
> 
>>
>> .. _general conventions: 
>> https://wiki.openstack.org/wiki/Documentation/Conventions
>> .. _proposal patch: https://review.openstack.org/#/c/107360
>> .. _rendered as html: 
>> http://docs-draft.openstack.org/60/107360/3/check/gate-infra-manual-docs/db428f9/doc/build/html/developers.html#code-review
>>
>> - Original Message -
>>> From: "Andreas Jaeger" 
>>> To: "Anita Kuno" , 
>>> openstack-infra@lists.openstack.org, "Anne Gentle" 
>>> Sent: Tuesday, July 22, 2014 8:29:13 AM
>>> Subject: Re: [OpenStack-Infra] Style Guide for Infra Manual
>>>
>>> On 07/21/2014 10:30 PM, Anita Kuno wrote:
>>>> Currently infra-manual doesn't have a style guide. We need one.
>>>>
>>>> There was some great work done at the QA/Infra meetup on infra-manual.
>>>> Pavel was offering some style markup for the infra-manual, but since we
>>>> don't have a style guide yet, it is difficult to get consistency with
>>>> the markup.
>>>>
>>>> Let's collect our thoughts about how we would like style to be used in
>>>> the infra-manual. We can then create a style-guide file inside the repo
>>>> to direct future patches and reviews.
&g

Re: [OpenStack-Infra] Requesting a Service Account for Third Party CI System

[Anita Kuno]

On 07/31/2014 11:24 AM, Rick Chen wrote:
> HI All:
>   I saw the third-pard CI members still increased, but our account is
> not accepted. Can you tell me why? Or how to solve this problem? 
Sure, one of the infra members with permissions to create the account
hasn't had the time to do it yet.

You are welcome to join the #openstack-infra irc channel or follow along
in the logs: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/

Thanks Rick,
Anita.
> 
>  1.  Attached file.
>  2.  A preferred username: prophetstor
>  3.  A human-readable: ProphetStor-CI
>  4.  Email address: prophetstor...@prophetstor.com
>  5.  For cinder volume driver certificate. BP:
> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver
> 
>>  Please help us to create service account. Thanks.
> -Original Message-
> From: Rick Chen [mailto:rick.c...@prophetstor.com] 
> Sent: Monday, July 28, 2014 10:41 PM
> To: 'Anita Kuno'; 'openstack-infra@lists.openstack.org'
> Cc: 'steve tan'; 'Albert Lin'
> Subject: RE: [OpenStack-Infra] Requesting a Service Account for Third Party
> CI System
> 
> HI Anita:
>   Does our service account ready?
>   I need change below information, please help me to correct? Or tell
> me how to change it?
>>> 3.  A human-readable: Prophetstor-CI --> ProphetStor-CI
> 
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: Monday, July 28, 2014 3:43 AM
> To: Rick Chen; openstack-infra@lists.openstack.org
> Cc: 'steve tan'; Albert Lin
> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third Party
> CI System
> 
> On 07/27/2014 01:07 PM, Rick Chen wrote:
>> Hi Anita:
>>  Prophetstor is my company name. I plan to verify our cinder volume 
>> driver.
>>  BP:
>> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver
>>  Please help us to create service account. Thanks.
> Great, thanks Rick. Linking the blueprint really helps.
> 
> We are working on getting me permissions to create accounts, which is soon
> but hasn't happened yet. In the meantime one of my infra colleagues may get
> the account created before I do.
> 
> Thanks,
> Anita.
>>
>> -Original Message-
>> From: Anita Kuno [mailto:ante...@anteaya.info]
>> Sent: Saturday, July 26, 2014 9:08 PM
>> To: openstack-infra@lists.openstack.org
>> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third 
>> Party CI System
>>
>> On 07/25/2014 08:36 PM, Rick Chen wrote:
>>> Hi Sir:
>>>
>>> Please help us to create service account, Thanks.
>>>
>>>  
>>>
>>> 1.  Attached file.
>>>
>>> 2.  A preferred username: prophetstor
>>>
>>> 3.  A human-readable: Prophetstor-CI
>>>
>>> 4.  Email address: prophetstor...@prophetstor.com
>>>
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Hi Rick:
>>
>> We are changing our documentation around requesting a service account, 
>> the patch hasn't been merged yet:
>> https://review.openstack.org/#/c/101013/11/doc/source/third_party.rst
>>
>> So Prophetstor is the name of your company, what details can you give 
>> me about what you intend to be verifying with your third party ci account?
>> It might be a piece of software or hardware or something else.
>> The more details you can offer, the better. If you have a blueprint or 
>> spec for it, linking to the blueprint or spec in your reply is really
> helpful.
>>
>> Thanks Rick,
>> 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] Requesting a Service Account for Third Party CI System

[Anita Kuno]

On 07/31/2014 12:39 PM, Steve Tan wrote:
> Hi Anita
> 
> This has been pending for quite a while now, are you able to help us forward 
> this request to the relevant people or do you have the email of who should we 
> contact for this? 
> 
> Thanks!
> Steve
Hi Steve:

The relevant people are already aware of your request.

We are working on getting me permissions to create accounts, I don't yet
have permissions to do so. The people who have permissions are extremely
busy with their regular tasks and one of them will get to your request
as soon as they are able. This is why we are working on getting
permissions for me.

Getting permissions for me consists of upstream changes to gerrit, most
of which are already merged, this patch is still pending:
https://gerrit-review.googlesource.com/#/c/58820/6 You are welcome to
review.

Then we need these changes merged into our gerrit branch:
https://review.openstack.org/#/q/status:open+project:openstack-infra/gerrit+branch:openstack/2.8.4,n,z
as well as the upstream change once it is merged. You are welcome to review.

Then we upgrade our gerrit-dev server and test it and if all goes well,
upgrade our gerrit server and then I can create and edit accounts. I
don't have a timeline other than it is a priority for myself and others
on the infra team.

You are already doing what needs to be done. You are welcome to join us
on #openstack-infra on the freenode network anytime you wish.

Thanks Steve,
Anita.
> 
>> On Jul 31, 2014, at 10:18 AM, Anita Kuno  wrote:
>>
>>> On 07/31/2014 11:24 AM, Rick Chen wrote:
>>> HI All:
>>>I saw the third-pard CI members still increased, but our account is
>>> not accepted. Can you tell me why? Or how to solve this problem?
>> Sure, one of the infra members with permissions to create the account
>> hasn't had the time to do it yet.
>>
>> You are welcome to join the #openstack-infra irc channel or follow along
>> in the logs: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/
>>
>> Thanks Rick,
>> Anita.
>>>
>>> 1.  Attached file.
>>> 2.  A preferred username: prophetstor
>>> 3.  A human-readable: ProphetStor-CI
>>> 4.  Email address: prophetstor...@prophetstor.com
>>> 5.  For cinder volume driver certificate. BP:
>>> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver
>>>
>>>>Please help us to create service account. Thanks.
>>> -Original Message-
>>> From: Rick Chen [mailto:rick.c...@prophetstor.com] 
>>> Sent: Monday, July 28, 2014 10:41 PM
>>> To: 'Anita Kuno'; 'openstack-infra@lists.openstack.org'
>>> Cc: 'steve tan'; 'Albert Lin'
>>> Subject: RE: [OpenStack-Infra] Requesting a Service Account for Third Party
>>> CI System
>>>
>>> HI Anita:
>>>Does our service account ready?
>>>I need change below information, please help me to correct? Or tell
>>> me how to change it?
>>>>> 3.  A human-readable: Prophetstor-CI --> ProphetStor-CI
>>>
>>>
>>> -Original Message-
>>> From: Anita Kuno [mailto:ante...@anteaya.info]
>>> Sent: Monday, July 28, 2014 3:43 AM
>>> To: Rick Chen; openstack-infra@lists.openstack.org
>>> Cc: 'steve tan'; Albert Lin
>>> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third Party
>>> CI System
>>>
>>>> On 07/27/2014 01:07 PM, Rick Chen wrote:
>>>> Hi Anita:
>>>>Prophetstor is my company name. I plan to verify our cinder volume 
>>>> driver.
>>>>BP:
>>>> https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver
>>>>Please help us to create service account. Thanks.
>>> Great, thanks Rick. Linking the blueprint really helps.
>>>
>>> We are working on getting me permissions to create accounts, which is soon
>>> but hasn't happened yet. In the meantime one of my infra colleagues may get
>>> the account created before I do.
>>>
>>> Thanks,
>>> Anita.
>>>>
>>>> -Original Message-
>>>> From: Anita Kuno [mailto:ante...@anteaya.info]
>>>> Sent: Saturday, July 26, 2014 9:08 PM
>>>> To: openstack-infra@lists.openstack.org
>>>> Subject: Re: [OpenStack-Infra] Requesting a Service Account for Third 
>>>> Party CI System
>>>>
>>>>> On 07/25/2014 08:36 PM, Rick Chen wrote:
>>>>> Hi Sir:
>>>>>
>>>>>Please help us

[OpenStack-Infra] reporting merge conflicts on patches tested by IBM Neutron Testing CI Account

[Anita Kuno]

https://review.openstack.org/#/c/13/7

Hello:

Currently your CI account is reporting merge conflicts on patches.
Please investigate this situation. At least one of our core contributors
is of the belief this is inappropriate behaviour. Please do share your
opinion as I would like to know what your position is on this matter.

On an unrelated note, the name of your system will be changing in
accordance with our new account policy:
http://ci.openstack.org/third_party.html#requesting-a-service-account

Please stay inform of third party ci expectations by attending the third
party meeting on a regular basis:
https://wiki.openstack.org/wiki/Meetings/ThirdParty

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] Setting http password for 3rd party CI accounts

[Anita Kuno]

On 08/08/2014 11:57 AM, Ryan Hsu wrote:
> Hi All,
> 
> Does anyone know if it’s possible to set up an http password for a 3rd party 
> CI account? We are looking to use some of the Gerrit REST API operations that 
> require authentication but according to this page [1], our account needs to 
> have a Gerrit http password set up. As far as I know, our CI account was only 
> given access to Gerrit via ssh keys meaning we would have to use the command 
> line API.
> 
> -Ryan
> 
> [1] 
> http://gerrit-review.googlesource.com/Documentation/rest-api.html#authentication
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Ryan:

Third Party CI accounts don't have access to the gui, only access via ssh.

I have not looked into setting an http password via ssh, but that would
be the only possibility for third party ci accounts as far as I know.

In short, I don't know if this is possible. I will add it to my list of
things to look at or to let you know about if I happen to fall over this
information. In the meantime if someone else reading this email has
become aware of the answer, do speak up.

Thanks Ryan,
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] Retrigger turbo-hipster

[Anita Kuno]

On 08/08/2014 02:53 PM, jswar...@linux.vnet.ibm.com wrote:
> 
> I'm unable to retrigger the turbo-hipster verification job on a change
> ("recheck migrations" comment retriggers Jenkins but not turbo-hipster)
> and I sent an e-mail to rc...@rcbops.com two days ago and still have not
> received a reply.  Has anyone else run into this problem and found a way
> to resolve it?
> 
> Thanks,
> 
> John
> 
> 
> ___
> OpenStack-dev mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi John:

I've included Josh on this email and also added the openstack-infra
mailing list (where the majority of third-party ci questions get posted).

Since it is the weekend in Australia it might be a day or so before we
get a response but I am confident we will get one.

Thanks John,
Anita.

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

Re: [OpenStack-Infra] Refreshing third-party CI service account credentials

[Anita Kuno]

On 08/06/2014 06:18 PM, Steven Kath wrote:
> Hello openstack-infra,
> 
> Here at Brocade, we have a handful of Openstack Third-party CI service 
> accounts.
> 
> We recently had a personnel change and will need to do a refresh of our 
> credentials (ex abundanti cautela). Presumably we'll need to generate new 
> keys and provide the new public keys to replace the previous ones.
> 
> Is there any documentation on how best to go about this? Or, can anyone 
> suggest an appropriate contact to work with on this?
> 
> Thanks!
> - Steven Kath
> 
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
If the accounts don't work for you now, provide new ssh public keys for
any of the accounts and provide the account name that corresponds to the
key. When someone with permissions has a chance they will update the keys.

Thanks Steven,
Anita.

Be sure that when you are test driving your system, you limit your
verification to the openstack-dev/sandbox repository. Thanks!

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

Re: [OpenStack-Infra] Setting http password for 3rd party CI accounts

[Anita Kuno]

On 08/08/2014 11:54 PM, Ryan Hsu wrote:
> Thanks very much Anita. According to the Gerrit documentation [1], there is a 
> command to set the http password for a given account. It does require 
> administrator privileges though.
> 
> set-account [--full-name ] [--active|--inactive] \
> [--add-email ] [--delete-email  | ALL] \
> [--add-ssh-key - | ] \
> [--delete-ssh-key - |  | ALL] \
> [--http-password ] 
> 
> Ryan
Good hunting Ryan.

Well I can add an item to the infra meeting next week[0] to get some
opinions from others about this feature, if we are willing to administer
it and how the process will look if we do.

Please attend the meeting to present your thoughts and answer questions
during the discussion. I can refer to this thread if you aren't there
and you can read the log[1] of the discussion after it takes place but
it is always a better outcome if you can attend and represent your own
interests.

Thanks Ryan,
Anita.

[0]
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
[1] http://eavesdrop.openstack.org/meetings/infra/

> 
> [1] https://review.openstack.org/Documentation/cmd-set-account.html
> 
> On Aug 8, 2014, at 9:05 PM, Anita Kuno 
> mailto:ante...@anteaya.info>> wrote:
> 
> On 08/08/2014 11:57 AM, Ryan Hsu wrote:
> Hi All,
> 
> Does anyone know if it’s possible to set up an http password for a 3rd party 
> CI account? We are looking to use some of the Gerrit REST API operations that 
> require authentication but according to this page [1], our account needs to 
> have a Gerrit http password set up. As far as I know, our CI account was only 
> given access to Gerrit via ssh keys meaning we would have to use the command 
> line API.
> 
> -Ryan
> 
> [1] 
> https://urldefense.proofpoint.com/v1/url?u=http://gerrit-review.googlesource.com/Documentation/rest-api.html%23authentication&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=0GxzU7fJvvhFTHF4JHrlbg%3D%3D%0A&m=yGjiRIfc0ONkg1KETfop%2Fw5QXjlII51Sf%2Fse0CNZp18%3D%0A&s=7b4cd6432bd1b52110fffad9345f94a1d31ca9a9817bd137e532c7e8a0c56a43
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org<mailto:OpenStack-Infra@lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
> Hi Ryan:
> 
> Third Party CI accounts don't have access to the gui, only access via ssh.
> 
> I have not looked into setting an http password via ssh, but that would
> be the only possibility for third party ci accounts as far as I know.
> 
> In short, I don't know if this is possible. I will add it to my list of
> things to look at or to let you know about if I happen to fall over this
> information. In the meantime if someone else reading this email has
> become aware of the answer, do speak up.
> 
> Thanks Ryan,
> Anita.
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org<mailto: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] Third Party CI System account

[Anita Kuno]

On 08/04/2014 08:42 AM, Erlon Cruz wrote:
> On 07/22/2014 05:15 PM, Wilfredo Ronsini wrote:
> 
>>> I work in the Flextronics Institute of Technology and I am in the process 
>>> of setting an OpenStack CI server.
>>>
>>> Please, create a Gerrit user account.
>>>
>>> Preferred username: wronsini
>>>
>>> Best regards,
>>> Wilfredo Raphael Ronsini Junior
>>> email: Wilfredo.Jr at fit-tecnologia.org.br
>>>
>>> Legal Disclaimer:
>>> The information contained in this message may be privileged and 
>>> confidential. It is intended to be read only by the individual or entity to 
>>> whom it is addressed or by their designee. If the reader of this message is 
>>> not the intended recipient, you are on notice that any distribution of this 
>>> message, in any> form, is strictly prohibited. If you have received this 
>>> message in error, please immediately notify the sender and delete or 
>>> destroy any copy of this message!
> 
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Hi Wilfredo:
>>
> 
> Hi Anita,
> 
> We need to have our CI system in the list of reviewers of the patches
> sent to cinder (like, EMC XIO CI, HP Cinder CI, etc).
> An ordinary gerrit account is enough for that?
> 
> Thanks,
> Erlon
No an ordinary gerrit account does not accomplish that.

What are you verifying to require you to have your CI system report on
cinder patches? Is it a cinder driver? If yes, do you have a link to the
cinder driver blueprint or spec?

Thanks Wilfredo,
Anita.

Also you might do well to join the third party meetings:
https://wiki.openstack.org/wiki/Meetings/ThirdParty
> 
>> The need for a third party ci account from gerrit comes into play if you
>> are looking to comment on patches with some kind of verification.
>>
>>
>>
>>
>> What do you plan on verifying?
>>
>> For instance businesses often want to verify their proprietary code or
>> hardware will work with each evaluated patch. What might you be verifying?
>>
>> If you aren't going to be reporting back any verification status, you
>> can hook into gerrit events with a normal user account using:
>> ssh -p 29418 @review.openstack.org gerrit stream-events
>>
>> and you can have your system trigger off of gerrit events and you don't
>> need to report anything back to the patch you are using as a trigger.
>>
>> Thanks Wilfredo,
>> 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] 3rd party CI account request

[Anita Kuno]

On 08/04/2014 04:51 AM, Sergey Lukjanov wrote:
> Anita, could you please confirm that congress-ci "Congress CI" is an
> acceptable name?
Sorry I have been traveling.

Actually we should go with VMware Congress CI. I hope to have gerrit
permissions to edit third party ci gerrit account names soon so I can
fix it then.

Thanks,
Anita.
> 
> On Wed, Jul 30, 2014 at 1:29 AM, Aaron Rosen  wrote:
>> Hi,
>>
>> I was on #openstack-infra I should also include a few more things which are
>> new requirements:
>>
>> company: VMware
>> Providing CI for the Openstack Congress project:
>> https://github.com/stackforge/congress
>>
>> Thanks,
>>
>> Aaron
>>
>>
>> On Tue, Jul 29, 2014 at 11:26 AM, Aaron Rosen  wrote:
>>>
>>> Hi,
>>>
>>> I'm following what's outlined here
>>> (http://ci.openstack.org/third_party.html#requesting-a-service-account) to
>>> setup a new account for 3rd party testing for a new openstack stackforge
>>> project.
>>>
>>> Desired username: Congress-CI
>>> contact: congres...@gmail.com
>>> Pub ssh key attached.
>>>
>>> Thanks!
>>>
>>> Aaron
>>
>>
>>
>> ___
>> 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] Account Request

[Anita Kuno]

On 08/11/2014 09:20 PM, Steven Sonnenberg wrote:
> 
> We have an existing account HDS-CI, but we need at least 2 accounts to cover 
> the different driver code bases.
> 
> 
> 1.Please rename (hds-ci) HDS CI to (hds-hnas-ci) HDS HNAS CI.
> 
> 
> 2.Please create another account as follows:
> 
> 
> Email: openstackdevelopm...@hds.com
> 
> Account Username (short): hds-hbsd-ci
> 
> Account Username (long): HDS HBSD CI
> 
> Contact Info: Steven Sonnenberg, 
> steve.sonnenb...@hds.com, IRC handle: 
> steveisoft, Mobile: 443-929-6543
> 
> Public Key:  sh-rsa 
> B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngBMovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h5HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc=
>  openstackdevelopm...@hds.com
> 
> Thanks,
> -steve
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Slow down, slow down.

I do believe there is an outstanding question about how many accounts
you need and I have tried to respond to your email all day and never got
to it.

Please allow me to respond to your original email prior to requesting an
additional account which you may not in fact need, I don't know yet, I
am still going through the material.

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] Rechecking OpenStack CI

[Anita Kuno]

On 08/12/2014 07:17 AM, Jeremy Stanley wrote:
> On 2014-08-12 17:43:37 +1000 (+1000), Joshua Hesketh wrote:
>> Right, and even if we did change all the 3rd parties over to
>> something that doesn't start with 'recheck' there will be
>> inconsistencies between 3rd parties and 1st party.
> [...]
> 
> If this is really something the various CI operators want to support
> (rather than merely something which has been cargo-culted as a
> behavior they're expected to emulate), I think we need a separate
> syntax for it which lacks the encumbrance of the currently ambiguous
> "recheck" ad-hoc language which has grown arbitrarily by convention.
> 
> However, I also don't personally think that rechecking one specific
> CI makes sense, and would rather just have them all run every time
> you say "recheck" since otherwise you end up pin-and-tumbler
> lockpicking racy bugs (selectively rerererecheck each CI until you
> get a good run and then hold that result while you work through the
> rest of them in turn).
> 
> I'm less worried about the small amount of resource waste in the
> upstream OpenStack project infrastructure from people getting jobs
> rerun when they recheck for some failed third-party result. The
> expectation we ultimately need to set is that every CI should pass
> pretty much all of the time on a good change and if it doesn't then
> it must be fixed (upstream CI included). Allowing you to selectively
> rerun jobs from one system reinforces the idea that it's okay to
> fail frequently as long as devs are eventually able to coax out a
> passing run.
> 
I'm not sure if the folks on this thread are aware of this patch
offering yet: https://review.openstack.org/#/c/109565/

It would be great to get your thoughts on it.

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] Third Party CI naming and contact (action required)

[Anita Kuno]

On 08/13/2014 08:14 PM, trinath.soman...@freescale.com wrote:
> Hi-
> 
> I have updated the page for 'Freescale CI'.
> 
> Need a change in the CI display name, Can you change 'Freescale CI' to 
> 'Freescale Neutron CI'. 
> 
> Here is the page I added, 
> https://wiki.openstack.org/wiki/ThirdPartySystems/Freescale_CI and the Index 
> page https://wiki.openstack.org/wiki/ThirdPartySystems
> 
> --
> Trinath Somanchi - B39208
> trinath.soman...@freescale.com | extn: 4048
> 
> -Original Message-
> From: James E. Blair [mailto:cor...@inaugust.com] 
> Sent: Wednesday, August 13, 2014 11:54 PM
> To: openstack-infra@lists.openstack.org
> Cc: openstack-...@lists.openstack.org
> Subject: [OpenStack-Infra] [infra] Third Party CI naming and contact (action 
> required)
> 
> Hi,
> 
> We've updated the registration requirements for third-party CI systems
> here:
> 
>   http://ci.openstack.org/third_party.html
> 
> We now have 86 third-party CI systems registered and have undertaken an 
> effort to make things more user-friendly for the developers who interact with 
> them.  There are two important changes to be aware of:
> 
> 1) We now generally name third-party systems in a descriptive manner 
> including the company and product they are testing.  We have renamed 
> currently-operating CI systems to match these standards to the best of our 
> abilities.  Some of them ended up with particularly bad names (like "Unknown 
> Function...").  If your system is one of these, please join us in 
> #openstack-infra on Freenode to establish a more descriptive name.
> 
> 2) We have established a standard wiki page template to supply a description 
> of the system, what is tested, and contact information for each system.  See 
> https://wiki.openstack.org/wiki/ThirdPartySystems for an index of such pages 
> and instructions for creating them.  Each third-party CI system will have its 
> own page in the wiki and it must include a link to that page in every comment 
> that it leaves in Gerrit.
> 
> If you operate a third-party CI system, please ensure that you register a 
> wiki page and update your system to link to it in every new Gerrit comment by 
> the end of August.  Beginning in September, we will disable systems that have 
> not been updated.
> 
> Thanks,
> 
> 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
> 
Your CI system won't be using openstack or any openstack project or
program names in it.

Thanks Trinath,
Anita.

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

Re: [OpenStack-Infra] request a gerrit system account

[Anita Kuno]

On 08/13/2014 07:48 PM, Wan, Sam wrote:
> Hi there,
> 
>I'd like to request a gerrit system account for test.
> 
> 1.   Public ssh key as attached.
> 
> 2.   Company: EMC
> 
> 3.   Cinder driver
> 
> 
> Thanks and regards
> 
> 
> Sam
> 
> 
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
Hi Sam:

So if you read
http://ci.openstack.org/third_party.html#requesting-a-service-account
the number 3 item is the identification of what you are verifying.

The OpenStack gate testing process verifies cinder. If you are verifying
a cinder driver, what is your cinder driver called?

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] Third Party CI naming and contact (action required)

[Anita Kuno]

On 08/14/2014 12:50 PM, Lucas Eznarriaga wrote:
> Hi,
> 
> Midokura CI should be up to date now too.
> We have a problem with zuul-merger when the host id of review.openstack.org
> changes. In this case, the new rsa key has to be added manually otherwise
> the build will fail with a:
> 
> Merge Failed.
> 
> This change was unable to be automatically merged with the current state of
> the repository. Please rebase your change and upload a new patchset
> 
> So if the review.openstack.org host changes soon it will start failing
> again.
> That said, taking into account that August is the usual vacation month in
> Europe and probably in some other parts as well, end of August sounds like
> a tight deadline. Also, I have been attending to third-party meetings
> regularly but the last one (I have checked the logs) and I feel like an
> announcement for these new requirements should have been done there.
> 
> Have a great summer!
> 
> Lucas
Hi Lucas:

Well this has been something I have been working on since summit and I
hadn't expected the issue of naming to bog me down for three months, but
it did. I'm grateful to Jim to have been able to address this issue and
clear it up so well.

Help me understand how creating a wikipage and populating it with
contact information and editing the formatting for your comments will
take more than 11 working days to accomplish. If it is really impossible
for you to accomplish this work in this time and can demonstrate this to
me, I will advocate on your behalf with the rest of the infra team. If
you would like me to do this, I will need a deadline which you will hold
yourself to.

Thanks Lucas,
Anita.
> 
> 
> 
> 
> On Wed, Aug 13, 2014 at 8:23 PM, James E. Blair  wrote:
> 
>> Hi,
>>
>> We've updated the registration requirements for third-party CI systems
>> here:
>>
>>   http://ci.openstack.org/third_party.html
>>
>> We now have 86 third-party CI systems registered and have undertaken an
>> effort to make things more user-friendly for the developers who interact
>> with them.  There are two important changes to be aware of:
>>
>> 1) We now generally name third-party systems in a descriptive manner
>> including the company and product they are testing.  We have renamed
>> currently-operating CI systems to match these standards to the best of
>> our abilities.  Some of them ended up with particularly bad names (like
>> "Unknown Function...").  If your system is one of these, please join us
>> in #openstack-infra on Freenode to establish a more descriptive name.
>>
>> 2) We have established a standard wiki page template to supply a
>> description of the system, what is tested, and contact information for
>> each system.  See https://wiki.openstack.org/wiki/ThirdPartySystems for
>> an index of such pages and instructions for creating them.  Each
>> third-party CI system will have its own page in the wiki and it must
>> include a link to that page in every comment that it leaves in Gerrit.
>>
>> If you operate a third-party CI system, please ensure that you register
>> a wiki page and update your system to link to it in every new Gerrit
>> comment by the end of August.  Beginning in September, we will disable
>> systems that have not been updated.
>>
>> Thanks,
>>
>> 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

Re: [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)

[Anita Kuno]

On 08/14/2014 01:18 PM, Lucas Eznarriaga wrote:
> If you operate a third-party CI system, please ensure that you register
>> >> a wiki page and update your system to link to it in every new Gerrit
>> >> comment by the end of August.  Beginning in September, we will disable
>> >> systems that have not been updated.

This is all that needs to be accomplished by the end of August. There is
no mention of zuul in the expectation by the end of August.

Thanks Lucas, I appreciate your understanding and hard work,
Anita.

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

Re: [OpenStack-Infra] Account Request

[Anita Kuno]

On 08/11/2014 09:45 PM, Anita Kuno wrote:
> On 08/11/2014 09:20 PM, Steven Sonnenberg wrote:
>>
>> We have an existing account HDS-CI, but we need at least 2 accounts to cover 
>> the different driver code bases.
>>
>>
>> 1.Please rename (hds-ci) HDS CI to (hds-hnas-ci) HDS HNAS CI.
>>
>>
>> 2.Please create another account as follows:
>>
>>
>> Email: openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com>
>>
>> Account Username (short): hds-hbsd-ci
>>
>> Account Username (long): HDS HBSD CI
>>
>> Contact Info: Steven Sonnenberg, 
>> steve.sonnenb...@hds.com<mailto:steve.sonnenb...@hds.com>, IRC handle: 
>> steveisoft, Mobile: 443-929-6543
>>
>> Public Key:  sh-rsa 
>> B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngBMovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h5HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc=
>>  openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com>
>>
>> Thanks,
>> -steve
>>
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
> Slow down, slow down.
> 
> I do believe there is an outstanding question about how many accounts
> you need and I have tried to respond to your email all day and never got
> to it.
> 
> Please allow me to respond to your original email prior to requesting an
> additional account which you may not in fact need, I don't know yet, I
> am still going through the material.
> 
> Thank you,
> Anita.
> 
Okay thanks Steven, now that I have had a moment to look at things I
realize I was confusing your request with someone else's request, my
apologies.

So your first request, the renaming has been accomplished. Please confirm.

Be aware we require all third party ci gerrit accounts to have a
wikipage created with the contact information for the account on the
page and the url for the wikipage in the comments returned to gerrit as
per this email:
http://lists.openstack.org/pipermail/openstack-dev/2014-August/042917.html
So I look forward to your wikipage for HDS HDNS CI.

As for your second request, the creation of a new account I have some
feedback.

Help me understand why you need a second account rather than using the
one account for testing both items? Many third party ci admins test many
items with one gerrit account. If you need more information on how this
works, do attend the third party meeting:
https://wiki.openstack.org/wiki/Meetings/ThirdParty

Thanks Steven,
Anita.




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

Re: [OpenStack-Infra] Account Request

[Anita Kuno]

On 08/14/2014 03:23 PM, Steven Sonnenberg wrote:
> Thanks, if we can do this with one account, we'd be happy too.
> I just noticed that other vendors have an account per driver platform, and we 
> have at least 2.
> In our case we are supporting CI for both Hitachi Data Systems, and Hitachi 
> LTD.
> 
> In any case, we requested the names
> 
>   HDS-HNAS-CI
> And
>  HDS-HBSD-CI
> 
> We will fill out the Wiki page soon.
> 
> It looks like you chose 
> 
>   HDS HDNS CI
We fullfilled this request:
Please rename (hds-ci) HDS CI to (hds-hnas-ci) HDS HNAS CI.

> 
> Maybe we should go back to HDS CI, until we determine that we need two 
> entries.
Actually having a name of something you are verifying is better than not.

Thanks,
Anita.

> 
> -steve
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info] 
> Sent: Thursday, August 14, 2014 5:09 PM
> To: openstack-infra@lists.openstack.org
> Subject: Re: [OpenStack-Infra] Account Request
> 
> On 08/11/2014 09:45 PM, Anita Kuno wrote:
>> On 08/11/2014 09:20 PM, Steven Sonnenberg wrote:
>>>
>>> We have an existing account HDS-CI, but we need at least 2 accounts to 
>>> cover the different driver code bases.
>>>
>>>
>>> 1.Please rename (hds-ci) HDS CI to (hds-hnas-ci) HDS HNAS CI.
>>>
>>>
>>> 2.Please create another account as follows:
>>>
>>>
>>> Email: 
>>> openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com>
>>>
>>> Account Username (short): hds-hbsd-ci
>>>
>>> Account Username (long): HDS HBSD CI
>>>
>>> Contact Info: Steven Sonnenberg, 
>>> steve.sonnenb...@hds.com<mailto:steve.sonnenb...@hds.com>, IRC 
>>> handle: steveisoft, Mobile: 443-929-6543
>>>
>>> Public Key:  sh-rsa 
>>> B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngBM
>>> ovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h5
>>> HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc= 
>>> openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com>
>>>
>>> Thanks,
>>> -steve
>>>
>>>
>>>
>>> ___
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>> Slow down, slow down.
>>
>> I do believe there is an outstanding question about how many accounts 
>> you need and I have tried to respond to your email all day and never 
>> got to it.
>>
>> Please allow me to respond to your original email prior to requesting 
>> an additional account which you may not in fact need, I don't know 
>> yet, I am still going through the material.
>>
>> Thank you,
>> Anita.
>>
> Okay thanks Steven, now that I have had a moment to look at things I realize 
> I was confusing your request with someone else's request, my apologies.
> 
> So your first request, the renaming has been accomplished. Please confirm.
> 
> Be aware we require all third party ci gerrit accounts to have a wikipage 
> created with the contact information for the account on the page and the url 
> for the wikipage in the comments returned to gerrit as per this email:
> http://lists.openstack.org/pipermail/openstack-dev/2014-August/042917.html
> So I look forward to your wikipage for HDS HDNS CI.
> 
> As for your second request, the creation of a new account I have some 
> feedback.
> 
> Help me understand why you need a second account rather than using the one 
> account for testing both items? Many third party ci admins test many items 
> with one gerrit account. If you need more information on how this works, do 
> attend the third party meeting:
> https://wiki.openstack.org/wiki/Meetings/ThirdParty
> 
> Thanks Steven,
> 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] Account Request

[Anita Kuno]

On 08/14/2014 03:39 PM, Steven Sonnenberg wrote:
> Ok, so HDNS was just a typo.
> 
> thanks
> 
Yes, I made a typo.

I don't do well with acronyms, I can't remember them and often get them
in the wrong order, I much prefer names in all cases of acronyms. This
is my personal perspective, I realize though there are many who like
acronyms, I am just not among them.

Thanks Steven,
Anita.
> 
> 
> -Original Message-
> From: Anita Kuno [mailto:ante...@anteaya.info]
> Sent: Thursday, August 14, 2014 5:38 PM
> To: Steven Sonnenberg; openstack-infra@lists.openstack.org
> Cc: Marcus Nascimento (marcus.nascime...@fit-tecnologia.org.br)
> Subject: Re: [OpenStack-Infra] Account Request
> 
> 
> 
> On 08/14/2014 03:23 PM, Steven Sonnenberg wrote:
> 
>> Thanks, if we can do this with one account, we'd be happy too.
> 
>> I just noticed that other vendors have an account per driver platform, and 
>> we have at least 2.
> 
>> In our case we are supporting CI for both Hitachi Data Systems, and Hitachi 
>> LTD.
> 
>>
> 
>> In any case, we requested the names
> 
>>
> 
>>   HDS-HNAS-CI
> 
>> And
> 
>>  HDS-HBSD-CI
> 
>>
> 
>> We will fill out the Wiki page soon.
> 
>>
> 
>> It looks like you chose
> 
>>
> 
>> HDS HDNS CI
> 
> We fullfilled this request:
> 
> Please rename (hds-ci) HDS CI to (hds-hnas-ci) HDS HNAS CI.
> 
> 
> 
>>
> 
>> Maybe we should go back to HDS CI, until we determine that we need two 
>> entries.
> 
> Actually having a name of something you are verifying is better than not.
> 
> 
> 
> Thanks,
> 
> Anita.
> 
> 
> 
>>
> 
>> -steve
> 
>>
> 
>> -Original Message-
> 
>> From: Anita Kuno [mailto:ante...@anteaya.info]
> 
>> Sent: Thursday, August 14, 2014 5:09 PM
> 
>> To: 
>> openstack-infra@lists.openstack.org<mailto:openstack-infra@lists.openstack.org>
> 
>> Subject: Re: [OpenStack-Infra] Account Request
> 
>>
> 
>> On 08/11/2014 09:45 PM, Anita Kuno wrote:
> 
>>> On 08/11/2014 09:20 PM, Steven Sonnenberg wrote:
> 
>>>>
> 
>>>> We have an existing account HDS-CI, but we need at least 2 accounts to 
>>>> cover the different driver code bases.
> 
>>>>
> 
>>>>
> 
>>>> 1.Please rename (hds-ci) HDS CI to (hds-hnas-ci) HDS HNAS CI.
> 
>>>>
> 
>>>>
> 
>>>> 2.Please create another account as follows:
> 
>>>>
> 
>>>>
> 
>>>> Email:
> 
>>>> openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com%3cmailto:openstackdevelopm...@hds.com>>
> 
>>>>
> 
>>>> Account Username (short): hds-hbsd-ci
> 
>>>>
> 
>>>> Account Username (long): HDS HBSD CI
> 
>>>>
> 
>>>> Contact Info: Steven Sonnenberg,
> 
>>>> steve.sonnenb...@hds.com<mailto:steve.sonnenb...@hds.com<mailto:steve.sonnenb...@hds.com%3cmailto:steve.sonnenb...@hds.com>>,
>>>>  IRC
> 
>>>> handle: steveisoft, Mobile: 443-929-6543
> 
>>>>
> 
>>>> Public Key:  sh-rsa
> 
>>>> B3NzaC1yc2EBIwAAAIEA2qs+GtPkRc7SNJLDF51J6IewX9Kt1mEMEGqi4ngB
> 
>>>> B3NzaC1yc2EBIwAAAIEA2qs+M
> 
>>>> ovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+hPhWchJZegtzN1h
> 
>>>> ovN9zwRXo+uAtgHxQ0zBghsdvpXlVocsC02vlfSVAl6HkXgz2MDl+5
> 
>>>> HOfWMYmCWeV1yturDn+j5lrg3mRTBW35eze7hmZPBsvZhhZIOntS49lPa1jzc=
> 
>>>> openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com<mailto:openstackdevelopm...@hds.com%3cmailto:openstackdevelopm...@hds.com>>
> 
>>>>
> 
>>>> Thanks,
> 
>>>> -steve
> 
>>>>
> 
>>>>
> 
>>>>
> 
>>>> ___
> 
>>>> OpenStack-Infra mailing list
> 
>>>> OpenStack-Infra@lists.openstack.org<mailto:OpenStack-Infra@lists.openstack.org>
> 
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
>>>>
> 
>>> Slow down, slow down.
> 
>>>
> 
>>> I do believe there is an outstanding question about how many accounts
> 
>>> you need and I have tried to respond to your email all day and never
> 
>>> got to it.
> 
>>>
> 
>>>

Re: [OpenStack-Infra] [Third Party Testing] Requesting a Service Account

[Anita Kuno]

On 08/18/2014 05:13 PM, Charles Hsu wrote:
> HI,
> 
> Here is a wiki page for our cluster
> https://wiki.openstack.org/wiki/ThirdPartySystems/SwiftStack_Cluster_CI
> 
> Thanks
> 
And we have consensus around SwiftStack Cluster CI and swiftstack-cluster-ci

Thanks,
Anita.
> 
> On Sun, Aug 17, 2014 at 11:10 PM, Charles Hsu  wrote:
> 
>> Hi,
>>
>> We're try to setup a CI cluster for swift, please help us to create a
>> gerrit account.
>> Here is required information.
>>
>> 1. SSH Public Key
>>
>> ssh-rsa 
>> B3NzaC1yc2EDAQABAAABAQCy7Dt+tiqeQZgFaFoRi1ItRad0/pt/9ziR/sfh0Vs6Y0vJVI6H+FG4WJyFh3lXcuwMDx2zuVMIdsd+Svq8fYsMsz/RLeF7NCMq7+BGB4CTKq1mAte1cADGOgFxncMjUII1Uwkqi19iP5lJOeXzEchizZ6InEiA5Y0wO0jVLWl274i6ua2K/Na42urMLizcerprAOb5CVly3a+wFZUzfNyOsd6NhOezmTDktw/k3YxbmpgXaa6RdfAhU0UEl3wemeenDmJicf0igJ2yzlZrR7SkYnPI0oHBibKJ/nBmSPYAdNIMB5KXdx51VPOrw4ZO9E2HTGXaW/C63cC0sNJyIMQP
>>  swiftstack@swift-qa-jenkins
>>
>>
>> 2. Company: SwiftStack
>> 3. Project: Swift
>> 4. Email: openstack...@swiftstack.com
>>
>> Thanks
>> --
>> Charles Hsu
>> SwiftStack.com
>>
>>
> 
> 
> 
> 
> ___
> 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