[OpenStack-DefCore] [Product] Accelerating the Enterprise Adoption of OpenStack

Jesse Cook jesse.cook at RACKSPACE.COM
Fri Jul 31 00:44:25 UTC 2015


Hi Shamail,

Thanks! I¹ll go ahead and include defcore. One point of clarification:
while having Scenarios to cover various ³reference architectures² is
incredibly valuable, I don¹t want to neglect permission to play Features.
To be a ³Cloud² there are certain things you must be able to do, and I¹m
not convinced that OpenStack is hitting all of them yet (especially in the
area of scale and elasticity). Clearly defining these and exposing them is
really important for us to prosper. Thanks for the helpful feedback. I¹m
looking forward to working with the WG.

Thanks,

Jesse




On 7/30/15, 2:59 PM, "Shamail" <itzshamail at gmail.com> wrote:

>Hi Jesse,
>
>The BDD looks like an interesting concept and it might help us identify
>additional user stories for specific themes.  I believe that this will
>probably fall outside of scope for Product WG for now but, as mentioned,
>the resulting user stories from the testing would definitely be something
>Product WG would be interested in.  The single source of truth for
>OpenStack Powered Clouds is indeed DefCore but the focus is on
>interoperability versus "reference architectures".
>
>I'm glad you find this group and we definitely look forward to working
>with you.  Welcome to the team!
>
>Summary workflow:
>
>testing -> review output -> generate bug|user story|blueprint (depending
>on the type of finding -> if the resulting change impacts testing of a
>widely adopted service then possibly looking into DefCore capability.
>
>Thanks,
>Shamail 
>
>
>
>> On Jul 30, 2015, at 11:29 AM, Jesse Cook <jesse.cook at RACKSPACE.COM>
>>wrote:
>> 
>> +nikhil
>> 
>> 
>> 
>>> On 7/30/15, 11:28 AM, "Jesse Cook" <jesse.cook at RACKSPACE.COM> wrote:
>>> 
>>> +openstack-docs, brianr
>>> 
>>> 
>>> 
>>>> On 7/30/15, 11:20 AM, "Jesse Cook" <jesse.cook at RACKSPACE.COM> wrote:
>>>> 
>>>> I recently discovered there was a product working group for OpenStack
>>>>and
>>>> joined the mailing list today. I've been trying to find a single
>>>>source
>>>> of truth for the expected behavior of OpenStack Powered Clouds. I've
>>>>seen
>>>> various things from def core and individual projects, but nothing so
>>>>far
>>>> that clearly illustrates the overarching expected behavior. I was
>>>> wondering if this was a good opportunity and the right place to
>>>>discuss
>>>> this.
>>>> 
>>>> I believe that the OpenStack community and the customers of OpenStack
>>>> Powered Clouds could really benefit from defining the expected
>>>>behaviors
>>>> (both permission to play and key value differentiators). One effective
>>>> way to do this is through a business / development process known as
>>>> Behavior Driven Development (BDD) [0]. I was wondering if we could use
>>>> something like this to document and test the expected performance of
>>>>an
>>>> OpenStack Cloud using the 1000 node clusters. A quick example of a
>>>> feature [1] might look like this:
>>>> 
>>>> Feature: Elasticity
>>>> 
>>>>   In order to briefly leverage the power of the Cloud to do some work,
>>>>   As an OpenStack Powered Cloud customer
>>>>   I want to quickly provision a large number of servers, perform some
>>>>   work, and then destroy them.
>>>> 
>>>>   Scenario Outline: Build Bursts
>>>>       Given <cells> cell(s)
>>>>       And each cell has <hosts> hosts
>>>>       And each host has <memory> free memory
>>>>       When I request <requests> VMs
>>>>       And each VM will have <size> of RAM
>>>>       Then every VM will be ready in <time>
>>>> 
>>>>       Examples: Performance Criteria
>>>>           | cells | hosts | memory | requests | size | time |
>>>>           |     1 |  1000 |   100G |     1000 |   2G | 600s |
>>>>           |    10 |   100 |   100G |     1000 |   2G | 600s |
>>>>           ...
>>>>   ...
>>>> 
>>>> [0] https://en.wikipedia.org/wiki/Behavior-driven_development
>>>> [1] http://pythonhosted.org/behave/tutorial.html#feature-files
>>>> 
>>>> Thanks,
>>>> 
>>>> Jesse J. Cook
>>>> Compute Team Lead
>>>> 
>>>>[http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.r
>>>>ac
>>>> k
>>>> cdn.com/signatures/images/rackspace_logo.png]
>>>> 
>>>> jesse.cook at rackspace.com<mailto:jesse.cook at rackspace.com>
>>>> irc: #compute-eng (gimchi)
>>>> mobile: 618-530-0659
>>>> 
>>>> <https://rackspacemarketing.com/signatyourEmail/>
>>>> 
>>>>[http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.r
>>>>ac
>>>> k
>>>> 
>>>>cdn.com/signatures/images/linkedin.png]<https://www.linkedin.com/pub/je
>>>>ss
>>>> e
>>>> -cook/8/292/620>
>>>> 
>>>>[http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.r
>>>>ac
>>>> k
>>>> cdn.com/signatures/images/google.png]
>>>> <https://plus.google.com/u/0/+JesseCooks/posts/p/pub>
>>>> 
>>>> On 7/23/15, 12:01 PM, "Egle Sigler"
>>>> <egle.sigler at rackspace.com<mailto:egle.sigler at rackspace.com>> wrote:
>>>> 
>>>> Hello OpenStack Community,
>>>> 
>>>> I am very excited to let you know that today Rackspace and Intel
>>>> announced our plans to form the "OpenStack Innovation Center," which
>>>>is
>>>> an exciting community-oriented initiative focused on accelerating the
>>>> enterprise features and adoption of OpenStack.  This initiative
>>>>includes:
>>>> 
>>>> 
>>>> ·      Largest OpenStack Developer Cloud - We are building and making
>>>> available to the community two 1,000 node clusters to support
>>>>advanced,
>>>> large-scale and testing of OpenStack.  The clusters should be
>>>>available
>>>> to the community within six months and you can sign up
>>>> here<http://goo.gl/forms/vCkfNBmXm4> to receive updates on this
>>>>effort.
>>>> 
>>>> ·      OpenStack Developer Training - We are creating a new training
>>>> curriculum designed to onboard and significantly increase the number
>>>>of
>>>> developers working upstream in the community.
>>>> 
>>>> ·      Joint OpenStack Engineering - Rackspace and Intel developers
>>>>will
>>>> work together in collaboration with the Enterprise Work Group and
>>>> community to eliminate bugs and develop new enterprise features.  Both
>>>> companies will recruit new developers to help further OpenStack
>>>> development.
>>>> 
>>>> ·      OpenStack Innovation Center - The center will be comprised of
>>>> Rackspace and Intel developers who will work upstream, using existing
>>>> community tools and processes to improve the scalability,
>>>>manageability
>>>> and usability of OpenStack.
>>>> 
>>>> To find out more, please check out the following resources:
>>>> 
>>>> Rackspace press
>>>> 
>>>>release<http://www.rackspace.com/blog/newsarticles/rackspace-collaborat
>>>>es
>>>> -
>>>> 
>>>>with-intel-to-accelerate-openstack-enterprise-feature-development-and-a
>>>>do
>>>> p
>>>> tion/>
>>>> Rackspace 
>>>> 
>>>>blog<http://www.rackspace.com/blog/rackspace-and-intel-form-the-opensta
>>>>ck
>>>> -
>>>> innovation-center>
>>>> Intel 
>>>> 
>>>>release<http://newsroom.intel.com/community/intel_newsroom/blog/2015/07
>>>>/2
>>>> 3
>>>> 
>>>>/intel-announces-cloud-for-all-initiative-to-deliver-benefits-of-the-cl
>>>>ou
>>>> d
>>>> -to-more-businesses>
>>>> Intel 
>>>> 
>>>>blog<https://communities.intel.com/community/itpeernetwork/datastack/bl
>>>>og
>>>> /
>>>> 2015/07/23/cloud-for-all>
>>>> 
>>>> We look forward to working with you to continue advancing the leading
>>>> open source cloud platform and welcome your feedback!
>>>> 
>>>> Best regards,
>>>> 
>>>> Egle Sigler
>>>> Rackspace Principal Architect
>>>> OpenStack Foundation Board Member
>>>> _______________________________________________
>>>> 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




More information about the Defcore-committee mailing list