Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-26 Thread Dmitry Tantsur 

On 11/25/2015 10:43 PM, Ben Nemec wrote:

On 11/23/2015 06:50 AM, Dmitry Tantsur wrote:

On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote:






 On 10 November 2015 at 15:08, Tzu-Mainn Chen > wrote:

 Hi all,

 At the last IRC meeting it was agreed that the new TripleO REST API
 should forgo the Tuskar name, and simply be called... the TripleO
 API.  There's one more point of discussion: where should the API
 live?  There are two possibilities:

 a) Put it in tripleo-common, where the business logic lives.  If we
 do this, it would make sense to rename tripleo-common to simply
 tripleo.


 +1 - I think this makes most sense if we are not going to support
 the tripleo repo as a library.


Okay, this seems to be the consensus, which is great.

The leftover question is how to package the renamed repo.  'tripleo' is
already intuitively in use by tripleo-incubator.
In IRC, bnemec and trown suggested splitting the renamed repo into two
packages - 'python-tripleo' and 'tripleo-api',
which seems sensible to me.


-1, that would be inconsistent with what other projects are doing. I
guess tripleo-incubator will die soon, and I think only tripleo devs
have any intuition about it. For me tripleo == instack-undercloud.


This was only referring to rpm packaging, and it is how we currently
package most of the other projects.  The repo itself would stay as one
thing, but would be split into python-tripleo and openstack-tripleo-api
rpms.

I don't massively care about package names, but given that there is no
(for example) openstack-nova package and openstack-tripleo is already in
use by a completely different project, I think it's reasonable to move
ahead with the split packages named this way.


Got it, sorry for confusion







What do others think?


Mainn


 b) Put it in its own repo, tripleo-api


 The first option made a lot of sense to people on IRC, as the
 proposed
 API is a very thin layer that's bound closely to the code in
 tripleo-
 common.  The major objection is that renaming is not trivial;
 however
 it was mentioned that renaming might not be *too* bad... as long as
 it's done sooner rather than later.

 What do people think?


 Thanks,
 Tzu-Mainn Chen

 
__
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-25 Thread Ben Nemec 
On 11/23/2015 06:50 AM, Dmitry Tantsur wrote:
> On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote:
>>
>> 
>>
>>
>>
>> On 10 November 2015 at 15:08, Tzu-Mainn Chen > > wrote:
>>
>> Hi all,
>>
>> At the last IRC meeting it was agreed that the new TripleO REST API
>> should forgo the Tuskar name, and simply be called... the TripleO
>> API.  There's one more point of discussion: where should the API
>> live?  There are two possibilities:
>>
>> a) Put it in tripleo-common, where the business logic lives.  If we
>> do this, it would make sense to rename tripleo-common to simply
>> tripleo.
>>
>>
>> +1 - I think this makes most sense if we are not going to support
>> the tripleo repo as a library.
>>
>>
>> Okay, this seems to be the consensus, which is great.
>>
>> The leftover question is how to package the renamed repo.  'tripleo' is
>> already intuitively in use by tripleo-incubator.
>> In IRC, bnemec and trown suggested splitting the renamed repo into two
>> packages - 'python-tripleo' and 'tripleo-api',
>> which seems sensible to me.
> 
> -1, that would be inconsistent with what other projects are doing. I 
> guess tripleo-incubator will die soon, and I think only tripleo devs 
> have any intuition about it. For me tripleo == instack-undercloud.

This was only referring to rpm packaging, and it is how we currently
package most of the other projects.  The repo itself would stay as one
thing, but would be split into python-tripleo and openstack-tripleo-api
rpms.

I don't massively care about package names, but given that there is no
(for example) openstack-nova package and openstack-tripleo is already in
use by a completely different project, I think it's reasonable to move
ahead with the split packages named this way.

> 
>>
>> What do others think?
>>
>>
>> Mainn
>>
>>
>> b) Put it in its own repo, tripleo-api
>>
>>
>> The first option made a lot of sense to people on IRC, as the
>> proposed
>> API is a very thin layer that's bound closely to the code in
>> tripleo-
>> common.  The major objection is that renaming is not trivial;
>> however
>> it was mentioned that renaming might not be *too* bad... as long as
>> it's done sooner rather than later.
>>
>> What do people think?
>>
>>
>> Thanks,
>> Tzu-Mainn Chen
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-25 Thread Richard Su 



On 11/24/2015 07:27 AM, Dougal Matthews wrote:



On 24 November 2015 at 07:45, Richard Su > wrote:




On 11/17/2015 07:31 AM, Tzu-Mainn Chen wrote:






On 10 November 2015 at 15:08, Tzu-Mainn Chen
> wrote:

Hi all,

At the last IRC meeting it was agreed that the new
TripleO REST API
should forgo the Tuskar name, and simply be called... the
TripleO
API.  There's one more point of discussion: where should
the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic
lives.  If we
do this, it would make sense to rename tripleo-common to
simply
tripleo.


+1 - I think this makes most sense if we are not going to
support the tripleo repo as a library.


Okay, this seems to be the consensus, which is great.

The leftover question is how to package the renamed repo. 
'tripleo' is already intuitively in use by tripleo-incubator.

In IRC, bnemec and trown suggested splitting the renamed repo
into two packages - 'python-tripleo' and 'tripleo-api',
which seems sensible to me.

What do others think?




I have started the process of renaming the repo with these patches:
https://review.openstack.org/#/c/247834/
https://review.gerrithub.io/#/c/252864/

Jan made an interesting suggestion that it may be easier to create
a new repo named tripleo and move the tripleo-common code there.
With renaming, I'm already see some complications with the
tripleo-common package builds failing in the CI until updated spec
is merged.

What do folks think about this? I am unsure which is more
complicated, creating a new repo and all the setup that goes with
it. Or renaming the existing repo and fixing CI issues along the way.


I'm not sure which is easier or better, but if we do create a new repo 
we need to make sure we carry over the git history.


Good idea. I have submitted a request to create the new repo.

https://review.openstack.org/#/c/249521/



- Richard



b) Put it in its own repo, tripleo-api


The first option made a lot of sense to people on IRC, as
the proposed
API is a very thin layer that's bound closely to the code
in tripleo-
common.  The major objection is that renaming is not
trivial; however
it was mentioned that renaming might not be *too* bad...
as long as
it's done sooner rather than later.

What do people think?


Thanks,
Tzu-Mainn Chen


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe


http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-24 Thread Dougal Matthews 
On 24 November 2015 at 07:45, Richard Su  wrote:

>
>
> On 11/17/2015 07:31 AM, Tzu-Mainn Chen wrote:
>
>
> --
>
>
>
> On 10 November 2015 at 15:08, Tzu-Mainn Chen < 
> tzuma...@redhat.com> wrote:
>
>> Hi all,
>>
>> At the last IRC meeting it was agreed that the new TripleO REST API
>> should forgo the Tuskar name, and simply be called... the TripleO
>> API.  There's one more point of discussion: where should the API
>> live?  There are two possibilities:
>>
>> a) Put it in tripleo-common, where the business logic lives.  If we
>> do this, it would make sense to rename tripleo-common to simply
>> tripleo.
>>
>
> +1 - I think this makes most sense if we are not going to support the
> tripleo repo as a library.
>
>
> Okay, this seems to be the consensus, which is great.
>
> The leftover question is how to package the renamed repo.  'tripleo' is
> already intuitively in use by tripleo-incubator.
> In IRC, bnemec and trown suggested splitting the renamed repo into two
> packages - 'python-tripleo' and 'tripleo-api',
> which seems sensible to me.
>
> What do others think?
>
>
>
> I have started the process of renaming the repo with these patches:
> https://review.openstack.org/#/c/247834/
> https://review.gerrithub.io/#/c/252864/
>
> Jan made an interesting suggestion that it may be easier to create a new
> repo named tripleo and move the tripleo-common code there. With renaming,
> I'm already see some complications with the tripleo-common package builds
> failing in the CI until updated spec is merged.
>
> What do folks think about this? I am unsure which is more complicated,
> creating a new repo and all the setup that goes with it. Or renaming the
> existing repo and fixing CI issues along the way.
>

I'm not sure which is easier or better, but if we do create a new repo we
need to make sure we carry over the git history.


>
> - Richard
>
>
> b) Put it in its own repo, tripleo-api
>>
>>
>> The first option made a lot of sense to people on IRC, as the proposed
>> API is a very thin layer that's bound closely to the code in tripleo-
>> common.  The major objection is that renaming is not trivial; however
>> it was mentioned that renaming might not be *too* bad... as long as
>> it's done sooner rather than later.
>>
>> What do people think?
>>
>>
>> Thanks,
>> Tzu-Mainn Chen
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-23 Thread Dmitry Tantsur 

On 11/17/2015 04:31 PM, Tzu-Mainn Chen wrote:






On 10 November 2015 at 15:08, Tzu-Mainn Chen > wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.


+1 - I think this makes most sense if we are not going to support
the tripleo repo as a library.


Okay, this seems to be the consensus, which is great.

The leftover question is how to package the renamed repo.  'tripleo' is
already intuitively in use by tripleo-incubator.
In IRC, bnemec and trown suggested splitting the renamed repo into two
packages - 'python-tripleo' and 'tripleo-api',
which seems sensible to me.


-1, that would be inconsistent with what other projects are doing. I 
guess tripleo-incubator will die soon, and I think only tripleo devs 
have any intuition about it. For me tripleo == instack-undercloud.




What do others think?


Mainn


b) Put it in its own repo, tripleo-api


The first option made a lot of sense to people on IRC, as the
proposed
API is a very thin layer that's bound closely to the code in
tripleo-
common.  The major objection is that renaming is not trivial;
however
it was mentioned that renaming might not be *too* bad... as long as
it's done sooner rather than later.

What do people think?


Thanks,
Tzu-Mainn Chen


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-23 Thread Dougal Matthews 
On 17 November 2015 at 15:31, Tzu-Mainn Chen  wrote:

>
> --
>
>
>
> On 10 November 2015 at 15:08, Tzu-Mainn Chen  wrote:
>
>> Hi all,
>>
>> At the last IRC meeting it was agreed that the new TripleO REST API
>> should forgo the Tuskar name, and simply be called... the TripleO
>> API.  There's one more point of discussion: where should the API
>> live?  There are two possibilities:
>>
>> a) Put it in tripleo-common, where the business logic lives.  If we
>> do this, it would make sense to rename tripleo-common to simply
>> tripleo.
>>
>
> +1 - I think this makes most sense if we are not going to support the
> tripleo repo as a library.
>
>
> Okay, this seems to be the consensus, which is great.
>
> The leftover question is how to package the renamed repo.  'tripleo' is
> already intuitively in use by tripleo-incubator.
> In IRC, bnemec and trown suggested splitting the renamed repo into two
> packages - 'python-tripleo' and 'tripleo-api',
> which seems sensible to me.
>
> What do others think?
>

Yup, that sounds good. Eventually when the CLI is untangled from
tripleo_common we wont need the python-tripleo package as it wont ever be
used as a library.


>
>
> Mainn
>
>
> b) Put it in its own repo, tripleo-api
>>
>>
>> The first option made a lot of sense to people on IRC, as the proposed
>> API is a very thin layer that's bound closely to the code in tripleo-
>> common.  The major objection is that renaming is not trivial; however
>> it was mentioned that renaming might not be *too* bad... as long as
>> it's done sooner rather than later.
>>
>> What do people think?
>>
>>
>> Thanks,
>> Tzu-Mainn Chen
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-23 Thread Richard Su 



On 11/17/2015 07:31 AM, Tzu-Mainn Chen wrote:






On 10 November 2015 at 15:08, Tzu-Mainn Chen > wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO
REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives. 
If we

do this, it would make sense to rename tripleo-common to simply
tripleo.


+1 - I think this makes most sense if we are not going to support
the tripleo repo as a library.


Okay, this seems to be the consensus, which is great.

The leftover question is how to package the renamed repo. 'tripleo' is 
already intuitively in use by tripleo-incubator.
In IRC, bnemec and trown suggested splitting the renamed repo into two 
packages - 'python-tripleo' and 'tripleo-api',

which seems sensible to me.

What do others think?




I have started the process of renaming the repo with these patches:
https://review.openstack.org/#/c/247834/
https://review.gerrithub.io/#/c/252864/

Jan made an interesting suggestion that it may be easier to create a new 
repo named tripleo and move the tripleo-common code there. With 
renaming, I'm already see some complications with the tripleo-common 
package builds failing in the CI until updated spec is merged.


What do folks think about this? I am unsure which is more complicated, 
creating a new repo and all the setup that goes with it. Or renaming the 
existing repo and fixing CI issues along the way.


- Richard



b) Put it in its own repo, tripleo-api


The first option made a lot of sense to people on IRC, as the
proposed
API is a very thin layer that's bound closely to the code in
tripleo-
common.  The major objection is that renaming is not trivial;
however
it was mentioned that renaming might not be *too* bad... as
long as
it's done sooner rather than later.

What do people think?


Thanks,
Tzu-Mainn Chen


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-17 Thread Dougal Matthews 
On 10 November 2015 at 15:08, Tzu-Mainn Chen  wrote:

> Hi all,
>
> At the last IRC meeting it was agreed that the new TripleO REST API
> should forgo the Tuskar name, and simply be called... the TripleO
> API.  There's one more point of discussion: where should the API
> live?  There are two possibilities:
>
> a) Put it in tripleo-common, where the business logic lives.  If we
> do this, it would make sense to rename tripleo-common to simply
> tripleo.
>

+1 - I think this makes most sense if we are not going to support the
tripleo repo as a library.



> b) Put it in its own repo, tripleo-api
>
>
> The first option made a lot of sense to people on IRC, as the proposed
> API is a very thin layer that's bound closely to the code in tripleo-
> common.  The major objection is that renaming is not trivial; however
> it was mentioned that renaming might not be *too* bad... as long as
> it's done sooner rather than later.
>
> What do people think?
>
>
> Thanks,
> Tzu-Mainn Chen
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-17 Thread Tzu-Mainn Chen 
- Original Message -

> On 10 November 2015 at 15:08, Tzu-Mainn Chen < tzuma...@redhat.com > wrote:

> > Hi all,
> 

> > At the last IRC meeting it was agreed that the new TripleO REST API
> 
> > should forgo the Tuskar name, and simply be called... the TripleO
> 
> > API. There's one more point of discussion: where should the API
> 
> > live? There are two possibilities:
> 

> > a) Put it in tripleo-common, where the business logic lives. If we
> 
> > do this, it would make sense to rename tripleo-common to simply
> 
> > tripleo.
> 

> +1 - I think this makes most sense if we are not going to support the tripleo
> repo as a library.

Okay, this seems to be the consensus, which is great. 

The leftover question is how to package the renamed repo. 'tripleo' is already 
intuitively in use by tripleo-incubator. 
In IRC, bnemec and trown suggested splitting the renamed repo into two packages 
- 'python-tripleo' and 'tripleo-api', 
which seems sensible to me. 

What do others think? 

Mainn 

> > b) Put it in its own repo, tripleo-api
> 

> > The first option made a lot of sense to people on IRC, as the proposed
> 
> > API is a very thin layer that's bound closely to the code in tripleo-
> 
> > common. The major objection is that renaming is not trivial; however
> 
> > it was mentioned that renaming might not be *too* bad... as long as
> 
> > it's done sooner rather than later.
> 

> > What do people think?
> 

> > Thanks,
> 
> > Tzu-Mainn Chen
> 

> > __
> 
> > OpenStack Development Mailing List (not for usage questions)
> 
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-17 Thread Dougal Matthews 
On 10 November 2015 at 16:12, Giulio Fidente  wrote:

> On 11/10/2015 04:47 PM, Dmitry Tantsur wrote:
>
>> On 11/10/2015 04:37 PM, Giulio Fidente wrote:
>>
>>> On 11/10/2015 04:16 PM, Dmitry Tantsur wrote:
>>>
 On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:

> Hi all,
>
> At the last IRC meeting it was agreed that the new TripleO REST API
> should forgo the Tuskar name, and simply be called... the TripleO
> API.  There's one more point of discussion: where should the API
> live?  There are two possibilities:
>
> a) Put it in tripleo-common, where the business logic lives.  If we
> do this, it would make sense to rename tripleo-common to simply
> tripleo.
>

 +1 for both


> b) Put it in its own repo, tripleo-api
>

>>> if both the api (coming) and the cli (currently python-tripleoclient)
>>> are meant to consume the shared code (business logic) from
>>> tripleo-common, then I think it makes sense to keep each in its own repo
>>> ... so that we avoid renaming tripleo-common as well
>>>
>>
>> tripleoclient should not consume tripleo-common
>>
>
> so FWIW I think my vote is different depending on the plans:
>
> a. if python-tripleoclient will be changed so that it uses tripleo-api,
> then I'd vote for option 1) (have tripleo-api in -common and rename)
>

I think this is what we want. Supporting both a Python API and REST API
adds a ton of extra work. It will take some time to transition the CLI
over, but I think it is worth it.



> b. if python-tripleoclient will be changed so that it uses the shared
> library in -common, then I'd vote for for option 2) (have tripleo-api in
> its own repo)
>
>
> on a side note, I think it should always be possible for the deployer to
> skip any business logic to give complete control over the template params
> for both the initial deployments and the updates
> --
> Giulio Fidente
> GPG KEY: 08D733BA | IRC: giulivo
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-16 Thread Jay Dobies 



On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.


+1

If the exercise is to move the logic behind an API, let's not have two 
avenues into that logic.



b) Put it in its own repo, tripleo-api


The first option made a lot of sense to people on IRC, as the proposed
API is a very thin layer that's bound closely to the code in tripleo-
common.  The major objection is that renaming is not trivial; however
it was mentioned that renaming might not be *too* bad... as long as
it's done sooner rather than later.

What do people think?


Thanks,
Tzu-Mainn Chen

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread Dmitry Tantsur 

On 11/10/2015 04:37 PM, Giulio Fidente wrote:

On 11/10/2015 04:16 PM, Dmitry Tantsur wrote:

On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.


+1 for both



b) Put it in its own repo, tripleo-api


if both the api (coming) and the cli (currently python-tripleoclient)
are meant to consume the shared code (business logic) from
tripleo-common, then I think it makes sense to keep each in its own repo
... so that we avoid renaming tripleo-common as well


tripleoclient should not consume tripleo-common or have any business 
logic. otherwise it undermines the whole goal of having API, as we'll 
have to reproduce the same logic on GUI.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread John Trowbridge 


On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote:
> Hi all,
> 
> At the last IRC meeting it was agreed that the new TripleO REST API
> should forgo the Tuskar name, and simply be called... the TripleO
> API.  There's one more point of discussion: where should the API
> live?  There are two possibilities:
> 
> a) Put it in tripleo-common, where the business logic lives.  If we
> do this, it would make sense to rename tripleo-common to simply
> tripleo.

This option makes the most sense to me now that I understand the
tripleoclient will also consume the REST API and not the underlying
python library with the "business logic".

>From a packaging point of view, I think this is pretty painless. I think
we would have a "python-tripleo" package for the library that
provides/obsoletes the current tripleo-common package. As well as a
"tripleo-api" package for the REST API service. We would not need to
touch the tripleo-incubator package that currently is named just "tripleo".

> 
> b) Put it in its own repo, tripleo-api
> 
> 
> The first option made a lot of sense to people on IRC, as the proposed
> API is a very thin layer that's bound closely to the code in tripleo-
> common.  The major objection is that renaming is not trivial; however
> it was mentioned that renaming might not be *too* bad... as long as
> it's done sooner rather than later.
> 
> What do people think?
> 
> 
> Thanks,
> Tzu-Mainn Chen
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread Giulio Fidente 

On 11/10/2015 04:47 PM, Dmitry Tantsur wrote:

On 11/10/2015 04:37 PM, Giulio Fidente wrote:

On 11/10/2015 04:16 PM, Dmitry Tantsur wrote:

On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.


+1 for both



b) Put it in its own repo, tripleo-api


if both the api (coming) and the cli (currently python-tripleoclient)
are meant to consume the shared code (business logic) from
tripleo-common, then I think it makes sense to keep each in its own repo
... so that we avoid renaming tripleo-common as well


tripleoclient should not consume tripleo-common


so FWIW I think my vote is different depending on the plans:

a. if python-tripleoclient will be changed so that it uses tripleo-api, 
then I'd vote for option 1) (have tripleo-api in -common and rename)


b. if python-tripleoclient will be changed so that it uses the shared 
library in -common, then I'd vote for for option 2) (have tripleo-api in 
its own repo)



on a side note, I think it should always be possible for the deployer to 
skip any business logic to give complete control over the template 
params for both the initial deployments and the updates

--
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread Tzu-Mainn Chen 
Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.

b) Put it in its own repo, tripleo-api


The first option made a lot of sense to people on IRC, as the proposed
API is a very thin layer that's bound closely to the code in tripleo-
common.  The major objection is that renaming is not trivial; however
it was mentioned that renaming might not be *too* bad... as long as
it's done sooner rather than later.

What do people think?


Thanks,
Tzu-Mainn Chen

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread Dmitry Tantsur 

On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.


+1 for both



b) Put it in its own repo, tripleo-api


The first option made a lot of sense to people on IRC, as the proposed
API is a very thin layer that's bound closely to the code in tripleo-
common.  The major objection is that renaming is not trivial; however
it was mentioned that renaming might not be *too* bad... as long as
it's done sooner rather than later.


Renaming is bad when there are strong backward compatibility guarantees. 
I'm not sure if it's the case for tripleo-common.




What do people think?


Thanks,
Tzu-Mainn Chen

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread Giulio Fidente 

On 11/10/2015 04:16 PM, Dmitry Tantsur wrote:

On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:

Hi all,

At the last IRC meeting it was agreed that the new TripleO REST API
should forgo the Tuskar name, and simply be called... the TripleO
API.  There's one more point of discussion: where should the API
live?  There are two possibilities:

a) Put it in tripleo-common, where the business logic lives.  If we
do this, it would make sense to rename tripleo-common to simply
tripleo.


+1 for both



b) Put it in its own repo, tripleo-api


if both the api (coming) and the cli (currently python-tripleoclient) 
are meant to consume the shared code (business logic) from 
tripleo-common, then I think it makes sense to keep each in its own repo 
... so that we avoid renaming tripleo-common as well

--
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Location of TripleO REST API

2015-11-10 Thread John Trowbridge 


On 11/10/2015 10:37 AM, Giulio Fidente wrote:
> On 11/10/2015 04:16 PM, Dmitry Tantsur wrote:
>> On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:
>>> Hi all,
>>>
>>> At the last IRC meeting it was agreed that the new TripleO REST API
>>> should forgo the Tuskar name, and simply be called... the TripleO
>>> API.  There's one more point of discussion: where should the API
>>> live?  There are two possibilities:
>>>
>>> a) Put it in tripleo-common, where the business logic lives.  If we
>>> do this, it would make sense to rename tripleo-common to simply
>>> tripleo.
>>
>> +1 for both
>>
>>>
>>> b) Put it in its own repo, tripleo-api
> 
> if both the api (coming) and the cli (currently python-tripleoclient)
> are meant to consume the shared code (business logic) from
> tripleo-common, then I think it makes sense to keep each in its own repo
> ... so that we avoid renaming tripleo-common as well

I generally agree with this logic... it is a bit weird to have one
consumer of the shared code in tree, while the other is out of tree.
That said, I am ok with wherever we put the api and whatever we call it
so long as we do it soon and commit to not changing it once decided.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev