[OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text

Rochelle.RochelleGrober rochelle.grober at huawei.com
Thu May 1 19:58:24 UTC 2014


+1

The outward facing APIs are critical to get settled and defined through tests, but I agree that the admin APIs may be just as important as OpenStack core is defined to encompass more (especially cross project core-ness)

--Rocky

-----Original Message-----
From: Monty Taylor [mailto:mordred at inaugust.com] 
Sent: Thursday, May 01, 2014 12:39 PM
To: Lew Tucker (letucker)
Cc: <Defcore-committee at lists.openstack.org>
Subject: Re: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text

I'm willing to stipulate that for now ... But I think in the private cloud space there is the possibility that people might want to write applications to install into the cloud and might want to be able to count on our private cloud offerings providing similar admin interfaces.

There's a lot of mights there, so it's perfectly fine with me if we punt on that for now.

On May 1, 2014 12:06 PM, "Lew Tucker (letucker)" <letucker at cisco.com> wrote:
>
> +1  Tenant-facing, public API¹s are what matters to application developers 
> for interoperability. 
>
> -Lew 
>
> -- 
> Lew Tucker 
> VP/CTO Cloud Computing 
> Cisco Systems 
> office:  408-894-5045 
> cell:  415-595-5906 
>
>
>
>
>
>
>
> On 4/30/14, 8:56 PM, "Troy Toman" <troy at tomanator.com> wrote: 
>
> >"Also, I¹d like to made a quick decision > PUBLIC APIs ONLY.  I was 
> >looking at the criteria and realized that non-admin trumps everything.  I 
> >believe that we just need to accept that Core is Public API only because 
> >that¹s required for interop.  Admin tests are great but will not be core.." 
> > 
> >+1 I think this is in line with starting core small and a focus on 
> >driving interoperability.  We could always elect to handle admin API's 
> >differently if we get broad feedback that it's necessary from the 
> >community. 
> > 
> >- Troy 
> > 
> >> On Apr 30, 2014, at 10:22 PM, <Rob_Hirschfeld at Dell.com> wrote: 
> >> 
> >> Also, I¹d like to made a quick decision > PUBLIC APIs ONLY.  I was 
> >>looking at the criteria and realized that non-admin trumps everything. 
> >>I believe that we just need to accept that Core is Public API only 
> >>because that¹s required for interop.  Admin tests are great but will not 
> >>be core. 
> > 
> >_______________________________________________ 
> >Defcore-committee mailing list 
> >Defcore-committee at lists.openstack.org 
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee 
>
>
> _______________________________________________ 
> Defcore-committee mailing list 
> Defcore-committee at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee 
>
_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


More information about the Defcore-committee mailing list