date:20171013

Re: [openstack-dev] [masakari] Propose changes of the core team

2017-10-13 Thread Bhor, Dinesh

Not a core but contributes to Masakari.


(A) Proposed to remove from Core team:
   (1) Toshikazu Ichikawa
   I think we should also consider Toshikazu Ichikawa San in "Confirm your 
availability as Core member".


B) Confirm your availability as Core member:
   Following members, please confirm your ability to contribute to
   Masakari in Queens and future cycles.
   (1) Takashi Kajinami
   (2) Masahito Muroi

   +1


(C) Add to new members to core team:
   (1) Adam Spiers (Suse)
   (2) Kengo Takahara (NTT-TX)

   ++1 Very much deserving candidates.


Thanks and Regards,

Dinesh Bhor | App. Software Dev. Cnslt.

dinesh.b...@nttdata.com | m. +91.9730809841 | 
VOIP. 8833 8622

NTT DATA Services | nttdataservices.com | 
@nttdataservices  | Digital & Application Services


From: Sam P 
Sent: 13 October 2017 15:09
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [masakari] Propose changes of the core team

Hi All Masakari Cores,

 I would like to propose following changes to Masakari core team.

Current core team:
Masahito Muroi
Rikimaru Honjo
Sampath Priyankara (samP)
Takashi Kajinami
Toshikazu Ichikawa
Tushar Patil
Yukinori Sagara

(A) Proposed to remove from Core team:
(1) Toshikazu Ichikawa
 He was one of the initial members of the project and did a great work
on design the initial Masakari API and Masakari architecture.
However, he is no longer a active member of the community.
I would like to take this opportunity to thank Toshikazu for his work
on Masakari.

(B) Confirm your availability as Core member:
 Following members, please confirm your ability to contribute to
Masakari in Queens and future cycles.
(1) Takashi Kajinami
(2) Masahito Muroi
I understand that you are extremely busy with other tasks or other projects
in OpenStack. If it is difficult for you to contribute to Masakari,
I suggest that you step down from core team for now. In future, if you are
wish to participate again, then we can discuss about reinstate you as a core
member of the team.

(C) Add to new members to core team:
(1) Adam Spiers (Suse)
  I would like to add  Adam to core team. He is the current maintainer
of the openstack-resource-agents and leader of the OpenStack HA team.
Considering his technical knowledge of the subject, and past work he
has done in Masakari and related work[1][2],
I think Adam is one of the best persons we can have in our team.

(2) Kengo Takahara (NTT-TX)
 Kengo has been an active contributor to the Masakari project from Newton
 and heavily contribute to crate masakari-monitors and python-masakariclient
 from scratch [3].

All Masakari core members, please respond with your comments and objections.
Please cast your vote on (A) and (C).

[1] 
https://review.openstack.org/#/q/project:openstack/openstack-resource-agents-specs
[2] https://etherpad.openstack.org/p/newton-instance-ha
[3] 
http://stackalytics.com/?project_type=all=all=commits_id=takahara.kengo@as.ntts.co.jp

--- Regards,
Sampath

__
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 mailing list - lists.openstack.org Mailing 
Lists
lists.openstack.org
This list for the developers of OpenStack to discuss development issues and 
roadmap. It is focused on the next release of OpenStack: you should post on 
this list if ...




__
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.__
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] [Swift] SPDK uses Swift as a target system to support k-v store

2017-10-13 Thread We We

Hi, all

I am a newcomer in Swift, I have proposed a proposal for k-v store  in the SPDK 
community. The  proposal has submitted on 
https://trello.com/b/P5xBO7UR/things-to-do 
, please spare some time to visit 
it. In this proposal, we would like to  uses Swift as a target system to 
support k-v store. Could you please share with me if you have any ideas about 
it. I'd love to hear from your professional thoughts.

Thx，

Helloway

__
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?

2017-10-13 Thread ChangBo Guo

 FeiLong, Thanks for raising the pain points as a non-English native
speaker. I had similar experience with you in last 5 years. Language,
timezone, culture are the common barriers for diversity and inclusiveness.
We could identify  what's
the biggest obstacles for contributors to contribute happily.  That could
be done through discussions occurred in local meetup/online meeting in
local language and bring conclusions back to the global community
discussion. record the obstacles and find the way to overcome them.  BTW, I
really like the TC office hours.





how you
think we could make our community more inclusive. What areas would you
improve
first?




2017-10-14 3:22 GMT+08:00 feilong :

> Thanks for asking, Flavio. That's one of the topic I mentioned in my
> candidacy, that's because as a Chinese working on OpenStack in the past 6
> years, I do have some experiences about this though I agree it couldn't be
> done in 1 cycle/year. But I think it's still a domain I can contribute for
> OpenStack.
>
> I can still remember I had to join the Glance meeting at 2:00AM, and was
> challenged because of saying "Hi guys" in a public channel though "Hi guys"
> is used very common in New Zealand. Should we expect a non-English native
> speaker to understand the details between “Hi there", "Hi guys" and "Hi
> folks"? I think that's the language and culture barrier for many new
> contributors. We (Brian, Erno） even tried to propose a panel at summit to
> discuss it before. Currently, it's more important than ever to keep those
> new contributors due to the changes happening around OpenStack nowadays.
>
> On 14/10/17 01:45, Flavio Percoco wrote:
>
> Greetings,
>
> Some of you, TC candidates, expressed concerns about diversity and
> inclusiveness
> (or inclusivity, depending on your taste) in your candidacy. I believe
> this is a
> broad, and some times ill-used, topic so, I'd like to know, from y'all,
> how you
> think we could make our community more inclusive. What areas would you
> improve
> first?
>
> Thank you,
> Flavio
>
> --
> @flaper87
> Flavio Percoco
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Cheers & Best regards,
> Feilong Wang (王飞龙)
> --
> Senior Cloud Software Engineer
> Tel: +64-48032246 <+64%204-803%202246>
> Email: flw...@catalyst.net.nz
> Catalyst IT Limited
> Level 6, Catalyst House, 150 Willis Street, Wellington
> --
>
>
> __
> 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
>
>


-- 
ChangBo Guo(gcb)
Community Director @EasyStack
__
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][infra] Zuul v3 rollout, the sequel returns

2017-10-13 Thread Sam Matzek

The legacy-trove-functional-dsvm-mysql and
legacy-trove-legacy-functional-dsvm-mysql jobs are running the wrong
post_test_hook and have the trove-integration project in $PROJECTS.
As such they will always vote -1. The functional integration tests
moved into Trove proper in Ocata.  I've added more details and links
to the zuulv3-issues etherpad.

I'm not familiar enough with the job definitions to be able to work on
the fix reviews for these but would like to learn.

Sam Matzek

On Fri, Oct 13, 2017 at 2:57 PM, Jeremy Stanley  wrote:
> The tl;dr is that we're planning to roll forward out of our partial
> Zuul v3 rollback starting at 22:00 UTC on Sunday October 15 (this
> weekend), so expect some CI downtime and all of the benefits (though
> hopefully none of the drawbacks!) you witnessed when we tried the
> first time. At that time, v2 jobs reported by the "Jenkins" account
> will cease to be relevant, and v3 jobs reported by the "Zuul"
> account will be used to determine whether your changes can merge.
>
> As Monty noted earlier in the week, our plans to roll forward onto
> Zuul v3 were halted by a number of unrelated infrastructure fires
> which demanded our immediate attention as a team, so we reluctantly
> postponed. Following a (brief) hiatus yesterday, check pipeline
> processing has been readded to zuulv3.openstack.org for all projects
> so you can get fresh results back on v3 jobs between now and our
> maintenance if you happen to be around testing it out. We also still
> have an expedited priority "infra-check" pipeline on zuulv3 for
> changes to the project-config repository so that emergency fixes
> for legacy jobs can be merged quickly, and we'll be keeping this for
> some time after the transition until it ceases to be necessary.
>
> We anticipate an outage for the CI system of somewhere between 30-60
> minutes starting at 22:00 UTC on Sunday October 15. In the meantime,
> if you've been digging into recent legacy job failures for your
> projects you should consider trying to bring them to our attention
> as soon as possible (in #openstack-infra on the Freenode IRC
> network, or replying on-list to this announcement) and work on
> fixing them if you're familiar enough with the failures to do so
> yourself. It also helps to get them onto the triage list we have
> been maintaining here:
>
> https://etherpad.openstack.org/p/zuulv3-issues
>
> We're assembling a sort of FAQ in the migration guide
> here:
>
> https://docs.openstack.org/infra/manual/zuulv3.html
>
> ...and we also have some more content in progress at:
>
> https://etherpad.openstack.org/p/zuulv3-migration-faq
>
> Here's to the week ahead!
> --
> Jeremy Stanley
>
> __
> 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] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

2017-10-13 Thread Emilien Macchi

On Fri, Oct 13, 2017 at 5:45 AM, Flavio Percoco  wrote:
> Some of you, TC candidates, expressed concerns about diversity and
> inclusiveness (or inclusivity, depending on your taste) in your candidacy. I 
> believe this
> is a broad, and some times ill-used, topic so, I'd like to know, from y'all, 
> how
> you think we could make our community more inclusive. What areas would you
> improve first?

Some rough ideas, that can be discussed as a community:

- Force changes in leadership roles: I'm believe in rotations when
that makes sense. We could think at some policy to not being at TC
more than 2 cycles in a row (can re-apply after one cycle break). Same
for PTL? (not sure on this one, some projects don't have much
volunteers do run this position). But you get the idea.
(some could ask why I didn't propose that during my TC mandate, it
just popup in my mind by writing this email).

- Keep encouraging asynchronous collaboration: dropping the TC meeting
(and adding office hours) was a good example of how we can now have
TC-related discussions around the globe without having to stay until
late in the evening. I would like to encourage other projects to look
at this concept. Hopefully we can get more contributors from around
the globe and not just in US-friendly timezone.

- Ensure projects growth: the number of core reviewers for some
projects is imho alarming. Lack of reviewers? Lack of trust? Here are
some number of the Top 5 projects (# of reviews in Pike, source
stackalitics):

#1 Nova - 12 cores
#2 Infra - 13 cores (core, not root)
#3 Cinder - 15 cores
#4 Neutron - 13 cores (not counting all plugins repos, but numbers
look good, probably thanks to the stadium)
#5 TripleO - 32
(and we can continue)

What TC can do? promote more mentoring, establish healthy policies to
promote cores in projects, by defining as a community the metrics
used, etc.


Anyway, these things are (again) rough ideas, that we can be discussed
here or somewhere else but I strongly believe we need people at TC who
can, by their experience and motivation, make our community growing in
healthy and diverse ways.
-- 
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

[openstack-dev] Developer Mailing List Digest September 30 - October 6

2017-10-13 Thread Mike Perez

HTML version: 
https://www.openstack.org/blog/2017/10/developer-mailing-list-digest-september-30-6-2017/

## Summaries
* OpenStack Technical Committee
*  [TC report 
40](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123063.html)
 by Chris Dent
* [TC report 
41](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123397.html)
 by Chris Dent
* [Technical Committee Status update, October 
6th](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123236.html)
 by Thierry Carrez
* [Technical Committee Status update, October 
13th](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123573.html)
 by Thierry Carrez
* Zuul
* [Zuul v3 Status - and Rollback 
Information](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123049.html)
  by Monty Taylor
* [Important information for people with in-repo Zuul v3 
config](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123064.html)
 by Monty Taylor
* [Zuul v3 rollout, the 
sequel](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123337.html)
 by Jeremy Stanley
* [Zuul v3 Rollout Update - devstack-gate issues 
edition](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123464.html)
 by Monty Taylor
* [Zuul v3 rollout, the sequel 
returns](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123618.html)
 by Jeremy Stanley
* [POST 
/api-sig/news](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123208.html)
* [Release countdown for week R-19, October 
13-20](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123516.html)
 by Sean McGinnis
* [QA Office Hours 
Report](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123520.html)
 by Andrea Frittoli
* [Keystone Office Hours 
Report](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123271.html)
 by Lance Bragstad
* Nova
* [Placement resource providers update 
36](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123244.html)
 by Chris Dent
* [Placement resource providers update 
38](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123581.html)
 by Chris Dent

## Sydney Forum Schedule Available
* [View it 
now!](https://www.openstack.org/summit/sydney-2017/summit-schedule/#day=2017-11-06_groups=63)

## TC Nomination Period Is Now Over
* Kendall Nelson has announced the [official candidate 
list](https://governance.openstack.org/election/#pike-tc-candidates).

## Prepping for the Stable/Newton EOL
* The [published timeline](https://releases.openstack.org/queens/schedule.html) 
is:
* Sep 29 : Final newton library releases
* Oct 09 : stable/newton branches enter Phase III
* Oct 11 : stable/newton branches get tagged EOL
* Given that those key dates were a little disrupted, Tony Breeds is proposing
  adding a week to each so the new timeline looks like:
* Oct 08 : Final newton library releases
* Oct 16 : stable/newton branches enter Phase III
* Oct 18 : stable/newton branches get tagged EOL
* 
[Thread](http://lists.openstack.org/pipermail/openstack-dev/2017-October/thread.html#123088)

## Policy Community Wide Goal Progress
* [The 
goal](https://governance.openstack.org/tc/goals/queens/policy-in-code.html)
* [Burn down chart](https://www.lbragstad.com/policy-burndown/)
* Over half the projects attempted the goal.
* 
[Message](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123040.html)

## Tempest Plugin Split Community Wide Goal Progress
* [The 
goal](https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html)
* [The 
reviews](https://review.openstack.org/#/q/topic:goal-split-tempest-plugins+status:open)
* List of projects which have already completed the goal:
- Barbican
- Designate
- Horizon
- Keystone
- Kuryr
- Os-win
- Sahara
- Solum
- Watcher
* List of projects which are working on the goal:
- Aodh
- Cinder
- Magnum
- Manila
- Murano
- Neutron
- Neutron L2GW
- Octavia
- Senlin
- Zaqar
- Zun
- 
[Message](http://lists.openstack.org/pipermail/openstack-dev/2017-October/123268.html)


signature.asc
Description: PGP 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] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

2017-10-13 Thread Emilien Macchi

Greeting folks,

I hope we can get attention from stable-maint, release-managers and
installers projects.

## Background

Some projects tried hard to follow stable policy but it didn't finish
well: https://review.openstack.org/#/c/507924/
This policy is too strict for projects like installers, although it's
not a reason why the projects wouldn't be "stable".
We decided to discuss again about the tag and how it works for installers.

## Proposal

Proposal 1: create a new policy that fits for projects like installers.
I kicked-off something here: https://review.openstack.org/#/c/511968/
(open for feedback).
Content can be read here:
http://docs-draft.openstack.org/68/511968/1/check/gate-project-team-guide-docs-ubuntu-xenial/1a5b40e//doc/build/html/stable-branches.html#support-phases
Tag created here: https://review.openstack.org/#/c/511969/ (same,
please review).

The idea is really to not touch the current stable policy and create a
new one, more "relax" that suits well for projects like installers.

Proposal 2: change the current policy and be more relax for projects
like installers.
I haven't worked on this proposal while it was something I was
considering doing first, because I realized it could bring confusion
in which projects actually follow the real stable policy and the ones
who have exceptions.
That's why I thought having a dedicated tag would help to separate them.

Proposal 3: no change anywhere, projects like installer can't claim
stability etiquette (not my best option in my opinion).

Anyway, feedback is welcome, I'm now listening. If you work on Kolla,
TripleO, OpenStack-Ansible, PuppetOpenStack (or any project who has
this need), please get involved in the review process.

Thanks,
--
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

67 matches

Mail list logo