Re: [openstack-dev] [all] [elections] Technical Committee Election Results

[Arkady.Kanevsky]

Congrats to all

From: Edgar Magana [mailto:edgar.mag...@workday.com]
Sent: Saturday, October 21, 2017 12:00 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [all] [elections] Technical Committee Election 
Results

An awesome team! Thanks for willing to continue the hard work of on the TC.

Cheers,

Edgar Magana

On Oct 21, 2017, at 6:56 AM, Amy Marrich 
> wrote:
Congrats everyone!

On Fri, Oct 20, 2017 at 6:59 PM, Kendall Nelson 
> wrote:
Hello Everyone :)

Please join me in congratulating the 6 newly elected members of the Technical 
Committee (TC)!

Colleen Murphy (cmurphy)
Doug Hellmann (dhellmann)
Emilien Macchi (emilienm)
Jeremy Stanley (fungi)
Julia Kreger (TheJulia)
Paul Belanger (pabelanger)

Full results: 
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ce86063991ef8aae

Election process details and results are also available here: 
https://governance.openstack.org/election/

Thank you to all of the candidates, having a good group of candidates helps 
engage the community in our democratic process.

Thank you to all who voted and who encouraged others to vote. We need to ensure 
your voice is heard.

Thank you for another great round.
-Kendall Nelson (diablo_rojo)

[1] 
https://review.openstack.org/#/c/513881/

__
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
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=_MZICzb6CeQO95qx98u8CjXJmL5mGEEXSfWKUHNzJrs=8zikRlZwVoA05HuwKswWyLaWXjuioxs6SJW_LjXQ_Q0=
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] latest centos iptables rpm broke tripleo ci

[Emilien Macchi]

On Sat, Oct 21, 2017 at 7:42 AM, Wesley Hayutin  wrote:
> Greetings,
>
> TripleO CI started to hit errors in any of the multinode node pool jobs last
> Friday afternoon.
> Please review the bug and patch to bring CI back online [1-2]
>
> More work needs to be done to discover exactly why the latest rpm breaks the
> vxlan network link between nodes.  It's also a good time to investigate
> options regarding additional gatting for CentOS packages.  This patch brings
> TripleO CI back online, but does not close the issue.
>
> Thanks, have a good weekend.
>
> [1] https://bugs.launchpad.net/tripleo/+bug/1725451
> [2] https://review.openstack.org/#/c/513891/
>

Just an FYI bis - David is working on a fix in the zuul-v3 playbooks,
which will probably help to solve the root cause issue:
https://review.openstack.org/#/c/513943/

Thanks Wes & David for helping out,
-- 
Emilien Macchi

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

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

[Edgar Magana]

An awesome team! Thanks for willing to continue the hard work of on the TC.

Cheers,

Edgar Magana

On Oct 21, 2017, at 6:56 AM, Amy Marrich 
> wrote:

Congrats everyone!

On Fri, Oct 20, 2017 at 6:59 PM, Kendall Nelson 
> wrote:
Hello Everyone :)

Please join me in congratulating the 6 newly elected members of the Technical 
Committee (TC)!

Colleen Murphy (cmurphy)
Doug Hellmann (dhellmann)
Emilien Macchi (emilienm)
Jeremy Stanley (fungi)
Julia Kreger (TheJulia)
Paul Belanger (pabelanger)

Full results: 
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ce86063991ef8aae

Election process details and results are also available here: 
https://governance.openstack.org/election/

Thank you to all of the candidates, having a good group of candidates helps 
engage the community in our democratic process.

Thank you to all who voted and who encouraged others to vote. We need to ensure 
your voice is heard.

Thank you for another great round.

-Kendall Nelson (diablo_rojo)

[1] 
https://review.openstack.org/#/c/513881/

__
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
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=_MZICzb6CeQO95qx98u8CjXJmL5mGEEXSfWKUHNzJrs=8zikRlZwVoA05HuwKswWyLaWXjuioxs6SJW_LjXQ_Q0=
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] latest centos iptables rpm broke tripleo ci

[Wesley Hayutin]

Greetings,

TripleO CI started to hit errors in any of the multinode node pool jobs
last Friday afternoon.
Please review the bug and patch to bring CI back online [1-2]

More work needs to be done to discover exactly why the latest rpm breaks
the vxlan network link between nodes.  It's also a good time to investigate
options regarding additional gatting for CentOS packages.  This patch
brings TripleO CI back online, but does not close the issue.

Thanks, have a good weekend.

[1] https://bugs.launchpad.net/tripleo/+bug/1725451
[2] https://review.openstack.org/#/c/513891/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] [elections] Technical Committee Election Results

[Amy Marrich]

Congrats everyone!

On Fri, Oct 20, 2017 at 6:59 PM, Kendall Nelson 
wrote:

> Hello Everyone :)
>
> Please join me in congratulating the 6 newly elected members of the
> Technical Committee (TC)!
>
> Colleen Murphy (cmurphy)
> Doug Hellmann (dhellmann)
> Emilien Macchi (emilienm)
> Jeremy Stanley (fungi)
> Julia Kreger (TheJulia)
> Paul Belanger (pabelanger)
>
> Full results: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_
> ce86063991ef8aae
>
> Election process details and results are also available here:
> https://governance.openstack.org/election/
>
> Thank you to all of the candidates, having a good group of candidates
> helps engage the community in our democratic process.
>
> Thank you to all who voted and who encouraged others to vote. We need to
> ensure your voice is heard.
>
> Thank you for another great round.
>
> -Kendall Nelson (diablo_rojo)
>
> [1] https://review.openstack.org/#/c/513881/
>
> __
> 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

Re: [openstack-dev] Fwd: [Openstack-operators][tc] [keystone][all] v2.0 API removal

[Jeremy Stanley]

On 2017-10-20 22:50:53 + (+), Fox, Kevin M wrote:
[...]
> Ideally, there should be an OpenStack overarching architecture
> team of some sort to handle this kind of thing I think.

There was one for a while, but it dissolved due to lack of community
participation. If you'd like to help reboot it, Clint B. can
probably provide you with background on the previous attempt.

> Without such an entity though, I think the TC is probably
> currently the best place to discuss it though?

Contrary to the impression some people seem to have, the TC is not
primarily composed of cloud architects; it's an elected body of
community leaders who seek informed input from people like you. I've
personally found no fault in the process and timeline the Keystone
team followed in this situation but I'm also not the primary
audience for their software, so it's good to hear from those who are
about ways to improve similar cases in the future. However, I also
understand that no matter how widely and carefully changes are
communicated, there's only so much anyone can do to avoid surprising
the subset of users who simply don't pay attention.
-- 
Jeremy Stanley


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

Re: [openstack-dev] Fwd: [Distutils][pbr][devstack][qa] Announcement: Pip 10 is coming, and will move all internal APIs

[Jeremy Stanley]

On 2017-10-20 17:50:15 -0400 (-0400), Sam Yaple wrote:
> On Fri, Oct 20, 2017 at 4:32 PM, Doug Hellmann  wrote:
[...]
> > 3. Remove the system package before installing from pip (why is
> > it there in the first place?).
[...]
> Option 3 is difficult to make work since so many packages have
> dependancies on python-* packages, I abandoned that approach
> fairly quickly.

Right, on Debian/Ubuntu it's not too terrible (cloud-init's
dependencies are usually the biggest issue there and we manage to
avoid them by building our own images with no cloud-init), but on
Red Hat derivatives there are a lot of deep operating system
internals built on top of packaged Python libraries which simply
can't be uninstalled cleanly nor safely.
-- 
Jeremy Stanley


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

[openstack-dev] OpenStack Bug Smash for Queens

[Fred Li]

Hi all OpenStackers,

Since April 2015, there have been 6 OpenStack Bug Smash events in
China. OpenStack Bug Smash has been a routine and exciting event by
OpenStacker expects. In the past 5 bug smashes, over 300 top
developers from many companies(Huawei,Intel,CMCC, IBM, Mirantis,
Awcloud, 99cloud, UnitedStack, EasyStack, LeTV, ZTE, and etc.)
contributed 600+ bugs to community. This achievement significantly
demonstrated the technical strength of Chinese engineers. Huawei,
Intel and those companies show the commitment of OpenStack Stability
to enterprise customers.

Now, the 7th OpenStack bug smash is coming. Intel, Huawei, Fiberhome
and CESI will host this event. Intel, Huawei and Fiberhome are all
OpenStack members[1].
Come to join other OpenStackers to make Queens a grand success!
Come to learn tips and gain a better understanding by working closely
with other talents.
Each focused project will have a core on standby to review patches and
vote for merges.

Queens Bug SmashObject: smash the critical and high bugs in key
projects. Focused projects: Nova, Neutron, Cinder, Keystone, Manila,
Heat, Telemetry, Karbor, Tricircle, and the ones you want to add.

To all the projects team leaders, you can discuss with your team
members in the project meeting and mark the bugs you expect OpenStack
Bug Smash Queens to fix. If you can arrange core reviewers to take
care of the patches during that week, that will be more efficient.

Date: from Nov 22 to Nov 24, which is 2 weeks prior to Queens-2 milestone[2].

Location: 中国湖北省武汉市洪山区邮科院路88号，烽火创新谷武汉国际创客中心五楼一号会议室 [3]


Please start to register in [4].
And start to list the bugs to be fixed in [5].

[1] https://www.openstack.org/foundation/companies/
[2] https://releases.openstack.org/queens/schedule.html
[3] 
https://www.google.co.jp/maps/place/88+You+Ke+Yuan+Lu,+GuangGu+ShangQuan,+Hongshan+Qu,+Wuhan+Shi,+Hubei+Sheng,+China,+430073/@30.5107646,114.392814,17z/data=!3m1!4b1!4m5!3m4!1s0x342ea4ce1537ed17:0x52ff45d6b5dba38c!8m2!3d30.51076!4d114.395008?hl=en
[4] https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan
[5] https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List


Regards
Fred Li (李永乐)

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

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

[Diana Clarke]

Congrats on being elected to the TC, Colleen!

You mentioned earlier in this thread that, "a major problem in the
tech world is not just attracting underrepresented contributors, but
retaining them".

I'm curious if the TC has considered polling the people that have left
OpenStack for their experiences on this front.

Something along the lines of:

"I see you contributed 20 patches in the last cycle, but haven't
contributed recently, why did you stop contributing?".

Given the recent layoffs, I suspect many of the responses will be
predicable, but you might find some worthwhile nuggets there
nonetheless.

Congrats again,

--diana

On Sun, Oct 15, 2017 at 3:38 AM, Colleen Murphy  wrote:
> A major problem in the tech world is not just attracting underrepresented
> contributors, but retaining them. They leave their communities or careers
> because of bias problems. To my knowledge, that doesn't happen in OpenStack,
> but just because I can't see it doesn't mean it's not there. A long-term
> study of participation by underrepresented demographics will help us answer
> this and fix it if necessary.

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

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

[Michał Jastrzębski]

Additionally you can build only images you need. Some of images we have are
quite.. niche. If you limit number of images to only those you care about,
that will lower total size significantly

On Oct 20, 2017 3:51 PM, "Steven Dake (stdake)"  wrote:

> Sam,
>
>
>
> Agreed this matches my experience. Building one by one though will result
> in massive image size sprawl.
>
>
>
> Regards
>
> -steve
>
>
>
> *From: *Sam Yaple 
> *Reply-To: *"s...@yaple.net" , "OpenStack Development
> Mailing List (not for usage questions)"  >
> *Date: *Thursday, October 19, 2017 at 10:37 PM
> *To: *Gabriele Cerami 
> *Cc: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [TripleO][Kolla] Concerns about containers
> images in DockerHub
>
>
>
>
>
>
>
> On Thu, Oct 19, 2017 at 11:23 PM, Gabriele Cerami 
> wrote:
>
> On 19 Oct, Sam Yaple wrote:
> > So it seems tripleo is building *all* images and then pushing them.
> > Reworking your number leads me to believe you will be consuming 10-15GB
> in
> > total on Dockerhub. Kolla images are only the size that you posted when
> > built as seperate services. Just keep building all the images at the same
> > time and you wont get anywhere near the numbers you posted.
>
> Makes sense, so considering the shared layers
> - a size of 10-15GB per build.
> - 4-6 builds rotated per release
> - 3-4 releases
>
>
>
> - a size of 1-2GB per build
>
> - 4-6 builds rotated per release
>
> - 3-4 releases
>
>
>
> At worst you are looking at 48GB not 360GB. Dont worry so much there!
>
>
> total size will be approximately be 360GB in the worst case, and 120GB in
> the best case, which seems a bit more reasonable.
>
> Thanks for he clarifications
>
>
>
> __
> 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