Re: [openstack-dev] [Murano] Repositoris re-organization

2014-02-18 Thread Sergey Lukjanov
Ruslan, I'm absolutely agree with you, only one correction, I think murano-guestagent will better fit the repo content. Thanks. On Tue, Feb 18, 2014 at 7:23 PM, Alexander Tivelkov wrote: > Hi Ruslan, > > Thanks for your feedback. I completely agree with these arguments: > actually, these were

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-02-18 Thread Alexander Tivelkov
Hi Ruslan, Thanks for your feedback. I completely agree with these arguments: actually, these were the reasons why I've initiated this discussion. Team, let's discuss this on the IRC meeting today. -- Regards, Alexander Tivelkov On Tue, Feb 18, 2014 at 5:55 PM, Ruslan Kamaldinov wrote: > I'd

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-02-18 Thread Ruslan Kamaldinov
I'd suggest to reduce number of Murano repositories for several reasons: * All other OpenStack projects have a single repo per project. While this point might look like something not worth mentioning, it's really important: - unified project structure simplifies life for new developers. once they

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-02-06 Thread Serg Melikyan
Hi, Alexander, In general I am completely agree with Clint and Robert, and as one of contributors of Murano I don't see any practical reasons for repositories reorganization. And regarding of your proposal I have a few thoughts that I would like to share below: >This enourmous amount of repositor

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-01-24 Thread Alexander Tivelkov
Clint, Rob, Thanks a lot for your input: that's really a good point, and we didn't consider it before, while we definitely should. Team, Let's discuss this topic again before making any final decisions. -- Regards, Alexander Tivelkov 2014/1/24 Robert Collins > On 24 January 2014 22:26, Clin

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-01-24 Thread Robert Collins
On 24 January 2014 22:26, Clint Byrum wrote: >> This enourmous amount of repositories adds too much infrustructural >> complexity, and maintaining the changes in in consistent and reliable >> manner becomes a really tricky tasks. We often have changes which require >> modifing two or more reposit

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-01-24 Thread Clint Byrum
Excerpts from Alexander Tivelkov's message of 2014-01-21 11:55:34 -0800: > Hi folks, > > As we are moving towards incubation application, I took a closer look at > what is going on with our repositories. > An here is what I found. We currently have 11 repositories at stackforge: > >- murano-a

Re: [openstack-dev] [Murano] Repositoris re-organization

2014-01-23 Thread Renat Akhmerov
On 21 Jan 2014, at 11:55, Alexander Tivelkov wrote: > > murano - main services, common, agents docs, deployments scripts > python-muranoclient - python bindings and CLI > murano-dashboard - OS Dashboard plugin > murano-apps - new repo for metadata, including core library and example apps. > mur

[openstack-dev] [Murano] Repositoris re-organization

2014-01-21 Thread Alexander Tivelkov
Hi folks, As we are moving towards incubation application, I took a closer look at what is going on with our repositories. An here is what I found. We currently have 11 repositories at stackforge: - murano-api - murano-conductor - murano-repository - murano-dashboard - murano-commo