date:20171113

Re: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

2017-11-13 Thread Chris Morgan

This reminds me, here are the minutes links from last meeting :

Meeting ended Tue Oct 31 15:00:02 2017 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
11:00 AM Minutes:
http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-31-14.01.html
11:00 AM Minutes (text):
http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-31-14.01.txt
11:00 AM Log:
http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-31-14.01.log.html

Agenda as always goes at the top of this page:

https://etherpad.openstack.org/p/ops-meetups-team

I see someone has made a start, excellent!

Chris

On Mon, Nov 13, 2017 at 12:33 PM, Chris Morgan  wrote:

> Yes, I plan to. The reminder on the timeslot is very timely and
> appreciated!
>
> Chris
>
> On Mon, Nov 13, 2017 at 12:26 PM, David Medberry 
> wrote:
>
>> I presume we're still on track for a meeting tomorrow at 14:00 UTC (which
>> will shift it an hour earlier if your timezone had previously recognized
>> DST in the northern hemisphere.)
>>
>> See you there #openstack-operators on Freenode.
>>
>> -dave
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
>
> --
> Chris Morgan 
>



-- 
Chris Morgan 
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Sydney Takeaways - UC

2017-11-13 Thread Melvin Hillsman

Hey David,

Nope, no action taken in a separate meeting. I had been thinking about this
for some time from the OpenStack Days China operators event in July as I
mentioned in the session and just wanted to get something down based on
things that had been swirling in my head and some notes I had sitting
around. Feel free to use the Google Doc or not, totally ok. I wanted to be
sure we captured key items from the Summit and got them down in the open to
ensure larger community is aware of what we are working on as UC.


On Tue, Nov 14, 2017 at 5:07 AM, David Medberry 
wrote:

> I took an action to work on this bit:
>
>1. "stackalytics" for user community
>
> Closely tied to #5. Assists with non-developers being able to show their
> impact in the community and justify travel amongst other things.
>
>- We should discuss how to make this happen and prioritize
>   - Started a document - https://docs.google.com/docu
>   ment/d/1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
>   
> 
>
> and will work with Jimmy McArthur. Though maybe Melvin also took an item
> in a separate meeting...
>
> On Mon, Nov 13, 2017 at 10:59 AM, Melvin Hillsman 
> wrote:
>
>> Hey everyone,
>>
>> Wanted to start a thread for UC specific takeaways from the Summit. Here
>> are the things that stood out and would love additions:
>>
>> UC Top 5 - https://etherpad.openstack.org/p/SYD-forum-uc - we have
>> discussed previously having goals as a UC and in Sydney we decided to put
>> together a top 5 list; mirroring what the TC has done. We should be able to
>> provide this to the Board, Staff, and TC as needed and continuously update
>> the community on progress. We have not decided on any of these of course
>> but here is what is currently listed.
>>
>>1. LTS
>>   - Conversation is going well via ML
>>   - Our discussion was to allow the folks who want to work on LTS
>>   the chance to do it as they see fit; no exact way but discussion 
>> actively
>>   going on, get involved
>>2. Operator midcycle integration into larger event/feedback ecosystem
>>   - We have as a community made significant changes to ensure user
>>   feedback getting in front of those working on the code earlier than 
>> before
>>   and we have to be sure that we tie into that process as it is designed.
>>   - Mexico City was an edge case of the past few midcycles that have
>>   been community-led but gave great insight into worse case scenario; 
>> what
>>   have we learned and what can we do better?
>>   - How specifically can the Foundation Staff help - again the
>>   biggest need is to ensure tying into bigger ecosystem
>>3. More operator proposed forum sessions
>>   - Very much tied to #2.
>>   4. Vision casting exercise
>>   - TC and documentation team has gone through this exercise; Doug
>>   Hellmann agreed to be available either F2F or via video conference to 
>> do
>>   this with UC
>>   5. Company view of non-developer community participation
>>   - It is easy for companies to hire/organize developers as FTEs for
>>   community work and impact is readily available via quantitative output 
>> from
>>   the community; commits, blueprints, etc.
>>   - It is equally important for companies to allow non-developers -
>>   project managers, product managers, system administrators, developers,
>>   devops engineers, etc - some percentage if not 100% to community work. 
>> It
>>   should not all be personal/volunteer time in order to increase the 
>> velocity
>>   of user community growth and impact.
>>   6. "stackalytics" for user community
>>   - Closely tied to #5. Assists with non-developers being able to
>>   show their impact in the community and justify travel amongst other 
>> things.
>>   - We should discuss how to make this happen and prioritize
>>   - Started a document - https://docs.google.com/docu
>>   ment/d/1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
>>   
>> 
>>7. Joint TC/UC meetings
>>   - Ensuring there is more parity between TC and UC.
>>   - Carrying forward from Boston Forum
>>  - Feel free to crash each others meetings
>>
>> User Survey
>>
>>- One important detail I took away from the User Survey session was a
>>request to move the survey to being held once a year in terms of analysis
>>and compilation.
>>- Survey is always available to take. Suggestion was to prod
>>community every quarter for example to take the survey while only 
>> compiling
>>yearly report.
>>
>> OpenLab
>>
>>- Initiated by OpenStack Foundation, Huawei, and Intel, currently
>>involved companies include Deutsche Telekom and VEXXHOST. OpenLab 
>> currently
>>is

Re: [Openstack-operators] Sydney Takeaways - UC

2017-11-13 Thread David Medberry

I took an action to work on this bit:

   1. "stackalytics" for user community

Closely tied to #5. Assists with non-developers being able to show their
impact in the community and justify travel amongst other things.

   - We should discuss how to make this happen and prioritize
  - Started a document - https://docs.google.com/document/d/
  1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
  


and will work with Jimmy McArthur. Though maybe Melvin also took an item in
a separate meeting...

On Mon, Nov 13, 2017 at 10:59 AM, Melvin Hillsman 
wrote:

> Hey everyone,
>
> Wanted to start a thread for UC specific takeaways from the Summit. Here
> are the things that stood out and would love additions:
>
> UC Top 5 - https://etherpad.openstack.org/p/SYD-forum-uc - we have
> discussed previously having goals as a UC and in Sydney we decided to put
> together a top 5 list; mirroring what the TC has done. We should be able to
> provide this to the Board, Staff, and TC as needed and continuously update
> the community on progress. We have not decided on any of these of course
> but here is what is currently listed.
>
>1. LTS
>   - Conversation is going well via ML
>   - Our discussion was to allow the folks who want to work on LTS the
>   chance to do it as they see fit; no exact way but discussion actively 
> going
>   on, get involved
>2. Operator midcycle integration into larger event/feedback ecosystem
>   - We have as a community made significant changes to ensure user
>   feedback getting in front of those working on the code earlier than 
> before
>   and we have to be sure that we tie into that process as it is designed.
>   - Mexico City was an edge case of the past few midcycles that have
>   been community-led but gave great insight into worse case scenario; what
>   have we learned and what can we do better?
>   - How specifically can the Foundation Staff help - again the
>   biggest need is to ensure tying into bigger ecosystem
>3. More operator proposed forum sessions
>   - Very much tied to #2.
>   4. Vision casting exercise
>   - TC and documentation team has gone through this exercise; Doug
>   Hellmann agreed to be available either F2F or via video conference to do
>   this with UC
>   5. Company view of non-developer community participation
>   - It is easy for companies to hire/organize developers as FTEs for
>   community work and impact is readily available via quantitative output 
> from
>   the community; commits, blueprints, etc.
>   - It is equally important for companies to allow non-developers -
>   project managers, product managers, system administrators, developers,
>   devops engineers, etc - some percentage if not 100% to community work. 
> It
>   should not all be personal/volunteer time in order to increase the 
> velocity
>   of user community growth and impact.
>   6. "stackalytics" for user community
>   - Closely tied to #5. Assists with non-developers being able to
>   show their impact in the community and justify travel amongst other 
> things.
>   - We should discuss how to make this happen and prioritize
>   - Started a document - https://docs.google.com/document/d/
>   1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
>   
> 
>7. Joint TC/UC meetings
>   - Ensuring there is more parity between TC and UC.
>   - Carrying forward from Boston Forum
>  - Feel free to crash each others meetings
>
> User Survey
>
>- One important detail I took away from the User Survey session was a
>request to move the survey to being held once a year in terms of analysis
>and compilation.
>- Survey is always available to take. Suggestion was to prod community
>every quarter for example to take the survey while only compiling yearly
>report.
>
> OpenLab
>
>- Initiated by OpenStack Foundation, Huawei, and Intel, currently
>involved companies include Deutsche Telekom and VEXXHOST. OpenLab currently
>is focusing on SDKs moving to define, stabilize, and support official
>OpenStack SDKs. Gophercloud is currently using OpenLab and work is being
>done to add the OpenStack provider for Terraform into the system.
>- Another phase of OpenLab is to tightly integrate with or learn
>heavily from OPNFV's XCI. Currently discussing this with the lead engineer
>of XCI and could possibly lead to re-branding XCI as OpenLab increasing the
>scope, collaboration, and integration of OpenLab components and Open Source
>communities.
>- As the UC, OpenLab is important to us, as it targets the user
>community of OpenStack and other user communities of
>tools/components/applications that work with

[Openstack-operators] Sydney Takeaways - UC

2017-11-13 Thread Melvin Hillsman

Hey everyone,

Wanted to start a thread for UC specific takeaways from the Summit. Here
are the things that stood out and would love additions:

UC Top 5 - https://etherpad.openstack.org/p/SYD-forum-uc - we have
discussed previously having goals as a UC and in Sydney we decided to put
together a top 5 list; mirroring what the TC has done. We should be able to
provide this to the Board, Staff, and TC as needed and continuously update
the community on progress. We have not decided on any of these of course
but here is what is currently listed.

   1. LTS
  - Conversation is going well via ML
  - Our discussion was to allow the folks who want to work on LTS the
  chance to do it as they see fit; no exact way but discussion
actively going
  on, get involved
   2. Operator midcycle integration into larger event/feedback ecosystem
  - We have as a community made significant changes to ensure user
  feedback getting in front of those working on the code earlier
than before
  and we have to be sure that we tie into that process as it is designed.
  - Mexico City was an edge case of the past few midcycles that have
  been community-led but gave great insight into worse case scenario; what
  have we learned and what can we do better?
  - How specifically can the Foundation Staff help - again the biggest
  need is to ensure tying into bigger ecosystem
   3. More operator proposed forum sessions
  - Very much tied to #2.
  4. Vision casting exercise
  - TC and documentation team has gone through this exercise; Doug
  Hellmann agreed to be available either F2F or via video conference to do
  this with UC
  5. Company view of non-developer community participation
  - It is easy for companies to hire/organize developers as FTEs for
  community work and impact is readily available via quantitative
output from
  the community; commits, blueprints, etc.
  - It is equally important for companies to allow non-developers -
  project managers, product managers, system administrators, developers,
  devops engineers, etc - some percentage if not 100% to community work. It
  should not all be personal/volunteer time in order to increase
the velocity
  of user community growth and impact.
  6. "stackalytics" for user community
  - Closely tied to #5. Assists with non-developers being able to show
  their impact in the community and justify travel amongst other things.
  - We should discuss how to make this happen and prioritize
  - Started a document -
  
https://docs.google.com/document/d/1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
   7. Joint TC/UC meetings
  - Ensuring there is more parity between TC and UC.
  - Carrying forward from Boston Forum
 - Feel free to crash each others meetings

User Survey

   - One important detail I took away from the User Survey session was a
   request to move the survey to being held once a year in terms of analysis
   and compilation.
   - Survey is always available to take. Suggestion was to prod community
   every quarter for example to take the survey while only compiling yearly
   report.

OpenLab

   - Initiated by OpenStack Foundation, Huawei, and Intel, currently
   involved companies include Deutsche Telekom and VEXXHOST. OpenLab currently
   is focusing on SDKs moving to define, stabilize, and support official
   OpenStack SDKs. Gophercloud is currently using OpenLab and work is being
   done to add the OpenStack provider for Terraform into the system.
   - Another phase of OpenLab is to tightly integrate with or learn heavily
   from OPNFV's XCI. Currently discussing this with the lead engineer of XCI
   and could possibly lead to re-branding XCI as OpenLab increasing the scope,
   collaboration, and integration of OpenLab components and Open Source
   communities.
   - As the UC, OpenLab is important to us, as it targets the user
   community of OpenStack and other user communities of
   tools/components/applications that work with OpenStack, so we should push
   with the Foundation to ensure it is successful.

Cross-Community Participation

   - gophercloud/terraform/k8s
  - greatly part of OpenLab (gophercloud integrated, terraform almost -
  +unittests/-acceptancetests - researching k8s connection
  - many sessions regarding SIGs of both k8s and OpenStack where many
  folks were interested in increased cross-pollination and not
being redundant
   - OPNFV's XCI - mentioned previously also closely tied to OpenLab -
   first meeting scheduled for Friday 11/17 9-10am CST - reply if interested
   - It makes sense for entire community to look for ways to work more
   closely with other communities relevant to current and future work

SIGs

   - Concern from UC on relevance due to many going to SIGs model - should
   discuss further via ML openstack-sigs with [meta] tag
   - Bi-weekly "newsletter/digest" much like the

[Openstack-operators] [User-committee] UC IRC Meeting on Monday 13/11 - Cancel

2017-11-13 Thread Edgar Magana

Folks,

I hope everybody who could attend the OpenStack summit in Sydney is safe back 
at home and ready to start this new cycle. Let’s have our UC IRC meeting next 
Monday because we do not actually an agenda planned for today. However, I would 
like to share the etherpad of some of the UC related session because we need to 
make sure we cover the action items and we follow up properly on those 
discussions during our meetings.

https://etherpad.openstack.org/p/SYD-forum-uc
https://etherpad.openstack.org/p/SYD-wg-and-uc
https://etherpad.openstack.org/p/SYD-feedback
https://etherpad.openstack.org/p/SYD-financial-wg-bof
https://etherpad.openstack.org/p/SYD-public-cloud-wg

Thanks,

UC Team


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

Re: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

2017-11-13 Thread Chris Morgan

Yes, I plan to. The reminder on the timeslot is very timely and appreciated!

Chris

On Mon, Nov 13, 2017 at 12:26 PM, David Medberry 
wrote:

> I presume we're still on track for a meeting tomorrow at 14:00 UTC (which
> will shift it an hour earlier if your timezone had previously recognized
> DST in the northern hemisphere.)
>
> See you there #openstack-operators on Freenode.
>
> -dave
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Chris Morgan 
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

2017-11-13 Thread David Medberry

I presume we're still on track for a meeting tomorrow at 14:00 UTC (which
will shift it an hour earlier if your timezone had previously recognized
DST in the northern hemisphere.)

See you there #openstack-operators on Freenode.

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

[Openstack-operators] [scientific] No Scientific SIG meeting this week

2017-11-13 Thread Martial Michel

Dear Scientific SIG members,

We will be skipping this week's scheduled Scientific SIG meeting and will
resume our regular meeting next week.

Thank you -- Martial
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

Re: [Openstack-operators] Sydney Takeaways - UC

Re: [Openstack-operators] Sydney Takeaways - UC

[Openstack-operators] Sydney Takeaways - UC

[Openstack-operators] [User-committee] UC IRC Meeting on Monday 13/11 - Cancel

Re: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

[Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

[Openstack-operators] [scientific] No Scientific SIG meeting this week

8 matches

Site Navigation

Mail list logo

Footer information