[openstack-dev] [openlab] October Report

2018-11-01 Thread 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-dev] [user-committee] UC Meeting Reminder

2018-10-29 Thread 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


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

2018-10-08 Thread 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-dev] [Openstack-sigs] Capturing Feedback/Input

2018-09-21 Thread 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-dev] Capturing Feedback/Input

2018-09-20 Thread 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...)

2018-09-20 Thread 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

2018-09-20 Thread 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

2018-09-19 Thread 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-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

2018-09-12 Thread 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)

2018-09-12 Thread 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-dev] [Openstack-operators] [all] Bringing the community together (combine the lists!)

2018-08-30 Thread 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-dev] Reminder: User Committee @ 1800 UTC

2018-07-30 Thread 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


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

2018-07-09 Thread 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


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

2018-06-18 Thread 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-dev] Reminder: UC Meeting Today 1400UTC / 0900CST

2018-06-11 Thread 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-dev] Reminder: UC Meeting Monday 1400UTC

2018-06-08 Thread 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-dev] OpenLab Cross-community Impact

2018-05-31 Thread 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-dev] [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Solar" release

2018-03-30 Thread 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


[openstack-dev] User Committee Elections

2018-02-19 Thread 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


[openstack-dev] Ohayo! Q1 2018

2018-01-03 Thread 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-dev] [all] Switching to longer development cycles

2017-12-13 Thread 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-dev] [all] Switching to longer development cycles

2017-12-13 Thread 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

2017-12-13 Thread 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-dev] [nova][cinder] Nova is now using the Cinder volume attachments API - multiattach comes next

2017-12-09 Thread Melvin Hillsman
Great work and congratulations to everyone involved!

On Sat, Dec 9, 2017 at 1:15 PM, Matt Riedemann <mriede...@gmail.com> wrote:

> I just wanted to take a minute to recognize that the patch [1] to make
> Nova use the new-style Cinder volume attach flow has merged.
>
> As one can tell from the patch set count alone, this has been in the works
> for a long time now.
>
> We were talking about volume multi-attach support back in Mitaka at the
> midcycle in Bristol. The early talks / patches would have piled more
> technical debt onto Nova and further baked in Nova's need to manage volume
> state, which is something we wanted to avoid, so at the Newton summit in
> Austin we changed course and decided to prioritize working on a new data
> model and API in Cinder, which eventually came out as the 3.27 volume
> attachments API in Ocata.
>
> There was then serious work on both sides in Pike to start using the new
> 3.27 API and we found out we needed some more changes to Cinder, which
> became the 3.44 Cinder API in Queens. Now Nova has merged the change at the
> end of a very long series of changes to enable the new flow once 3.44 is
> available to Nova and computes are all upgraded to understand the new flow.
> One can appreciate the complexity here if you read through the Nova spec
> for the new attach flow [2].
>
> I was really happy to see [1] merge this week because I knew we needed to
> get that in by the queens-2 milestone if we were going to have a shot at
> (1) flushing out stability issues before Queens RC1 and (2) a good chance
> to get multi-attach support into Nova in Queens.
>
> We have a plan for multi-attach support [3] which I think is doable before
> feature freeze. The Cinder 3.48 API is now available too which Nova needs
> to correctly detach a multi-attach volume.
>
> I want to thank everyone that's helped push this along for their
> dedication and patience, especially John Griffith, Ildiko Vancsa, Steve
> Noyes and John Garbutt. And thanks to Sean McGinnis, Jay Bryant, Walter
> Boring and Balazs Gibizer for review support.
>
> We've had weekly meetings between the Nova and Cinder teams for at least
> two years now and I can finally see the end so let's keep up the momentum.
>
> [1] https://review.openstack.org/#/c/330285/
> [2] https://specs.openstack.org/openstack/nova-specs/specs/queen
> s/approved/cinder-new-attach-apis.html
> [3] https://specs.openstack.org/openstack/nova-specs/specs/queen
> s/approved/cinder-volume-multi-attach.html
>
> --
>
> 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


[openstack-dev] OpenStack Ops Meetup Topic Brainstorming

2017-12-08 Thread Melvin Hillsman
https://etherpad.openstack.org/p/TYO-ops-meetup-2018

Hey everyone,

Just a friendly reminder that the Ops Meetup for Spring 2018 is approaching
March 7-8, 2018 in Tokyo and we are looking for topics. Some have been
gathered already but brainstorming could definitely use some love.

What is different about this meetup compared to others is the addition of
focus areas; tracks. 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.

-- 
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] Community managed tech/dev blog: Call for opinions and ideas

2017-11-27 Thread Melvin Hillsman
On Mon, Nov 27, 2017 at 8:16 AM, Dan Prince <dpri...@redhat.com> wrote:

>
>
> On Mon, Nov 27, 2017 at 8:55 AM, Flavio Percoco <fla...@redhat.com> wrote:
>
>> Greetings,
>>
>> Last Thursday[0], at the TC office hours, we brainstormed a bit around
>> the idea
>> of having a tech blog. This idea came first from Joshua Harlow and it was
>> then
>> briefly discussed at the summit too.
>>
>> The idea, we have gathered, is to have a space where the community could
>> write
>> technical posts about OpenStack. The idea is not to have an aggregator
>> (that's
>> what our planet[1] is for) but a place to write original and curated
>> content.
>>
>
> Why not just write article's on existing blogs, link them into planet, and
> then if they are really good promote them at a higher level?
>
> Having a separate blog that is maintained by a few seems a bit elitist to
> me.
>
> Dan
>

+1


>
>> During the conversation, we argued about what kind of content would be
>> acceptable for this platform. Here are some ideas of things we could have
>> there:
>>
>> - Posts that are dev-oriented (e.g: new functions on an oslo lib)
>> - Posts that facilitate upstream development (e.g: My awesome dev setup)
>> - Deep dive into libvirt internals
>>
>
> What is really missing in our current infrastructure setup that really
> prevents any of the above?
>

+1


>
>
>> - ideas?
>>
>> As Chris Dent pointed out on that conversation, we should avoid making
>> this
>> place a replacement for things that would otherwise go on the mailing
>> list -
>> activity reports, for example. Having dev news in this platform, we would
>> overlap with things that go already on the mailing list and, arguably, we
>> would
>> be defeating the purpose of the platform. But, there might be room for
>> both(?)
>>
>> Ultimately, we should avoid topics promoting new features in services as
>> that's what
>> superuser[2] is for.
>>
>> So, what are your thoughts about this? What kind of content would you
>> rather
>> have posted here? Do you like the idea at all?
>>
>> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23op
>> enstack-tc.2017-11-23.log.html#t2017-11-23T15:01:25
>> [1] http://planet.openstack.org/
>> [2] http://superuser.openstack.org/
>>
>> Flavio
>>
>> --
>> @flaper87
>> Flavio Percoco
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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
>
>

My .02, I would like to encourage in general we try to streamline and make
more effective what we already do versus adding more and remove excess.


-- 
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] [tc][election] TC non-candidacy

2017-10-10 Thread Melvin Hillsman
Awesome! Means I can bug you just a little bit more :)

On Tue, Oct 10, 2017 at 7:55 PM, joehuang <joehu...@huawei.com> wrote:

> Thank you very much, Monty. You always provide great help if needed,
> friendly.
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> 
> From: Monty Taylor [mord...@inaugust.com]
> Sent: 11 October 2017 7:40
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [tc][election] TC non-candidacy
>
> Hey everybody!
>
> I have decided not to seek reelection for the TC.
>
> I have had the honor and privilege of serving you on the TC and it's
> predecessor the PPB since the fall of 2011 (with one six month absence
> that I blame on Jay Pipes)
>
> There are a wealth of amazing people running for the TC this cycle, many
> of whom have a different genetic, cultural or geographic background than
> I do. I look forward to seeing how they shepherd our amazing community.
>
> I am not going anywhere. We're just getting Zuul v3 rolled out, there's
> a pile of work to do to merge and rationalize shade and openstacksdk and
> I managed to sign myself up to implement application credentials in
> Keystone. I still haven't even managed to convince all of you that
> Floating IPs are a bad idea...
>
> Thank you, from the bottom of my heart, for the trust you have placed in
> me. I look forward to seeing as many of you as I can in Sydney,
> Vancouver, Berlin and who knows where else.
>
> Monty
>
> __
> 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] Thanks for all the fish

2017-10-10 Thread Melvin Hillsman
Hey Lana!

Glad you found a home. Hope to see you back opensourcing soon, thanks for
your encouragement, kindness, introductions, and help as I was getting
started working in the community.

On Tue, Oct 10, 2017 at 8:21 PM, Amy Marrich <a...@demarco.com> wrote:

> We'll miss you Lana but so glad you found something finally!!!
>
> Amy (spotz)
>
> On Tue, Oct 10, 2017 at 7:34 PM, Lana Brindley <openst...@lanabrindley.com
> > wrote:
>
>> Hi everyone,
>>
>> As most of you know, I was caught up in the Rackspace layoffs that
>> happened earlier this year, and have been looking for work (in between knee
>> surgery) since then. Well, in good news for my bank account, I have now
>> secured a new job with a startup based here in Brisbane. The bad news is
>> that, while it's working on cool stuff and is likely to be at least
>> partially open sourced at some point, there's currently no scope for me to
>> continue working on OpenStack. Sadly, an OpenStack related position just
>> did not come my way, despite my best efforts.
>>
>> So, this is goodbye for now. I'm going to unsubscribe from the OpenStack
>> mailing lists, and resign my core positions, but you can still email me at
>> this address if you want to. Feel free to hit me up on LinkedIn or Twitter,
>> if that's your thing.
>>
>> I'm going to miss being part of the community we built here, and all the
>> fabulous people I've met over my OpenStack years. Keep being awesome, I'll
>> be cheering from the sidelines.
>>
>> Keep on Doc'ing :)
>>
>> Lana
>>
>> --
>> Lana Brindley
>> Technical Writer
>> http://lanabrindley.com
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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] [python-openstacksdk] Status of python-openstacksdk project

2017-08-04 Thread Melvin Hillsman
Stack better - so that's another argument in favor of that
> direction of merge ... it would look something like this:
>
>   # make Connection objects for every cloud-region in clouds.yaml
>   clouds = openstack.OpenStack()
>   # thread/asyncio parallel fetch of images across all clouds
>   images = clouds.list_images()
>   # all objects in shade have a "location" field which contains
>   # cloud, region, domain and project info for the resource
>   print([image for image in images if image.location.cloud='vexxhost'])
>   # Location is a required parameter for creation
>   vexxhost = clouds.get_location(name='vexxhost')
>   clouds.create_image(
> location=vexxhost, name='my-fedora-26',
> filename='fedora26.qcow2')
>
> Most of this work can actually likely be done with one smart metaclass ...
> finding the methods on OpenStackCloud and either doing a set of parallel
> gets on a list of objects or adding a location argument to write operations
> doesn't vary depending on the type of object. Since all the methods are
> named consistently, finding 'list_*' and making a set of corresponding
> list_ methods on the OpenStack object is essentially just one chunk of
> smart constructor.
>
> * Finish per-resource caching / batched client-side rate-limiting work.
> shade has a crazy cool ability to do batched and rate-limited operations
> ... this is how nodepool works at the scale it does. But it's currently
> only really plumbed through for server, floating-ip and port. (guess what
> nodepool has to deal with) This should be generalized to all of the
> resources, configurable on a per-resource name in clouds.yaml, and should
> work whether high or low level interfaces are used. This is super hard to
> get RIGHT, so it's one of those "spend 4 weeks writing 10 lines of code"
> kind of things, but it's also super important.
>
> * Implement a flag for toggling list/client-side-filter vs. remote-get
> operations. Most single-resource operations in shade are actually done as a
> list followed by a client-side filter. Again this model is there to support
> nodepool-scale (amusingly enough it makes it less load on the clouds at
> scale) but at small scale it is more costly and some users find it
> annoying. We've discussed having the ability to toggle this at constructor
> time - and then having things like the ansible modules default the flag to
> use remote-get instead of list/filter - since those are doing lots of
> independent processes so the optimization of list/filter isn't ever
> realized.
>
> * Implement smarter and more comprehensive "pushdown" filtering. I think
> we can piggyback a bunch of this off of the SDK layer - but there are
> attributes that can be used for server-side filtering, there are attributes
> that can't, and there are attributes that are client-side created via
> normalization that either can be translated into a server-side filter or
> must be client-side filtered. Resource has the structure for dealing with
> this sanely I believe, but it needs to be tracked through.
>
> * Add python3-style type annotations. We just started doing this in zuul
> and it's pretty cool - and is possible to do in a python2 compatible way.
>
> Longer Goals
> 
>
> That gets us a home for openstacksdk, a path towards consolidation of
> effort and a clear story for our end users. There are a few longer-term
> things we should be keeping in mind as we work on this:
>
> * suitability for python-openstackclient. Dean and Steve have been laying
> in the groundwork for doing direct-REST in python-openstackclient because
> python-*client are a mess from an end-user perspective and openstacksdk
> isn't suitable. If we can sync on requirements hopefully we can produce
> something that python-openstackclient can honestly use for that layer
> instead of needing local code.
>
> * suitability for heat/horizon - both heat and horizon make calls to other
> OpenStack services as a primary operation (plenty of services make
> service-to-service calls, but for heat and horizon is a BIG part of their
> life) The results of this work should allow heat and horizon to remove
> local work they have using python-*client, doing local version discovery or
> any of the rest - and should expose to them rich primitives they can use
> easily.
>
> Conclusion
> --
>
> As I mentioned at the top, I'd been thinking some of this already and had
> planned on chatting with folks in person at the PTG, but it seems we're at
> a place where that's potentially counter productive.
>
> Depending on what people think I can follow this up with some governance
> resolutions and more detailed specs.
>
> Thanks!
> Monty
>
>
> __
> 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] Reminder: User Committee Nominations Start Today!

2017-07-31 Thread Melvin Hillsman
For our non-US community members, a gentle reminder.

On Mon, Jul 31, 2017 at 10:12 AM, Melvin Hillsman <mrhills...@gmail.com>
wrote:

> Hey everyone,
>
> Just a friendly reminder that the UC elections are now open for candidates
> to be peer- or self-nominated. In order to do so please send an email to
> the user-commit...@lists.openstack.org mailing list and include the
> phrase "UC Candidacy" in the subject line. More details can be found at the
> following - https://governance.openstack.org/uc/reference/uc-election-
> aug2017.html#candidates
>
> --
> Kind regards,
>
> OpenStack User Committee
> (Jon, Shilla, Shamail, Edgar, Melvin)
>



-- 
Kind regards,

OpenStack User Committee
(Jon, Shilla, Shamail, Edgar, Melvin)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [all] Reminder: User Committee Nominations Start Today!

2017-07-31 Thread Melvin Hillsman
Hey everyone,

Just a friendly reminder that the UC elections are now open for candidates
to be peer- or self-nominated. In order to do so please send an email to
the user-commit...@lists.openstack.org mailing list and include the phrase
"UC Candidacy" in the subject line. More details can be found at the
following -
https://governance.openstack.org/uc/reference/uc-election-aug2017.html#candidates

-- 
Kind regards,

OpenStack User Committee
(Jon, Shilla, Shamail, Edgar, Melvin)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] Ops Midcycle

2017-07-18 Thread Melvin Hillsman
Hey everyone,

I am sending this to dev ML hoping to get some projects to add questions
for folks attending the midcycle which may be beneficial. The etherpad for
sessions can be found at https://etherpad.openstack.org/p/MEX-ops-meetup
feel free to add new or add to existing sessions.

-- 
Kind regards,

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

Learner | Ideation | Belief | Responsibility | Command
__
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 Operators Midcycle

2017-07-14 Thread Melvin Hillsman
Just a friendly reminder for those who are up on the other side of the
globe. Please take a moment to put some ideas for sessions in the etherpad
- https://etherpad.openstack.org/p/MEX-ops-meetup

Even if you are not able to make the midcycle, please take time to propose
sessions.

On Wed, Jul 5, 2017 at 10:32 PM, Melvin Hillsman <mrhills...@gmail.com>
wrote:

> Just a friendly reminder for those who are waking up on the other side of
> the globe. Please take a moment to put some ideas for sessions in the
> etherpad - https://etherpad.openstack.org/p/MEX-ops-meetup
>
> Even if you are not able to make the midcycle, please take time to propose
> sessions.
>
> On Mon, Jul 3, 2017 at 7:40 AM, Melvin Hillsman <mrhills...@gmail.com>
> wrote:
>
>> Hey everyone,
>>
>> Happy 4th of July Eve! We have the upcoming Operator Midcycle in Mexico
>> City, Mexico August 9-10th, 2017. Sign up via Eventbrite now*, space is
>> limited* - https://www.eventbrite.com/e/mexico-city-openstack-operators
>> -meetup-tickets-34989052197
>>
>> We are taking session ideas and need your help generating them. Right now
>> we have Kubernetes, Containers, NFV, and few more -
>> https://etherpad.openstack.org/p/MEX-ops-meetup
>>
>> --
>> Kind regards
>>
>> OpenStack User Committee
>> (Edgar, Jon, Melvin, Shamail, Shilla)
>>
>
>
> --
> Kind regards,
>
> Melvin Hillsman
> mrhills...@gmail.com
> mobile: (832) 264-2646
>
> Learner | Ideation | Belief | Responsibility | Command
>



-- 
-- 
Kind regards,

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

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


[openstack-dev] [all] Announcing openstack-sigs ML

2017-07-13 Thread Melvin Hillsman
Hi everyone,

Earlier this year we discussed areas we could collectively come together as
a community and be better. One area identified was getting unanswered
requirements simply put, answered[1]. After some small and larger
conversations the goal of adopting the SIG model, as touted by other
OpenSource communities like k8s and Fedora for example, was introduced at
the Forum[2].

With this goal in mind we understand that it is not the only single perfect
solution but it is one step in the right direction. Rather than wait for
ideas and implementation details to coalesce delaying the opportunity to
learn we decided to take to a couple actions:


   1. Start the openstack-sigs mailing list


   1. Propose creation of Meta SIG (
   http://lists.openstack.org/pipermail/openstack-sigs/2017-July/00.html
   ) *be sure to read this*


An initial thread[3] surrounding the effectiveness and implementation of
SIGs had been started and folks should continue the conversation by using
the [meta] tag on the openstack-sigs mailing list. We look forward to
lively and above all practical and applicable discussions taking place
within SIGs which result in unanswered requirements being answered.

Also we would like to encourage current folks to use the [meta] tag in your
emails to the mailing list to discuss any successes, failures, advantages,
disadvantages, improvements, suggestions, etc.

[1]
http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements
[3] http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html

-- 
Melvin Hillsman and Thierry Carrez
__
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] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-11 Thread Melvin Hillsman
++ As I was not sure how to word it without sounding too opinionated
without appropriate technical jargon. When most folks hear "mostly the
same" regarding a critical component, and sometimes not so critical ones,
that raises all kinds of red flags. I could not think from purely code
aspect of what that means but from operations it means potentially it could
affect the bottom line and well, that affects everyone generally :)

On Tue, Jul 11, 2017 at 6:45 AM, Davanum Srinivas <dava...@gmail.com> wrote:

> On Tue, Jul 11, 2017 at 7:33 AM, Chris Dent <cdent...@anticdent.org>
> wrote:
> > On Tue, 11 Jul 2017, Mikhail Fedosin wrote:
> >
> >> For example, deactivating an image in Glance looks like *POST*
> >> /v2/images/{image_id}/actions/deactivate with empty body.
> >> At one time, Chris Dent advised us to avoid such decisions, and simply
> >> change the status of the artifact to 'deactivated' using *PATCH*, which
> we
> >> did.
> >
> >
> > Indeed I did. The point of that was to avoid "actions" style URLs on
> > resources that already have that information in their
> > representations so that the interface is more RESTful and doesn't
> > have a profusion of verby URLs. The other option is to PUT a full
> > representation with the status changed.
> >
> > But that's not the point here. The issue is that in order for Glare
> > to provide a seamless compatibility layer with Glance it needs to be
> > able to present a facade which is _identical_ to Glance. Not mostly
> > the same but with improvement, but identical with all the same
> > warts.
>
> Big +1 to "Not mostly the same but with improvement, but identical
> with all the same warts.". Anything else is a deal breaker IMHO.
>
> Thanks,
> Dims
>
> >
> > This provides a critical part in a smooth migration plan. As people
> > become aware of glare being there, they can start taking advantage
> > of the new features in their new code or code that they are ready to
> > update, without having to update old stuff.
> >
> > If Glare has fairly good separation between the code that handles
> > URLs and processes bodies (in and out) and the code that does stuff
> > with those bodies[1], it ought to be somewhat straightforward to
> > create such a facade.
> >
> > [1] Not gonna use model, view, controller here; those terms have
> > never been accurate for web-based APIs.
> >
> >
> >
> > --
> > Chris Dent  ┬──┬◡ノ(° -°ノ)   https://anticdent.org/
> > freenode: cdent tw: @anticdent
> >
> > 
> __
> > 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
> >
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> 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

Learner | Ideation | Belief | Responsibility | Command
__
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 Operators Midcycle

2017-07-05 Thread Melvin Hillsman
Just a friendly reminder for those who are waking up on the other side of
the globe. Please take a moment to put some ideas for sessions in the
etherpad - https://etherpad.openstack.org/p/MEX-ops-meetup

Even if you are not able to make the midcycle, please take time to propose
sessions.

On Mon, Jul 3, 2017 at 7:40 AM, Melvin Hillsman <mrhills...@gmail.com>
wrote:

> Hey everyone,
>
> Happy 4th of July Eve! We have the upcoming Operator Midcycle in Mexico
> City, Mexico August 9-10th, 2017. Sign up via Eventbrite now*, space is
> limited* - https://www.eventbrite.com/e/mexico-city-openstack-
> operators-meetup-tickets-34989052197
>
> We are taking session ideas and need your help generating them. Right now
> we have Kubernetes, Containers, NFV, and few more -
> https://etherpad.openstack.org/p/MEX-ops-meetup
>
> --
> Kind regards
>
> OpenStack User Committee
> (Edgar, Jon, Melvin, Shamail, Shilla)
>


-- 
Kind regards,

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

Learner | Ideation | Belief | Responsibility | Command
__
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][tc] Wiki (was: How to deal with confusion around "hosted projects")

2017-07-03 Thread Melvin Hillsman
Additionally there are non-project folks who use the wiki - Working Groups
/ UC Teams / SIGs (potentially) - so I also request not making the wiki
read-only.

On Mon, Jul 3, 2017 at 10:04 AM, Doug Hellmann <d...@doughellmann.com>
wrote:

> Excerpts from Flavio Percoco's message of 2017-07-03 16:11:44 +0200:
> > On 03/07/17 13:58 +0200, Thierry Carrez wrote:
> > >Flavio Percoco wrote:
> > >> Sometimes I wonder if we still need to maintain a Wiki. I guess some
> > >> projects still use it but I wonder if the use they make of the Wiki
> could be moved
> > >> somewhere else.
> > >>
> > >> For example, in the TC we use it for the Agenda but I think that
> could be moved
> > >> to an etherpad. Things that should last forever should be documented
> somewhere
> > >> (project repos, governance repo in the TC case) where we can actually
> monitor
> > >> what goes in and easily clean up.
> > >
> > >This is a complete tangent, but I'll bite :) We had a thorough
> > >discussion about that last year, summarized at:
> > >
> > >http://lists.openstack.org/pipermail/openstack-dev/2016-
> June/096481.html
> > >
> > >TL,DR; was that while most authoritative content should (and has been
> > >mostly) moved off the wiki, it's still useful as a cheap publication
> > >platform for teams and workgroups, somewhere between a git repository
> > >with a docs job and an etherpad.
> > >
> > >FWIW the job of migrating authoritative things off the wiki is still
> > >on-going. As an example, Thingee is spearheading the effort to move the
> > >"How to Contribute" page and other first pointers to a reference website
> > >(see recent thread about that).
> >
> > I guess the short answer is that we hope one day we won't need it. I
> certainly
> > do.
> >
> > What would happen if we make the wiki read-only? Would that break peopl's
> > workflow?
> >
> > Do we know what teams modify the wiki more often and what it is they do
> there?
> >
> > Thanks for biting :)
> > Flavio
> >
>
> The docs team is looking for operators to take over the operators guide
> and move that content to the wiki (operators have said they don't want
> to deal with gerrit reviews).
>
> Please don't make the wiki read-only.
>
> Doug
>
>
> __
> 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

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


[openstack-dev] OpenStack Operators Midcycle

2017-07-03 Thread Melvin Hillsman
Hey everyone,

Happy 4th of July Eve! We have the upcoming Operator Midcycle in Mexico
City, Mexico August 9-10th, 2017. Sign up via Eventbrite now*, space is
limited* -
https://www.eventbrite.com/e/mexico-city-openstack-operators-meetup-tickets-34989052197

We are taking session ideas and need your help generating them. Right now
we have Kubernetes, Containers, NFV, and few more -
https://etherpad.openstack.org/p/MEX-ops-meetup

-- 
Kind regards

OpenStack User Committee
(Edgar, Jon, Melvin, Shamail, Shilla)
__
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][tc] Turning TC/UC workgroups into OpenStack SIGs

2017-06-26 Thread Melvin Hillsman
 how many
> different work groups are there that care about scaling? So rather than
> have 5 work groups that all overlap on some level for a specific issue,
> create a SIG for that specific issue so the people involved can work on
> defining the specific problem and work to come up with a solution that can
> then be implemented by the upstream development teams, either within a
> single project or across projects depending on the issue. And once the
> specific issue is resolved, close down the SIG.


> Examples here would be things that fall under proposed community wide
> goals for a release, like running API services under wsgi, py3 support,
> moving policy rules into code, hierarchical quotas, RBAC "admin of admins"
> policy changes, etc. Have a SIG that is comprised of people with different
> roles (project managers, product managers, operators, developers, docs, QA)
> that are focused on solving that one specific issue and drive it, and then
> close it down once some completion criteria is met.
>
>
A SIG possibly should continue to exist for something like scaling, as it
will more than likely not have been created for a defined work dealing with
scaling but rather scaling itself which a number of work items would come
out of.

That still doesn't mean you're going to get the attendance you need from
> all parties. I don't know how you solve that one. People are going to work
> on what they are paid to work on.


Part of the resolution SIGs can assist with in getting folks to attend,
getting paid or not, are a number of outcomes from SIGs, well thought out
feature requests (PjMs), understanding of what should/should not/can/can
not be done (DEVs), why it makes sense to resolve one or more should/can
nots (OPs), resources to speed time to resolution (PrMs), single point of
discussion (ALL), etc, etc. Possibly when folks see that rather than
spending 100% of their resources on a work item that load can be shared and
there is a simple way to determine so by participating in a SIG that will
help as well.


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

Learner | Ideation | Belief | Responsibility | Command
__
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][tc][uc] Turning TC/UC workgroups into OpenStack SIGs

2017-06-22 Thread Melvin Hillsman
>> it's been reborn as a TC workgroup, led by a couple of devs, and is
>> lacking app user input. Artificial barriers discourage people to join.
>> Let's just call all of them SIGs.
>>
>> - the "Public Cloud WG" tries to cover an extremely important use case
>> for all of OpenStack (we all need successful OpenStack public clouds).
>> However, so far I've hardly seen a developer joining, because it's seen
>> as an Ops group just trying to make requirements emerge. I want the few
>> developers that OVH or CityCloud or other public clouds are ready to
>> throw upstream to use the rebranded "Public Cloud SIG" as a rally point,
>> to coordinate their actions. Because if they try to affect upstream
>> separately, they won't go far, and we badly need them involved.
>>
>> Yes, it's mostly a rebranding exercise, but perception matters.
>> Hope this clarifies,
>>
>> --
>> Thierry Carrez (ttx)
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Thanks,
> Shamail Tahir
> t: @ShamailXD
> tz: Eastern Time
>
> __
> 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

Learner | Ideation | Belief | Responsibility | Command
__
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][tc] Moving away from "big tent" terminology

2017-06-15 Thread Melvin Hillsman
Just my .02,

I agree with those who have said distinction is still difficult with
initial thoughts and possibly fleshing out more clearly how that would be
handled - opium branding, questions/criteria proposed by Chris, etc. - can
address the identified potential confusion. I like the idea of branding the
infra team - wonder what they think of that. As others have stated I do not
have any good suggestions just throwing in an extra +1 where appropriate :)

On Thu, Jun 15, 2017 at 7:57 AM, Thierry Carrez <thie...@openstack.org>
wrote:

> Sean Dague wrote:
> > [...]
> > I think those are all fine. The other term that popped into my head was
> > "Friends of OpenStack" as a way to describe the openstack-hosted efforts
> > that aren't official projects. It may be too informal, but I do think
> > the OpenStack-Hosted vs. OpenStack might still mix up in people's head.
>
> My original thinking was to call them "hosted projects" or "host
> projects", but then it felt a bit incomplete. I kinda like the "Friends
> of OpenStack" name, although it seems to imply some kind of vetting that
> we don't actually do.
>
> An alternative would be to give "the OpenStack project infrastructure"
> some kind of a brand name (say, "Opium", for OpenStack project
> infrastructure ultimate madness) and then call the hosted projects
> "Opium projects". Rename the Infra team to Opium team, and voilà!
>
> --
> Thierry Carrez (ttx)
>
> __
> 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

Learner | Ideation | Belief | Responsibility | Command
__
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] [ironic][nova] Goodbye^W See you later

2017-06-09 Thread Melvin Hillsman
...

No words can express, will try to keep in touch, and congratulations on
your new adventure sir! Continue to be a great influence and valued member
of your new team.

On Thu, Jun 8, 2017 at 7:45 AM, Jim Rollenhagen <j...@jimrollenhagen.com>
wrote:

> Hey friends,
>
> I've been mostly missing for the past six weeks while looking for a new
> job, so maybe you've forgotten me already, maybe not. I'm happy to tell you
> I've found one that I think is a great opportunity for me. But, I'm sad to
> tell you that it's totally outside of the OpenStack community.
>
> The last 3.5 years have been amazing. I'm extremely grateful that I've
> been able to work in this community - I've learned so much and met so many
> awesome people. I'm going to miss the insane(ly awesome) level of
> collaboration, the summits, the PTGs, and even some of the bikeshedding.
> We've built amazing things together, and I'm sure y'all will continue to do
> so without me.
>
> I'll still be lurking in #openstack-dev and #openstack-ironic for a while,
> if people need me to drop a -2 or dictate old knowledge or whatever, feel
> free to ping me. Or if you just want to chat. :)
>
> <3 jroll
>
> P.S. obviously my core permissions should be dropped now :P
>
> __
> 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

Learner | Ideation | Belief | Responsibility | Command
__
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] [go][all] Settling on gophercloud as the go based API library for all OpenStack projects

2017-05-23 Thread Melvin Hillsman
+1 as again it can assist us as an entire community (dev/non-dev) to
galvanize around one tool

On Tue, May 23, 2017 at 3:32 PM, Sean McGinnis <sean.mcgin...@gmx.com>
wrote:

> On Tue, May 23, 2017 at 10:54:13AM -0400, Davanum Srinivas wrote:
> > Folks,
> >
> > This has come up several times in various conversations.
> >
> > Can we please stop activity on
> > https://git.openstack.org/cgit/openstack/golang-client/ and just
> > settle down on https://github.com/gophercloud/gophercloud ?
> >
>
> +1
>
> I think we are all better off if we can focus our efforts in one place.
>
> > This becomes important since new container-y projects like
> > stackube/fuxi/kuryr etc can just pick one that is already working and
> > not worry about switching later. This is also a NIH kind of behavior
> > (at least from a casual observer from outside).
> >
> > Thanks,
> > Dims
> >
> > --
> > Davanum Srinivas :: https://twitter.com/dims
> >
> > 
> __
> > 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

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


[openstack-dev] Board Initiative: Strategy for Unanswered Requirements

2017-05-11 Thread Melvin Hillsman
Good morning everyone!

If you are at the Summit and available at 9:50am please take time to join
us in Room 104 at the Hynes Convention Center. Just a couple things to
remember:

Context:
http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/

Etherpad:
https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements

-- 
Kind regards,

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

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


[openstack-dev] Ops Meetup Team

2017-04-25 Thread Melvin Hillsman
Hey everyone,

We have been having some great momentum since the Foundation enlisted a
small group of operators to manage the Midcycle and to form the Ops Meetup
Team. We have a few asks related to the teaml:

   1. More people! We need more folks to participate in the team meetings
   and activities; the more the merrier. You do not have to be an "operator";
   everyone is welcome!
   2. Themed midcycle. In an effort to continue to ensure the midcycle is
   relevant, we would like feedback on if folks agree with the midcycle being
   themed. Basically wherever the midcycle is being held, contact some folks
   in the region and focus on content that is more relevant to the folks in
   the region.

More information on the team can be found on the wiki[1]. Meeting day and
time is Tuesdays @ 1500UTC in #openstack-operators. We will also have a
session[2] in Boston around the team, its purpose, and some items to make
decisions on; looking forward to seeing you all in Boston!

[1] https://wiki.openstack.org/wiki/Ops_Meetups_Team
[2] https://www.openstack.org/summit/boston-2017/summit-schedule
/events/18935/openstack-operators-ops-meetup-team-catch-up

-- 
Kind regards,

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

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


[openstack-dev] [Forum] Unanswered Requirements

2017-04-25 Thread Melvin Hillsman
Hey everyone,

I would like to take the opportunity to open the discussion up for feedback
from the community leading into the Boston Forum.

*Session Description*: Collaborate/communicate around user stories, gap
analysis, what fits in the current state of tech, prioritize what would
have the greatest impact in reducing pain for users. Ideally we would like
to discuss in this session successes and failures of the current state of
our feedback loop. We should be able to identify patterns that fit within a
larger system/process that we are able to iterate through as the way to get
user requirements implemented into code. [1]

Moving the conversation forward is the aim with the ultimate goal being the
first iteration of a plan that can be implemented, and one that gathers
data/insight consistently to make specific and relevant improvements.

[1] https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements

-- 
Kind regards,

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

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


[openstack-dev] Ops Team Meeting 042417 Canceled

2017-04-24 Thread Melvin Hillsman
Hey everyone,

Apologies for the late notice. Unless someone can facilitate the ops team
meeting we will have to cancel for today:

http://eavesdrop.openstack.org/#OpenStack_OSOps_Team

-- 
Kind regards,

Melvin Hillsman
OpenStack Engineer, Rackspace

mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://rackspace.com

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


[openstack-dev] Ops Meetups Team Meeting Reminder

2017-04-11 Thread Melvin Hillsman
Hey everyone,

Just a reminder that the meetups team will be meeting today 4/11 at 1500UTC

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


https://www.worldtimebuddy.com/?qm=1=100,1816670,2147714,4699066=100=2017-4-11=15-16
https://www.worldtimebuddy.com/?qm=1=100,2643743,5391959,2950159=100=2017-4-11=15-16

-- 
Kind regards,

Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center

mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://osic.org

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


[openstack-dev] UC Meeting 04/10/17 Cancelled

2017-04-10 Thread Melvin Hillsman
Hey everyone,

Apologies for the late notice. We are cancelling the meeting today. We have
moved to a weekly cadence with meetings being subject to new agenda items
having to be proposed/added by the Friday before the meeting. In other
words, for UC meeting scheduled for 04/17/17 agenda items will need to be
proposed/added by this Friday 04/14/17

Thanks very much,

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


[openstack-dev] Reminder User Committee Meeting

2017-04-10 Thread Melvin Hillsman
Hey everyone,

User Committee will meet today in #openstack-meeting @ 1900UTC. If you have
any requests for agenda items you can reply to this email or message any of
the UC members via email as well as IRC - #openstack-uc

-- 
Kind regards,

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


[openstack-dev] OSOps Meetings for April

2017-04-09 Thread Melvin Hillsman
Hey everyone,

Just a friendly reminder that OSOps meetings for April will happen on
Monday April 10th and April 24th at 1400UTC in #openstack-meeting-5

Please feel free to add to the agenda and invite 100 people :)

https://etherpad.openstack.org/p/osops-meeting

You can catch up on previous meeting notes/logs by visiting
http://eavesdrop.openstack.org/meetings/osops

-- 
Kind regards,

Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center

mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://osic.org

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


[openstack-dev] Boston Forum Submission Deadline!

2017-03-31 Thread Melvin Hillsman
Hey everyone,

Please take time to *submit your proposals *from the etherpad(s) or any
other place you have captured/brainstormed. This is  a friendly reminder
that all proposed Forum session leaders must submit their abstracts at:

http://forumtopics.openstack.org/

*before 11:59PM UTC on Sunday April 2nd!*

Regards,

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


[openstack-dev] Boston Forum Reminder

2017-03-27 Thread Melvin Hillsman
Hey everyone,

This is  a friendly reminder that all proposed Forum session leaders must
submit their abstracts at:

http://forumtopics.openstack.org/

*before 11:59PM UTC on Sunday April 2nd!*

Regards,

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


[openstack-dev] Reminder -- Forum Topic Submission

2017-03-22 Thread Melvin Hillsman
Hey everyone,

This is  a friendly reminder that all proposed Forum session leaders must
submit their abstracts at:

http://forumtopics.openstack.org/

*before 11:59PM UTC on Sunday April 2nd!*

Regards,

TC/UC
__
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