Re: [Openstack] my ask.openstack.org question has waited for moderator approval for 17 days

[Melvin Hillsman]

Thanks Jimmy

On Mon, Nov 26, 2018 at 12:02 PM Jimmy McArthur  wrote:

> Hi all -
>
> Just a quick follow up on this... I just discovered a quirky UX bug that
> might explain some frustration people have been having with the
> moderation.  There were messages dating back to March 2018.  Basically,
> when you click to approve/disapprove/etc... it appears that the queue is
> cleared. But if you go to the menu and go back to the moderation page (or
> just reload), you get a whole new batch.  My guess is moderators have been
> thinking they're clearing things out, but not. I know that's what happened
> to me multiple times over a period of many months.
>
> I've since really and truly cleared out the queue.  I found about 25 users
> that were spammers and blocked all of them.  I also auto-approved anyone
> that was a valid poster so they can post without moderation moving forward.
>
> Ask.openstack.org is still a valued tool for our community and another
> way for people to engage outside of the mls.  It's full of not just valid
> questions, but a lot of valid answers.  I highly encourage those that are
> curious about becoming a moderator to check it out and let me know. I'm
> happy to elevate your user to a moderator if you want to contribute.
>
> Cheers,
> Jimmy
>
>
>
> Bernd Bausch 
> October 29, 2018 at 6:16 PM
> If there is a shortage of moderators, I volunteer.
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Jacob Burckhardt 
> October 29, 2018 at 6:03 PM
> My question on ask.openstack.org says "This post is awaiting moderation".
>
> It has been like that for 17 days. If you are a moderator, I'd appreciate
> if you'd decide whether to publicly post my question:
>
>
> https://ask.openstack.org/en/question/116591/is-there-example-of-using-python-zunclient-api/
>
> Thanks.
>
> -Jacob Burckhardt
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [OpenStack-Infra] Proposed changes to how we run our meeting

[Melvin Hillsman]

++

On Sun, Nov 18, 2018 at 2:32 PM Jeremy Stanley  wrote:

> On 2018-11-18 11:09:29 -0800 (-0800), Clark Boylan wrote:
> [...]
> > I propose that we require agenda updates 24 hours prior to the
> > meeting start time and if there are no agenda updates we cancel
> > the meeting. Curious to hear if others think this will be helpful
> > and if 24 hours is enough lead time to be helpful.
> [...]
>
> Sounds great to me, thanks for considering putting these ideas into
> practice!
> --
> Jeremy Stanley
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[Openstack] [openlab] October Report

[Melvin Hillsman]

Hi everyone,

Here are some highlights from OpenLab for the month of October:

CI additions
  - cluster-api-provider-openstack
  - AdoptOpenJDK
- very important open source project
- many Java developers
- strategic for open source ecosystem

Website redesign completed
  - fielding resource and support requests via GitHub
  - ML sign up via website
  - Community page
  - CI Infrastructure and High level request pipeline still manual but
driven by Google Sheets
  - closer to being fully automated; easier to manage via spreadsheet
instead of website backend

Promotion
  - OSN Day Dallas, November 6th, 2018
https://events.linuxfoundation.org/events/osn_days_2018/north-america/
dallas/
  - Twitter account is live - @askopenlab

Mailing List - https://lists.openlabtesting.org
  - running latest mailman
  - postorious frontend
  - net new members - 7

OpenLab Tests
  (October)
- total number of tests run - 3504
  - SUCCESS - 2421
  - FAILURE - 871
  - POST_FAILURE- 72
  - RETRY_LIMIT - 131
  - TIMED_OUT - 9
  - NODE_FAILURE - 0
  - SKIPPED - 0
- 69.0925% : 30.9075% (success to fail/other job ratio)

  (September)
- total number of tests run - 4350
  - SUCCESS - 2611
  - FAILURE - 1326
  - POST_FAILURE- 336
  - RETRY_LIMIT - 66
  - TIMED_OUT - 11
  - NODE_FAILURE - 0
  - SKIPPED - 0
- 60.0230% : 39.9770% (success to fail/other job ratio)

  Delta
- 9.0695% increase in success to fail/other job ratio
  - testament to great support by Chenrui and Liusheng "keeping the
lights on".

  Additional Infrastructure
- Packet
  - 80 vCPUs, 80G RAM, 1000G Disk
- ARM
  - ARM-based OpenStack Cloud
- Managed by codethink.co.uk
  - single compute node - 96 vCPUs, 128G RAM, 800G Disk
- Massachusetts Open Cloud
  - in progress
  - small project for now
  - academia partner


Build Status Legend:
SUCCESS
job executed correctly and exited without failure
FAILURE
job executed correctly, but exited with a failure
RETRY_LIMIT
pre-build tasks/plays failed more than the maximum number of retry
attempts
POST_FAILURE
post-build tasks/plays failed
SKIPPED
one of the build dependencies failed and this job was not executed
NODE_FAILURE
no device available to run the build
TIMED_OUT
build got stuck at some point and hit the timeout limit

Thank you to everyone who has read through this month’s update. If you have
any question/concerns please feel free to start a thread on the mailing
list or if it is something not to be shared publicly right now you can
email i...@openlabtesting.org

Kind regards,

OpenLab Governance Team


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] [openlab] October Report

[Melvin Hillsman]

Hi everyone,

Here are some highlights from OpenLab for the month of October:

CI additions
  - cluster-api-provider-openstack
  - AdoptOpenJDK
- very important open source project
- many Java developers
- strategic for open source ecosystem

Website redesign completed
  - fielding resource and support requests via GitHub
  - ML sign up via website
  - Community page
  - CI Infrastructure and High level request pipeline still manual but
driven by Google Sheets
  - closer to being fully automated; easier to manage via spreadsheet
instead of website backend

Promotion
  - OSN Day Dallas, November 6th, 2018
https://events.linuxfoundation.org/events/osn_days_2018/north-america/
dallas/
  - Twitter account is live - @askopenlab

Mailing List - https://lists.openlabtesting.org
  - running latest mailman
  - postorious frontend
  - net new members - 7

OpenLab Tests
  (October)
- total number of tests run - 3504
  - SUCCESS - 2421
  - FAILURE - 871
  - POST_FAILURE- 72
  - RETRY_LIMIT - 131
  - TIMED_OUT - 9
  - NODE_FAILURE - 0
  - SKIPPED - 0
- 69.0925% : 30.9075% (success to fail/other job ratio)

  (September)
- total number of tests run - 4350
  - SUCCESS - 2611
  - FAILURE - 1326
  - POST_FAILURE- 336
  - RETRY_LIMIT - 66
  - TIMED_OUT - 11
  - NODE_FAILURE - 0
  - SKIPPED - 0
- 60.0230% : 39.9770% (success to fail/other job ratio)

  Delta
- 9.0695% increase in success to fail/other job ratio
  - testament to great support by Chenrui and Liusheng "keeping the
lights on".

  Additional Infrastructure
- Packet
  - 80 vCPUs, 80G RAM, 1000G Disk
- ARM
  - ARM-based OpenStack Cloud
- Managed by codethink.co.uk
  - single compute node - 96 vCPUs, 128G RAM, 800G Disk
- Massachusetts Open Cloud
  - in progress
  - small project for now
  - academia partner


Build Status Legend:
SUCCESS
job executed correctly and exited without failure
FAILURE
job executed correctly, but exited with a failure
RETRY_LIMIT
pre-build tasks/plays failed more than the maximum number of retry
attempts
POST_FAILURE
post-build tasks/plays failed
SKIPPED
one of the build dependencies failed and this job was not executed
NODE_FAILURE
no device available to run the build
TIMED_OUT
build got stuck at some point and hit the timeout limit

Thank you to everyone who has read through this month’s update. If you have
any question/concerns please feel free to start a thread on the mailing
list or if it is something not to be shared publicly right now you can
email i...@openlabtesting.org

Kind regards,

OpenLab Governance Team


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] [openlab] October Report

[Melvin Hillsman]

Hi everyone,

Here are some highlights from OpenLab for the month of October:

CI additions
  - cluster-api-provider-openstack
  - AdoptOpenJDK
- very important open source project
- many Java developers
- strategic for open source ecosystem

Website redesign completed
  - fielding resource and support requests via GitHub
  - ML sign up via website
  - Community page
  - CI Infrastructure and High level request pipeline still manual but
driven by Google Sheets
  - closer to being fully automated; easier to manage via spreadsheet
instead of website backend

Promotion
  - OSN Day Dallas, November 6th, 2018
https://events.linuxfoundation.org/events/osn_days_2018/north-america/
dallas/
  - Twitter account is live - @askopenlab

Mailing List - https://lists.openlabtesting.org
  - running latest mailman
  - postorious frontend
  - net new members - 7

OpenLab Tests
  (October)
- total number of tests run - 3504
  - SUCCESS - 2421
  - FAILURE - 871
  - POST_FAILURE- 72
  - RETRY_LIMIT - 131
  - TIMED_OUT - 9
  - NODE_FAILURE - 0
  - SKIPPED - 0
- 69.0925% : 30.9075% (success to fail/other job ratio)

  (September)
- total number of tests run - 4350
  - SUCCESS - 2611
  - FAILURE - 1326
  - POST_FAILURE- 336
  - RETRY_LIMIT - 66
  - TIMED_OUT - 11
  - NODE_FAILURE - 0
  - SKIPPED - 0
- 60.0230% : 39.9770% (success to fail/other job ratio)

  Delta
- 9.0695% increase in success to fail/other job ratio
  - testament to great support by Chenrui and Liusheng "keeping the
lights on".

  Additional Infrastructure
- Packet
  - 80 vCPUs, 80G RAM, 1000G Disk
- ARM
  - ARM-based OpenStack Cloud
- Managed by codethink.co.uk
  - single compute node - 96 vCPUs, 128G RAM, 800G Disk
- Massachusetts Open Cloud
  - in progress
  - small project for now
  - academia partner


Build Status Legend:
SUCCESS
job executed correctly and exited without failure
FAILURE
job executed correctly, but exited with a failure
RETRY_LIMIT
pre-build tasks/plays failed more than the maximum number of retry
attempts
POST_FAILURE
post-build tasks/plays failed
SKIPPED
one of the build dependencies failed and this job was not executed
NODE_FAILURE
no device available to run the build
TIMED_OUT
build got stuck at some point and hit the timeout limit

Thank you to everyone who has read through this month’s update. If you have
any question/concerns please feel free to start a thread on the mailing
list or if it is something not to be shared publicly right now you can
email i...@openlabtesting.org

Kind regards,

OpenLab Governance Team


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] [user-committee] UC Meeting Reminder

[Melvin Hillsman]

UC meeting in #openstack-uc  at
1800UTC

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] [user-committee] UC Meeting Reminder

[Melvin Hillsman]

UC meeting in #openstack-uc  at
1800UTC

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] [user-committee] UC Meeting Reminder

[Melvin Hillsman]

UC meeting in #openstack-uc  at
1800UTC

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] Fwd: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

[Melvin Hillsman]

-- Forwarded message -
From: Samuel Cassiba 
Date: Fri, Sep 21, 2018 at 12:15 AM
Subject: Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the
lists! (was: Bringing the community together...)
To: openstack-dev 


On Thu, Sep 20, 2018 at 2:48 PM Doug Hellmann  wrote:
>
> Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +:
> > tl;dr: The openstack, openstack-dev, openstack-sigs and
> > openstack-operators mailing lists (to which this is being sent) will
> > be replaced by a new openstack-disc...@lists.openstack.org mailing
> > list.
>
> Since last week there was some discussion of including the openstack-tc
> mailing list among these lists to eliminate confusion caused by the fact
> that the list is not configured to accept messages from all subscribers
> (it's meant to be used for us to make sure TC members see meeting
> announcements).
>
> I'm inclined to include it and either use a direct mailing or the
> [tc] tag on the new discuss list to reach TC members, but I would
> like to hear feedback from TC members and other interested parties
> before calling that decision made. Please let me know what you think.
>
> Doug
>

+1 including the TC list as a tag makes sense to me and my tangent
about intent in online communities.

__
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


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Fwd: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

[Melvin Hillsman]

-- Forwarded message -
From: Samuel Cassiba 
Date: Fri, Sep 21, 2018 at 12:15 AM
Subject: Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the
lists! (was: Bringing the community together...)
To: openstack-dev 


On Thu, Sep 20, 2018 at 2:48 PM Doug Hellmann  wrote:
>
> Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +:
> > tl;dr: The openstack, openstack-dev, openstack-sigs and
> > openstack-operators mailing lists (to which this is being sent) will
> > be replaced by a new openstack-disc...@lists.openstack.org mailing
> > list.
>
> Since last week there was some discussion of including the openstack-tc
> mailing list among these lists to eliminate confusion caused by the fact
> that the list is not configured to accept messages from all subscribers
> (it's meant to be used for us to make sure TC members see meeting
> announcements).
>
> I'm inclined to include it and either use a direct mailing or the
> [tc] tag on the new discuss list to reach TC members, but I would
> like to hear feedback from TC members and other interested parties
> before calling that decision made. Please let me know what you think.
>
> Doug
>

+1 including the TC list as a tag makes sense to me and my tangent
about intent in online communities.

__
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


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [all] Naming the T release of OpenStack

[Melvin Hillsman]

I agree with Anita and wonder why Train did not meet the criteria? If there
is no way for Train to be an option outside of killing the voting, than for
the sake of integrity of processes which I have heard quite a few people
hold close to we should drop Train from the list. It is an unfortunate
thing in my view because I am actually a "non-developer" who agreed during
the feedback session that Train would be a great name but Anita is right on
this one imho.

On Thu, Oct 18, 2018 at 10:32 AM Anita Kuno  wrote:

> On 2018-10-18 2:35 a.m., Tony Breeds wrote:
> > Hello all,
> >  As per [1] the nomination period for names for the T release have
> > now closed (actually 3 days ago sorry).  The nominated names and any
> > qualifying remarks can be seen at2].
> >
> > Proposed Names
> >   * Tarryall
> >   * Teakettle
> >   * Teller
> >   * Telluride
> >   * Thomas
> >   * Thornton
> >   * Tiger
> >   * Tincup
> >   * Timnath
> >   * Timber
> >   * Tiny Town
> >   * Torreys
> >   * Trail
> >   * Trinidad
> >   * Treasure
> >   * Troublesome
> >   * Trussville
> >   * Turret
> >   * Tyrone
> >
> > Proposed Names that do not meet the criteria
> >   * Train
> >
> > However I'd like to suggest we skip the CIVS poll and select 'Train' as
> > the release name by TC resolution[3].  My think for this is
> >
> >   * It's fun and celebrates a humorous moment in our community
> >   * As a developer I've heard the T release called Train for quite
> > sometime, and was used often at the PTG[4].
> >   * As the *next* PTG is also in Colorado we can still choose a
> > geographic based name for U[5]
> >   * If train causes a problem for trademark reasons then we can always
> > run the poll
> >
> > I'll leave[3] for marked -W for a week for discussion to happen before
> the
> > TC can consider / vote on it.
> >
> > Yours Tony.
> >
> > [1]
> http://lists.openstack.org/pipermail/openstack-dev/2018-September/134995.html
> > [2] https://wiki.openstack.org/wiki/Release_Naming/T_Proposals
> > [3]
> https://review.openstack.org/#/q/I0d8d3f24af0ee8578712878a3d6617aad1e55e53
> > [4] https://twitter.com/vkmc/status/1040321043959754752
> > [5] https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T–Z
>
> I stand in opposition to any action that further undermines democracy.
>
> I have avoided events in Denver lately for this reason.
>
> If the support for Train is as universal as is portrayed, the poll with
> show us that.
>
> I don't care what the name is. I do want to participate in the
> selection. The method of participating has heretofore been a poll. I
> have seen no convincing argument to abandon the use of a poll now.
>
> I stand for what democracy there remains. I would like to participate in
> a poll.
>
> Thank you, Anita
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [openstack-dev] [SIGS] Ops Tools SIG

[Melvin Hillsman]

terday, during the Oslo meeting we discussed [6] the
> possibility
> >> >>>> of creating a new Special Interest Group [1][2] to provide home
> and release
> >> >>>> means for operator related tools [3] [4] [5]
> >> >>>>
> >> >>>>
> >> >>all of those tools have python dependencies related to openstack
> such as
> >> >> python-openstackclient or python-pbr. Which is exactly the reason
> why we
> >> >> moved osops-tools-monitoring-oschecks packaging away from OpsTools
> SIG to
> >> >> Cloud SIG. AFAIR we had some issues of having opstools SIG being
> dependent
> >> >> on openstack SIG. I believe that Cloud SIG is proper home for tools
> like
> >> >> [3][4][5] as they are related to OpenStack anyway. OpsTools SIG
> contains
> >> >> general tools like fluentd, sensu, collectd.
> >> >>
> >> >>
> >> >> Hope this helps,
> >> >> Martin
> >> >>
> >> >
> >> > Hey Martin,
> >> >
> >> > I'm not sure I understand the issue with these tools have
> dependencies on other
> >> > packages and the relationship to SIG ownership. Is your concern (or
> the history
> >> > of a concern you are pointing out) that the tools would have a more
> difficult
> >> > time if they required updates to dependencies if they are owned by a
> different
> >> > group?
> >> >
> >> > Thanks!
> >> > Sean
> >> >
> >>
> >> Hello,
> >>
> >> the mentioned sigs (opstools/cloud) are in CentOS scope and mention
> >> repository dependencies. That shouldn't bother us here now.
> >>
> >>
> >> There is already a SIG under the CentOS project, providing tools for
> >> operators[7], but also documentation and integrational bits.
> >>
> >> Also, there is some overlap with other groups and SIGs, such as
> >> Barometer[8].
> >>
> >> Since there is already some duplication, I don't know where it makes
> >> sense to have a single group for this purpose?
> >>
> >> If that hasn't been clear yet, I'd be absolutely interested in
> >> joining/helping this effort.
> >>
> >>
> >> Matthias
> >>
> >>
> >>
> >> [7] https://wiki.centos.org/SpecialInterestGroup/OpsTools
> >> [8] https://wiki.opnfv.org/collector/pages.action?key=fastpath
> >>
> >> --
> >> Matthias Runge 
> >>
> >> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
> >> Commercial register: Amtsgericht Muenchen, HRB 153243,
> >> Managing Directors: Charles Cachera, Michael Cunningham,
> >>  Michael O'Neill, Eric Shander
> >>
> >> ___
> >> OpenStack-operators mailing list
> >> OpenStack-operators@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >
> >
> > --
> > Miguel Ángel Ajo
> > OSP / Networking DFG, OVN Squad Engineering
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [all] Stepping down from Release Management team

[Melvin Hillsman]

Nooo! lol

Sorry to see you go but do stay in touch and I will do the same. Cheers to 
going on and continuing to do great things Anne; excited to see what you are up 
to in the coming days.

From: Anne Bertucio 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, October 8, 2018 at 11:40 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [all] Stepping down from Release Management team

Hi all,

I have had a fantastic time getting to work on the Release Management team and 
getting to know you all through the release marketing work, however, it is time 
for me to step down from my role on the Release Management team as I am moving 
on from my role at the Foundation and will no longer be working on upstream 
OpenStack. I cannot thank you all enough for how you all welcomed me into the 
OpenStack community and for how much I have learned about open source 
development in my time here.

If you have questions about cycle-highlights, swing by #openstack-release.
If you have questions about release marketing, contact 
lau...@openstack.org.
For other inquiries, contact 
alli...@openstack.org.
While I won't be working upstream anymore, I'll only be a Tweet or IRC message 
away.

Thank you again, and remember that cycle-highlights should be submitted by RC1.

Best,
Anne Bertucio
irc: annabelleB
twitter: @whyhiannabelle


Anne Bertucio
OpenStack Foundation
a...@openstack.org | irc: annabelleB





__
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] [Openstack-sigs] Capturing Feedback/Input

[Melvin Hillsman]

On Fri, Sep 21, 2018 at 11:16 AM Doug Hellmann 
wrote:

> Excerpts from Melvin Hillsman's message of 2018-09-21 10:18:26 -0500:
> > On Fri, Sep 21, 2018 at 9:41 AM Doug Hellmann 
> wrote:
> >
> > > Excerpts from Melvin Hillsman's message of 2018-09-20 17:30:32 -0500:
> > > > Hey everyone,
> > > >
> > > > During the TC meeting at the PTG we discussed the ideal way to
> capture
> > > > user-centric feedback; particular from our various groups like SIGs,
> WGs,
> > > > etc.
> > > >
> > > > Options that were mentioned ranged from a wiki page to a standalone
> > > > solution like discourse.
> > > >
> > > > While there is no perfect solution it was determined that Storyboard
> > > could
> > > > facilitate this. It would play out where there is a project group
> > > > openstack-uc? and each of the SIGs, WGs, etc would have a project
> under
> > > > this group; if I am wrong someone else in the room correct me.
> > > >
> > > > The entire point is a first step (maybe final) in centralizing
> > > user-centric
> > > > feedback that does not require any extra overhead be it cost, time,
> or
> > > > otherwise. Just kicking off a discussion so others have a chance to
> chime
> > > > in before anyone pulls the plug or pushes the button on anything and
> we
> > > > settle as a community on what makes sense.
> > > >
> > >
> > > I like the idea of tracking the information in storyboard. That
> > > said, one of the main purposes of creating SIGs was to separate
> > > those groups from the appearance that they were "managed" by the
> > > TC or UC. So, rather than creating a UC-focused project group, if
> > > we need a single project group at all, I would rather we call it
> > > "SIGs" or something similar.
> > >
> >
> > What you bring up re appearances makes sense definitely. Maybe we call it
> > openstack-feedback since the purpose is focused on that and I actually
> > looked at -uc as user-centric rather than user-committee; but
> appearances :)
>
> Feedback implies that SIGs aren't engaged in creating OpenStack, though,
> and I think that's the perception we're trying to change.
>
> > I think limiting it to SIGs will well, limit it to SIGs, and again could
> > appear to be specific to those groups rather than for example the Public
> > Cloud WG or Financial Team.
>
> OK, I thought those groups were SIGs.
>
> Maybe we're overthinking the organization on this. What is special about
> the items that would be on this list compared to items opened directly
> against projects?
>

Yeah unfortunately we do have a tendency to overthink/complicate things.
Not saying Storyboard is the right tool but suggested rather than having
something extra to maintain was what I understood. There are at least 3
things that were to be addressed:

- single pane so folks know where to provide/see updates
- it is not a catchall/dumpsite
  - something still needs to be flushed out/prioritized (Public Cloud WG's
missing features spreadsheet for example)
- not specific to a single project (i thought this was a given since there
is already a process/workflow for single project)

I could very well be wrong so I am open to be corrected. From my
perspective the idea in the room was to not circumvent anything internal
but rather make it easy for external viewers, passerbys, etc. When feedback
is gathered from Ops Meetup, OpenStack Days, Local meetups/events, we
discussed putting that here as well.


>
> Doug
>
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack-operators] [Openstack-sigs] Capturing Feedback/Input

[Melvin Hillsman]

On Fri, Sep 21, 2018 at 11:16 AM Doug Hellmann 
wrote:

> Excerpts from Melvin Hillsman's message of 2018-09-21 10:18:26 -0500:
> > On Fri, Sep 21, 2018 at 9:41 AM Doug Hellmann 
> wrote:
> >
> > > Excerpts from Melvin Hillsman's message of 2018-09-20 17:30:32 -0500:
> > > > Hey everyone,
> > > >
> > > > During the TC meeting at the PTG we discussed the ideal way to
> capture
> > > > user-centric feedback; particular from our various groups like SIGs,
> WGs,
> > > > etc.
> > > >
> > > > Options that were mentioned ranged from a wiki page to a standalone
> > > > solution like discourse.
> > > >
> > > > While there is no perfect solution it was determined that Storyboard
> > > could
> > > > facilitate this. It would play out where there is a project group
> > > > openstack-uc? and each of the SIGs, WGs, etc would have a project
> under
> > > > this group; if I am wrong someone else in the room correct me.
> > > >
> > > > The entire point is a first step (maybe final) in centralizing
> > > user-centric
> > > > feedback that does not require any extra overhead be it cost, time,
> or
> > > > otherwise. Just kicking off a discussion so others have a chance to
> chime
> > > > in before anyone pulls the plug or pushes the button on anything and
> we
> > > > settle as a community on what makes sense.
> > > >
> > >
> > > I like the idea of tracking the information in storyboard. That
> > > said, one of the main purposes of creating SIGs was to separate
> > > those groups from the appearance that they were "managed" by the
> > > TC or UC. So, rather than creating a UC-focused project group, if
> > > we need a single project group at all, I would rather we call it
> > > "SIGs" or something similar.
> > >
> >
> > What you bring up re appearances makes sense definitely. Maybe we call it
> > openstack-feedback since the purpose is focused on that and I actually
> > looked at -uc as user-centric rather than user-committee; but
> appearances :)
>
> Feedback implies that SIGs aren't engaged in creating OpenStack, though,
> and I think that's the perception we're trying to change.
>
> > I think limiting it to SIGs will well, limit it to SIGs, and again could
> > appear to be specific to those groups rather than for example the Public
> > Cloud WG or Financial Team.
>
> OK, I thought those groups were SIGs.
>
> Maybe we're overthinking the organization on this. What is special about
> the items that would be on this list compared to items opened directly
> against projects?
>

Yeah unfortunately we do have a tendency to overthink/complicate things.
Not saying Storyboard is the right tool but suggested rather than having
something extra to maintain was what I understood. There are at least 3
things that were to be addressed:

- single pane so folks know where to provide/see updates
- it is not a catchall/dumpsite
  - something still needs to be flushed out/prioritized (Public Cloud WG's
missing features spreadsheet for example)
- not specific to a single project (i thought this was a given since there
is already a process/workflow for single project)

I could very well be wrong so I am open to be corrected. From my
perspective the idea in the room was to not circumvent anything internal
but rather make it easy for external viewers, passerbys, etc. When feedback
is gathered from Ops Meetup, OpenStack Days, Local meetups/events, we
discussed putting that here as well.


>
> Doug
>
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [Openstack-sigs] Capturing Feedback/Input

[Melvin Hillsman]

On Fri, Sep 21, 2018 at 11:16 AM Doug Hellmann 
wrote:

> Excerpts from Melvin Hillsman's message of 2018-09-21 10:18:26 -0500:
> > On Fri, Sep 21, 2018 at 9:41 AM Doug Hellmann 
> wrote:
> >
> > > Excerpts from Melvin Hillsman's message of 2018-09-20 17:30:32 -0500:
> > > > Hey everyone,
> > > >
> > > > During the TC meeting at the PTG we discussed the ideal way to
> capture
> > > > user-centric feedback; particular from our various groups like SIGs,
> WGs,
> > > > etc.
> > > >
> > > > Options that were mentioned ranged from a wiki page to a standalone
> > > > solution like discourse.
> > > >
> > > > While there is no perfect solution it was determined that Storyboard
> > > could
> > > > facilitate this. It would play out where there is a project group
> > > > openstack-uc? and each of the SIGs, WGs, etc would have a project
> under
> > > > this group; if I am wrong someone else in the room correct me.
> > > >
> > > > The entire point is a first step (maybe final) in centralizing
> > > user-centric
> > > > feedback that does not require any extra overhead be it cost, time,
> or
> > > > otherwise. Just kicking off a discussion so others have a chance to
> chime
> > > > in before anyone pulls the plug or pushes the button on anything and
> we
> > > > settle as a community on what makes sense.
> > > >
> > >
> > > I like the idea of tracking the information in storyboard. That
> > > said, one of the main purposes of creating SIGs was to separate
> > > those groups from the appearance that they were "managed" by the
> > > TC or UC. So, rather than creating a UC-focused project group, if
> > > we need a single project group at all, I would rather we call it
> > > "SIGs" or something similar.
> > >
> >
> > What you bring up re appearances makes sense definitely. Maybe we call it
> > openstack-feedback since the purpose is focused on that and I actually
> > looked at -uc as user-centric rather than user-committee; but
> appearances :)
>
> Feedback implies that SIGs aren't engaged in creating OpenStack, though,
> and I think that's the perception we're trying to change.
>
> > I think limiting it to SIGs will well, limit it to SIGs, and again could
> > appear to be specific to those groups rather than for example the Public
> > Cloud WG or Financial Team.
>
> OK, I thought those groups were SIGs.
>
> Maybe we're overthinking the organization on this. What is special about
> the items that would be on this list compared to items opened directly
> against projects?
>

Yeah unfortunately we do have a tendency to overthink/complicate things.
Not saying Storyboard is the right tool but suggested rather than having
something extra to maintain was what I understood. There are at least 3
things that were to be addressed:

- single pane so folks know where to provide/see updates
- it is not a catchall/dumpsite
  - something still needs to be flushed out/prioritized (Public Cloud WG's
missing features spreadsheet for example)
- not specific to a single project (i thought this was a given since there
is already a process/workflow for single project)

I could very well be wrong so I am open to be corrected. From my
perspective the idea in the room was to not circumvent anything internal
but rather make it easy for external viewers, passerbys, etc. When feedback
is gathered from Ops Meetup, OpenStack Days, Local meetups/events, we
discussed putting that here as well.


>
> Doug
>
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] Capturing Feedback/Input

[Melvin Hillsman]

Hey everyone,

During the TC meeting at the PTG we discussed the ideal way to capture
user-centric feedback; particular from our various groups like SIGs, WGs,
etc.

Options that were mentioned ranged from a wiki page to a standalone
solution like discourse.

While there is no perfect solution it was determined that Storyboard could
facilitate this. It would play out where there is a project group
openstack-uc? and each of the SIGs, WGs, etc would have a project under
this group; if I am wrong someone else in the room correct me.

The entire point is a first step (maybe final) in centralizing user-centric
feedback that does not require any extra overhead be it cost, time, or
otherwise. Just kicking off a discussion so others have a chance to chime
in before anyone pulls the plug or pushes the button on anything and we
settle as a community on what makes sense.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Capturing Feedback/Input

[Melvin Hillsman]

Hey everyone,

During the TC meeting at the PTG we discussed the ideal way to capture
user-centric feedback; particular from our various groups like SIGs, WGs,
etc.

Options that were mentioned ranged from a wiki page to a standalone
solution like discourse.

While there is no perfect solution it was determined that Storyboard could
facilitate this. It would play out where there is a project group
openstack-uc? and each of the SIGs, WGs, etc would have a project under
this group; if I am wrong someone else in the room correct me.

The entire point is a first step (maybe final) in centralizing user-centric
feedback that does not require any extra overhead be it cost, time, or
otherwise. Just kicking off a discussion so others have a chance to chime
in before anyone pulls the plug or pushes the button on anything and we
settle as a community on what makes sense.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] Capturing Feedback/Input

[Melvin Hillsman]

Hey everyone,

During the TC meeting at the PTG we discussed the ideal way to capture
user-centric feedback; particular from our various groups like SIGs, WGs,
etc.

Options that were mentioned ranged from a wiki page to a standalone
solution like discourse.

While there is no perfect solution it was determined that Storyboard could
facilitate this. It would play out where there is a project group
openstack-uc? and each of the SIGs, WGs, etc would have a project under
this group; if I am wrong someone else in the room correct me.

The entire point is a first step (maybe final) in centralizing user-centric
feedback that does not require any extra overhead be it cost, time, or
otherwise. Just kicking off a discussion so others have a chance to chime
in before anyone pulls the plug or pushes the button on anything and we
settle as a community on what makes sense.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

[Melvin Hillsman]

 I agree all lists should be merged as discussed otherwise why not just
leave all things as they are :P

On Thu, Sep 20, 2018 at 4:49 PM Emilien Macchi  wrote:

>
>
> On Thu, Sep 20, 2018 at 5:47 PM Doug Hellmann 
> wrote:
>
>> Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +:
>> > tl;dr: The openstack, openstack-dev, openstack-sigs and
>> > openstack-operators mailing lists (to which this is being sent) will
>> > be replaced by a new openstack-disc...@lists.openstack.org mailing
>> > list.
>>
>> Since last week there was some discussion of including the openstack-tc
>> mailing list among these lists to eliminate confusion caused by the fact
>> that the list is not configured to accept messages from all subscribers
>> (it's meant to be used for us to make sure TC members see meeting
>> announcements).
>>
>> I'm inclined to include it and either use a direct mailing or the
>> [tc] tag on the new discuss list to reach TC members, but I would
>> like to hear feedback from TC members and other interested parties
>> before calling that decision made. Please let me know what you think.
>>
>
> +2 , easier to manage, easier to reach 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
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] [docs] Nominating Ian Y. Choi for openstack-doc-core

[Melvin Hillsman]

++

On Thu, Sep 20, 2018 at 3:11 PM Frank Kloeker  wrote:

> Am 2018-09-19 20:54, schrieb Andreas Jaeger:
> > On 2018-09-19 20:50, Petr Kovar wrote:
> >> Hi all,
> >>
> >> Based on our PTG discussion, I'd like to nominate Ian Y. Choi for
> >> membership in the openstack-doc-core team. I think Ian doesn't need an
> >> introduction, he's been around for a while, recently being deeply
> >> involved
> >> in infra work to get us robust support for project team docs
> >> translation and
> >> PDF builds.
> >>
> >> Having Ian on the core team will also strengthen our integration with
> >> the i18n community.
> >>
> >> Please let the ML know should you have any objections.
> >
> > The opposite ;), heartly agree with adding him,
> >
> > Andreas
>
> ++
>
> Frank
>
>
> __
> 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
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] [Openstack-sigs] [tc]Global Reachout Proposal

[Melvin Hillsman]

er to read scrollback, and certainly not for more than a couple of
> channels.
>
> Other people, however, have a completely different perspective: they
> want a place where they are guaranteed to be reachable at any time (even
> if they don't see it until later) and the entire record is always right
> there. I think Slack was built for those kinds of people. You would have
> to drag me kicking and screaming into Slack even if it weren't
> proprietary software.
>
> I don't know where WeChat falls on that spectrum. But maybe part of the
> issue is that we're creating too high an expectation of what it means to
> participate in the community (e.g. if you're not going to set up a
> bouncer and be reachable 24/7 then you might as well not get involved at
> all - this is 100% untrue). I've seen several assertions, including in
> the review, that any decisions must be documented on the mailing list or
> IRC, and I'm not sure I agree. IMHO, any decisions should be documented
> on the mailing list, period.
>
> I'd love to see more participation on the mailing list. Since it is
> asynchronous already it's somewhat friendlier to those in APAC time
> zones (although there are still issues, real or perceived, with
> decisions being reached before anyone on that side of the world has a
> chance to weigh in), and a lot easier than carrying on a conversation in
> real time for those who don't speak English natively. And while can
> still be technical challenges with mailing lists, almost every company
> allows email through their corporate firewall.
>
> AIUI though, augmenting IRC was not the point of the proposal. Rather, I
> think it was for TC members to 'fly the flag' in WeChat to be more
> visible and available to the portion of the community that is there.
>
> > In that sense, It would be great to have
> > OpenStack community provided, simplified and well-written, written in
> > multiple language, IRC guide docs. Alternatively, if OpenStack community
> > can provide a good web-based irc client tool, that would be fantastic.
>
> I haven't tried it but: https://webchat.freenode.net/
>
> > As I described the above, we can certainly have a healthy discussion on
> > what different and real problems we are facing from Asia.
> > However, I don't think this TC resolution is good way to do that.
> >
> > Cheers,
> > --
> >
> > Jaesuk Ahn, Team Lead
> > Virtualization SW Lab, SW R Center
> >
> > SK Telecom
> >
> >
> > ___
> > openstack-sigs mailing list
> > openstack-s...@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
> >
>
>
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

[Melvin Hillsman]

You're welcome!

-- 

Kind regards,

Melvin Hillsman

mrhills...@gmail.com
mobile: (832) 264-2646

On Wed, Sep 12, 2018, 5:52 PM Matt Riedemann  wrote:

> On 9/12/2018 5:32 PM, Melvin Hillsman wrote:
> > We basically spent the day focusing on two things specific to what you
> > bring up and are in agreement with you regarding action not just talk
> > around feedback and outreach. [1]
> > We wiped the agenda clean, discussed our availability (set reasonable
> > expectations), and revisited how we can be more diligent and successful
> > around these two principles which target your first comment, "...get
> > their RFE/bug list ranked from the operator community (because some of
> > the requests are not exclusive to public cloud), and then put pressure
> > on the TC to help project manage the delivery of the top issue..."
> >
> > I will not get into much detail because again this response is specific
> > to a portion of your email so in keeping with feedback and outreach the
> > UC is making it a point to be intentional. We have already got action
> > items [2] which target the concern you raise. We have agreed to hold
> > each other accountable and adjusted our meeting structure to facilitate
> > being successful.
> >
> > Not that the UC (elected members) are the only ones who can do this but
> > we believe it is our responsibility to; regardless of what anyone else
> > does. The UC is also expected to enlist others and hopefully through our
> > efforts others are encouraged participate and enlist others.
> >
> > [1] https://etherpad.openstack.org/p/uc-stein-ptg
> > [2] https://etherpad.openstack.org/p/UC-Election-Qualifications
>
> Awesome, thank you Melvin and others on the UC.
>
> --
>
> Thanks,
>
> Matt
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

[Melvin Hillsman]

You're welcome!

-- 

Kind regards,

Melvin Hillsman

mrhills...@gmail.com
mobile: (832) 264-2646

On Wed, Sep 12, 2018, 5:52 PM Matt Riedemann  wrote:

> On 9/12/2018 5:32 PM, Melvin Hillsman wrote:
> > We basically spent the day focusing on two things specific to what you
> > bring up and are in agreement with you regarding action not just talk
> > around feedback and outreach. [1]
> > We wiped the agenda clean, discussed our availability (set reasonable
> > expectations), and revisited how we can be more diligent and successful
> > around these two principles which target your first comment, "...get
> > their RFE/bug list ranked from the operator community (because some of
> > the requests are not exclusive to public cloud), and then put pressure
> > on the TC to help project manage the delivery of the top issue..."
> >
> > I will not get into much detail because again this response is specific
> > to a portion of your email so in keeping with feedback and outreach the
> > UC is making it a point to be intentional. We have already got action
> > items [2] which target the concern you raise. We have agreed to hold
> > each other accountable and adjusted our meeting structure to facilitate
> > being successful.
> >
> > Not that the UC (elected members) are the only ones who can do this but
> > we believe it is our responsibility to; regardless of what anyone else
> > does. The UC is also expected to enlist others and hopefully through our
> > efforts others are encouraged participate and enlist others.
> >
> > [1] https://etherpad.openstack.org/p/uc-stein-ptg
> > [2] https://etherpad.openstack.org/p/UC-Election-Qualifications
>
> Awesome, thank you Melvin and others on the UC.
>
> --
>
> Thanks,
>
> Matt
>
__
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] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

[Melvin Hillsman]

We basically spent the day focusing on two things specific to what you
bring up and are in agreement with you regarding action not just talk
around feedback and outreach. [1]

We wiped the agenda clean, discussed our availability (set reasonable
expectations), and revisited how we can be more diligent and successful
around these two principles which target your first comment, "...get their
RFE/bug list ranked from the operator community (because some of the
requests are not exclusive to public cloud), and then put pressure on the
TC to help project manage the delivery of the top issue..."

I will not get into much detail because again this response is specific to
a portion of your email so in keeping with feedback and outreach the UC is
making it a point to be intentional. We have already got action items [2]
which target the concern you raise. We have agreed to hold each other
accountable and adjusted our meeting structure to facilitate being
successful.

Not that the UC (elected members) are the only ones who can do this but we
believe it is our responsibility to; regardless of what anyone else does.
The UC is also expected to enlist others and hopefully through our efforts
others are encouraged participate and enlist others.

[1] https://etherpad.openstack.org/p/uc-stein-ptg
[2] https://etherpad.openstack.org/p/UC-Election-Qualifications

On Wed, Sep 12, 2018 at 6:13 PM Jeremy Stanley  wrote:

> On 2018-09-12 17:05:17 -0600 (-0600), Lance Bragstad wrote:
> [...]
> > IMHO, I think the point Matt is making here is more about ensuring
> > sure we have people to do what we've agreed upon, as a community,
> > as being mission critical. Enablement is imperative, but no matter
> > how good we are at it, sometimes we really just needs hands to do
> > the work.
> [...]
>
> Sure, and I'm saying that instead I think the influence of TC
> members _can_ be more valuable in finding and helping additional
> people to do these things rather than doing it all themselves, and
> it's not just about the limited number of available hours in the day
> for one person versus many. The successes goal champions experience,
> the connections they make and the elevated reputation they gain
> throughout the community during the process of these efforts builds
> new leaders for us all.
> --
> 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
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] Cinder HA with zookeeper or redis?

[Melvin Hillsman]

Additionally if you require some resources to test this against OpenLab is
a great resource - https://openlabtesting.org provides more info -
https://github.com/theopenlab/resource-requests/issues/new - is where you
can skip having to go through the site to do so

On Mon, Sep 10, 2018 at 3:19 PM Jay S Bryant  wrote:

>
> On 9/9/2018 10:58 PM, Adam Spiers wrote:
> > Hi James,
> >
> > James Penick  wrote:
> >> Hey folks,
> >> Does anyone have experience using zookeeper or redis to handle HA
> >> failover
> >> in cinder clusters?
> >
> > I'm guessing you mean failover of an active/passive cinder-volume
> > service?
> >
> >> I know there's docs on pacemaker, however we already
> >> have the other two installed and don't want to add yet another
> >> component to
> >> package and maintain in our clusters.
> >
> > I'm afraid I don't, but if you make any progress on this, please let
> > me know as it would be great to document:
> >
> >  - how this would work
> >  - any pros and cons vs. Pacemaker
> >
> > and maybe I can help with that.
> >
> > One particular question: if the node running the service becomes
> > unreachable, is it safe to fail it over straight away, or is fencing
> > required first?  (I'm pretty sure I've asked this same question
> > before, but I can't remember the answer - sorry!)
> James,
>
> I echo Adam's input.  I have only heard of people implementing with
> pacemaker but there is no reason that this couldn't be tried with other
> HA solutions.
>
> If you are able to try it and document it would be great to add
> documentation here:  [1]
>
> Also, Gorka Eguileor is a good contact as he has been doing much of the
> work on HA Cinder though his focus is on Active/Active HA.
>
> Let us know if you have any further questions.
>
> Thanks!
> Jay
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack] [Openstack-operators] [openstack-dev] [all] Bringing the community together (combine the lists!)

[Melvin Hillsman]

I think the more we can reduce the ML sprawl the better. I also recall us
discussing having some documentation or way of notifying net new signups of
how to interact with the ML successfully. An example was having some
general guidelines around tagging. Also as a maintainer for at least one of
the mailing lists over the past 6+ months I have to inquire about how that
will happen going forward which again could be part of this
documentation/initial message.

Also there are many times I miss messages that for one reason or another do
not hit the proper mailing list. I mean we could dive into the minutia or
start up the mountain of why keeping things the way they are is worst than
making this change and vice versa but I am willing to bet there are more
advantages than disadvantages.

On Thu, Aug 30, 2018 at 4:45 PM Jimmy McArthur  wrote:

>
>
> Jeremy Stanley wrote:
>
> On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote:
> [...]
>
> I really don't want this. I'm happy with things being sorted in
> multiple lists, even though I'm subscribed to multiples.
>
> IMO this is easily solved by tagging.  If emails are properly tagged
> (which they typically are), most email clients will properly sort on rules
> and you can just auto-delete if you're 100% not interested in a particular
> topic.
>

Yes, there are definitely ways to go about discarding unwanted mail
automagically or not seeing it at all. And to be honest I think if we are
relying on so many separate MLs to do that for us it is better community
wide for the responsibility for that to be on individuals. It becomes very
tiring and inefficient time wise to have to go through the various issues
of the way things are now; cross-posting is a great example that is
steadily getting worse.


> SNIP
>
> As the years went by, it's become apparent to me that this is
> actually an antisocial behavior pattern, and actively harmful to the
> user base. I believe OpenStack actually wants users to see the
> development work which is underway, come to understand it, and
> become part of that process. Requiring them to have their
> conversations elsewhere sends the opposite message.
>
> I really and truly believe that it has become a blocker for our
> community.  Conversations sent to multiple lists inherently splinter and we
> end up with different groups coming up with different solutions for a
> single problem.  Literally the opposite desired result of sending things to
> multiple lists.  I believe bringing these groups together, with tags, will
> solve a lot of immediate problems. It will also have an added bonus of
> allowing people "catching up" on the community to look to a single place
> for a thread i/o 1-5 separate lists.  It's better in both the short and
> long term.
>

+1


>
> Cheers,
> Jimmy
>
> __
> 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
>
>
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack-operators] [openstack-dev] [all] Bringing the community together (combine the lists!)

[Melvin Hillsman]

I think the more we can reduce the ML sprawl the better. I also recall us
discussing having some documentation or way of notifying net new signups of
how to interact with the ML successfully. An example was having some
general guidelines around tagging. Also as a maintainer for at least one of
the mailing lists over the past 6+ months I have to inquire about how that
will happen going forward which again could be part of this
documentation/initial message.

Also there are many times I miss messages that for one reason or another do
not hit the proper mailing list. I mean we could dive into the minutia or
start up the mountain of why keeping things the way they are is worst than
making this change and vice versa but I am willing to bet there are more
advantages than disadvantages.

On Thu, Aug 30, 2018 at 4:45 PM Jimmy McArthur  wrote:

>
>
> Jeremy Stanley wrote:
>
> On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote:
> [...]
>
> I really don't want this. I'm happy with things being sorted in
> multiple lists, even though I'm subscribed to multiples.
>
> IMO this is easily solved by tagging.  If emails are properly tagged
> (which they typically are), most email clients will properly sort on rules
> and you can just auto-delete if you're 100% not interested in a particular
> topic.
>

Yes, there are definitely ways to go about discarding unwanted mail
automagically or not seeing it at all. And to be honest I think if we are
relying on so many separate MLs to do that for us it is better community
wide for the responsibility for that to be on individuals. It becomes very
tiring and inefficient time wise to have to go through the various issues
of the way things are now; cross-posting is a great example that is
steadily getting worse.


> SNIP
>
> As the years went by, it's become apparent to me that this is
> actually an antisocial behavior pattern, and actively harmful to the
> user base. I believe OpenStack actually wants users to see the
> development work which is underway, come to understand it, and
> become part of that process. Requiring them to have their
> conversations elsewhere sends the opposite message.
>
> I really and truly believe that it has become a blocker for our
> community.  Conversations sent to multiple lists inherently splinter and we
> end up with different groups coming up with different solutions for a
> single problem.  Literally the opposite desired result of sending things to
> multiple lists.  I believe bringing these groups together, with tags, will
> solve a lot of immediate problems. It will also have an added bonus of
> allowing people "catching up" on the community to look to a single place
> for a thread i/o 1-5 separate lists.  It's better in both the short and
> long term.
>

+1


>
> Cheers,
> Jimmy
>
> __
> 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
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [Openstack-operators] [all] Bringing the community together (combine the lists!)

[Melvin Hillsman]

I think the more we can reduce the ML sprawl the better. I also recall us
discussing having some documentation or way of notifying net new signups of
how to interact with the ML successfully. An example was having some
general guidelines around tagging. Also as a maintainer for at least one of
the mailing lists over the past 6+ months I have to inquire about how that
will happen going forward which again could be part of this
documentation/initial message.

Also there are many times I miss messages that for one reason or another do
not hit the proper mailing list. I mean we could dive into the minutia or
start up the mountain of why keeping things the way they are is worst than
making this change and vice versa but I am willing to bet there are more
advantages than disadvantages.

On Thu, Aug 30, 2018 at 4:45 PM Jimmy McArthur  wrote:

>
>
> Jeremy Stanley wrote:
>
> On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote:
> [...]
>
> I really don't want this. I'm happy with things being sorted in
> multiple lists, even though I'm subscribed to multiples.
>
> IMO this is easily solved by tagging.  If emails are properly tagged
> (which they typically are), most email clients will properly sort on rules
> and you can just auto-delete if you're 100% not interested in a particular
> topic.
>

Yes, there are definitely ways to go about discarding unwanted mail
automagically or not seeing it at all. And to be honest I think if we are
relying on so many separate MLs to do that for us it is better community
wide for the responsibility for that to be on individuals. It becomes very
tiring and inefficient time wise to have to go through the various issues
of the way things are now; cross-posting is a great example that is
steadily getting worse.


> SNIP
>
> As the years went by, it's become apparent to me that this is
> actually an antisocial behavior pattern, and actively harmful to the
> user base. I believe OpenStack actually wants users to see the
> development work which is underway, come to understand it, and
> become part of that process. Requiring them to have their
> conversations elsewhere sends the opposite message.
>
> I really and truly believe that it has become a blocker for our
> community.  Conversations sent to multiple lists inherently splinter and we
> end up with different groups coming up with different solutions for a
> single problem.  Literally the opposite desired result of sending things to
> multiple lists.  I believe bringing these groups together, with tags, will
> solve a lot of immediate problems. It will also have an added bonus of
> allowing people "catching up" on the community to look to a single place
> for a thread i/o 1-5 separate lists.  It's better in both the short and
> long term.
>

+1


>
> Cheers,
> Jimmy
>
> __
> 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
>
>
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] OpenStack PTG!

[Melvin Hillsman]

Hi everyone,

Friendly reminder that ticket prices will increase to USD $599 on August 22
at 11:59pm PT (August 23 at 6:59 UTC) for the PTG. So purchase your tickets
before the price increases.

Register here: https://denver2018ptg.eventbrite.com <
https://denver2018ptg.eventbrite.com/>

Also the discounted hotel block is filling up if it has not already and the
last date to book in the hotel block is TODAY! so book now here:
www.openstack.org/ptg <http://www.openstack.org/ptg>

PTG questions?, please email ptg at openstack.org <mailto:ptg at
openstack.org>

--
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] getting back onto our IRC channel

[Melvin Hillsman]

I just tried irssi on MacOS without any other stuff added to the config
just a fresh install and I am able to talk to NickServ and appears I can
register the nick if I so choose. Quite possible your IP or an IP along
your path of talking to Freenode is blacklisted Chris.

On Wed, Aug 8, 2018 at 2:23 PM iain MacDonnell 
wrote:

>
> According to:
>
>
> https://superuser.com/questions/1220409/irc-how-to-register-on-freenode-using-hexchat-when-i-get-disconnected-immediat
>
> there's a blacklist of source address ranges from which SASL auth/e is
> required.
>
>  ~iain
>
>
>
> On 08/08/2018 12:03 PM, Chris Morgan wrote:
> > I'm sure I'm doing something wrong, but it's really not obvious, hence
> > this email.
> >
> > I tried just "/connect chat.freenode.net
> > <
> https://urldefense.proofpoint.com/v2/url?u=http-3A__chat.freenode.net=DwMFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs=XitLUTp1htaMQO9yd3X4qTLgEaEKYUScTKuga61xBnM=hZAfF36UBBrPqqDYxYnjUXSWNOyfTga0P_lzOaA1Ax0=>"
>
> > and then "/msg nickserv ..." a few times. I always got dumped and it
> > said "You need to identify via SASL to use this server". Something like
> > that.
> >
> > If I don't connect first, then I just get "Not connected to server" when
> > I try to /msg nickserv
> >
> > chris
> >
> > On Wed, Aug 8, 2018 at 2:57 PM Jeremy Stanley  > <mailto:fu...@yuggoth.org>> wrote:
> >
> > On 2018-08-08 14:43:33 -0400 (-0400), Chris Morgan wrote:
> > [...]
> >  > What did not work for me is trying to msg nickserv from the
> > command-line
> >  > IRC client (irssi). I can't send a message to nickserv without
> > connecting,
> >  > and (it seems to me anyway) can't connect without a nickname.
> > Seems a bit
> >  > chicken and egg to this IRC newbie.
> > [...]
> >
> > It's been a while since I used irssi personally (switched to weechat
> > some 5-6 years ago), but it should only have rejected your ability
> > to auto-join OpenStack official IRC channels until you
> > registered/identified and not prevented you from connecting to
> > Freenode. You only need to be in a server buffer and connected to be
> > able to `/msg nickserv ...` but don't need to be in any channels at
> > all so shouldn't be a chicken-and-egg scenario.
> > --
> > Jeremy Stanley
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > <mailto:OpenStack-operators@lists.openstack.org>
> >
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> > <
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators=DwMFaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs=XitLUTp1htaMQO9yd3X4qTLgEaEKYUScTKuga61xBnM=pOs2IpLof7IqciYxf2K2rTsQ9jqCKkIAlL_mvXqqCDo=
> >
> >
> >
> >
> > --
> > Chris Morgan mailto:mihali...@gmail.com>>
> >
> >
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators=DwIGaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs=XitLUTp1htaMQO9yd3X4qTLgEaEKYUScTKuga61xBnM=pOs2IpLof7IqciYxf2K2rTsQ9jqCKkIAlL_mvXqqCDo=
> >
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: User Committee Meeting @ 1400UTC

[Melvin Hillsman]

Hi everyone,

Reminder about UC meeting in #openstack-uc; please add to agenda:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: User Committee @ 1800 UTC

[Melvin Hillsman]

Hi everyone,

UC meeting today in #openstack-uc
Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee

-- 

Kind regards,

Melvin Hillsman

mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] Reminder: User Committee @ 1800 UTC

[Melvin Hillsman]

Hi everyone,

UC meeting today in #openstack-uc
Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee

-- 

Kind regards,

Melvin Hillsman

mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] [openstack-community] Openstack package repo

[Melvin Hillsman]

May I suggest install python-pip and then pip install python-swiftclient
(python-openstackclient, python-whateverclient, etc at that point)

On Tue, Jul 10, 2018 at 10:32 AM, Amy Marrich  wrote:

> Alfredo,
>
> Forwarding this to the OPS list in the hopes of it reaching the
> appropriate folks, but you might also want to checkout the RDO repos
>
> https://trunk.rdoproject.org/centos7/current/
>
>
> Thanks,
>
>
> Amy (spotz)
>
> On Tue, Jul 10, 2018 at 10:07 AM, Alfredo De Luca <
> alfredo.del...@gmail.com> wrote:
>
>> Hi all.
>> I have centos/7 on a VM Virtualbox... I want to install all the openstack
>> python clients (nova, swift etc).
>> I installed
>> *yum install centos-release-openstack-queens *
>>
>> and all good but when I try to install one client I have the following
>> error:
>>
>> yum install python-swiftclient
>>
>> **
>> Loaded plugins: fastestmirror
>> Loading mirror speeds from cached hostfile
>>  * base: mirror.infonline.de
>>  * extras: mirror.infonline.de
>>  * updates: centos.mirrors.psw.services
>> centos-ceph-luminous
>> | 2.9 kB  00:00:00
>> centos-openstack-queens
>>  | 2.9 kB  00:00:00
>> *http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/repodata/repomd.xml
>> <http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/repodata/repomd.xml>:
>> [Errno 14] HTTP Error 404 - Not Found*
>> Trying other mirror.
>> To address this issue please refer to the below wiki article
>>
>> https://wiki.centos.org/yum-errors
>> **
>>
>> Now the only way to install the package (or any other) is to disable that
>> repo
>> *yum-config-manager --disable centos-qemu-ev*
>>
>> then I can install the client...
>>
>> Any idea?
>> It looks like *http://mirror.centos.org/altarch/7/virt/x86_64
>> <http://mirror.centos.org/altarch/7/virt/x86_64> doesn't exist.*
>>
>>
>>
>>
>>
>>
>> --
>> *Alfredo*
>>
>>
>> ___
>> Community mailing list
>> commun...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>>
>>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack] Reminder: UC Meeting Today 1800UTC / 1300CST

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/Us
erCommittee for UC meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646

>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Reminder: UC Meeting Today 1800UTC / 1300CST

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/Us
erCommittee for UC meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646

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

[openstack-dev] Reminder: UC Meeting Today 1800UTC / 1300CST

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/Us
erCommittee for UC meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646

>
__
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-operators] Reminder: User Committee Meeting - Monday July 2nd @1400UTC

[Melvin Hillsman]

In case you did not get the reminder on Friday afternoon ;)

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646

On Fri, Jun 29th, 2018 at 12:59 PM, Melvin Hillsman  
wrote:

> 
> Hi everyone,
> 
> 
> Please be sure to join us - if not getting ready for firecrackers - on
> Monday July 2nd @1400UTC in #openstack-uc for weekly User Committee
> meeting.
> 
> 
> Also you can freely add to the meeting agenda here - 
> (
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs
> )
> 
> 
> 
> Governance/Foundation/UserCommittee - OpenStack (
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs
> ) (
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs
> ) WIKI.OPENSTACK.ORG (
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs
> )
> 
> 
> 
> 
> 
> 
> 
> -- 
> Kind regards,
> 
> Melvin Hillsman
> mrhills...@gmail.com
> mobile: (832) 264-2646
>___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Fwd: Reminder: User Committee Meeting - Monday July 2nd @1400UTC

[Melvin Hillsman]

Hi everyone,

Please be sure to join us - if not getting ready for firecrackers - on
Monday July 2nd @1400UTC in #openstack-uc for weekly User Committee meeting.

Also you can freely add to the meeting agenda here -
Governance/Foundation/UserCommittee - OpenStack
<https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs>
<https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs>
WIKI.OPENSTACK.ORG
<https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs>
<https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: User Committee Meeting - Monday July 2nd @1400UTC

[Melvin Hillsman]

Hi everyone,

Please be sure to join us - if not getting ready for firecrackers - on Monday 
July 2nd @1400UTC in #openstack-uc for weekly User Committee meeting.

Also you can freely add to the meeting agenda here - 
( 
https://share.polymail.io/v1/z/b/NWIzNjZlYzY4YmFm/a4uka23nadCqVfJyXGVUd8seO-2TVguxjo5CXjMRfv6BfwuOHgsFdwaD5gqm42rq7S0EQJ2MIGcgH9AtUVfEieePkQzsFoAt1OaUgaIp0NtZpZK4dWfyHXTS3KuBASt50Uw1EdlADr41wcc2nQVQpFf9trzWdTHt9_ZjAc0PQrBJvTlG2nXDmvunA1m2N-H8jMIRsejqbpleDwqc7eXzV-xJPvCinnzRWGeMohmiMraUGS3wlftXrtqhmmXCWh0aW0Xrr-GB2aoJBOwSodyJl5DisHXFxMlnk_z6OYrHfl2rU_ByIO4rhUL9zYxT
 )

Governance/Foundation/UserCommittee - OpenStack ( 
https://share.polymail.io/v1/z/b/NWIzNjZlYzY4YmFm/a4uka23nadCqVfJyXGVUd8seO-2TVguxjo5CXjMRfv6BfwuOHgsFdwaD5gqm42rq7S0EQJ2MIGcgH9AtUVfEieePkQzsFoAt1OaUgaIp0NtZpZK4dWfyHXTS3KuBASt50Uw1EdlADr41wcc2nQVQpFf9trzWdTHt9_ZjAc0PQrBJvTlG2nXDmvunA1m2N-H8jMIRsejqbpleDwqc7eXzV-xJPvCinnzRWGeMohmiMraUGS3wlftXrtqhmmXCWh0aW0Xrr-GB2aoJBOwSodyJl5DisHXFxMlnk_z6OYrHfl2rU_ByIO4rhUL9zYxT
 ) ( 
https://share.polymail.io/v1/z/b/NWIzNjZlYzY4YmFm/a4uka23nadCqVfJyXGVUd8seO-2TVguxjo5CXjMRfv6BfwuOHgsFdwaD5gqm42rq7S0EQJ2MIGcgH9AtUVfEieePkQzsFoAt1OaUgaIp0NtZpZK4dWfyHXTS3KuBASt50Uw1EdlADr41wcc2nQVQpFf9trzWdTHt9_ZjAc0PQrBJvTlG2nXDmvunA1m2N-H8jMIRsejqbpleDwqc7eXzV-xJPvCinnzRWGeMohmiMraUGS3wlftXrtqhmmXCWh0aW0Xrr-GB2aoJBOwSodyJl5DisHXFxMlnk_z6OYrHfl2rU_ByIO4rhUL9zYxT
 ) WIKI.OPENSTACK.ORG ( 
https://share.polymail.io/v1/z/b/NWIzNjZlYzY4YmFm/a4uka23nadCqVfJyXGVUd8seO-2TVguxjo5CXjMRfv6BfwuOHgsFdwaD5gqm42rq7S0EQJ2MIGcgH9AtUVfEieePkQzsFoAt1OaUgaIp0NtZpZK4dWfyHXTS3KuBASt50Uw1EdlADr41wcc2nQVQpFf9trzWdTHt9_ZjAc0PQrBJvTlG2nXDmvunA1m2N-H8jMIRsejqbpleDwqc7eXzV-xJPvCinnzRWGeMohmiMraUGS3wlftXrtqhmmXCWh0aW0Xrr-GB2aoJBOwSodyJl5DisHXFxMlnk_z6OYrHfl2rU_ByIO4rhUL9zYxT
 )

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack] Get Your Survey On!

[Melvin Hillsman]

Hi everyone,

Running, operating, supporting an OpenStack cloud?

Participate in the User Survey <http://www.openstack.org/user-survey> to
share more about your technology implementations and provide feedback for
the community.

The deadline to complete the survey and be part of the next report is
*Friday, August
3 at 23:59 UTC.*

   - Login and complete the OpenStack User Survey here:
   http://www.openstack.org/user-survey
   <http://www.openstack.org/user-survey>
   - Help with the survey analysis by jointing the OpenStack User Survey
   Working Group: https://openstackfoundation.formstack.com/forms/user_
   survey_working_group
   - And promote the User Survey!: https://twitter.com/Op
   enStack/status/993589356312088577
   <https://twitter.com/OpenStack/status/993589356312088577>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Reminder: UC Meeting Today 1800UTC

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Reminder: UC Meeting Today 1800UTC

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] Reminder: UC Meeting Today 1800UTC

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] Reminder: UC Meeting Today 1400UTC / 0900CST

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Reminder: UC Meeting Today 1400UTC / 0900CST

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] Reminder: UC Meeting Today 1400UTC / 0900CST

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee for UC meeting info and add additional agenda items if needed.


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] Creation of a server get stuck at Building state

[Melvin Hillsman]

I would recommend grepping for the request ID across all logs if they are
centralized. Additionally if you have not turned on debugging, more than
likely doing so for at least nova-scheduler prior to trying to spin up an
instance again should help. Providing error messages is generally
beneficial as if you are not able to see any there is really no way for
anyone to assist without some additional details so I first suggest you
look a bit more at all your logs and in general your environment and
provide a bit more detail for assistance. Hope this helps.

On Sat, Jun 9, 2018 at 1:52 PM, ravi@us.fujitsu.com <
ravi@us.fujitsu.com> wrote:

> Hi All,
>
>I have installed openstack queens using packstack on a multimode setup.
> One controller and two compute nodes.
>
> Openstack hypervisor list shows all 3 compute nodes as up.
>
> I was able to spinup about 5 servers and all of them got hosted on the
> controller node which is also a compute.
>
> When I try to spin the 6th server it is getting stuck at the build state.
> Looks like it is not able to use the other two compute nodes.
>
> I have already verified all the cells_v2 settings and they all look ok.
>
> Can one of you please let me know what logs to check to understand what is
> causing this issue.
>
> None of the Nova logs on the controller has any errors..
>
> Any help to resolve this is greatly appreciated.
>
> Regards,
>
> Ravi..
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Reminder: UC Meeting Monday 1400UTC

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/
Foundation/UserCommittee for UC meeting info and add additional agenda
items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Reminder: UC Meeting Monday 1400UTC

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/
Foundation/UserCommittee for UC meeting info and add additional agenda
items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] Reminder: UC Meeting Monday 1400UTC

[Melvin Hillsman]

Hey everyone,

Please see https://wiki.openstack.org/wiki/Governance/
Foundation/UserCommittee for UC meeting info and add additional agenda
items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] OpenLab Cross-community Impact

[Melvin Hillsman]

Hi everyone,

I know we have sent out quite a bit of information over the past few days
with the OpenStack Summit and other updates recently. Additionally there
are plenty of meetings we all attend. I just want to take time to point to
something very significant in my opinion and again give big thanks to
Chris, Dims, Liusheng, Chenrui, Zhuli, Joe (gophercloud), and anyone else
contributing to OpenLab.

A member of the release team working on the testing infrastructure for
Kubernetes did a shoutout to the team for the following:

(AishSundar)
Shoutout to @dims and OpenStack team for quickly getting their 1.11
Conformance results piped to CI runs and contributing results to
Conformance dashboard !
https://k8s-testgrid.appspot.com/sig-release-1.11-all#Conformance%20-%20OpenStack=

Here is why this is significant and those working on this who I previously
mentioned should get recognition:

(hogepodge)
OpenStack and GCE are the first two clouds that will release block on
conformance testing failures. Thanks @dims for building out the test
pipeline and @mrhillsman for leading the OpenLab efforts that are reporting
back to the test grid. @RuiChen for his contributions to the testing
effort. Amazing work for the last six months.

In other words, if the external cloud provider ci conformance tests we do
in OpenLab are not passing, it will be one of the signals used for blocking
the release. OpenStack and GCE are the first two clouds to achieve this and
it is a significant accomplishment for the OpenLab team and the OpenStack
community overall regarding our relationship with the Kubernetes community.
Thanks again Chris, Dims, Joe, Liusheng, Chenrui, and Zhuli for the work
you have done and continue to do in this space.

Personally I hope we take a moment to really consider this milestone and
work to ensure OpenLab's continued success as we embark on working on other
integrations. We started OpenLab hoping we could make substantial impact
specifically for the ecosystem that builds on top of OpenStack and this is
evidence we can and should do more.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] OpenLab Cross-community Impact

[Melvin Hillsman]

Hi everyone,

I know we have sent out quite a bit of information over the past few days
with the OpenStack Summit and other updates recently. Additionally there
are plenty of meetings we all attend. I just want to take time to point to
something very significant in my opinion and again give big thanks to
Chris, Dims, Liusheng, Chenrui, Zhuli, Joe (gophercloud), and anyone else
contributing to OpenLab.

A member of the release team working on the testing infrastructure for
Kubernetes did a shoutout to the team for the following:

(AishSundar)
Shoutout to @dims and OpenStack team for quickly getting their 1.11
Conformance results piped to CI runs and contributing results to
Conformance dashboard !
https://k8s-testgrid.appspot.com/sig-release-1.11-all#Conformance%20-%20OpenStack=

Here is why this is significant and those working on this who I previously
mentioned should get recognition:

(hogepodge)
OpenStack and GCE are the first two clouds that will release block on
conformance testing failures. Thanks @dims for building out the test
pipeline and @mrhillsman for leading the OpenLab efforts that are reporting
back to the test grid. @RuiChen for his contributions to the testing
effort. Amazing work for the last six months.

In other words, if the external cloud provider ci conformance tests we do
in OpenLab are not passing, it will be one of the signals used for blocking
the release. OpenStack and GCE are the first two clouds to achieve this and
it is a significant accomplishment for the OpenLab team and the OpenStack
community overall regarding our relationship with the Kubernetes community.
Thanks again Chris, Dims, Joe, Liusheng, Chenrui, and Zhuli for the work
you have done and continue to do in this space.

Personally I hope we take a moment to really consider this milestone and
work to ensure OpenLab's continued success as we embark on working on other
integrations. We started OpenLab hoping we could make substantial impact
specifically for the ecosystem that builds on top of OpenStack and this is
evidence we can and should do more.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] Ops Community Documentation - first anchor point

[Melvin Hillsman]

 > > are a very good toolset in place for testing and publishing
> documents.
> :> > > There are also various text editors for rst extensions available,
> like in
> :> > > vim, notepad++ or also online services. I understand the concerns
> and when
> :> > > people are sad because their patches are ignored for months. But
> it's
> :> > > alltime a question of responsibilty and how can spend people time.
> :> > > I would be available for help. As I18n PTL I could imagine that a
> :> > > OpenStack Operations Guide is available in different languages and
> portable
> :> > > in different formats like in Sphinx. For us as translation team
> it's a good
> :> > > possibility to get feedback about the quality and to understand the
> :> > > requirements, also for other documents.
> :> > > So let's move on.
> :> > >
> :> > > kind regards
> :> > >
> :> > > Frank
> :> > >
> :> > > [1] https://review.openstack.org/#/admin/groups/30,members
> :> > > [2] https://github.com/openstack/operations-guide
> :> > >
> :> > >
> :> > > Am 2018-05-24 03:38, schrieb Chris Morgan:
> :> > >
> :> > >> Hello Everyone,
> :> > >>
> :> > >> In the Ops Community documentation working session today in
> Vancouver,
> :> > >> we made some really good progress (etherpad here:
> :> > >> https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not
> all of
> :> > >> the good stuff is yet written down).
> :> > >>
> :> > >> In short, we're going to course correct on maintaining the
> Operators
> :> > >> Guide, the HA Guide and Architecture Guide, not edit-in-place via
> the
> :> > >> wiki and instead try still maintaining them as code, but with a
> :> > >> different, new set of owners, possibly in a new Ops-focused repo.
> :> > >> There was a strong consensus that a) code workflow >> wiki workflow
> :> > >> and that b) openstack core docs tools are just fine.
> :> > >>
> :> > >> There is a lot still to be decided on how where and when, but we do
> :> > >> have an offer of a rewrite of the HA Guide, as long as the changes
> :> > >> will be allowed to actually land, so we expect to actually start
> :> > >> showing some progress.
> :> > >>
> :> > >> At the end of the session, people wanted to know how to follow
> along
> :> > >> as various people work out how to do this... and so for now that
> place
> :> > >> is this very email thread. The idea is if the code for those
> documents
> :> > >> goes to live in a different repo, or if new contributors turn up,
> or
> :> > >> if a new version we will announce/discuss it here until such time
> as
> :> > >> we have a better home for this initiative.
> :> > >>
> :> > >> Cheers
> :> > >>
> :> > >> Chris
> :> > >>
> :> > >> --
> :> > >> Chris Morgan <mihali...@gmail.com>
> :> > >> ___
> :> > >> OpenStack-operators mailing list
> :> > >> OpenStack-operators@lists.openstack.org
> :> > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
> :> > >>
> :> > >
> :> > >
> :> > > ___
> :> > > OpenStack-operators mailing list
> :> > > OpenStack-operators@lists.openstack.org
> :> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
> :> > >
> :> >
> :
> :___
> :OpenStack-operators mailing list
> :OpenStack-operators@lists.openstack.org
> :http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Community Documentation - first anchor point

[Melvin Hillsman]

gt; > >> https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not all
> of
> > >> the good stuff is yet written down).
> > >>
> > >> In short, we're going to course correct on maintaining the Operators
> > >> Guide, the HA Guide and Architecture Guide, not edit-in-place via the
> > >> wiki and instead try still maintaining them as code, but with a
> > >> different, new set of owners, possibly in a new Ops-focused repo.
> > >> There was a strong consensus that a) code workflow >> wiki workflow
> > >> and that b) openstack core docs tools are just fine.
> > >>
> > >> There is a lot still to be decided on how where and when, but we do
> > >> have an offer of a rewrite of the HA Guide, as long as the changes
> > >> will be allowed to actually land, so we expect to actually start
> > >> showing some progress.
> > >>
> > >> At the end of the session, people wanted to know how to follow along
> > >> as various people work out how to do this... and so for now that place
> > >> is this very email thread. The idea is if the code for those documents
> > >> goes to live in a different repo, or if new contributors turn up, or
> > >> if a new version we will announce/discuss it here until such time as
> > >> we have a better home for this initiative.
> > >>
> > >> Cheers
> > >>
> > >> Chris
> > >>
> > >> --
> > >> Chris Morgan <mihali...@gmail.com>
> > >> ___
> > >> OpenStack-operators mailing list
> > >> OpenStack-operators@lists.openstack.org
> > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
> > >>
> > >
> > >
> > > ___
> > > OpenStack-operators mailing list
> > > OpenStack-operators@lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
> > >
> >
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Community Documentation - first anchor point

[Melvin Hillsman]

Also, apologies, if consolidation or reorganizing all these is reasonable,
what do you think that would look like; i.e.

osops
> tools
>> contrib
>> generic
>> monitoring
>> logging
> docs
> example-configs


On Wed, May 23, 2018 at 10:26 PM, Melvin Hillsman <mrhills...@gmail.com>
wrote:

> Great to see this moving. I have some questions/concerns based on your
> statement Doug about docs.openstack.org publishing and do not want to
> detour the conversation but ask for feedback. Currently there are a number
> of repositories under osops-
>
> https://github.com/openstack-infra/project-config/blob/
> master/gerrit/projects.yaml#L5673-L5703
>
> Generally active:
> osops-tools-contrib
> osops-tools-generic
> osops-tools-monitoring
>
>
> Probably dead:
> osops-tools-logging
> osops-coda
> osops-example-configs
>
> Because you are more familiar with how things work, is there a way to
> consolidate these vs coming up with another repo like osops-docs or
> whatever in this case? And second, is there already governance clearance to
> publish based on the following - https://launchpad.net/osops - which is
> where these repos originated.
>
>
> On Wed, May 23, 2018 at 9:56 PM, Frank Kloeker <eu...@arcor.de> wrote:
>
>> Hi Chris,
>>
>> thanks for summarize our session today in Vancouver. As I18n PTL and one
>> of the Docs Core I put Petr in Cc. He is currently Docs PTL, but
>> unfortunatelly not on-site.
>> I couldn't also not get the full history of the story and that's also not
>> the idea to starting finger pointing. As usualy we moving forward and there
>> are some interesting things to know what happened.
>> First of all: There are no "Docs-Team" anymore. If you look at [1] there
>> are mostly part-time contributors like me or people are more involved in
>> other projects and therefore busy. Because of that, the responsibility of
>> documentation content are moved completely to the project teams. Each repo
>> has a user guide, admin guide, deployment guide, and so on. The small
>> Documentation Team provides only tooling and give advices how to write and
>> publish a document. So it's up to you to re-use the old repo on [2] or
>> setup a new one. I would recommend to use the best of both worlds. There
>> are a very good toolset in place for testing and publishing documents.
>> There are also various text editors for rst extensions available, like in
>> vim, notepad++ or also online services. I understand the concerns and when
>> people are sad because their patches are ignored for months. But it's
>> alltime a question of responsibilty and how can spend people time.
>> I would be available for help. As I18n PTL I could imagine that a
>> OpenStack Operations Guide is available in different languages and portable
>> in different formats like in Sphinx. For us as translation team it's a good
>> possibility to get feedback about the quality and to understand the
>> requirements, also for other documents.
>> So let's move on.
>>
>> kind regards
>>
>> Frank
>>
>> [1] https://review.openstack.org/#/admin/groups/30,members
>> [2] https://github.com/openstack/operations-guide
>>
>>
>> Am 2018-05-24 03:38, schrieb Chris Morgan:
>>
>>> Hello Everyone,
>>>
>>> In the Ops Community documentation working session today in Vancouver,
>>> we made some really good progress (etherpad here:
>>> https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not all of
>>> the good stuff is yet written down).
>>>
>>> In short, we're going to course correct on maintaining the Operators
>>> Guide, the HA Guide and Architecture Guide, not edit-in-place via the
>>> wiki and instead try still maintaining them as code, but with a
>>> different, new set of owners, possibly in a new Ops-focused repo.
>>> There was a strong consensus that a) code workflow >> wiki workflow
>>> and that b) openstack core docs tools are just fine.
>>>
>>> There is a lot still to be decided on how where and when, but we do
>>> have an offer of a rewrite of the HA Guide, as long as the changes
>>> will be allowed to actually land, so we expect to actually start
>>> showing some progress.
>>>
>>> At the end of the session, people wanted to know how to follow along
>>> as various people work out how to do this... and so for now that place
>>> is this very email thread. The idea is if the code for those documents
>>> goes to live in a different repo, or if new contributors turn up, or
>>> 

Re: [Openstack-operators] Ops Community Documentation - first anchor point

[Melvin Hillsman]

Great to see this moving. I have some questions/concerns based on your
statement Doug about docs.openstack.org publishing and do not want to
detour the conversation but ask for feedback. Currently there are a number
of repositories under osops-

https://github.com/openstack-infra/project-config/blob/master/gerrit/projects.yaml#L5673-L5703

Generally active:
osops-tools-contrib
osops-tools-generic
osops-tools-monitoring


Probably dead:
osops-tools-logging
osops-coda
osops-example-configs

Because you are more familiar with how things work, is there a way to
consolidate these vs coming up with another repo like osops-docs or
whatever in this case? And second, is there already governance clearance to
publish based on the following - https://launchpad.net/osops - which is
where these repos originated.


On Wed, May 23, 2018 at 9:56 PM, Frank Kloeker <eu...@arcor.de> wrote:

> Hi Chris,
>
> thanks for summarize our session today in Vancouver. As I18n PTL and one
> of the Docs Core I put Petr in Cc. He is currently Docs PTL, but
> unfortunatelly not on-site.
> I couldn't also not get the full history of the story and that's also not
> the idea to starting finger pointing. As usualy we moving forward and there
> are some interesting things to know what happened.
> First of all: There are no "Docs-Team" anymore. If you look at [1] there
> are mostly part-time contributors like me or people are more involved in
> other projects and therefore busy. Because of that, the responsibility of
> documentation content are moved completely to the project teams. Each repo
> has a user guide, admin guide, deployment guide, and so on. The small
> Documentation Team provides only tooling and give advices how to write and
> publish a document. So it's up to you to re-use the old repo on [2] or
> setup a new one. I would recommend to use the best of both worlds. There
> are a very good toolset in place for testing and publishing documents.
> There are also various text editors for rst extensions available, like in
> vim, notepad++ or also online services. I understand the concerns and when
> people are sad because their patches are ignored for months. But it's
> alltime a question of responsibilty and how can spend people time.
> I would be available for help. As I18n PTL I could imagine that a
> OpenStack Operations Guide is available in different languages and portable
> in different formats like in Sphinx. For us as translation team it's a good
> possibility to get feedback about the quality and to understand the
> requirements, also for other documents.
> So let's move on.
>
> kind regards
>
> Frank
>
> [1] https://review.openstack.org/#/admin/groups/30,members
> [2] https://github.com/openstack/operations-guide
>
>
> Am 2018-05-24 03:38, schrieb Chris Morgan:
>
>> Hello Everyone,
>>
>> In the Ops Community documentation working session today in Vancouver,
>> we made some really good progress (etherpad here:
>> https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not all of
>> the good stuff is yet written down).
>>
>> In short, we're going to course correct on maintaining the Operators
>> Guide, the HA Guide and Architecture Guide, not edit-in-place via the
>> wiki and instead try still maintaining them as code, but with a
>> different, new set of owners, possibly in a new Ops-focused repo.
>> There was a strong consensus that a) code workflow >> wiki workflow
>> and that b) openstack core docs tools are just fine.
>>
>> There is a lot still to be decided on how where and when, but we do
>> have an offer of a rewrite of the HA Guide, as long as the changes
>> will be allowed to actually land, so we expect to actually start
>> showing some progress.
>>
>> At the end of the session, people wanted to know how to follow along
>> as various people work out how to do this... and so for now that place
>> is this very email thread. The idea is if the code for those documents
>> goes to live in a different repo, or if new contributors turn up, or
>> if a new version we will announce/discuss it here until such time as
>> we have a better home for this initiative.
>>
>> Cheers
>>
>> Chris
>>
>> --
>> Chris Morgan <mihali...@gmail.com>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: UC Meeting Monday 1800UTC

[Melvin Hillsman]

Hey everyone,

Please see
https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee for UC
meeting info and add additional agenda items if needed.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack] help

[Melvin Hillsman]

Douaa can you provide details on the error you are getting? Also I am
adding the Operators ML as some more practitioners may be able to see it
from there.

On Mon, Apr 23, 2018 at 11:55 AM, Douaa <zinouba...@gmail.com> wrote:

> Hello
> I'm trying to use openstack (VIM) on openbaton for that i create to VMs
> one for OpenStack and the second for Opnebaton.
> i have installed packstack on CentOS and Openbaton on ubuntu 16.04. Now
> i'm trying to create VIM Openstack on openbaton but i have erreur there is
> any plugins or configuration i have to do it before creating VIM Openstack ?
>  Thanks for helping
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack-operators] [Openstack] help

[Melvin Hillsman]

Douaa can you provide details on the error you are getting? Also I am
adding the Operators ML as some more practitioners may be able to see it
from there.

On Mon, Apr 23, 2018 at 11:55 AM, Douaa <zinouba...@gmail.com> wrote:

> Hello
> I'm trying to use openstack (VIM) on openbaton for that i create to VMs
> one for OpenStack and the second for Opnebaton.
> i have installed packstack on CentOS and Openbaton on ubuntu 16.04. Now
> i'm trying to create VIM Openstack on openbaton but i have erreur there is
> any plugins or configuration i have to do it before creating VIM Openstack ?
>  Thanks for helping
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openst...@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [OpenStack] [user-committee] Reminder: UC Meeting 4/23 @ 1800UTC

[Melvin Hillsman]

Hi everyone,

Friendly reminder we have a UC meeting tomorrow in #openstack-uc on
freenode at 18:00UTC

Agenda:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCo
mmittee#Meeting_Agenda.2FPrevious_Meeting_Logs


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: UC Meeting 4/23 @ 1800UTC

[Melvin Hillsman]

Hi everyone,

Friendly reminder we have a UC meeting tomorrow in #openstack-uc on
freenode at 18:00UTC

Agenda:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCo
mmittee#Meeting_Agenda.2FPrevious_Meeting_Logs


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [OpenStack-Infra] PTG September 10-14 in Denver

[Melvin Hillsman]

Planning on being in attendance (travel approval pending)

On Fri, Apr 20, 2018 at 12:58 PM, Jeremy Stanley <fu...@yuggoth.org> wrote:

> On 2018-04-20 10:42:48 -0700 (-0700), Clark Boylan wrote:
> [...]
> > Let me know (doesn't have to be to the list if you aren't
> > comfortable with that) and thanks!
>
> You can expect me there. Not only was the venue great, the
> restaurants within walking distance were just my speed and, as icing
> on the cake, Denver is one of the few airports to/from which I can
> get direct flights!
> --
> Jeremy Stanley
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [Openstack-operators] UC Meeting Reminder - 4/9 @ 1800UTC

[Melvin Hillsman]

UC Meeting started :)

On Mon, Apr 9, 2018 at 9:17 AM, Melvin Hillsman <mrhills...@gmail.com>
wrote:

> Hi everyone,
>
> Friendly reminder we have a UC meeting today in #openstack-uc on freenode
> at 18:00UTC
>
> Agenda:
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCo
> mmittee#Meeting_Agenda.2FPrevious_Meeting_Logs
>
>
> --
> Kind regards,
>
> Melvin Hillsman
> mrhills...@gmail.com
> mobile: (832) 264-2646
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] UC Meeting Reminder - 4/9 @ 1800UTC

[Melvin Hillsman]

Hi everyone,

Friendly reminder we have a UC meeting today in #openstack-uc on freenode
at 18:00UTC

Agenda:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCo
mmittee#Meeting_Agenda.2FPrevious_Meeting_Logs


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

[Melvin Hillsman]

+1

On Mon, Apr 2, 2018 at 11:39 AM, Jimmy McArthur <ji...@openstack.org> wrote:

> Hi all -
>
> I'd like to check in to see if we've come to a consensus on the colocation
> of the Ops Meetup.  Please let us know as soon as possible as we have to
> alert our events team.
>
> Thanks!
> Jimmy
>
> Chris Morgan <mihali...@gmail.com>
> March 27, 2018 at 11:44 AM
> Hello Everyone,
>   This proposal looks to have very good backing in the community. There
> was an informal IRC meeting today with the meetups team, some of the
> foundation folk and others and everyone seems to like a proposal put
> forward as a sample definition of the combined event - I certainly do, it
> looks like we could have a really great combined event in September.
>
> I volunteered to share that a bit later today with some other info. In the
> meanwhile if you have a viewpoint please do chime in here as we'd like to
> declare this agreed by the community ASAP, so in particular IF YOU OBJECT
> please speak up by end of week, this week.
>
> Thanks!
>
> Chris
>
>
>
>
> --
> Chris Morgan <mihali...@gmail.com>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> Jonathan Proulx <j...@csail.mit.edu>
> March 23, 2018 at 10:07 AM
> On Thu, Mar 22, 2018 at 09:02:48PM -0700, Yih Leong, Sun. wrote:
> :I support the ideas to try colocating the next Ops Midcycle and PTG.
> :Although scheduling could be a potential challenge but it worth give it a
> :try.
> :
> :Also having an joint social event in the evening can also help Dev/Ops to
> :meet and offline discussion. :)
>
> Agreeing stongly with Matt and Melvin's comments about Forum -vs-
> PTG/OpsMidcycle
>
> PTG/OpsMidcycle (as I see them) are about focusing inside teams to get
> work done ("how" is a a good one word I think). The advantage of
> colocation is for cross team questions like "we're thinking of doing
> this thing this way, does this have any impacts on your work my might
> not have considered", can get a quick respose in the hall, at lunch,
> or over beers as Yih Leong suggests.
>
> Forum has become about coming to gather across groups for more
> conceptual "what" discussions.
>
> So I also thing they are very distinct and I do see potential benefits
> to colocation.
>
> We do need to watch out for downsides. The concerns around colocation
> seemed mostly about larger events costing more and being generally
> harder to organize. If we try we will find out if there is merit to
> this concern, but (IMO) it is important to keep both of the
> events as cheap and simple as possible.
>
> -Jon
>
> :
> :On Thursday, March 22, 2018, Melvin Hillsman <mrhills...@gmail.com>
> <mrhills...@gmail.com> wrote:
> :
> :> Thierry and Matt both hit the nail on the head in terms of the very
> :> base/purpose/point of the Forum, PTG, and Ops Midcycles and here is my
> +2
> :> since I have spoke with both and others outside of this thread and agree
> :> with them here as I have in individual discussions.
> :>
> :> If nothing else I agree with Jimmy's original statement of at least
> giving
> :> this a try.
> :>
> :> On Thu, Mar 22, 2018 at 4:54 PM, Matt Van Winkle
> <mvanw...@rackspace.com> <mvanw...@rackspace.com>
> :> wrote:
> :>
> :>> Hey folks,
> :>> Great discussion! There are number of points to comment on going back
> :>> through the last few emails. I'll try to do so in line with Theirry's
> :>> latest below. From a User Committee perspective (and as a member of the
> :>> Ops Meetup planning team), I am a convert to the idea of co-location,
> but
> :>> have come to see a lot of value in it. I'll point some of that out as I
> :>> respond to specific comments, but first a couple of overarching points.
> :>>
> :>> In the current model, the Forum sessions are very much about WHAT the
> :>> software should do. Keeping the discussions focused on behavior,
> feature
> :>> and function has made it much easier for an operator to participate
> :>> effectively in the conversation versus the older, design sessions, that
> :>> focused largely on blueprints, coding approaches, etc. These are HOW
> the
> :>> developers should make things work and, now, are a large part of the
> focus
> :>> of the PTG. I realize it's not that cut and dry, but current model has
> :>> allowed for this division of "what" and "how" in many areas, and I

[Openstack-operators] Meeting Reminder - 4/2 @ 1400UTC

[Melvin Hillsman]

Hi everyone,

Friendly reminder we have a UC meeting tomorrow in #openstack-uc on
freenode at 14:00UTC

Agenda:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCo
mmittee#Meeting_Agenda.2FPrevious_Meeting_Logs

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Solar" release

[Melvin Hillsman]

;)

On Fri, Mar 30, 2018 at 9:49 AM, Sean McGinnis <sean.mcgin...@gmx.com>
wrote:

> > While at it, we should also discuss about what will be the NEXT_MIN
> > libvirt and QEMU versions for the "Solar" release.  To that end, I've
> > spent going through different distributions and updated the
> > DistroSupportMatrix Wiki[2].
> >
> > Taking the DistroSupportMatrix into picture, for the sake of discussion,
> > how about the following NEXT_MIN versions for "Solar" release:
> >
> Correction - for the "Stein" release. :)
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Solar" release

[Melvin Hillsman]

;)

On Fri, Mar 30, 2018 at 9:49 AM, Sean McGinnis <sean.mcgin...@gmx.com>
wrote:

> > While at it, we should also discuss about what will be the NEXT_MIN
> > libvirt and QEMU versions for the "Solar" release.  To that end, I've
> > spent going through different distributions and updated the
> > DistroSupportMatrix Wiki[2].
> >
> > Taking the DistroSupportMatrix into picture, for the sake of discussion,
> > how about the following NEXT_MIN versions for "Solar" release:
> >
> Correction - for the "Stein" release. :)
>
>
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] Ops Meetup, Co-Location options, and User Feedback

[Melvin Hillsman]

isrupt the current spirit of the sessions
> Theirry describes above
>
> The Forum format, on the other hand, is organized around specific
> discussion topics where you want to maximize feedback and input. Forum
> sessions are not attached to a specific workgroup or team, they are
> defined by their topic. They are well-advertised on the event schedule,
> and happen at a precise time. It takes advantage of the thousands of
> attendees being present to get the most relevant feedback possible. It
> allows to engage beyond the work groups, to people who can't spend much
> time getting more engaged and contribute back.
>
> Agreed.  Again, I over simplified as the "what", but these sessions are so
> valuable as the bring dev and ops in a room and focus on what the software
> needs to do or the impact (positive or negative) that planned behaviors
> might have on Operators and users.  To Tim's earlier question, no I think
> this change doesn't reduce the need for Forum sessions.  If anything, I
> think it increases the need for us to get REALLY good at channeling output
> from the Ops mid-cycle in to session topics at the next Summit.
>
> The Ops meetup under its current format is mostly work sessions, and
> those would fit pretty well in the PTG event format. Ideally I would
> limit the feedback-gathering sessions there and use the Forum (and
> regional events like OpenStack days) to collect it. That sounds like a
> better way to reach out to "all users" and take into account their
> feedback and needs...
>
> They are largely work sessions, but independent of the co-location
> discussion, the UC is focused on improving the ability for tangible output
> to come from Ops mid-cycles, OpenStack Days and regional meetups - largely
> in the form of Forum sessions and ultimately changes in the software.  So
> we, as a committee, see a lot of similarities in what you just said.  I'm
> not bold enough to predict exactly how co-location might change the
> tone/topic of the Ops sessions, but I agree that we shouldn't expect a lot
> of real-time feedback time with devs at the PTG/mid-summit event (what ever
> we end up calling it).  We want the devs to be focused on what's already
> planned for the N+1 version or beyond.  The conversations/sessions at the
> Ops portion of the event would hopefully lead to Forum sessions on N+2
> features, functions, bug fixes, etc
>
> Overall, I still see co-location as a positive move.  There will be some
> tricky bits we need to figure out between to the "two sides" of the event
> as we want to MINIMIZE any perceived us/them between dev and ops - not add
> to it.  But, the work session themselves, should still honor the spirit of
> the PTG and Ops Mid-cycle as they are today.  We just get the added benefit
> of time together as a whole community - and hopefully solve a few
> logistic/finance/sponsorship/venue issues that trouble one event or the
> other today.
>
> Thanks!
> VW
> --
> Thierry Carrez (ttx)
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-operators
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack] nova live migration setup

[Melvin Hillsman]

Here is some detail on some work regarding live migration -
http://superuser.openstack.org/wp-content/uploads/2017/06/ha-livemigrate-whitepaper.pdf

Some information on that report in terms of setting up live migration was
gleaned from -
https://www.mirantis.com/blog/tutorial-openstack-live-migration-with-kvm-hypervisor-and-nfs-shared-storage/
- in particular the libvirt configuration parts

Hope this helps.

On Wed, Mar 21, 2018 at 4:07 PM, David Medberry <openst...@medberry.net>
wrote:

> Best practice is to use shared storage and then the "copy" is really only
> the active memory. A few changes came about in about the newton? timeframe
> that allows for some memory convergence.
>
> Take a look at the nova release notes from that time forward and you
> should see reference to the change(s).
>
> You likely won't get much more detail without providing a lot more detail
> about your environment (and maybe not even then.) This functionality is
> very dependent on your specific configuration regarding:
> storage design
> hypervisor choice
> and is also very dependent upon
> network load
> network bandwidth
> VM size
> VM busy-ness
> network design
> nova structure (regions AZs, etc.)
>
> -dave
>
> On Wed, Mar 21, 2018 at 1:35 PM, Torin Woltjer <
> torin.wolt...@granddial.com> wrote:
>
>> I can't find any up to date official documentation on the topic, and only
>> find documentation referring to the commands used. What is the best
>> practice for setting up live migration for nova? I have used live migration
>> over SSH in the past, but the documentation for how to do so is lost to me.
>> Also there is live migration over TCP, is this preferable to ssh and how
>> would you set it up. What are any general best practices for doing this,
>> and what recommendations do you have?
>>
>> Thanks,
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [forum] We want your session ideas for the Vancouver Forum!

[Melvin Hillsman]

Hey everyone,

Please take time to put ideas for sessions at the forum in the TC and/or UC
catch-all etherpads or any of the others that are appropriate:

https://wiki.openstack.org/wiki/Forum/Vancouver2018

We really want to get as many session ideas as possible so that the
committee has too many to choose from :)

Here is an idea of the types of sessions to think about proposing:

*Project-specific sessions*

Where developers can ask users specific questions about their experience,
users can provide feedback from the last release and cross-community
collaboration on the priorities and 'blue sky' ideas for the next release
can occur.

*Strategic, whole-of-community discussions*

To think about the big picture, including beyond just one release cycle and
new technologies

*Cross-project sessions*

In a similar vein to what has happened at past design summits, but with
increased emphasis on issues that are of relevant to all areas of the
community


If you have organized any events in the past year you probably have heard
of or been in some sessions that are perfect for the Forum.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] [forum] We want your session ideas for the Vancouver Forum!

[Melvin Hillsman]

Hey everyone,

Please take time to put ideas for sessions at the forum in the TC and/or UC
catch-all etherpads or any of the others that are appropriate:

https://wiki.openstack.org/wiki/Forum/Vancouver2018

We really want to get as many session ideas as possible so that the
committee has too many to choose from :)

Here is an idea of the types of sessions to think about proposing:

*Project-specific sessions*

Where developers can ask users specific questions about their experience,
users can provide feedback from the last release and cross-community
collaboration on the priorities and 'blue sky' ideas for the next release
can occur.

*Strategic, whole-of-community discussions*

To think about the big picture, including beyond just one release cycle and
new technologies

*Cross-project sessions*

In a similar vein to what has happened at past design summits, but with
increased emphasis on issues that are of relevant to all areas of the
community


If you have organized any events in the past year you probably have heard
of or been in some sessions that are perfect for the Forum.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack] [forum] We want your session ideas for the Vancouver Forum!

[Melvin Hillsman]

Hey everyone,

Please take time to put ideas for sessions at the forum in the TC and/or UC
catch-all etherpads or any of the others that are appropriate:

https://wiki.openstack.org/wiki/Forum/Vancouver2018

We really want to get as many session ideas as possible so that the
committee has too many to choose from :)

Here is an idea of the types of sessions to think about proposing:

*Project-specific sessions*

Where developers can ask users specific questions about their experience,
users can provide feedback from the last release and cross-community
collaboration on the priorities and 'blue sky' ideas for the next release
can occur.
*Strategic, whole-of-community discussions*

To think about the big picture, including beyond just one release cycle and
new technologies
*Cross-project sessions*

In a similar vein to what has happened at past design summits, but with
increased emphasis on issues that are of relevant to all areas of the
community


If you have organized any events in the past year you probably have heard
of or been in some sessions that are perfect for the Forum.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] [forum] We want your session ideas for the Vancouver Forum!

[Melvin Hillsman]

Hey everyone,

Please take time to put ideas for sessions at the forum in the TC and/or UC
catch-all etherpads or any of the others that are appropriate:

https://wiki.openstack.org/wiki/Forum/Vancouver2018

We really want to get as many session ideas as possible so that the
committee has too many to choose from :)

Here is an idea of the types of sessions to think about proposing:

*Project-specific sessions*

Where developers can ask users specific questions about their experience,
users can provide feedback from the last release and cross-community
collaboration on the priorities and 'blue sky' ideas for the next release
can occur.
*Strategic, whole-of-community discussions*

To think about the big picture, including beyond just one release cycle and
new technologies
*Cross-project sessions*

In a similar vein to what has happened at past design summits, but with
increased emphasis on issues that are of relevant to all areas of the
community


If you have organized any events in the past year you probably have heard
of or been in some sessions that are perfect for the Forum.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Stable Branch EOL and "Extended Maintenance" Resolution

[Melvin Hillsman]

Hi everyone,

I believe this resolution is getting close to being passed and so I highly
suggest anyone interested provide any feedback they have
good/bad/indifferent -
https://review.openstack.org/#/c/548916/3/resolutions/20180301-stable-branch-eol.rst

On Thu, Mar 8, 2018 at 7:42 AM, Anne Bertucio <a...@openstack.org> wrote:

> Hi all,
>
> Given our conversations this morning at the Ops Midcycle about Extended
> Maintenance, particularly how projects individually deciding stable
> maintenance policies would affect operators, I wanted to pop this to the
> top of your inbox again. The thread is actively moving, so it’d be good to
> get your operator input in there: https://review.openstack.org/#/c/548916/
>
>
> Anne Bertucio
> OpenStack Foundation
> a...@openstack.org | irc: annabelleB
>
>
>
>
>
> On Mar 7, 2018, at 1:16 PM, Chris Morgan <mihali...@gmail.com> wrote:
>
> Thanks for pointing this one out!
>
> Chris
>
> On Tue, Mar 6, 2018 at 9:53 PM, Melvin Hillsman <mrhills...@gmail.com>
> wrote:
>
>> Hi everyone,
>>
>> If you are interested in the items in the subject please be sure to take
>> time to review and comment on the following patch -
>> https://review.openstack.org/#/c/548916/
>>
>> --
>> Kind regards,
>>
>> Melvin Hillsman
>> mrhills...@gmail.com
>> mobile: (832) 264-2646
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
>
> --
> Chris Morgan <mihali...@gmail.com>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: UC Meeting Today - 14:00 UTC #openstack-uc

[Melvin Hillsman]

Hi everyone,

Friendly reminder we have a UC meeting today in #openstack-uc on freenode
at 14:00UTC

Agenda:
https://wiki.openstack.org/wiki/Governance/Foundation/
UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Stable Branch EOL and "Extended Maintenance" Resolution

[Melvin Hillsman]

Hi everyone,

If you are interested in the items in the subject please be sure to take
time to review and comment on the following patch -
https://review.openstack.org/#/c/548916/

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack] Fwd: [Openstack-sigs] [forum] Brainstorming Topics for Vancouver 2018

[Melvin Hillsman]

-- Forwarded message --
From: Mike Perez <thin...@gmail.com>
Date: Mon, Mar 5, 2018 at 5:15 PM
Subject: [Openstack-sigs] [forum] Brainstorming Topics for Vancouver 2018
To: openstack-...@lists.openstack.org
Cc: openstack-s...@lists.openstack.org,
openstack-operat...@lists.openstack.org, user-commit...@list.openstack.org


Hi all,

Welcome to the topic selection process for our Forum in Vancouver. Note that
this is not a classic conference track with speakers and presentations.
OpenStack community members (participants in development teams, SIGS,
working
groups, and other interested individuals) discuss the topics they want to
cover
and get alignment on and we welcome your participation.

The Forum is for the entire community to come together, to create a
neutral space rather than having separate "ops" and "dev" days. Users should
should aim to come with ideas for for the next release, gather feedback on
the
past version and have strategic discussions that go beyond just one release
cycle. We aim to ensure the broadest coverage of topics that will allow for
multiple parts of the community getting together to discuss key areas within
our community/projects.

There are two stages to the brainstorming:

1. Starting today, set up an etherpad with your team and start
discussing ideas you'd like to talk about at the Forum and work out
which ones to submit - just like you did prior to the design summit.

2. Then, in a couple of weeks, we will open up a more formal web-based
tool for you to submit abstracts for the most popular sessions that came
out of your brainstorming.

Make an etherpad and add it to the list at:
https://wiki.openstack.org/wiki/Forum/Vancouver2018

One key thing we'd like to see (as always?) is cross-project
collaboration, and discussion between every area of the community. Try
to see if there is an interested working group on the user side to add
to your ideas.

Examples of typical discussions that include multiple parts of the
community getting together to discuss:

  * Strategic, whole-of-community discussions, to think about the big
picture, including beyond just one release cycle and new technologies
  o eg Making OpenStack One Platform for containers/VMs/Bare Metal
(Strategic session) the entire community congregates to share
opinions on how to make OpenStack achieve its integration engine
goal
  * Cross-project sessions, in a similar vein to what has happened at
past design summits, but with increased emphasis on issues that are
of relevant to all areas of the community
  o eg Rolling Upgrades at Scale (Cross-Project session) -- the
Large Deployments Team collaborates with Nova, Cinder and
Keystone to tackle issues that come up with rolling upgrades
when there's a large number of machines.
  * Project-specific sessions, where developers can ask users specific
questions about their experience, users can provide feedback from
the last release and cross-community collaboration on the priorities
and 'blue sky' ideas for the next release.
  o eg Neutron Pain Points (Project-Specific session) --
Co-organized by neutron developers and users. Neutron developers
bring some specific questions they want answered, Neutron users
bring feedback from the latest release and ideas about the future.

Think about what kind of session ideas might end up as:
Project-specific, cross-project or strategic/whole-of-community
discussions. There'll be more slots for the latter two, so do try and
think outside the box!

This part of the process is where we gather broad community consensus -
in theory the second part is just about fitting in as many of the good
ideas into the schedule as we can.

Further details about the forum can be found at:
https://wiki.openstack.org/wiki/Forum

--
Mike Perez (thingee)

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




-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646


pgpTRjPgCyN9x.pgp
Description: PGP signature
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [OpenStack-Infra] Team dinner at Dublin PTG

[Melvin Hillsman]

I think reservation may make sense depending on who all will be attending.
Count me in...? :)

On Mon, Feb 26, 2018 at 10:52 PM, Paul Belanger <pabelan...@redhat.com>
wrote:

> On Mon, Feb 19, 2018 at 06:57:29PM -0500, Paul Belanger wrote:
> > On Thu, Feb 15, 2018 at 03:17:58PM -0500, Paul Belanger wrote:
> > > Greetings,
> > >
> > > It is that time again when we all get out from behind our computers
> and attempt
> > > to be social for the evening. Talking about great subjects like
> sportsball and
> > > favorite beers.
> > >
> > > As usually, please indicate which datetime works better for you by
> adding your
> > > name and vote to ethercalc[1].
> > >
> > > Right now, we are likely going to end up at a pub for drinks and food,
> if you
> > > have a specific place in mind, please reply.  I'll do my best to find
> enough
> > > room for everybody, however unsure if everybody will sit together at a
> large
> > > table.
> > >
> > > [1] https://ethercalc.openstack.org/pqhemnrgnz7t
> >
> > Just a reminder to please take a moment to add your name to the team
> dinner
> > list, so far it looks like we'll meet on Monday or Tuesday night.
> >
> > Thanks,
> > Paul
>
> Greetings everybody!  Hopefully this isnt' too late in the process, but it
> does
> seem Tuesday was the best evening for everybody to meet up.
>
> On Sunday I was at Fagan’s Pub, a short walk from The Croke Park hotel for
> drinks and food, and it seems very Irish like.
>
> So, I am proposing after the Official PTG Networking Reception @ 7:30pm we
> meet
> in the lobby of the hotel and walk over and obtain drinks and food. I
> haven't
> requested any sort of reservations, but if we think that is required. I'm
> happy
> to take some time tomorrow morning to confirm we can sit everybody.
>
> Thanks again, and hopefully clarkb won't slap me with a trout on IRC.
>
> Paul
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

[Openstack-operators] User Committee Elections

[Melvin Hillsman]

Hi everyone,

We had to push the voting back a week if you have been keeping up with the
UC elections[0]. That being said, election officials have sent out the poll
and so voting is now open! Be sure to check out the candidates -
https://goo.gl/x183he - and get your vote in before the poll closes.

[0] https://governance.openstack.org/uc/reference/uc-election-feb2018.html

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack] User Committee Elections

[Melvin Hillsman]

Hi everyone,

We had to push the voting back a week if you have been keeping up with the
UC elections[0]. That being said, election officials have sent out the poll
and so voting is now open! Be sure to check out the candidates -
https://goo.gl/x183he - and get your vote in before the poll closes.

[0] https://governance.openstack.org/uc/reference/uc-election-feb2018.html

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[openstack-dev] User Committee Elections

[Melvin Hillsman]

Hi everyone,

We had to push the voting back a week if you have been keeping up with the
UC elections[0]. That being said, election officials have sent out the poll
and so voting is now open! Be sure to check out the candidates -
https://goo.gl/x183he - and get your vote in before the poll closes.

[0] https://governance.openstack.org/uc/reference/uc-election-feb2018.html

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] [User-committee] Stepping aside announcement

[Melvin Hillsman]

Thanks for your service to the community Edgar! Hope to see you at an event
soon and we can toast to your departure and continued success!

On Mon, Jan 29, 2018 at 11:59 AM, Amy Marrich <a...@demarco.com> wrote:

> Edgar,
>
> Thank you for all your hard work and contributions!
>
> Amy (spotz)
>
> On Mon, Jan 29, 2018 at 11:12 AM, Edgar Magana <edgar.mag...@workday.com>
> wrote:
>
>> Dear Community,
>>
>>
>>
>> This is an overdue announcement but I was waiting for the right moment
>> and today it is with the opening of the UC election. It has been almost
>> seven years of full commitment to OpenStack and the entire ecosystem around
>> it. During the last couple of years, I had the opportunity to serve as
>> Chair of the User Committee. I have participated in this role with nothing
>> more important but passion and dedication for the users and operators.
>> OpenStack has been very important for me and it will be always the most
>> enjoyable work I have ever done.
>>
>>
>>
>> It is time to move on. Our team is extending its focus to other cloud
>> domains and I will be leading one of the those. Therefore, I would like to
>> announce that I am stepping aside from my role as UC Chair. Per our UC
>> election, there will be no just 2 seats available but three:
>> https://governance.openstack.org/uc/reference/uc-election-feb2018.html
>>
>>
>>
>> I want to encourage the whole AUC community to participate, be part of
>> the User Committee is a very important and grateful activity. Please, go
>> for it!
>>
>>
>>
>> Thank you all,
>>
>>
>>
>> Edgar Magana
>>
>> Sr. Principal Architect
>>
>> Workday, Inc.
>>
>>
>>
>>
>>
>>
>>
>> ___
>> User-committee mailing list
>> user-commit...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>>
>>
>
> ___
> User-committee mailing list
> user-commit...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [OpenStack-Infra] Talks for the Vancouver CFP ?

[Melvin Hillsman]

I would be willing to do something with a more seasoned Zuul'r (core or ptl
even) around work we are doing in OpenLab; gophercloud + terraform
integration we have already done, work we are doing to add k8s

On Mon, Jan 22, 2018 at 4:12 PM, David Moreau Simard <dmsim...@redhat.com>
wrote:

> Hi,
>
> Did we want to brainstorm around topics and talks suggestions from an
> openstack-infra perspective for Vancouver [1] ?
>
> The deadline is February 8th and the tracks are the following:
> - CI / CD
> - Container Infrastructure
> - Edge Computing
> - HPC / GPU / AI
> - Open Source Community
> - Private & Hybrid Cloud
> - Public Cloud
> - Telecom & NFV
>
> CI/CD has Zuul and Nodepool written all over it, of course.
> FWIW I'm already planning on submitting a talk that covers how a
> commit in an upstream project ends up being released by RDO which
> includes the upstream Zuul and RDO's instance of Zuul (amongst other
> things).
>
> I started an etherpad [2], we can brainstorm there ?
>
> [1]: https://www.openstack.org/summit/vancouver-2018/call-
> for-presentations/
> [2]: https://etherpad.openstack.org/p/infra-vancouver-cfp
>
> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra




-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Re: [Openstack] Production deployment mirantis vs tripleO

[Melvin Hillsman]

There are also the options of OpenStack-Ansible[0] or Kolla-Ansible[1]

[0] https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/
[1] https://docs.openstack.org/project-deploy-guide/kolla-ansible/pike/

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: +1 (832) 264-2646
irc: mrhillsman

On 1/15/18, 12:55 PM, "Jay Pipes" <jaypi...@gmail.com> wrote:

On 01/15/2018 12:58 PM, Satish Patel wrote:
> But Fuel is active project, isn't it?
> 
> https://docs.openstack.org/fuel-docs/latest/

No, it is no longer developed or supported.

-jay

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] OpenStack Individual BoD Elections

[Melvin Hillsman]

Hi everyone,

 

Just a friendly reminder that the Individual BoD elections has started. Please 
take time to consider all the candidates and vote accordingly:

https://www.openstack.org/election/2018-individual-director-election/CandidateList

 

You should have your ballot via the email associated with your OpenStack 
Foundation profile.

 

-- 

Kind regards,

Melvin Hillsman

mrhills...@gmail.com
mobile: +1 (832) 264-2646

irc: mrhillsman

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

[Openstack] Ohayo! Q1 2018

[Melvin Hillsman]

https://etherpad.openstack.org/p/TYO-ops-meetup-2018


​

Hey everyone,

What do you think about the new logo! Just a friendly reminder that the Ops
Meetup for Spring 2018 is approaching March 7-8, 2018 in Tokyo and we are
looking for additional topics.

Spring 2018 will have NFV+General on day one and Enterprise+General on day
two. Add additional topics to the etherpad or +/- 1 those already proposed.

Additionally if you are attending and would like to moderate a session, add
your name to the moderator list near the bottom of the etherpad.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Ohayo! Q1 2018

[Melvin Hillsman]

https://etherpad.openstack.org/p/TYO-ops-meetup-2018


​

Hey everyone,

What do you think about the new logo! Just a friendly reminder that the Ops
Meetup for Spring 2018 is approaching March 7-8, 2018 in Tokyo and we are
looking for additional topics.

Spring 2018 will have NFV+General on day one and Enterprise+General on day
two. Add additional topics to the etherpad or +/- 1 those already proposed.

Additionally if you are attending and would like to moderate a session, add
your name to the moderator list near the bottom of the etherpad.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] Ohayo! Q1 2018

[Melvin Hillsman]

https://etherpad.openstack.org/p/TYO-ops-meetup-2018


​

Hey everyone,

What do you think about the new logo! Just a friendly reminder that the Ops
Meetup for Spring 2018 is approaching March 7-8, 2018 in Tokyo and we are
looking for additional topics.

Spring 2018 will have NFV+General on day one and Enterprise+General on day
two. Add additional topics to the etherpad or +/- 1 those already proposed.

Additionally if you are attending and would like to moderate a session, add
your name to the moderator list near the bottom of the etherpad.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] [Openstack-operators] Certifying SDKs

[Melvin Hillsman]

+1 to editing the sheet as well and because you are spot on with your 
assessment of what I meant; scenarios we can “guarantee” an SDK allows/affords 
a tool to deliver on.
-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: +1 (832) 264-2646
irc: mrhillsman

On 12/15/17, 1:53 PM, "Davanum Srinivas" <dava...@gmail.com> wrote:

Joe,

+1 to edit the sheet directly.

Thanks,
Dims

On Fri, Dec 15, 2017 at 2:45 PM, Joe Topjian <j...@topjian.net> wrote:
> Hi all,
>
> I've been meaning to reply to this thread. Volodymyr, your reply reminded 
me
> :)
>
> I agree with what you said that the SDK should support everything that the
> API supports. In that way, one could simply review the API reference docs
> and create a checklist for each possible action. I've often thought about
> doing this for Gophercloud so devs/users can see its current state of 
what's
> supported and what's missing.
>
> But Melvin highlighted the word "guaranteed", so I think he's looking for
> the most common scenarios/actions rather than an exhaustive list. For 
that,
> I can recommend the suite of Terraform acceptance tests. I've added a test
> each time a user has either reported a bug or requested a feature, so
> they're scenarios that I know are being used "in the wild".
>
> You can find these tests here:
> 
https://github.com/terraform-providers/terraform-provider-openstack/tree/master/openstack
>
> Each file that begins with "resource" and ends in "_test.go" will contain
> various scenarios at the bottom. For example, compute instances:
> 
https://github.com/terraform-providers/terraform-provider-openstack/blob/master/openstack/resource_openstack_compute_instance_v2_test.go#L637-L1134
>
> This contains tests for:
>
> * Basic launch of an instance
> * Able to add and remove security groups from an existing instance
> * Able to boot from a new volume or an existing volume
> * Able to edit metadata of an instance.
> * Able to create an instance with multiple ephemeral disks
> * Able to create an instance with multiple NICs, some of which are on the
> same network, some of which are defined as ports.
>
> Terraform is not an SDK, but it's a direct consumer of Gophercloud and is
> more user-facing, so I think it's quite applicable here. The caveat being
> that if Terraform or Gophercloud does not support something, it's not
> available as a test. :)
>
> Melvin, if this is of interest, I can either post a raw list of these
> tests/scenarios here or edit the sheet directly.
>
> Thanks,
> Joe
>
>
> On Fri, Dec 15, 2017 at 12:43 AM, Volodymyr Litovka <doka...@gmx.com> 
wrote:
>>
>> Hi Melvin,
>>
>> isn't SDK the same as Openstack REST API? In my opinion (can be 
erroneous,
>> though), SDK should just support everything that API supports, providing
>> some basic checks of parameters (e.g. verify compliancy of passed 
parameter
>> to IP address format, etc) before calling API (in order to decrease load 
of
>> Openstack by eliminating obviously broken requests).
>>
>> Thanks.
>>
>>
>> On 12/11/17 8:35 AM, Melvin Hillsman wrote:
>>
>> Hey everyone,
>>
>> On the path to potentially certifying SDKs we would like to gather a list
>> of scenarios folks would like to see "guaranteed" by an SDK.
>>
>> Some examples - boot instance from image, boot instance from volume,
>> attach volume to instance, reboot instance; very much like InterOp works 
to
>> ensure OpenStack clouds provide specific functionality.
>>
>> Here is a document we can share to do this -
>> 
https://docs.google.com/spreadsheets/d/1cdzFeV5I4Wk9FK57yqQmp5JJdGfKzEOdB3Vtt9vnVJM/edit#gid=0
>>
>> --
>> Kind regards,
>>
>> Melvin Hillsman
>> mrhills...@gmail.com
>> mobile: (832) 264-2646
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>> --
>> Volodymyr Litovka
>>   "Vision without Execution is Hallucination." -- Thomas Edison
>>
>>
>> __

Re: [Openstack-operators] [Openstack] Certifying SDKs

[Melvin Hillsman]

+1 to editing the sheet as well and because you are spot on with your 
assessment of what I meant; scenarios we can “guarantee” an SDK allows/affords 
a tool to deliver on.
-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: +1 (832) 264-2646
irc: mrhillsman

On 12/15/17, 1:53 PM, "Davanum Srinivas" <dava...@gmail.com> wrote:

Joe,

+1 to edit the sheet directly.

Thanks,
Dims

On Fri, Dec 15, 2017 at 2:45 PM, Joe Topjian <j...@topjian.net> wrote:
> Hi all,
>
> I've been meaning to reply to this thread. Volodymyr, your reply reminded 
me
> :)
>
> I agree with what you said that the SDK should support everything that the
> API supports. In that way, one could simply review the API reference docs
> and create a checklist for each possible action. I've often thought about
> doing this for Gophercloud so devs/users can see its current state of 
what's
> supported and what's missing.
>
> But Melvin highlighted the word "guaranteed", so I think he's looking for
> the most common scenarios/actions rather than an exhaustive list. For 
that,
> I can recommend the suite of Terraform acceptance tests. I've added a test
> each time a user has either reported a bug or requested a feature, so
> they're scenarios that I know are being used "in the wild".
>
> You can find these tests here:
> 
https://github.com/terraform-providers/terraform-provider-openstack/tree/master/openstack
>
> Each file that begins with "resource" and ends in "_test.go" will contain
> various scenarios at the bottom. For example, compute instances:
> 
https://github.com/terraform-providers/terraform-provider-openstack/blob/master/openstack/resource_openstack_compute_instance_v2_test.go#L637-L1134
>
> This contains tests for:
>
> * Basic launch of an instance
> * Able to add and remove security groups from an existing instance
> * Able to boot from a new volume or an existing volume
> * Able to edit metadata of an instance.
> * Able to create an instance with multiple ephemeral disks
> * Able to create an instance with multiple NICs, some of which are on the
> same network, some of which are defined as ports.
>
> Terraform is not an SDK, but it's a direct consumer of Gophercloud and is
> more user-facing, so I think it's quite applicable here. The caveat being
> that if Terraform or Gophercloud does not support something, it's not
> available as a test. :)
>
> Melvin, if this is of interest, I can either post a raw list of these
> tests/scenarios here or edit the sheet directly.
>
> Thanks,
> Joe
>
>
> On Fri, Dec 15, 2017 at 12:43 AM, Volodymyr Litovka <doka...@gmx.com> 
wrote:
>>
>> Hi Melvin,
>>
>> isn't SDK the same as Openstack REST API? In my opinion (can be 
erroneous,
>> though), SDK should just support everything that API supports, providing
>> some basic checks of parameters (e.g. verify compliancy of passed 
parameter
>> to IP address format, etc) before calling API (in order to decrease load 
of
>> Openstack by eliminating obviously broken requests).
>>
>> Thanks.
>>
>>
>> On 12/11/17 8:35 AM, Melvin Hillsman wrote:
>>
>> Hey everyone,
>>
>> On the path to potentially certifying SDKs we would like to gather a list
>> of scenarios folks would like to see "guaranteed" by an SDK.
>>
>> Some examples - boot instance from image, boot instance from volume,
>> attach volume to instance, reboot instance; very much like InterOp works 
to
>> ensure OpenStack clouds provide specific functionality.
>>
>> Here is a document we can share to do this -
>> 
https://docs.google.com/spreadsheets/d/1cdzFeV5I4Wk9FK57yqQmp5JJdGfKzEOdB3Vtt9vnVJM/edit#gid=0
>>
>> --
>> Kind regards,
>>
>> Melvin Hillsman
>> mrhills...@gmail.com
>> mobile: (832) 264-2646
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openst...@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>> --
>> Volodymyr Litovka
>>   "Vision without Execution is Hallucination." -- Thomas Edison
>>
>>
>> __

Re: [openstack-dev] [all] Switching to longer development cycles

[Melvin Hillsman]

On Wed, Dec 13, 2017 at 9:13 PM, Matt Riedemann <mriede...@gmail.com> wrote:

> On 12/13/2017 4:15 PM, Thierry Carrez wrote:
>
>> Based on several discussions I had with developers working part-time on
>> OpenStack at various events lately, it sounded like slowing down our
>> pace could be helpful to them and generally reduce stress in OpenStack
>> development. I know people who can spend 100% of their time upstream can
>> cope with our current rhythm. I just observe that we have less and less
>> of those full-time people and need to attract more of the part-time one.
>>
>> If this proposal is not helping developers and making OpenStack
>> development less painful, I don't think we should do it:)
>>
>
> Given I have the luxury of working mostly full time upstream, I've
> obviously got a skewed perspective on this whole discussion.
>
> I am interested in which part time developers are having issues keeping up
> and how, i.e. are these core team members that don't feel they can be good
> core reviewers if they aren't around enough to keep up with the changes
> that are happening? I could definitely see a case like that with some of
> the complicated stuff going on in nova like the placement and cells v2 work.
>
> If we're talking about part time contributors that are contributing bug
> fixes here and there, docs patches, random reviews, I'm not sure how this
> is substantially better for them.
>
> We've said in this thread that project teams are encouraged to still do
> intermediate releases, often. And we're still going to be working on
> features, so how does that help slow things down for the part time
> contributor?
>
> If *everyone* must slow down then that's going to be a problem I think,
> unless we do something like alternating intermediate releases where there
> are new features and then only bug fixes, something like that - up to the
> discretion of each project team as they see fit.
>

This sounds like a path we should consider/discuss more. Are you suggesting
do 1 year but 6 months for new features then next 6 for bug fixes only or
vice versa? Or keep current 6 month cadence and communicate our spring
release is feature rich with ... feature (when the time comes of course),
and our fall release is bug-fix only?


>
> I haven't seen anyone mention this yet either, but if "slowing down"
> begins to look like we're entering maintenance mode, I don't think that's
> going to attract new developers and it's likely to mean long-time key
> maintainers are going to lose interest and start looking elsewhere to
> scratch their itches. It's hard to say what would happen. I can certainly
> keep myself busy with docs patches and bug fixes until the cows come home.
>
> --
>
> Thanks,
>
> Matt
>
>
> __
> 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
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-operators] thierry's longer dev cycle proposal

[Melvin Hillsman]

I think this is a good opportunity to allow some stress relief to the developer 
community and offer space for more discussions with operators where some 
operators do not feel like they are bothering/bugging developers. I believe 
this is the main gain for operators; my personal opinion. In general I think 
the opportunity costs/gains are worth it for this and it is the responsibility 
of the community to make the change be useful as you mentioned in your original 
thread Thierry. It is not a silver bullet for all of the issues folks have with 
the way things are done but I believe that if it does not hurt things and 
offers even a slight gain in some area it makes sense.

Any change is not going to satisfy/dis-satisfy 100% of the constituents.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: +1 (832) 264-2646
irc: mrhillsman

On 12/13/17, 4:39 PM, "Jeremy Stanley" <fu...@yuggoth.org> wrote:

On 2017-12-13 22:35:41 +0100 (+0100), Thierry Carrez wrote:
[...]
> It's not really fait accompli, it's just a proposal up for discussion at
> this stage. Which is the reason why I started the thread on -dev -- to
> check the sanity of the change from a dev perspective first. If it makes
> things harder and not simpler on that side, I don't expect the TC to
> proceed.
[...]

With my TC hat on, regardless of what impression the developer
community has on this, I plan to take subsequent operator and
end-user/app-dev feedback into account as well before making any
binding decisions (and expect other TC members feel the same).
-- 
Jeremy Stanley
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




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

Re: [openstack-dev] [all] Switching to longer development cycles

[Melvin Hillsman]

t cycles, we think that this significant change goes well
> > beyond the release team and needs to be discussed across all of the
> > OpenStack community, with a final decision made by the Technical
> Committee.
> >
> > So... What do you think ?
> >
>
> All in all, like anything, we wouldn't know how this would shake out
> until we tried it and gave enough time to sink it and evaluate. On the
> surface I don't think this really helps with much of anything. As noted,
> a 1 year dev cycle isn't going to get the code written or reviewed any
> faster, but maybe that's not a primary focus. Maybe the primary focus is
> fewer people are focusing on doing OpenStack development and therefore
> we can/should slow down because our developer pool is moving on to other
> shinier things. Elections can be changed without this. Summits that
> aren't in Australia can be changed without this (I would think?).
> Upgrades aren't going to be magically easier as a result, and it would
> arguably make upgrades potentially harder since you'd be consuming a
> year's worth of changes rather than 6 months.
>
> --
>
> Thanks,
>
> Matt
>
> __
> 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
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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] Switching to longer development cycles

[Melvin Hillsman]

There are definitely pros and cons to this approach but I think
considerable amount of time and concern went into this prior to being
posted on the ML and agree with JP there will be folks who agree and/or
disagree with some or all of this so TC vote is best. I think getting away
from the debatable pieces of this, it offers some flexibility on a number
of fronts. Personally I was able to hear some of the discussions around
this prior to today and 100% agree with it as well.

On Wed, Dec 13, 2017 at 11:06 AM, Jean-Philippe Evrard <
jean-phili...@evrard.me> wrote:

> On 13 December 2017 at 16:49, Jeremy Stanley <fu...@yuggoth.org> wrote:
> > On 2017-12-13 16:45:14 + (+), Chris Jones wrote:
> > [...]
> >> For me the first thing that comes to mind with this proposal, is
> >> how would the milestones/FF/etc be arranged within that year?
> > [...]
> >
> > Excellent point. If it's not too much work for the Release team, it
> > would be very helpful to have a straw man release schedule for a
> > year-long Rocky so we can see what that might look like.
> > --
> > 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
> >
>
> Hello,
>
> 100% agreed on all of the above.
>
> I'd think it would be nice to move to 1 year, starting from Rocky.
>
> Thierry, with your position it seems logical that you started this
> conversation and ask for a TC vote.
> I guess there will always be happy/unhappy people anyway, so a TC vote
> seems good.
>
> Best regards,
> JP
>
> __
> 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
>



-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
__
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-Infra] Zuul roadmap

[Melvin Hillsman]

Hey Paul,

I am also interested in helping here; will read over the etherpad today just to 
make sure I am caught up.

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: +1 (832) 264-2646
irc: mrhillsman

On 12/12/17, 10:29 AM, "Paul Belanger" <pabelan...@redhat.com> wrote:

On Tue, Dec 12, 2017 at 05:01:41PM +0100, Matthieu Huin wrote:
> Hello,
> 
> If the getting-started documentation effort is also aimed at end
> users, I'd be happy to help Leif with this: we've written a quick
> start guide for Software Factory explaining how to set up pipelines
> and jobs with Zuul3, and this would probably be better hosted upstream
> with minimal adaptations. Let me know if there's interest for this
> (the storyboard item at
> https://storyboard.openstack.org/#!/story/2001332 doesn't specify
> which kind of doc is expected) and I can submit some patches to the
> documentatoin.
> 
I was just talking with leifmadsen about it this morning and we're going to
organize a working group on docs in the coming days. With holidays coming up
quick, it might be difficult to wrap things up before Christmas.

I know there already has been some discussion between Jim and Leif, plus 
myself
and Leif documented in the etherpad[1]. Using Fedora and github, I believe 
the
etherpad notes are correct. So the next steps are reformatting into RST and
tuning the docs.

TL;DR we have some docs, and jobs ran, now to make that a little more user
friendly.

[1] https://etherpad.openstack.org/p/zuulv3-quickstart

> Best regards,
> 
> MHU
> 
> On Fri, Dec 8, 2017 at 9:25 PM, David Shrewsbury
> <shrewsbury.d...@gmail.com> wrote:
> > Hi!
> >
> > On Wed, Dec 6, 2017 at 10:34 AM, James E. Blair <cor...@inaugust.com> 
wrote:
> >
> > 
> >
> >>
> >> * Add finger gateway
> >>
> >> The fact that the executor must be started as root in order to listen 
on
> >> port 79 is awkward for new users.  It can be avoided by configuring it
> >> to listen on a different port, but that's also awkward.  In either 
case,
> >> it's a significant hurdle, and it's one of the most frequently asked
> >> questions in IRC.  The plan to deal with this is to create a new 
service
> >> solely to multiplex the finger streams.  This is very similar to the
> >> zuul-web service for multiplexing the console streams, so all the
> >> infrastructure is in place.  And of course, running this service will 
be
> >> optional, so it means that new users don't even have to deal with it to
> >> get up and running, like they do now.  Adding a new service to the 3.0
> >> list should not be done lightly, but the improvement in experience for
> >> new users will be significant.
> >>
> >> David Shrewsbury has started on this.  I don't think it is out of 
reach.
> >
> >
> >
> > Indeed, it is not out of reach:
> >
> >https://review.openstack.org/525276
> >
> >
> >
> > --
> > David Shrewsbury (Shrews)
> >
> > ___
> > OpenStack-Infra mailing list
> > OpenStack-Infra@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
> 
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

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



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

[Openstack] Certifying SDKs

[Melvin Hillsman]

Hey everyone,

On the path to potentially certifying SDKs we would like to gather a list
of scenarios folks would like to see "guaranteed" by an SDK.

Some examples - boot instance from image, boot instance from volume, attach
volume to instance, reboot instance; very much like InterOp works to ensure
OpenStack clouds provide specific functionality.

Here is a document we can share to do this -
https://docs.google.com/spreadsheets/d/1cdzFeV5I4Wk9FK57yqQmp5JJdGfKzEOdB3Vtt9vnVJM/edit#gid=0

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack-operators] Certifying SDKs

[Melvin Hillsman]

Hey everyone,

On the path to potentially certifying SDKs we would like to gather a list
of scenarios folks would like to see "guaranteed" by an SDK.

Some examples - boot instance from image, boot instance from volume, attach
volume to instance, reboot instance; very much like InterOp works to ensure
OpenStack clouds provide specific functionality.

Here is a document we can share to do this -
https://docs.google.com/spreadsheets/d/1cdzFeV5I4Wk9FK57yqQmp5JJdGfKzEOdB3Vtt9vnVJM/edit#gid=0

-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators