Re: [OpenStack-Infra] git review -d without check out

[Tony Breeds]

On Tue, Mar 27, 2018 at 02:16:32PM +0300, Ram Rachum wrote:
> Hi,
> 
> Is there a way to do `git review -d` without having it do a checkout? i.e.
> I just want to have these commits in my Git database so I could cherrypick
> them on some other branch. We've got tons of submodules so checking out
> often creates problems.
> 
> I tried `git fetch gerrit my_commit_hash:temporary_branch_name` but that's
> insanely slow for some reason.

Thanks more or less what I do.

This is my ~bin/git-os-change
---
#!/usr/bin/env bash

review=$1
revision=${2:-1}

if [ -z "$review" ] ; then
echo Need an OpenStack gerrit review number >&2
exit 1
fi

ref=$(printf "refs/changes/%d/%d/%d" "${review: -2}" "${review}" "${revision}")
git fetch gerrit "${ref}:${ref}"
---

It's about the same speed as git review.

---
[tony@thor ~]$ cd tmp
/home/tony/tmp
[tony@thor tmp]$ cp -a ~/projects/openstack/openstack-dev/devstack devstack-1
[tony@thor tmp]$ cp -a ~/projects/openstack/openstack-dev/devstack devstack-2
[tony@thor tmp]$ cd devstack-1
/home/tony/tmp/devstack-1
[tony@thor devstack-1]$ time git review -d 554977
Downloading refs/changes/77/554977/3 from gerrit
Switched to branch "review/eric_berglund/etcd_version"

real0m3.892s
user0m0.508s
sys 0m0.225s
[tony@thor devstack-1]$ cd ../devstack-2
[tony@thor devstack-2]$ time git os-change 554977 3
remote: Counting objects: 7, done
remote: Finding sources: 100% (4/4)
remote: Total 4 (delta 3), reused 3 (delta 3)
Unpacking objects: 100% (4/4), done.
From ssh://review.openstack.org:29418/openstack-dev/devstack
 * [new ref]   refs/changes/77/554977/3 -> refs/changes/77/554977/3

real0m2.813s
user0m0.182s
sys 0m0.152s
---

Yours Tony.


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

Re: [OpenStack-Infra] [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

[Tony Breeds]

On Mon, Mar 26, 2018 at 06:19:10PM -0400, Paul Belanger wrote:
> On Tue, Mar 27, 2018 at 08:56:09AM +1100, Tony Breeds wrote:
> > Hi folks,
> > Can we ask someone from infra to do this, or add me to bootstrappers
> > to do it myself?
> > 
> Give that we did this last time, I don't see why we can't add you to
> boostrappers again.
> 
> Will confirm.

Thanks.  I only small problem with that is I need to stay way from
review.o.o while I'm in the bootstrappers group "so many new buttons ..
must not click them"  :D

Yours Tony.


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

Re: [OpenStack-Infra] Adding new etcd binaries to tarballs.o.o

[Tony Breeds]

On Tue, Mar 27, 2018 at 10:22:26AM +1100, Ian Wienand wrote:
> On 03/27/2018 09:25 AM, Tony Breeds wrote:
> > Can we please add the appropriate files for the 3.3.2 (or 3.2.17)
> > release of etcd added to tarballs.o.o
> 
> ISTR that we had problems even getting them from there during runs, so
> moved to caching this.  I had to check, this isn't well documented ...
> 
> The nodepool element caching code [1] should be getting the image name
> from [2], which gets the URL for the tarball via the environment
> variables in stackrc.  dib then stuffs that tarball into /opt/cache on
> all our images.
> 
> In the running devstack code, we use get_extra_file [3] which should
> look for the tarball in the on-disk cache, or otherwise download it
> [4].
> 
> Ergo, I'm pretty sure these files on tarballs.o.o are unused.  Bumping
> the version in devstack should "just work" -- it will download
> directly until the next day's builds come online with the file cached.

Except something sets ETCD_DOWNLOAD_URL to tarballs.o.o

See:
http://logs.openstack.org/77/554977/1/check/devstack/4cc8483/controller/logs/_.localrc_auto.txt.gz
 
and
http://logs.openstack.org/77/554977/1/check/devstack/4cc8483/controller/logs/devstacklog.txt.gz#_2018-03-21_16_52_00_998

So we have a egg<->chicken problem don't we and we still need/want the
data on tarballs.o.o even if it's seldom used
 
> I think we can discuss this in that review, but it seems likely from
> our discussions in IRC that 3.2 will be the best choice here.  It is
> in bionic & fedora; so we can shortcut all of this and install from
> packages there.

Yup we can discuss that on the review.

Yours Tony.


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

[OpenStack-Infra] Adding new etcd binaries to tarballs.o.o

[Tony Breeds]

Hi All,
Dredging up the past a little here ... In Denver James, Monty, Paul,
Clark and I talked about the fact that we have an unoffical mirror for
etcd binaries on tarballs.o.o[1].  We all agreed that this was ...
sub-optimal.  So I took ownership of getting etcd 3.2 (for all
architectures) into 18.04 which has happened [2,3].

3rd party CI systems running on non x86 CPUs have been manually patching
the etcd version to get devstack working.

Can we please add the appropriate files for the 3.3.2 (or 3.2.17)
release of etcd added to tarballs.o.o

I realise that 18.04 is just around the corner but doing this now gives
us scope to land [4] soon and consider stable branches etc while we
transition to bionic images and then dismantle the devstack
infrastructure for consuming these tarballs


Yours Tony.

[1] http://tarballs.openstack.org/etcd/
[2] https://packages.ubuntu.com/bionic/etcd-server
[3] https://packages.ubuntu.com/bionic/etcd-client
[4] https://review.openstack.org/#/c/554977/1


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

Re: [OpenStack-Infra] [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

[Tony Breeds]

Hi folks,
Can we ask someone from infra to do this, or add me to bootstrappers
to do it myself?

On Thu, Mar 15, 2018 at 10:57:58AM +, Jean-Philippe Evrard wrote:
> Looks good to me.
> 
> On 15 March 2018 at 01:11, Tony Breeds  wrote:
> > On Wed, Mar 14, 2018 at 09:40:33PM +, Jean-Philippe Evrard wrote:
> >> Hello folks,
> >>
> >> The list is almost perfect: you can do all of those except
> >> openstack/openstack-ansible-tests.
> >> I'd like to phase out openstack/openstack-ansible-tests and
> >> openstack/openstack-ansible later.
> >
> > Okay excluding the 2 repos above and filtering out projects that don't
> > have newton branches we came down to:
> >
> > # EOL repos belonging to OpenStackAnsible
> > eol_branch.sh -- stable/newton newton-eol \
> >  openstack/ansible-hardening \
> >  openstack/openstack-ansible-apt_package_pinning \
> >  openstack/openstack-ansible-ceph_client \
> >  openstack/openstack-ansible-galera_client \
> >  openstack/openstack-ansible-galera_server \
> >  openstack/openstack-ansible-haproxy_server \
> >  openstack/openstack-ansible-lxc_container_create \
> >  openstack/openstack-ansible-lxc_hosts \
> >  openstack/openstack-ansible-memcached_server \
> >  openstack/openstack-ansible-openstack_hosts \
> >  openstack/openstack-ansible-openstack_openrc \
> >  openstack/openstack-ansible-ops \
> >  openstack/openstack-ansible-os_aodh \
> >  openstack/openstack-ansible-os_ceilometer \
> >  openstack/openstack-ansible-os_cinder \
> >  openstack/openstack-ansible-os_glance \
> >  openstack/openstack-ansible-os_gnocchi \
> >  openstack/openstack-ansible-os_heat \
> >  openstack/openstack-ansible-os_horizon \
> >  openstack/openstack-ansible-os_ironic \
> >  openstack/openstack-ansible-os_keystone \
> >  openstack/openstack-ansible-os_magnum \
> >  openstack/openstack-ansible-os_neutron \
> >  openstack/openstack-ansible-os_nova \
> >  openstack/openstack-ansible-os_rally \
> >  openstack/openstack-ansible-os_sahara \
> >  openstack/openstack-ansible-os_swift \
> >  openstack/openstack-ansible-os_tempest \
> >  openstack/openstack-ansible-pip_install \
> >  openstack/openstack-ansible-plugins \
> >  openstack/openstack-ansible-rabbitmq_server \
> >  openstack/openstack-ansible-repo_build \
> >  openstack/openstack-ansible-repo_server \
> >  openstack/openstack-ansible-rsyslog_client \
> >  openstack/openstack-ansible-rsyslog_server \
> >  openstack/openstack-ansible-security
> >
> > If you confirm I have the list right this time I'll work on this tomorrow
> >
> > Yours Tony.
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Yours Tony.


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

Re: [OpenStack-Infra] Zuul roadmap

[Tony Breeds]

On Thu, Nov 02, 2017 at 12:33:30AM +, Tristan Cacqueray wrote:
> On November 1, 2017 11:56 pm, Tony Breeds wrote:
> > On Wed, Nov 01, 2017 at 02:47:20PM -0700, James E. Blair wrote:
> > > Hi,
> > > 
> > > At the PTG we brainstormed a road map for Zuul once we completed the
> > > infra cutover.  I think we're in a position now that we can get back to
> > > thinking about this, so I've (slightly) cleaned it up and organized it
> > > here.
> > 
> > 
> > > How does this look?
> > 
> > Something we talked about on IRC that I didnt' see there was a REST API
> > to get the current config for a project.  Something that requirements
> > and release management can use to validate that $project has the correct
> > templates in place for all the automation to work.
> > 
> > Right now we're just checking-project as assuming that's good enough and

checking-project ?  That should be 'checking project-config' :/

I can't even blame a lack of coffee.

> > it probably is ;P but It'd still be cool if the REST API was there at
> > some point.
> > 
> > Yours Tony.
> 
> That's a great idea, actually the zuul-web dashboard[0] mentioned in the
> "very near term" is actually a REST API from the zuul-web service.
> It currently only exposes jobs list and build result history, though it
> should be possible to expose a projects.json endpoint to give you that
> information. I think this would be a great addition to provide more visual
> feedback about project's pipeline and job dependencies.
> 
> Perhaps we would also need a templates.json endpoint too so that a
> project configuration would reference templates instead/alongside the
> expanded configuration.

That sounds good.  I'm sorry I didn't equate the dashboard and the REST
API.

Yours Tony.


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

Re: [OpenStack-Infra] Zuul roadmap

[Tony Breeds]

On Wed, Nov 01, 2017 at 02:47:20PM -0700, James E. Blair wrote:
> Hi,
> 
> At the PTG we brainstormed a road map for Zuul once we completed the
> infra cutover.  I think we're in a position now that we can get back to
> thinking about this, so I've (slightly) cleaned it up and organized it
> here.


 
> How does this look?

Something we talked about on IRC that I didnt' see there was a REST API
to get the current config for a project.  Something that requirements
and release management can use to validate that $project has the correct
templates in place for all the automation to work.

Right now we're just checking-project as assuming that's good enough and
it probably is ;P but It'd still be cool if the REST API was there at
some point.

Yours Tony.


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

Re: [OpenStack-Infra] Infra Team PTG Dinner

[Tony Breeds]

On Sun, Sep 03, 2017 at 04:26:19PM -0700, Clark Boylan wrote:
> I'm not sure we need a doodle. Based on the etherpad Tuesday and
> Wednesday are the only two evenings everyone is in town and of those two
> Tuesday is the only day that hasn't already been listed as a conflict.
> 
> Can we go with Tuesday at the Lowry Beer Garden? I think there is a
> happy hour thing happening at the PTG that evening so we could meetup
> after that and shuttle over to the beer garden (looks like shouldn't be
> more than a 10-15 minute car ride).
> 
> Does this work?

#winning!

Thanks!

Yours Tony.


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

Re: [OpenStack-Infra] Group permissions - requirements-stable-core

[Tony Breeds]

On Mon, Jun 19, 2017 at 07:29:14PM +1000, Tony Breeds wrote:
> Hi All,
> We now have a requirement-sstable-core group.  Can we please set
> the owner to stable-maint-core, and add it as an included group, so the
> stable team can appoint new members.
> 
> This is similar to how we handle nova, keystone etc and by and large
> sets the initial group to the same people as before the requirements
> specific team existed.

Oh I see now that I'm a member I can do that myself.  Sorry for the
noise.

Yours Tony.


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

[OpenStack-Infra] Group permissions - requirements-stable-core

[Tony Breeds]

Hi All,
We now have a requirement-sstable-core group.  Can we please set
the owner to stable-maint-core, and add it as an included group, so the
stable team can appoint new members.

This is similar to how we handle nova, keystone etc and by and large
sets the initial group to the same people as before the requirements
specific team existed.

Tony
Yours Tony.




Yours Tony.


signature.asc
Description: PGP signature
___
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

[Tony Breeds]

On Thu, Feb 23, 2017 at 12:57:21PM +1100, Michael Still wrote:
> Certainly this is what nova has done in the past: collected co-authors,
> verified their membership status, and then proposed them to extra-atcs.

Where would this script live?

openstack/election ?
openstack-infra/release-tools ?

I know there was one but I knocked one together:
http://paste.openstack.org/show/600424

Tony.


signature.asc
Description: PGP signature
___
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

[Tony Breeds]

On Thu, Feb 23, 2017 at 08:27:49PM +, Henry Fourie wrote:
> Jeremy,
>Cathy is an owner of a recent commit: https://review.openstack.org/401349

That change is owned by Louie not Cathy.

Note I am not an election offical but the election timeline [2] states:

The electorate for this election are the Foundation individual members that
are also committers for one of the official project teams repositories over
the Newton-Ocata timeframe (Apr 11, 2016 00:00 UTC to Jan 23, 2017 23:59
UTC).

So from there we can deduce the following URL[2]:

https://review.openstack.org/#/q/after:2016-04-11+before:2017-01-24+is:merged+owner:cathy

Which would make Cathy eligable to vote in an election in Release Management
but not Neutron.

Yours Tony.

[1] https://governance.openstack.org/election/#electorate
[2] The date range in the URL is slightly more generous than the one specified
in [1]


signature.asc
Description: PGP signature
___
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

[Tony Breeds]

On Thu, Feb 23, 2017 at 12:44:43AM +, Tristan Cacqueray wrote:
> Hi,
> 
> The electorate roll generation tool[0] we used only collect owner of
> gerrit merged review and Cathy actually wasn't part of the Neutron's
> roll for Pike. It seems like the tool would need to also check for
> Co-Author in commit message, but afaik it's not possible to assert
> Foundation Member status solly based on mail address...
> 
> Perhaps for such case, co-author could be added to the extra-atc list?

Yup that's a per-project decision right now.  I s'pose we could ask for a TC
resolution to clarify / madate this if someone in the community felt strongly
enough about this.

Yours Tony.


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

Re: [OpenStack-Infra] [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

[Tony Breeds]

On Wed, Feb 08, 2017 at 09:55:41AM -0800, Ihar Hrachyshka wrote:
> Has the liberty-eol cleanup happened? Because I still see
> stable/liberty branch in openstack/neutron repo, which gets in the way
> of some logic around proactive backports:
> https://review.openstack.org/#/c/427936/4/bugs-fixed-since.py@75, and
> I see backports proposed for the branch that is no longer supported
> and has broken gate setup.

It seems I setup the second wave and then neglected to ask the infra team to 
process them.

Infra tema (*cough* Josh *cough*) can you remove the branches marke Please EOL 
in

https://gist.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4ac/raw/4f781426270cb2030f978f47b1f46dae6f5aecb4/liberty_eol_data.txt

Once that's done I can do a final pass for jobs that may break and we can drop
the devstack, devstack-gate and requirements branches.

Tony.


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

Re: [OpenStack-Infra] [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

[Tony Breeds]

On Wed, Dec 14, 2016 at 08:28:46PM -0800, Sumit Naiksatam wrote:
> On Wed, Dec 14, 2016 at 4:54 AM, Joshua Hesketh
>  wrote:
> > The repos listed[0] have had stable/liberty branch removed and replaced with
> > a liberty-eol tag. Any open reviews have been abandoned.
> >
> > Please let me know if there are any mistakes or latecomers to the list.
> 
> Hi Joshua, Apologies for chiming in late, but we request that the
> openstack/group-based-policy repo’s stable/liberty branch be _not_
> removed/EOL’ed and the currently open patches not be abandoned. We
> have consumers of this branch and we do backport bug fixes. Thanks in
> advance!

As Josh pointed out you're not in the list due to the problems we had retiring
kilo.

I do have a request for you though.  Currently your gate (both kilo and
liberty) relies on devstack and requirements and probably isn't testing what
you thin it is.  Can you please update project-config with a gate config that
will work on this branches *without* the need to keep liberty (and kilo) alive
in those repos.

If you need help feel free to reach out.

Yours Tony.


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

Re: [OpenStack-Infra] [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

[Tony Breeds]

On Tue, Nov 22, 2016 at 01:35:48PM +1100, Tony Breeds wrote:

> I'll batch the removal of the stable/liberty branches between Nov 28th and Dec
> 3rd (UTC+1100).  Then during Decemeber I'll attempt to cleanup 
> zuul/layout.yaml
> to remove liberty exclusions and jobs.

This took longer as there are a few repos that are scheduled for EOL that were a
little problematic during the kilo cycle.  I've updated the list at [1]

Can the infra team please run eol_branch.sh [2] over the repos listed at that
URL [1] and flagged with 'Please EOL'.  The others will need to be done later.

eol_branch.sh needs just the repo names what can be generated with something 
like:

URL=https://gist.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4ac/raw/liberty_eol_data.txt
eol_branch.sh REPOS=$(curl -s $URL | awk '/Please EOL/ {print $1}')

The data format is a balance between human and machine readable.

Yours Tony.

[1] 
https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt
[2] 
http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh


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

Re: [OpenStack-Infra] Tri-Weekly IRC meetings?

[Tony Breeds]

On Fri, Nov 11, 2016 at 03:10:04PM +0100, Thierry Carrez wrote:
> Blair Bethwaite wrote:
> > On 10 Nov 2016 8:56 PM, "Thierry Carrez"  > > wrote:
> >>
> >> The issue with this solution is that any "monthly" slot ends up being
> >> exactly the same as a "weekly" slot: you can't schedule any
> >> weekly/biweekly meetings at the same time and location. Monthly meetings
> >> are therefore paradoxically more wasteful than biweekly meetings, and
> >> there is therefore little point in adding them to the software since you
> >> can emulate them with "weekly" bookings and just skip most meetings.
> > 
> > That seems to be based on the assumption that other groups wouldn't want
> > monthly scheduling?
> > 
> > Also, I'd suggest we avoid "monthly" altogether and instead use
> > "4weekly", that would seem to allow biweekly meetings to use the same
> > day&time on the alternate (odd/even) week.
> 
> 4weekly sounds like a good idea! Less conflicts ftw.
> 
> If we really really want monthly stuff, we could create a channel
> dedicated to monthly meetings, to avoid creating conflicts on every
> channels.

I feel like there'is a tension here that we need to work through

is yaml2ical a library for others (outside OpenStack) to use?  If it is and
*they* want monthly meetings then I really think we shoudl include them.  The
conflict deection isn't *that* hard and the need for other recurrence types
would tidy the code.  So form this POV I htink we shoudl certainly allow for
this.

Within OpenStack, we have several groups that want Monthly meetings so we
shoudl work out a way to support that.

What we do right now is schedule a weekly meeting and then add a description to
say "we only hold this on thr nth $day" [1]

We could create a 4weekly which would reduce the wastage.  I'm also open to
creating #openstack-meeting-monthly and just moving all the monthly meetings
there.  I feel like we get asked for a solution to this often enough that we
need to define an answer.

Yours Tony.

[1] http://eavesdrop.openstack.org/#Documentation_User_Guides_Team_Meeting


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

Re: [OpenStack-Infra] Tri-Weekly IRC meetings?

[Tony Breeds]

On Wed, Nov 09, 2016 at 10:56:38AM +0100, Thierry Carrez wrote:

> Our scheduling system currently only supports biweekly or weekly
> meetings. We don't currently support monthly or triweekly meetings
> (mostly to avoid having to detect complex conflicts with biweekly meetings).
> 
> I guess we could evolve openstack-infra/yaml2ical to detect more complex
> conflicts. We'd gain in scheduling flexibility, but lose in our ability
> to pack the schedule tightly and make it pretty difficult to find empty
> slots manually.

Yeah I think we should add monthly (which would more-or-less cover triweekly)
In that you could have a monthly-1st, monthly-3rd and monthly-4th events.
---
  - time:   '1400'
day:Monday
irc:openstack-meeting
frequency:  monthly-1st # 1400 on the 1st Monday of the month
  - time:   '2100'
day:Thursday
irc:openstack-meeting-alt
frequency:  monthly-3rd # 2100 on the 3rd Thursday of the month
  - time:   '0930'
day:Thursday
irc:openstack-meeting-alt
frequency:  monthly-4th # 0930 on the 4th Thursday of the month
---

It isn't quite a tri-weekly rotation but may be close enough.

Of course adding this would mean adding tools to grok the data ad see if a
meeting slot is open

search-open --day Monday --time 1000 --freq weekly ?

Which could list the available irc channels or nothing.  Later it could be
extended to list "nearby options"

Yours Tony.


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

Re: [OpenStack-Infra] pypi mirrors out of sync

[Tony Breeds]

On Wed, Oct 12, 2016 at 03:11:14PM -0700, Clark Boylan wrote:

> I think I got this sorted out today. It broke on the 11th trying to sync
> a whole bunch of frida packages which took longer than our 30 minute
> timeout. I had to run bandersnatch several times in the foreground
> without a timeout to get it to reach a steady state then released the
> AFS volume. Current bandersnatch runs are falling well under the timeout
> so we should syncing automatically now as well.
> 
> We should probably tweak the timeout to make it longer to avoid these
> sorts of issues in the future.

Thanks everyone!


Yours Tony.


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

Re: [OpenStack-Infra] pypi mirrors out of sync

[Tony Breeds]

On Thu, Sep 22, 2016 at 12:28:48PM +1000, Tony Breeds wrote:
> Hi All,
> I know a lot of the infra team are in Germany for the sprint, howveer I'm
> see what seems like a lot of upper-constraint bumps that are failing due to
> mirrors being out of sync.

This seem to have happened again.

In review https://review.openstack.org/#/c/385099/ specifically the logs [1]

we see:
---
Could not find a version that satisfies the requirement oslo.policy===1.15.0 
(from -c 
/home/jenkins/workspace/gate-cross-nova-python27-db-ubuntu-xenial/upper-constraints.txt
 (line 225)) (from versions: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.3.2, 0.4.0, 0.5.0, 
0.6.0, 0.7.0, 0.8.0, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 1.0.0, 1.1.0, 
1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.11.0, 1.12.0, 
1.13.0, 1.14.0)
No matching distribution found for oslo.policy===1.15.0 (from -c 
/home/jenkins/workspace/gate-cross-nova-python27-db-ubuntu-xenial/upper-constraints.txt
 (line 225))
---

A quick check of https://pypi.python.org//simple/oslo-policy/ vs
http://mirror.regionone.osic-cloud1.openstack.org/pypi/simple/oslo-policy/
shows that 1.15.0 is on pypi but not our mirrors

For the sake of transparency this is basically the same thing I mentioned on
IRC[2]

Any chance we can get a manual run (of bandersnatch?) to clear the issues?

Yours Tony.

[1] 
htitp://logs.openstack.org/99/385099/1/check/gate-cross-nova-python27-db-ubuntu-xenial/3468229/console.html#_2016-10-12_04_18_53_131481
 
[2]
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-10-12.log.html#t2016-10-12T05:29:20


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

Re: [OpenStack-Infra] pypi mirrors out of sync

[Tony Breeds]

On Thu, Sep 22, 2016 at 06:32:59PM +1000, Ian Wienand wrote:

> So fungi started the process for a manual sync [1]; I had a look at
> the screen session he started about 30 minutes later.  I was too hasty
> and didn't save the screen session from fungi's run, but the sync that
> started seemed to be incomplete.  I did capture
> 
>   2016-09-22 04:44:41,143 INFO: Resuming interrupted sync from local todo 
> list.
> 
> from it, which might be related.
> 
> Anyway, I re-ran the mirror and it seemed to actually sync.  There's
> logs in mirror-update:root/screen0.log when I turned on logging in the
> screen session.
> 
> Once this finished I did a vos release on the pypi volume and it all
> seemed to go fine.  The above 0.9.7 package appears in the mirror.
> 
> So, very sorry for killing the output of the first run that might have
> been a good debugging point.  I'm guessing it cleared out something or
> other which let the second manual run work.  I have exited the screen
> session to release the mirror flock; but clearly we'll want to check
> on this for the next little bit.

Many thanks to Ian and fungi for takign care of this.

Several chnages that were blocked becuase of this are free to merge or have
merged.

Yours Tony.


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

[OpenStack-Infra] pypi mirrors out of sync

[Tony Breeds]

Hi All,
I know a lot of the infra team are in Germany for the sprint, howveer I'm
see what seems like a lot of upper-constraint bumps that are failing due to
mirrors being out of sync.

The most recent example of this is

https://review.openstack.org/374469/

where you can see:
---
Could not find a version that satisfies the requirement openstacksdk===0.9.7 
(from -c /opt/stack/new/requirements/upper-constraints.txt (line 205)) (from 
versions: 0.6.0, 0.6.1, 0.6.2, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.8.0, 0.8.1, 
0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 
0.9.6)
---

Checking pypi[2] shows:
 ...
openstacksdk-0.9.7.tar.gz
openstacksdk-0.8.6-py2.py3-none-any.whl
openstacksdk-0.9.7-py2.py3-none-any.whl
openstacksdk-0.7.3.tar.gz
...
But the mirror for that job[3] shows:
...
openstacksdk-0.9.5.tar.gz
openstacksdk-0.9.6.tar.gz
...

Is there some what we can frob the mirrors? or add a fallback to pypi if the
requested pacakge isn't there?

Yours Tony.

[1] 
http://logs.openstack.org/69/374469/2/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/e9af99d/logs/devstacklog.txt.gz#_2016-09-22_02_02_48_865
[2] https://pypi.python.org/simple/openstacksdk/
[3] http://mirror.mtl01.internap.openstack.org/pypi/simple/openstacksdk/


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

Re: [OpenStack-Infra] [openstack-dev] Announcing firehose.openstack.org

[Tony Breeds]

On Mon, Sep 19, 2016 at 10:50:31AM -0400, Matthew Treinish wrote:
> Hi Everyone,
> 
> I wanted to announce the addition of a new infra service we started running
> recently, the firehose. Running at firehose.openstack.org the firehose is an
> MQTT based unified message bus for infra services. The concept behind is it 
> that
> there are a lot of infra services many of which emit events, however there
> wasn't a single place to go to for anything. If you have a script or tool 
> which
> is listening for events from an infra service, or has a poll loop (like 
> anything
> using gerritlib) there is now a single place to go for consuming those 
> messages.
> We also have 2 interfaces to subscribe to topics on the firehose, either via 
> the
> MQTT protocol on the default port or via a websockets over port 80. The 
> websocket
> interface should enable easier consumption for people on networks with 
> stricter
> firewalls.

Awesome!  I have a fun little project I'm going to use this for.  Thanks
everyone involved.

Tony.


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

[OpenStack-Infra] eavesdrop.o.o site not updating.

[Tony Breeds]

Hi All,
It was pointed out that eavesdrop.o.o isn't updating.  It looks to be a
permissions problem after switching to the new zuul 2.5

For instance the last publish job's logs are at [1] and towards the end of [2]
we see:
---
2016-06-30 01:28:06,461 p=24849 u=zuul |  fatal: [node -> 127.0.0.1]: FAILED! 
=> {"changed": true, "cmd": "/usr/bin/rsync --delay-updates -F --compress -rt 
--safe-links --rsync-path=\"mkdir -p /srv/meetbot-openstack && rsync\" 
--rsh=\"/usr/bin/ssh -i /var/lib/zuul/ssh/id_rsa -S none -o 
StrictHostKeyChecking=no -q\" --out-format=\"<>%i %n%L\" 
`/usr/bin/find \"/tmp/tmpiMWk_1/staging/tmpA9wFLL\" -type f` 
\"jenk...@eavesdrop.openstack.org:/srv/meetbot-openstack\"", "delta": 
"0:00:00.299574", "end": "2016-06-30 01:28:06.439478", "failed": true, "rc": 
23, "start": "2016-06-30 01:28:06.139904", "stderr": "rsync: delete_file: 
unlink(index.html) failed: Permission denied (13)\ncould not make way for new 
regular file: index.html\nrsync error: some files/attrs were not transferred 
(see previous errors) (code 23) at main.c(1183) [sender=3.1.0]", "stdout": "", 
"stdout_lines": [], "warnings": ["Consider using synchronize module rather than 
running rsync"]}
---

Josh and I looked at this a while ago but it lost focus. Can we get
some reviews on:
https://review.openstack.org/#/q/topic:eavesdrop+is:open

Yours Tony.

[1] 
http://logs.openstack.org/93/93e9a07e6853b288f12fadd41cad65b50f5a7afa/post/irc-meetings-publish/31a5b06/
[2] 
http://logs.openstack.org/93/93e9a07e6853b288f12fadd41cad65b50f5a7afa/post/irc-meetings-publish/31a5b06/_zuul_ansible/ansible_log.txt


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

Re: [OpenStack-Infra] [stable] Tag and EOL kilo branches.

[Tony Breeds]

On Thu, Jun 09, 2016 at 05:15:06PM +1000, Tony Breeds wrote:
> Hello gerrit/git admins :)
> 
> When you have time can you please abandon the changes at:
> http://tiny.cc/os-kilo-still-open
> 
> And tag kilo-eol tag and deleet the stable/kilo branches from the repos 
> listsed
> in the attached yaml file.

It seems that group-baseed-policy would like to keep the stable/kilo branch 
alive.

I have updated the list of open reviews at:
http://tiny.cc/os-kilo-still-open
Provided a review to drop the dsvm jobs from the kilo branch of
group-baseed-policy at:
https://review.openstack.org/#/c/328011/

Please find attached a list of repos to EOL and tag

Tony.
---
- openstack-dev/devstack
- openstack-dev/grenade
- openstack-dev/pbr
- openstack/astara
- openstack/astara-appliance
- openstack/astara-horizon
- openstack/astara-neutron
- openstack/barbican
- openstack/bareon-ironic
- openstack/ceilometermiddleware
- openstack/cliff
- openstack/cloudkitty
- openstack/cloudkitty-dashboard
- openstack/cloudpulse
- openstack/compute-hyperv
- openstack/congress
- openstack/debtcollector
- openstack/designate
- openstack/django_openstack_auth
- openstack/dragonflow
- openstack/ec2-api
- openstack/freezer
- openstack/freezer-api
- openstack/freezer-web-ui
- openstack/fuel-plugin-purestorage-cinder
- openstack/glance_store
- openstack/keystonemiddleware
- openstack/kolla
- openstack/magnum
- openstack/manila
- openstack/manila-ui
- openstack/mistral
- openstack/mistral-dashboard
- openstack/mistral-extra
- openstack/murano
- openstack/murano-agent
- openstack/murano-dashboard
- openstack/networking-arista
- openstack/networking-bagpipe
- openstack/networking-bigswitch
- openstack/networking-brocade
- openstack/networking-cisco
- openstack/networking-hyperv
- openstack/networking-l2gw
- openstack/networking-midonet
- openstack/networking-mlnx
- openstack/networking-nec
- openstack/networking-odl
- openstack/networking-ofagent
- openstack/networking-ovs-dpdk
- openstack/networking-plumgrid
- openstack/networking-vsphere
- openstack/neutron-fwaas
- openstack/nova-docker
- openstack/nova-solver-scheduler
- openstack/openstack-chef-repo
- openstack/openstack-manuals
- openstack/openstack-resource-agents
- openstack/oslo-incubator
- openstack/oslo.concurrency
- openstack/oslo.config
- openstack/oslo.context
- openstack/oslo.db
- openstack/oslo.i18n
- openstack/oslo.log
- openstack/oslo.messaging
- openstack/oslo.middleware
- openstack/oslo.policy
- openstack/oslo.rootwrap
- openstack/oslo.serialization
- openstack/oslo.utils
- openstack/oslo.versionedobjects
- openstack/oslo.vmware
- openstack/oslosphinx
- openstack/oslotest
- openstack/powervc-driver
- openstack/puppet-ceilometer
- openstack/puppet-cinder
- openstack/puppet-designate
- openstack/puppet-glance
- openstack/puppet-gnocchi
- openstack/puppet-heat
- openstack/puppet-horizon
- openstack/puppet-ironic
- openstack/puppet-keystone
- openstack/puppet-manila
- openstack/puppet-neutron
- openstack/puppet-nova
- openstack/puppet-openstack-integration
- openstack/puppet-openstack_extras
- openstack/puppet-openstacklib
- openstack/puppet-sahara
- openstack/puppet-swift
- openstack/puppet-tempest
- openstack/puppet-tripleo
- openstack/puppet-trove
- openstack/puppet-tuskar
- openstack/puppet-vswitch
- openstack/pycadf
- openstack/python-barbicanclient
- openstack/python-ceilometerclient
- openstack/python-cinderclient
- openstack/python-cloudkittyclient
- openstack/python-cloudpulseclient
- openstack/python-congressclient
- openstack/python-designateclient
- openstack/python-ganttclient
- openstack/python-glanceclient
- openstack/python-heatclient
- openstack/python-ironicclient
- openstack/python-keystoneclient
- openstack/python-magnumclient
- openstack/python-manilaclient
- openstack/python-mistralclient
- openstack/python-muranoclient
- openstack/python-neutronclient
- openstack/python-novaclient
- openstack/python-openstackclient
- openstack/python-saharaclient
- openstack/python-swiftclient
- openstack/python-tackerclient
- openstack/python-troveclient
- openstack/python-zaqarclient
- openstack/requirements
- openstack/sahara-extra
- openstack/sahara-image-elements
- openstack/stevedore
- openstack/swift
- openstack/swiftonfile
- openstack/tacker
- openstack/tacker-horizon
- openstack/taskflow
- openstack/tooz
- openstack/training-labs
- openstack/vmware-nsx
- openstack/yaql
- openstack/zaqar


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

[OpenStack-Infra] [stable] Tag and EOL kilo branches.

[Tony Breeds]

Hello gerrit/git admins :)

When you have time can you please abandon the changes at:
http://tiny.cc/os-kilo-still-open

And tag kilo-eol tag and deleet the stable/kilo branches from the repos listsed
in the attached yaml file.

Yours Tony.
---
- openstack-dev/devstack
- openstack-dev/grenade
- openstack-dev/pbr
- openstack/astara
- openstack/astara-appliance
- openstack/astara-horizon
- openstack/astara-neutron
- openstack/barbican
- openstack/bareon-ironic
- openstack/ceilometermiddleware
- openstack/cliff
- openstack/cloudkitty
- openstack/cloudkitty-dashboard
- openstack/cloudpulse
- openstack/compute-hyperv
- openstack/congress
- openstack/debtcollector
- openstack/designate
- openstack/django_openstack_auth
- openstack/dragonflow
- openstack/ec2-api
- openstack/freezer
- openstack/freezer-api
- openstack/freezer-web-ui
- openstack/fuel-plugin-purestorage-cinder
- openstack/glance_store
- openstack/group-based-policy
- openstack/group-based-policy-automation
- openstack/group-based-policy-ui
- openstack/keystonemiddleware
- openstack/kolla
- openstack/magnum
- openstack/manila
- openstack/manila-ui
- openstack/mistral
- openstack/mistral-dashboard
- openstack/mistral-extra
- openstack/murano
- openstack/murano-agent
- openstack/murano-dashboard
- openstack/networking-arista
- openstack/networking-bagpipe
- openstack/networking-bigswitch
- openstack/networking-brocade
- openstack/networking-cisco
- openstack/networking-hyperv
- openstack/networking-l2gw
- openstack/networking-midonet
- openstack/networking-mlnx
- openstack/networking-nec
- openstack/networking-odl
- openstack/networking-ofagent
- openstack/networking-ovs-dpdk
- openstack/networking-plumgrid
- openstack/networking-vsphere
- openstack/neutron-fwaas
- openstack/nova-docker
- openstack/nova-solver-scheduler
- openstack/openstack-chef-repo
- openstack/openstack-manuals
- openstack/openstack-resource-agents
- openstack/oslo-incubator
- openstack/oslo.concurrency
- openstack/oslo.config
- openstack/oslo.context
- openstack/oslo.db
- openstack/oslo.i18n
- openstack/oslo.log
- openstack/oslo.messaging
- openstack/oslo.middleware
- openstack/oslo.policy
- openstack/oslo.rootwrap
- openstack/oslo.serialization
- openstack/oslo.utils
- openstack/oslo.versionedobjects
- openstack/oslo.vmware
- openstack/oslosphinx
- openstack/oslotest
- openstack/powervc-driver
- openstack/puppet-ceilometer
- openstack/puppet-cinder
- openstack/puppet-designate
- openstack/puppet-glance
- openstack/puppet-gnocchi
- openstack/puppet-heat
- openstack/puppet-horizon
- openstack/puppet-ironic
- openstack/puppet-keystone
- openstack/puppet-manila
- openstack/puppet-neutron
- openstack/puppet-nova
- openstack/puppet-openstack-integration
- openstack/puppet-openstack_extras
- openstack/puppet-openstacklib
- openstack/puppet-sahara
- openstack/puppet-swift
- openstack/puppet-tempest
- openstack/puppet-tripleo
- openstack/puppet-trove
- openstack/puppet-tuskar
- openstack/puppet-vswitch
- openstack/pycadf
- openstack/python-barbicanclient
- openstack/python-ceilometerclient
- openstack/python-cinderclient
- openstack/python-cloudkittyclient
- openstack/python-cloudpulseclient
- openstack/python-congressclient
- openstack/python-designateclient
- openstack/python-ganttclient
- openstack/python-glanceclient
- openstack/python-group-based-policy-client
- openstack/python-heatclient
- openstack/python-ironicclient
- openstack/python-keystoneclient
- openstack/python-magnumclient
- openstack/python-manilaclient
- openstack/python-mistralclient
- openstack/python-muranoclient
- openstack/python-neutronclient
- openstack/python-novaclient
- openstack/python-openstackclient
- openstack/python-saharaclient
- openstack/python-swiftclient
- openstack/python-tackerclient
- openstack/python-troveclient
- openstack/python-zaqarclient
- openstack/requirements
- openstack/sahara-extra
- openstack/sahara-image-elements
- openstack/stevedore
- openstack/swift
- openstack/swiftonfile
- openstack/tacker
- openstack/tacker-horizon
- openstack/taskflow
- openstack/tooz
- openstack/training-labs
- openstack/vmware-nsx
- openstack/yaql
- openstack/zaqar


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

Re: [OpenStack-Infra] What is openstack-infra/ansible-build-image ?

[Tony Breeds]

On Tue, May 17, 2016 at 02:24:49PM +, Jeremy Stanley wrote:

> We normally make the governance addition change depend on the infra
> addition change, but that got overlooked in this case and the TC
> approved a repo which doesn't exist yet.

Yeah in this case the dependencies were the other way around.  Which is
probably why the TC approved it :)

Yours Tony.


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

Re: [OpenStack-Infra] What is openstack-infra/ansible-build-image ?

[Tony Breeds]

On Tue, May 17, 2016 at 09:17:37AM -0400, Paul Belanger wrote:
> See review 166547[2], it is still an open review. Once mordred is back from
> vacation we should be able to follow up on this.

Ahh okay, I'll leave it be then.  I have to admit I did't look in
project-config I should have.

Yours Tony.


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

[OpenStack-Infra] What is openstack-infra/ansible-build-image ?

[Tony Breeds]

Hi All,
I'm currently writing a tool to help me find out which repos in the big
tent I should try to EOL with kilo, but that's not really to point of this
message.

My "super awesome(tm)" script failed with[1]:
---
Traceback (most recent call last):
  File "get-stable-branches.py", line 48, in 
if check_has_branch(git_base, repo, eol_branch):
  File "get-stable-branches.py", line 24, in check_has_branch
with setcwd(os.path.join(base, repo)):
  File "get-stable-branches.py", line 17, in __enter__
os.chdir(self.new_dir)
OSError: [Errno 2] No such file or directory: 
'/Users/tony8129/projects/openstack/openstack-infra/ansible-build-image'
---

Which basically means I don't have that repo locally.  I did a fresh update-all
(which will clone new projects) and it's still not there.  So I checked and
it's in in the output of "ssh review gerrit ls-projects"

A little git archaeology shows that it was added to projects.yaml with
I22bc72a4683e2a24b4575abcdac35122df8c57e1 just over a year ago.

So what is openstack-infra/ansible-build-image ?
Should it still be listed in projects.yaml?

Yours Tony.
[1] Not so super awesome after all ;P


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

Re: [OpenStack-Infra] UNSTABLE jobs on the periodic-stable pipeline

[Tony Breeds]

On Tue, May 03, 2016 at 04:57:02PM +1000, Joshua Hesketh wrote:
> Hey,
> 
> Yolanda is helping repair this. Basically the log filesystem needs
> repairing and should be back shortly.

Thanks for the prompt response.

Yours Tony.


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

[OpenStack-Infra] UNSTABLE jobs on the periodic-stable pipeline

[Tony Breeds]

So the subject says it all really ;P

The last batch of periodic-stable jobs all failed reporting 'UNSTABLE' as the 
result.

The ones I checked had missing log files.

eg 
http://lists.openstack.org/pipermail/openstack-stable-maint/2016-May/004275.html

I reported this on IRC but just in case that gets lost in the scrollback I 
thought I'd also drop it here.

Yours Tony.


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

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

[Tony Breeds]

Hi All,
I see that my review[1] to add devstack-plugin-additional-pkg-repos has 
merged
and the import from github has completed[2].

Can you please add my (gerrit ID tonyb) to gerrit groups:
 * devstack-plugin-apr-core
 * devstack-plugin-apr-release

If possible with rights to add members to those groups.  If that isn't possible
then I'll come back with additional members for the "core" team.

Thanks,
Tony.

[1] https://review.openstack.org/#/c/293775/
[2] 
https://review.openstack.org/gitweb?p=openstack/devstack-plugin-additional-pkg-repos.git;a=shortlog;h=refs/heads/master


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

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

[Tony Breeds]

On Thu, Mar 17, 2016 at 08:37:52PM -0400, Paul Belanger wrote:

> Greeting OpenStack contributor! I've successfully added you to both groups.
> Happy hacking.

Yagg thanks mtey!
(for Anita)

Yours Tony.


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

Re: [OpenStack-Infra] Missing content from project-team-guide

[Tony Breeds]

On Tue, Dec 15, 2015 at 04:34:00PM +, Jeremy Stanley wrote:

> If you look at the job log for the last two commits in the repo's
> history, you'll see we have a bit of a publication race when
> multiple changes are approved at roughly the same time. If the
> first[1] change takes slightly longer to complete than the second[2]
> then the resulting publication represents the older of the two. This
> will "correct" itself the next time someone approves another change
> to that repo.

Thanks Jeremy

Yours Tony.


pgpc5P8kTeo2C.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Missing content from project-team-guide

[Tony Breeds]

Hi All,
I'm not really sure what could have gone wrong but heres the context.

[1] Merged and the publish job ran [2], AFICT successfully. The hunk that
was added in [1] isn't visible.  Compare [3] with [4]

A quick check with:
---
(docs)$ git remote update
Fetching origin
Fetching gerrit
(docs)$ git show --oneline HEAD
b15b9a7 Merge "stable: open doors for 'safe' backports in Phase 2+"

(docs)$ python setup.py --version
0.0.1.dev67
---
Looking at the footer of [4] it says OpenStack Project Team Guide 0.0.1.dev65 
documentation

My questions are:
1) Is it possible to re-publish origin/master
2) Any idea how things got out of sync?

Tony.

[1] https://review.openstack.org/#/c/247415/
[2] https://jenkins03.openstack.org/job/project-team-guide-publish/4/console
[3] 
http://docs-draft.openstack.org/15/247415/1/gate/gate-project-team-guide-docs/30096b8//doc/build/html/stable-branches.html#support-phases
[4] 
http://docs.openstack.org/project-team-guide/stable-branches.html#support-phases



pgpFhgAjk0sEh.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] [openstack-dev] [devstack] Upgrading Icehouse to Juno

[Tony Breeds]

On Mon, Dec 07, 2015 at 10:58:18AM +0530, Abhishek Shrivastava wrote:
> Hi Folks,
> 
> I have a stable/icehouse devstack setup and I am planning to upgrade it to
> stable/kilo but following the guide mentioned in Openstack Manuals does not
> seems to work correctly.

Umm you don't really upgrade a devstack install.  Just start from scratch on
the new release (and I'd suggest liberty rather than juno or kilo).

If you've managed to get production data in you icehouse devstack, preserving
that is a different discussion.

Yours Tony.


pgpg3NF6gYk1P.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] logstash URL queries.

[Tony Breeds]

On Fri, Oct 16, 2015 at 11:37:45AM -0400, Sean Dague wrote:

> It turns out new kibana is more strict on quotes.
> project:"openstack/requirements" with your query works correctly.

Ah okay.  Thanks Sean.
 
Yours Tony.


pgpjypd5agHb9.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] logstash URL queries.

[Tony Breeds]

On Fri, Oct 16, 2015 at 10:24:58AM -0400, Matthew Treinish wrote:

> That's better than what I get, when I click it I get an empty bar.

Oh ... click in that empty bar and you get the URL.

Yours Tony.


pgpXUdMOI4Arn.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] logstash URL queries.

[Tony Breeds]

Hi Everybody,
So it looks to me like we recently updated logstash.openstack.org to a
newer version of kibabna?

I'll very openly admit that my logstash fu is wanting but I'm having a little
trouble

1) I can't work out how to after performing my query/filtering share the
   results (for example in a LP bug).  I tried using the sharable link but it
   always comes up with:
   http://logstash.openstack.org/#dashboard/undefined/undefined
   and that URL doesn't work by magic :(

   How do we share queries now?

2) It looks to me like all our old saved URLs are now invalid, this is a big of
   a problem for open bugs with logstash URLs in them.

   Is there anyway we can make the old URLs work again?

3) I'm sure that the following is a valid query:
   message:"ValueError: git history requires a target version of 
pbr.version.SemanticVersion(5.0.1), but target version is 
pbr.version.SemanticVersion(5.0.0)" AND tags:"console" AND 
project:openstack/requirements
   but it just spins and never seems to return any matches.  If instead I set
   the query to :
   message:"ValueError: git history requires a target version of 
pbr.version.SemanticVersion(5.0.1), but target version is 
pbr.version.SemanticVersion(5.0.0)"
   and use the UI to add filters for tags:"console" and 
project:openstack/requirements

   I do get some results.

   Is there a problem with my query or the backend?

Just to be clear, I don't mean this email to sound like I'm complaining, I'm
just confused and looking for help.


Yours Tony.


pgpoQIIb7VFh_.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

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

[Tony Breeds]

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

For those playing along at home:
https://review.openstack.org/#/c/230167/

Yours Tony.


pgpRbYiytZf2b.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Scheduling a monthly meeting

[Tony Breeds]

On Tue, Jun 16, 2015 at 04:00:52PM +0800, Tom Fifield wrote:
> Hi all,
> 
> A couple of things I'm working on at the moment would like to meet on a
> monthly basis.
> 
> From irc-meetings: " Options for the `frequency` are `weekly`,
> `biweekly-even`, and  `biweekly-odd` at the moment.", and in
> yaml2ical/recurrence.py [1] it's pretty clear that there's no support
> for Monthly.
> 
> So ... first question: is there some enormous trap that means adding
> support to the code for monthly meetings is best avoided/really hard?

I coded this up before the summit but after talking to Thierry I abanonded it
due to the resource utilisation concerens which I agree are valid and not
something I'd considered.

Yours Tony.


pgpT8m9ZYbdxI.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Nodepool for ubuntu vivid.

[Tony Breeds]

On Fri, Jun 05, 2015 at 12:55:19PM +1000, Ian Wienand wrote:
> On 06/05/2015 12:02 PM, Tony Breeds wrote:
> >> Don't plan on doing much else
> > 
> > Ever? or just for sometime while I get it going?
> 
> The thing is that it's only ever one commit way from not-going.  Given
> the rate of change not just of Open Stack, but everything it sits
> on-top of, you should expect to spend considerable time just
> maintaining it.

Hmm okay. I didn't realise that the nodepool images were so fragile.

I have to admit I assumed it'd more or less be:
grab the vivid.img from $cloud-provider / Canonical
customise
save and upload.

Looks like I have a lot more learning to do.

Thanks Ian.
 
Yours Tony.


pgp_ofTbHYkVM.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Nodepool for ubuntu vivid.

[Tony Breeds]

On Fri, Jun 05, 2015 at 11:49:58AM +1000, Ian Wienand wrote:
 
> There is not.  First thing is probably to make it so diskimage-builder is
> creating vivid images (maybe it is already, I don't know)
> 
> At that point, you should boot that image and try out the devstack-gate
> scripts to ensure that we can do all the stuff puppet does by following [1]
> 
> After that, you can propose adding the images, see the f22 example [2]
> 
> After that, nodepool will build them, you can see the logs at [3].  It
> never quite works the same there, so expect it to fail at first :)
> 
> After that, in theory, you should have nodes ready to go.  We can then
> bring up a job that runs on that node ... there's a few tricks but we
> can cross that bridge when we get there.  Again the Fedora job is a
> good template.

Thanks.  I'll look at all that.  That's many of the missing pieces.

> >2) Have someone on the infra team help/mentor me through the process
> >   for 15.04 so that I can do 15.10 by myself.
> 
> I've been through all this multiple times with Red Hat platforms.
> Happy to help.
> 
> >Also council me on what I'm signing up for ;P
> 
> Don't plan on doing much else

Ever? or just for sometime while I get it going?

Yours Tony.


pgpXjPlbBvIUE.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] Nodepool for ubuntu vivid.

[Tony Breeds]

Hi All,
CLearly I'm new here and I appologise if this is a stale topic.  I also
apologise for this being somewhat incoherant.

I'd like to test the current dev release of ubuntu (15.04) in the gate. 
If I read nodepool.yaml.erb correctly then there currently isn't a nodepool
image defined for this.

I'd also like to do this in such a way that makes it easy to switch to 15.10
when that comes out.

My aims for doing this are:
1) http://docs.openstack.org/developer/devstack/overview.html
   claims we "support" devstack on the current ubuntu dev release so we shoudl 
probably try that :)
   Perhaps I'm mistaken but I'd expect that if do the intermediate dev releases
   then when a new LTS comes out there shoudl be less surprises.
2) I'd like to be able to test nova with "bleeding edge" qemu/libvirt
   *releases*.  My aim is to use a devstack plugin for that but I'd also like a
   job on the experimental queue and this ubuntu image would be the base for 
that.

What I'd like to achieve form this discussion is
1) Does this sound reasonable to the infra team?
2) Have someone on the infra team help/mentor me through the process for 15.04
   so that I can do 15.10 by myself.  Also council me on what I'm signing up 
for ;P

Note: As I said I'm happy to do this (with help) but right now I'm not in a
position to committ to a timeline.

Yours Tony.


pgpTRKjt9u8Yv.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] PTL election season?

[Tony Breeds]

On Thu, Mar 12, 2015 at 11:00:07PM +, Jeremy Stanley wrote:
 
> I'm not sure why this is an -infra ML topic, but from what I've seen
> those have all been unofficial projects which are trying to apply
> for official status with the TC under the new "big tent" model and
> as such need to meet the requirement of having an elected PTL.

Thanks.

Sorry if this wasn't an appropriate venue.
 
Yours Tony.


pgpvWMJMmF3Pr.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[OpenStack-Infra] PTL election season?

[Tony Breeds]

Hi All,
I have a quick question.  I;m seeing some projects self announce candidates
for PTL but I don't recall seeing a "Election season is open" email.  Did I
miss something or are these projects ahead of the game?

Yours Tony.


pgp9uHFcVIZA7.pgp
Description: PGP signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra