On 05/21/2015 08:42 PM, Spencer Krum wrote:
How did we get here?
For a long time there were two place to put configuration: the <thing>
module, or the openstack_project::<thing> class. Both of these were in the
same repository and it didn't much matter to anyone where configuration
went.
In my mind we should move everything we responsibly can into the modules
themselves. That greatly reduces the volume of code in openstackci and
openstack_project. Such refactors across repos does break the utility of
tools like git-bisect, but the history is still preserved in system-config
and someone who knows our history can find that easily.
My point was not keep things in system-config, it was move them into
openstackci namespace inside system-config to preserve the history.
Then, once you are happy openstackci is working like you want, then move
it into the external module.
project-config and system-config, we kept the history for each until
they diverged. Now, puppet-openstackci has 10 commits.
On Thu, May 21, 2015 at 8:31 PM, Paul Belanger <pabelan...@redhat.com>
wrote:
Preface, Ramy I'm happy you are leading the effort and sorry for being so
confused when we talked today.
On to my email,
So, I had a chance to attend (pretty late honestly) to the
puppet-openstackci working group. And have to admit, I was pretty surprise
to see how the break out of the puppet module was happening.
I know the ship has sailed, but I feel it is a shame we are basically
losing the git commit history of the system-config repo in this process.
To be honest, I don't know the motivation around _not_ preserving the
history however, I do see a path available to do this:
system-config/
modules/
openstack_project/
openstackci/
Creating, top level openstackci, for the purpose of the migration. Then,
once the core requirements of the break has happened, extra the data out
(like we did with system-config / project-config) into its own
puppet-openstackci.
Again, it is not the only way to do it, but does preserve the git history.
I don't want to stop the process, because I think it is important, but
want to stress (for me) the lack of git history will make it harder for me
to consume as a 3rd party operator. Well, maybe stop the process, since we
can revert some changes :)
Hit me up on Friday summit day if you want to smack me around.
_______________________________________________
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
_______________________________________________
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra