Open Stack

If I were to pick my top concern it¹s Randy¹s.  (AJ¹s #1 below.)  I think
a number of things flow out of getting that right.  If we don¹t get that
right then I think we have virtually no hope of keeping the teams
coordinated at some level.  As part of Randy¹s I¹d also drive to establish
the concept of ³themes² for each release - and specifying those themes
more than one release out.  So, for example, if a theme is reliability,
each project can point to efforts in that direction.  Or interoperability,
or whatever.

Jim

On 1/20/15, 11:33 AM, "AJ Park" <aj.park at icloud.com> wrote:

>My votes:
>
>1. (Randy) establish a process by which longer term vision and product
>direction can emerge from within the community,
>http://lists.openstack.org/pipermail/product-wg/2014-December/000051.html
>
>2. (Sarob)Tagging approach to project maturity,
>http://ttx.re/the-way-forward.html, TC spec
>https://review.openstack.org/#/c/138504/5/resolutions/20141202-project-str
>ucture-reform-spec.rst
>
>3. (sarob) 2-3 year architecture / use case strategy. Win the Enterprise
>is doing parts of this.
>https://wiki.openstack.org/wiki/Win_the_Enterprise. Each project has its
>own vision for the future. This group should debate the current state of
>binding use cases to development plans on a ongoing basis.
>
>Note: I expect #3 to emerge when we follow the process determined in #1.
>
>Best,
>AJ
>
>On Jan 20, 2015, at 12:04 PM, Mike Cohen <cohen at noironetworks.com> wrote:
>
>Ideas I've heard on this thread that I would vote for:
>
>- rob on defcore / revstack. , Should cover broader governance changes for
>projects here or in an adjacent session.
>- multi-release strategy / long term vision (maybe randy?)
>- Discussion on what the goals of this group are / what charter is.
>Doesn't seem we've closed on this over email.
>- Use Cases / Key gaps in OpenStack that need to be filled
>- Overview / Review of what operators group is doing / has done (for
>background for everyone)
>
>
>On Mon, Jan 19, 2015 at 1:45 PM, Rochelle Grober
><rochelle.grober at huawei.com
>wrote:
>
>sean roberts [mailto:seanroberts66 at gmail.com], Monday, January 19, 2015
>1:18 PM wrote:
>The win the enterprise group continues to come up with use cases. It's
>working on adding filling gaps in the docs as well.
>Between the operator, win the enterprise groups, this subteam would
>isolate and test out those use cases and publish the results?
>[Rockyg]
>Excellent question. I think it would be really useful to have/get a quick
>overview of these non-developer groups and their charter/mission. I was
>under the impression that the win the enterprise group was a cross between
>product marketing and product management? Not sure.
>My thoughts on the reference architecture team(s) would be that as a cross
>project group, they could identify/specify architectures based on use
>cases, then work together to define, document, automate installation and
>interop testing and publish all of the generated information.
>I think, after the initial implement/document/publish cycle, the hardest
>part will be updating for every OpenStack release. And, if the devs get
>the upgrade process correct, then it might mostly be documenting the new
>and deprecated features.
>The key take away here is that there should be a less than one day process
>for any of the endusers to install a small multimode cloud for their own
>purposes, similar to what devstack does for devs. And for endusers, it
>needs to be extremely well documented.
>This could even be used in training courses for the lab work phases.
>--Rocky
>On Monday, January 19, 2015, Rochelle Grober <rochelle.grober at huawei.com
><mailto:rochelle.grober at huawei.com>> wrote:
>I believe Rob Hirschfeld will be in attendance so, Rob (and I if he wants
>me) can cover the DefCore and Refstack session. Rob is certainly the
>expert on DefCore.
>I'd also like to propose a session on defining/finding a project manager
>to start creating some reference architectures with tested installs. Right
>now there is a discussion on the Operators' list on a small installation,
>3-5 nodes, with HA. This could be a fine first reference architecture with
>all the code and docs to make it similar (or better) to install than
>devstack. This is also a good architecture for prospective users for
>prototyping, testing, or small business installation. Spec'ing this out
>during the summit, or at least getting a good start, along with a
>volunteer
>project manager, would be a very worthwhile endeavor for the meetup.
>--Rocky
>-----Original Message-----
>From: sean roberts [mailto:seanroberts66 at gmail.com<javascript:;>]
>Sent: Sunday, January 18, 2015 11:44 AM
>To: product-wg at lists.openstack.org<javascript:;>
>Subject: [Product] Time to Pick Topics
>It¹s time to finalize the OpenStack Product Management topics for the Kilo
>midcycle meeting
><
>http://sarob.com/2015/01/openstack-kilo-product-management-midcycle-coming
>-to-a-greater-understanding/
>>
>coming
>up. We will need speakers for each topic. I want to get the best authority
>possible for each talk, so locking down the topics is required. I will
>need
>to get their commitment as soon as possible.
>More details on this post
>http://sarob.com/2015/01/getting-ready-for-the-product-management-kilo-mid
>cycle/
>--
>~sean
>_______________________________________________
>Product-wg mailing list
>Product-wg at lists.openstack.org<javascript:;>
>http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>--
>~sean
>_______________________________________________
>Product-wg mailing list
>Product-wg at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>_______________________________________________
>Product-wg mailing list
>Product-wg at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>_______________________________________________
>Product-wg mailing list
>Product-wg at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg