[Openstack-operators] [External] OpenStack-create volume backup through heat template

Jain, Bhumika A. bhumika.a.jain at accenture.com
Tue Nov 14 13:11:51 UTC 2017


Hi Team,

Can we create volume backup through heat template?

Thanks,
Bhumika

-----Original Message-----
From: openstack-operators-request at lists.openstack.org [mailto:openstack-operators-request at lists.openstack.org]
Sent: Tuesday, November 14, 2017 5:30 PM
To: openstack-operators at lists.openstack.org
Subject: [External] OpenStack-operators Digest, Vol 85, Issue 13

Send OpenStack-operators mailing list submissions to
openstack-operators at lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=U2XkVxR7nr3__D_L2mzbp9BvsOlRgrU-DqLnOEQKHpI&e=

or, via email, send a message with subject or body 'help' to
openstack-operators-request at lists.openstack.org

You can reach the person managing the list at
openstack-operators-owner at lists.openstack.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of OpenStack-operators digest..."


Today's Topics:

   1. [scientific] No Scientific SIG meeting thisweek (Martial Michel)
   2. Ops Meetup Meeting Tomorrow? 14:00 UTC (David Medberry)
   3. Re: Ops Meetup Meeting Tomorrow? 14:00 UTC (Chris Morgan)
   4. [User-committee] UC IRC Meeting on Monday13/11 - Cancel
      (Edgar Magana)
   5. Sydney Takeaways - UC (Melvin Hillsman)
   6. Re: Sydney Takeaways - UC (David Medberry)
   7. Re: Sydney Takeaways - UC (Melvin Hillsman)
   8. Re: Ops Meetup Meeting Tomorrow? 14:00 UTC (Chris Morgan)
   9. LTS pragmatic example (Saverio Proto)
  10. Re: [openstack-dev] LTS pragmatic example (Davanum Srinivas)


----------------------------------------------------------------------

Message: 1
Date: Mon, 13 Nov 2017 17:23:12 +0000
From: Martial Michel <martialmichel at datamachines.io>
To: openstack-sigs at lists.openstack.org,  openstack-operators
<openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] [scientific] No Scientific SIG meeting
thisweek
Message-ID:
<CAAXGpAoY1+0m7WQ9ZFXbL6DT2=5fNammkmVCStcdSev04LDPyg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171113_2f31e89a_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=g77k2kd6bYi2-oTp4b2bLl2fv2_t8r9CQ3JyaLVLOHs&e=>

------------------------------

Message: 2
Date: Mon, 13 Nov 2017 10:26:55 -0700
From: David Medberry <openstack at medberry.net>
To: "openstack-operators at lists.openstack.org"
<openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC
Message-ID:
<CAJhvMSvcpiYQMuSMNE1stF9YUy=JAxxFe6tnCbAv2A6cCYv8-w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171113_9ec629c9_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=b1F_rXN3TnGXORdiHSx0p6s_ULlSi2LHoeqJ6KLBBWw&e=>

------------------------------

Message: 3
Date: Mon, 13 Nov 2017 12:33:47 -0500
From: Chris Morgan <mihalis68 at gmail.com>
To: David Medberry <openstack at medberry.net>
Cc: "openstack-operators at lists.openstack.org"
<openstack-operators at lists.openstack.org>
Subject: Re: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00
UTC
Message-ID:
<CA+NmNoNfi4f47tA5GKPWTw+Rf=f8zD3MWKNPEqg+AmsYJtK--g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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 <openstack at medberry.net>
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 at lists.openstack.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.or
> g_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=eIGjsITf
> XP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMlo
> GAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=U2XkVxR7nr
> 3__D_L2mzbp9BvsOlRgrU-DqLnOEQKHpI&e=
>
>


--
Chris Morgan <mihalis68 at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171113_8334ad14_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=suHilIyyvMvuSv283w0vDyBjedI3UgY1NWeXodWMaPs&e=>

------------------------------

Message: 4
Date: Mon, 13 Nov 2017 17:38:32 +0000
From: Edgar Magana <edgar.magana at workday.com>
To: user-committee <user-committee at lists.openstack.org>,
openstack-operators <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] [User-committee] UC IRC Meeting on
Monday13/11 - Cancel
Message-ID: <D7B438D2-59FF-49FA-AB2A-4FA43F7A41F8 at workday.com>
Content-Type: text/plain; charset="utf-8"

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://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dforum-2Duc&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=j9vlch_TIx8tboUp7Klnflb2y2V9BK5k7UjuaTUfcQs&e=https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dwg-2Dand-2Duc&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=dpz7qMTEiYcmDewuW6eCIG1hjv4kJ2F5iYskX4zl_WY&e=https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dfeedback&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=tZTpZ2EL67jYw3IY-1a6kfE8v_4jmVCXUUthyfNBI5Q&e=https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dfinancial-2Dwg-2Dbof&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=G90WCxXpIjrv3WGEkQ54DyddxJxmaAhnq4Ao16bIK28&e=https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dpublic-2Dcloud-2Dwg&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=hVKLmIukS9FCreI9Sg0FTx5n_2xosSnVc_gks8wJkaY&e=Thanks,UC Team-------------- next part -------------- An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171113_938c3888_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=w6zNuEpjJ-K0NQzSZcLS75ZuzQn1NzC7W5D-B_A-1VY&e=>

------------------------------

Message: 5
Date: Tue, 14 Nov 2017 04:59:24 +1100
From: Melvin Hillsman <mrhillsman at gmail.com>
To: user-committee <user-committee at lists.openstack.org>,  OpenStack
Operators <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] Sydney Takeaways - UC
Message-ID:
<CAMVtB2H_59=xmnMREGrcYMaDcF++o+T9mN0O6oX5EXOnj3Xewg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_SYD-2Dforum-2Duc&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=j9vlch_TIx8tboUp7Klnflb2y2V9BK5k7UjuaTUfcQs&e= - 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://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=lExIRu7rt6BY87caW8Ir456Q5KiVLu4qcDvhti7a0Ek&e=
   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-dev list summary
      - single etherpad allowing SIGs to provide an update which will be
      compiled
   - Communication on what SIGs are and how they relate to existing Working
   Group/Project/Team structure (superuser, youtube, etc)



Again, please add more items as you feel necessary. We want to be able to create next steps from these items.

--
Kind regards,

OpenStack User Committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171114_33530f8a_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=6WZD96wCb0doTg2mR0hPSUBrYgJEVMGVirquEEOHZWo&e=>

------------------------------

Message: 6
Date: Mon, 13 Nov 2017 11:07:12 -0700
From: David Medberry <openstack at medberry.net>
To: Melvin Hillsman <mrhillsman at gmail.com>
Cc: OpenStack Operators <openstack-operators at lists.openstack.org>,
user-committee <user-committee at lists.openstack.org>
Subject: Re: [Openstack-operators] Sydney Takeaways - UC
Message-ID:
<CAJhvMSu4Ef00RiiB9VeJDRygeynT6QypZkuJGay4-yUSQ_RSXA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=_cK_Af5O5lcvM4sZHsjwXmrirFoPQ9x6wyVTylWLa2Y&e=
      1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
      <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=lExIRu7rt6BY87caW8Ir456Q5KiVLu4qcDvhti7a0Ek&e=>

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 <mrhillsman at gmail.com>
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://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstac
> k.org_p_SYD-2Dforum-2Duc&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8I
> rwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX
> _-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=j9vlch_TIx8tboUp7Klnflb2y2V9BK5k7Uju
> aTUfcQs&e= - 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://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=_cK_Af5O5lcvM4sZHsjwXmrirFoPQ9x6wyVTylWLa2Y&e=
>       1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
>       <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=lExIRu7rt6BY87caW8Ir456Q5KiVLu4qcDvhti7a0Ek&e=>
>    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-dev list
>    summary
>       - single etherpad allowing SIGs to provide an update which will be
>       compiled
>    - Communication on what SIGs are and how they relate to existing
>    Working Group/Project/Team structure (superuser, youtube, etc)
>
>
>
> Again, please add more items as you feel necessary. We want to be able
> to create next steps from these items.
>
> --
> Kind regards,
>
> OpenStack User Committee
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.or
> g_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=eIGjsITf
> XP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMlo
> GAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=U2XkVxR7nr
> 3__D_L2mzbp9BvsOlRgrU-DqLnOEQKHpI&e=
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171113_7b8d56ff_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=LH4CVtxxRISB-mWEnV25Q_-vRqkR07Hbolg3u8LpP-w&e=>

------------------------------

Message: 7
Date: Tue, 14 Nov 2017 05:21:23 +1100
From: Melvin Hillsman <mrhillsman at gmail.com>
To: David Medberry <openstack at medberry.net>
Cc: OpenStack Operators <openstack-operators at lists.openstack.org>,
user-committee <user-committee at lists.openstack.org>
Subject: Re: [Openstack-operators] Sydney Takeaways - UC
Message-ID:
<CAMVtB2GVmCszNcEDsfBH-DW73mL3RxQywint1c1ruVqd3-jeCg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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 <openstack at medberry.net>
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://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docu&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=yUJrBQdNDstIGhsq7fQvt2JK19pdFSOPoiPVN90DsJU&e=
>       ment/d/1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
>
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_
> document_d_1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0&d=DwIGaQ&c=eIG
> jsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40Mfl
> BcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=lExIR
> u7rt6BY87caW8Ir456Q5KiVLu4qcDvhti7a0Ek&e=>
>
> 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
> <mrhillsman at gmail.com>
> 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://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.opensta
>> ck.org_p_SYD-2Dforum-2Duc&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK
>> 8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvE
>> FyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=j9vlch_TIx8tboUp7Klnflb2y2V9BK5k
>> 7UjuaTUfcQs&e= - 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://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docu&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=yUJrBQdNDstIGhsq7fQvt2JK19pdFSOPoiPVN90DsJU&e=
>>       ment/d/1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0
>>       <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1P4b8A9ybBaEYCu7xwVFt37jcZYzs9taxfNprwKlbdh0&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=lExIRu7rt6BY87caW8Ir456Q5KiVLu4qcDvhti7a0Ek&e=>
>>    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-dev list
>>    summary
>>       - single etherpad allowing SIGs to provide an update which will be
>>       compiled
>>    - Communication on what SIGs are and how they relate to existing
>>    Working Group/Project/Team structure (superuser, youtube, etc)
>>
>>
>>
>> Again, please add more items as you feel necessary. We want to be
>> able to create next steps from these items.
>>
>> --
>> Kind regards,
>>
>> OpenStack User Committee
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.o
>> rg_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=eIGjsI
>> TfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBc
>> MloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=U2XkVx
>> R7nr3__D_L2mzbp9BvsOlRgrU-DqLnOEQKHpI&e=
>>
>>
>


--
Kind regards,

Melvin Hillsman
mrhillsman at gmail.com
mobile: (832) 264-2646
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171114_6bef56ed_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=OgFbq17uOoAF8WBkW0SD73FUKCJkb6OjLQN7gUp0PwA&e=>

------------------------------

Message: 8
Date: Mon, 13 Nov 2017 14:17:24 -0500
From: Chris Morgan <mihalis68 at gmail.com>
To: David Medberry <openstack at medberry.net>
Cc: "openstack-operators at lists.openstack.org"
<openstack-operators at lists.openstack.org>
Subject: Re: [Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00
UTC
Message-ID:
<CA+NmNoMsuyJN0ZimDD+27J=xxmNkz4d2eNWeTpZZ-xjLJo8A_Q at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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 https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.debian.org_MeetBot&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=QppqPlmgyI2K2ErXu7qBgbDhDP8Z1R4_3fJkj65nTug&e= . (v 0.1.4)
11:00 AM Minutes:
https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_meetings_ops-5Fmeetup-5Fteam_2017_ops-5Fmeetup-5Fteam.2017-2D10-2D31-2D14.01.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=PIK3zJoeF_LpLWld1bv2TqMNd2d6LVRDZ8vxp3DjM4A&e=
11:00 AM Minutes (text):
https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_meetings_ops-5Fmeetup-5Fteam_2017_ops-5Fmeetup-5Fteam.2017-2D10-2D31-2D14.01.txt&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=nk3DUaAbuDGODdz_HWyULnOiME91_6SOVeiAbCOwH8M&e=
11:00 AM Log:
https://urldefense.proofpoint.com/v2/url?u=http-3A__eavesdrop.openstack.org_meetings_ops-5Fmeetup-5Fteam_2017_ops-5Fmeetup-5Fteam.2017-2D10-2D31-2D14.01.log.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=j_dwSEl5G8FiG_hx-M-SdJodlKyLrBpl3myQbgw6dXw&e=

Agenda as always goes at the top of this page:

https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_ops-2Dmeetups-2Dteam&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=c7GaPRrNAZzHr8uLjOSCdHiJFda51AxZsX5gOmPezmA&e=

I see someone has made a start, excellent!

Chris

On Mon, Nov 13, 2017 at 12:33 PM, Chris Morgan <mihalis68 at gmail.com> 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
> <openstack at medberry.net>
> 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 at lists.openstack.org
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.o
>> rg_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=eIGjsI
>> TfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBc
>> MloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=U2XkVx
>> R7nr3__D_L2mzbp9BvsOlRgrU-DqLnOEQKHpI&e=
>>
>>
>
>
> --
> Chris Morgan <mihalis68 at gmail.com>
>



--
Chris Morgan <mihalis68 at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_pipermail_openstack-2Doperators_attachments_20171113_a37747f6_attachment-2D0001.html&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=Nnio9eLgRIz4i-undh73MwVnBct9_MsOJ1aTRRp5iCo&e=>

------------------------------

Message: 9
Date: Tue, 14 Nov 2017 10:02:07 +0100
From: Saverio Proto <zioproto at gmail.com>
To: OpenStack Operators <openstack-operators at lists.openstack.org>,
OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
Subject: [Openstack-operators] LTS pragmatic example
Message-ID:
<CAPmmg8udWUAnG7z1fF=PTKLgoZuFRkfrxc4gbW325kCd+_tEpA at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Hello,

here an example of a trivial patch that is important for people that do operations, and they have to troubleshoot stuff.

with the old Stable Release thinking this patch would not be accepted on old stable branches.

Let's see if this gets accepted back to stable/newton

https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_q_If525313c63c4553abe8bea6f2bfaf75431ed18ea&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=bzoRclyzdbf2yv_jNxQTOqg-UEh1cgtQUISswJBcG5U&e=

Please note that a developers/operators that make the effort of fixing this in master, should do also all the cherry-pickes back. We dont have any automatic procudure for this.

thank you

Saverio



------------------------------

Message: 10
Date: Tue, 14 Nov 2017 22:33:57 +1100
From: Davanum Srinivas <davanum at gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org>
Cc: OpenStack Operators <openstack-operators at lists.openstack.org>
Subject: Re: [Openstack-operators] [openstack-dev] LTS pragmatic
example
Message-ID:
<CANw6fcFPPJNqwvL4fxVC+1mYYkWHMEQ2-MWgQoERRAPbiV_T_g at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Saverio,

This is still under the stable team reviews... NOT LTS.

Your contacts for the Nova Stable team is ...
https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_admin_groups_540-2Cmembers&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=kJcyJ55Fn2VlPjiXG0TvnwUq7sYZdRD-x2qntwm7Wis&e=

Let's please be clear, we need new people to help with LTS plans.
Current teams can't scale, they should not have to and it's totally unfair to expect them to do so.

Thanks,
Dims

On Tue, Nov 14, 2017 at 8:02 PM, Saverio Proto <zioproto at gmail.com> wrote:
> Hello,
>
> here an example of a trivial patch that is important for people that
> do operations, and they have to troubleshoot stuff.
>
> with the old Stable Release thinking this patch would not be accepted
> on old stable branches.
>
> Let's see if this gets accepted back to stable/newton
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.
> org_-23_q_If525313c63c4553abe8bea6f2bfaf75431ed18ea&d=DwIGaQ&c=eIGjsIT
> fXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMl
> oGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=bzoRclyzd
> bf2yv_jNxQTOqg-UEh1cgtQUISswJBcG5U&e=
>
> Please note that a developers/operators that make the effort of fixing
> this in master, should do also all the cherry-pickes back. We dont
> have any automatic procudure for this.
>
> thank you
>
> Saverio
>
> ______________________________________________________________________
> ____ OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.or
> g_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwIGaQ&c=eIGjsITfXP_y-D
> LLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aV
> wckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=s2m_wwMm15udg_Q5
> 7cMpL3HZ3nCzNVSMmBJhY6DJv3g&e=



--
Davanum Srinivas :: https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_dims&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=G3UdV-9Y0RBF3o1to0ps5ex1sdzOMaFGmRQszcvQQWI&e=



------------------------------

Subject: Digest Footer

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=drxJX5pWE9z1Y2RMsXdP-G40MflBcMloGAe-aVwckCM&m=rj7woCkvEFyX_-GAcZo-d4HBONVi1jmuo8svljw36vQ&s=U2XkVxR7nr3__D_L2mzbp9BvsOlRgrU-DqLnOEQKHpI&e=


------------------------------

End of OpenStack-operators Digest, Vol 85, Issue 13
***************************************************

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com


More information about the OpenStack-operators mailing list