Re: [OpenStack-Infra] IMPORTANT upcoming change to technical elections

[Jeremy Stanley]

On 2017-08-03 02:33:30 + (+), Jeremy Stanley wrote:
[...]
> I am attaching a list of OpenStack Foundation Individual Member
> IDs and names for contributors to official deliverable
> repositories between 2016-09-17 and the present (members.txt.gz,
> 2315 entries in total, these should be eligible to vote in
> elections for projects to which they contributed if a runoff is
> held). I'm also attaching a list of the names of contributors over
> the same time period who could not be automatically matched up to
> foundation membership profiles (nonmembers.txt.gz, 291 entries in
> total).
[...]

Unfortunately those attachments had to be gzip-compressed to keep
the total message under our 40KiB moderation limit, and so may not
be easily readable by some mail clients. With that in mind, I've
pasted the lists at the following URLs as well:

members.txt - http://paste.openstack.org/raw/617357/

nonmembers.txt - http://paste.openstack.org/raw/617358

-- 
Jeremy Stanley


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

Re: [OpenStack-Infra] IMPORTANT upcoming change to technical elections

[Jeremy Stanley]

On 2017-07-17 16:17:00 + (+), Jeremy Stanley wrote:
> If you want to run or vote in upcoming elections for PTL and TC,
> make sure your Foundation Individual Membership is active and has at
> least one Email address which matches an Email address in your
> Gerrit account: log in at https://www.openstack.org/profile/ and
> check that it says "Current Member Level: Foundation Member" near
> the top and that at least one of the Primary, Second or Third Email
> Address fields contains an address which matches at least one of the
> entries available in the Preferred Email drop-down at
> https://review.openstack.org/#/settings/contact (case sensitivity
> doesn't matter but they at least need to be spelled the same).
> 
> If you're an "extra-ATC" and don't have a Gerrit account (this is
> common for translators on the I18n team) then you still need to be a
> Foundation Member to participate in technical elections and should
> make sure your member profile includes the Email address listed for
> you on your team's page at
> https://governance.openstack.org/tc/reference/projects/ .
[...]

For those who haven't double-checked their memberships, I am
attaching a list of OpenStack Foundation Individual Member IDs and
names for contributors to official deliverable repositories between
2016-09-17 and the present (members.txt.gz, 2315 entries in total,
these should be eligible to vote in elections for projects to which
they contributed if a runoff is held). I'm also attaching a list of
the names of contributors over the same time period who could not be
automatically matched up to foundation membership profiles
(nonmembers.txt.gz, 291 entries in total).

If you want to vote in upcoming elections and your membership isn't
lining up with your contributor account/addresses (that is to say,
your name is in the attached nonmembers.txt.gz file) then please
follow the quoted instructions above from my earlier message as soon
as possible.
-- 
Jeremy Stanley


members.txt.gz
Description: application/gzip


nonmembers.txt.gz
Description: application/gzip


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

[OpenStack-Infra] Opendayight Internship (Jenkins job builder) Week 9 status update July 24th - July 30th 2017

[Yolande Amate]

Hi,

This past week I did the following:

-Thoroughly went through the list of plugins currently installed in
OpenDaylight's production system to find those which currently lack support
or have missing features in Jenkins job builder.

-Did some findings on how to add support for a new plugin to Jenkins Job
Builder.

This week, I plan to:

- Add support for new plugin/plugin features
- Respond to code review
- Do code review

Attached below is a link to my Jenkins job builder project proposal
document with a table of plugins(under activity details) that I have worked
on so far[1].

Cheers,
Yolande

[1]
https://docs.google.com/document/d/13YGxDwt76K5mhRUlmC_bzXK_mCRSiVGStp-CJL4VYtA/edit#
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [OpenStack-Infra] Tag stable/mitaka as eol for Monasca Ceilometer

[Hochmuth, Roland M]

Hi Ashwin and Andreas, Yes, you can eol stable/mitaka for 
openstack/monasca-ceilometer. Regards --Roland

On 7/25/17, 12:03 PM, "Ashwin Agate"  wrote:

Hi Roland,

Can you please confirm? I think we can safely eol stable/mitaka for
monasca-ceilometer. Should we bring it up in the weekly meeting
tomorrow?

Thanks
Ashwin

On Thu, 2017-07-20 at 08:45 +0200, Andreas Jaeger wrote:
> On 2017-07-19 20:29, Ashwin Agate wrote:
> > 
> > Hi,
> > 
> > Can you please delete stable/mitaka branch for openstack/monasca-
> > ceilometer project and create a mitaka-eol tag?
> > 
> > Please see https://review.openstack.org/#/c/484494/6 for some
> > discussion with Andreas Jaeger on this subject.
> 
> Roland, as PTL, can you confirm, please?
> 
> Andreas


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

[OpenStack-Infra] Zuulv3 discussion on pbx.o.o

[Paul Belanger]

Greetings,

We had a voice discussion on pbx.o.o today, wanted to give a summary for people
following at home.

jeblair, mordred, fungi and myself held it on sip:6...@pbx.openstack.org.

The initial question posed by myself was how to best organize our tarballs.o.o
publisher for tox jobs. This came as a result of me working on the new zuulv3
jobs to handle this.

The main issue was because we need to add_host (ansible) for tarballs.o.o within
a playbook / role, where would this best be done.  Adding it to our base job
didn't make much sense, since not all jobs need access to tarballs.o.o.

After a quick discussion, it was decided we'd create a new job (trusted 
playbook)
in project-config called 'tox-publisher' (name open to bike shed), that would
parent to tox-tarball.

This then evolved into if we actually need to upload a tarball to tarballs.o.o,
before then publishing to pypi, eventually we agreed it is still useful because
of master branch tarballs.

We then realized we needed to GPG sign our tarball files, but quickly found our
length of 4096 bits limit [1] would be an issue for our GPG sub keys. jeblair
propose we revisit and implement our solution for the 4096 limitation[2].
However mordred / fungi believe breaking our secret up into 4096 chucks and
creating a secret object / list would also allow us to work around the limit.

It was proposed that zuulv3 would already know how to read this list of secrets
and concat them together a job run time creating the whole secret. We agree this
might be worth doing.

This is very high level of the discussion we had.

[1] 
https://docs.openstack.org/infra/zuul/feature/zuulv3/user/encryption.html#encryption
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-March/114398.html

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