Open Stack

Hi Joshua,

Is the 'tools ecosystem' about: a) tools built on top of OpenStack APIs, or
b) tools built for integration with OpenStack?

If it was b), then IMHO a *running* TryStack is not very suitable for
developers, as they may need full administrator privilege to test if their
tools can be integrated with with OpenStack well. In this case, the
reference environment needs to be described in documents, and developers
can follow the documents to build their own environment, and then do
whatever they want to do.

Thanks, Zhidong


On Tue, Apr 15, 2014 at 12:44 AM, Joshua McKenty <joshua at pistoncloud.com>wrote:

> Perhaps I can clarify a bit:
>
> When we proposed RefStack at the OpenStack board meeting in 2013, we
> divided the effort into several parts:
>
>  - A test-based mechanism for improving interop of OpenStack clouds (this
> is part of the DefCore effort and the current RefStack codebase)
>  - A publishing mechanism so that the user/operator community would have
> visibility into this capability matrix (also a target for the refstack.orgwebsite)
>  - A *running* reference openstack environment (with a documented method
> of installation and configuration) that the tools ecosystem could test
> their software against.
>
> The 3rd item is what you’re discussing; it ended up being (if that’s
> possible) even more politically complicated than the first two, simply
> because there’s no consensus within OpenStack as to whether or not the
> OpenStack framework should include an installer.
>
> The closest thing to this right now is TryStack (at least conceptually) -
> it’s likely that we’ll make it a deliverable of the DefCore committee in a
> future cycle, however.
>
> --
>
> Joshua McKenty
> Chief Technology Officer
> Piston Cloud Computing, Inc.
> +1 (650) 242-5683
> +1 (650) 283-6846
> http://www.pistoncloud.com
>
> "Oh, Westley, we'll never survive!"
> "Nonsense. You're only saying that because no one ever has."
>
> On Apr 14, 2014, at 8:07 AM, matt <matt at nycresistor.com> wrote:
>
> well in hardware engineering, when you are buying a part, from small parts
> like a 555 timer to big parts like an SOC ( system on chip ) such as a
> bluetooth transceiver, the datasheets will generally include what's called
> a reference design.
>
> so in addition to gobs of infortmation about the component, including
> thermal variances, pin outs, and anything else you might need to know, it
> will also generally include a simple circuit design that makes full use of
> the part.
>
> so that the person intending to use the part, has a basic working
> environment to test with before they do their own development.  Or just to
> see how it might fit into a circuit.  usually this is pretty easy to do
> since most new chips also have development boards designed for them as
> well.  you can usually just take chunks from the development board to turn
> into a reference design.
>
> a reference stack architecture would likely be similar to this.
>
> -matt
>
>
> On Mon, Apr 14, 2014 at 8:36 AM, Zhidong Yu <zdyu2000 at gmail.com> wrote:
>
>> The refstack.org website says RefStack is "A reference OpenStack
>> environment for tools developer". What does it mean exactly?
>>
>> I am getting started with DefCore/RefStack. While I can understand
>> RefStack is "a proof of the certified APIs" and "a certification process"
>> (also from the homepage of the website), it is not clear to me what "a
>> reference environment" means exactly.
>>
>> Thanks, Zhidong
>>
>> _______________________________________________
>> FITs mailing list
>> FITs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/fits
>>
>>
> _______________________________________________
> FITs mailing list
> FITs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/fits
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/fits/attachments/20140415/f91f9b55/attachment-0001.html>