On Mon, Dec 8, 2014 at 1:06 PM, Adam Young wrote:
> Isn't this what the API repos are for? Should EG the Keystone schemes be
> served from
>
> https://github.com/openstack/identity-api/
>
>
>
The -api repos will go away once we have the merges completed for
replacing with the -specs repo info.
Keystone also has API documentation in the keystone-spec repo [1], which
went in with [2] and [3].
[1] https://github.com/openstack/keystone-specs/tree/master/api
[2] https://review.openstack.org/#/c/128712/
[3] https://review.openstack.org/#/c/130577/
On Mon, Dec 8, 2014 at 1:06 PM, Adam Young
Isn't this what the API repos are for? Should EG the Keystone schemes
be served from
https://github.com/openstack/identity-api/
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/opens
> >From: Sandy Walsh [sandy.wa...@rackspace.com] Monday, December 01, 2014 9:29
> >AM
> >
> >>From: Duncan Thomas [duncan.tho...@gmail.com]
> >>Sent: Sunday, November 30, 2014 5:40 AM
> >>To: OpenStack Development Mailing List
> >>Subje
>From: Sandy Walsh [sandy.wa...@rackspace.com] Monday, December 01, 2014 9:29 AM
>
>>From: Duncan Thomas [duncan.tho...@gmail.com]
>>Sent: Sunday, November 30, 2014 5:40 AM
>>To: OpenStack Development Mailing List
>>Subject: Re: [openstack-dev] Where should Schema
>From: Duncan Thomas [duncan.tho...@gmail.com]
>Sent: Sunday, November 30, 2014 5:40 AM
>To: OpenStack Development Mailing List
>Subject: Re: [openstack-dev] Where should Schema files live?
>
>Duncan Thomas
>On Nov 27, 2014 10:32 PM, "Sandy Walsh" wrote:
>>
Duncan Thomas
On Nov 27, 2014 10:32 PM, "Sandy Walsh" wrote:
>
> We were thinking each service API would expose their schema via a new
/schema resource (or something). Nova would expose its schema. Glance its
own. etc. This would also work well for installations still using older
deployments.
Th
>From: Eoghan Glynn [egl...@redhat.com] Tuesday, November 25, 2014 1:49 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] Where should Schema files live?
>
>> I think Doug's suggestion of keeping the schema files in-tree a
>From: Jay Pipes [jaypi...@gmail.com] Wednesday, November 26, 2014 5:22 PM
>On 11/20/2014 08:12 AM, Sandy Walsh wrote:
>>
>> We're early in thinking about these problems, but would like to start the
>> conversation now to get your opinions.
>>
>
>OK, so the goal of this effort should be to have a
On 11/20/2014 08:12 AM, Sandy Walsh wrote:
Hey y'all,
To avoid cross-posting, please inform your -infra / -operations buddies about
this post.
We've just started thinking about where notification schema files should live
and how they should be deployed. Kind of a tricky problem. We could rea
> I think Doug's suggestion of keeping the schema files in-tree and pushing
> them to a well-known tarball maker in a build step is best so far.
>
> It's still a little clunky, but not as clunky as having to sync two repos.
Yes, I tend to agree.
So just to confirm that my understanding lines u
>From: Eoghan Glynn [egl...@redhat.com] Friday, November 21, 2014 11:03 AM
>> >> Some problems / options:
>> >> a. Unlike Python, there is no simple pip install for text files. No
>> >> version control per se. Basically whatever we pull from the repo. The
>> >> problem with a git clone is we need t
> >> Some problems / options:
> >> a. Unlike Python, there is no simple pip install for text files. No
> >> version control per se. Basically whatever we pull from the repo. The
> >> problem with a git clone is we need to tweak config files to point to a
> >> directory and that's a pain for gatin
> >>> Why wouldn’t they live in the repo of the application that generates the
> >>> notification, like we do with the database schema and APIs defined by
> >>> those apps?
> >>
> >> That would mean downstream consumers (potentially in different languages)
> >> would need to pull all repos and ex
On Nov 21, 2014, at 9:11 AM, Sandy Walsh wrote:
>> From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 5:09
>> PM
>> On Nov 20, 2014, at 3:40 PM, Sandy Walsh wrote:
>>> From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014
>>> 3:51 PM
On Nov 20, 2014
>From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 5:09 PM
>On Nov 20, 2014, at 3:40 PM, Sandy Walsh wrote:
>> From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 3:51
>> PM
>>> On Nov 20, 2014, at 8:12 AM, Sandy Walsh wrote:
The assumptions:
1
>
>From: Eoghan Glynn [egl...@redhat.com] Thursday, November 20, 2014 5:34 PM
>
>Some questions/observations inline.
>
>> Hey y'all,
>>
>> To avoid cross-posting, please inform your -infra / -operations buddies
>> about this post.
>>
>> We've just started th
Thanks for raising this Sandy,
Some questions/observations inline.
> Hey y'all,
>
> To avoid cross-posting, please inform your -infra / -operations buddies about
> this post.
>
> We've just started thinking about where notification schema files should live
> and how they should be deployed.
On Nov 20, 2014, at 3:40 PM, Sandy Walsh wrote:
> From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 3:51
> PM
>> On Nov 20, 2014, at 8:12 AM, Sandy Walsh wrote:
>>> Hey y'all,
>>>
>>> To avoid cross-posting, please inform your -infra / -operations buddies
>>> about this
From: Doug Hellmann [d...@doughellmann.com] Thursday, November 20, 2014 3:51 PM
>On Nov 20, 2014, at 8:12 AM, Sandy Walsh wrote:
>> Hey y'all,
>>
>> To avoid cross-posting, please inform your -infra / -operations buddies
about this post.
>>
>> We've just started thinking about w
On Nov 20, 2014, at 8:12 AM, Sandy Walsh wrote:
> Hey y'all,
>
> To avoid cross-posting, please inform your -infra / -operations buddies about
> this post.
>
> We've just started thinking about where notification schema files should live
> and how they should be deployed. Kind of a tricky p
Hey y'all,
To avoid cross-posting, please inform your -infra / -operations buddies about
this post.
We've just started thinking about where notification schema files should live
and how they should be deployed. Kind of a tricky problem. We could really use
your input on this problem ...
The
22 matches
Mail list logo
