Change Details

Services is currently handling most of the administrative tasks around the RESTBase cassandra cluster. In that capacity, we often need to tweak the cassandra submodule. Currently the development process for these changes is less than ideal, as each change requires two +2s from ops, one for the submodule change & one for the submodule update. The other issue is that we can't use the puppet compiler to check changes until a change is merged in the submodule. @eevans created a patch to eliminate the submodule at https://gerrit.wikimedia.org/r/#/c/196335/, but this met resistance from Andrew because it would complicate the reuse of this submodule in Vagrant. Instead, we I think we should consider granting +2 rights on the cassandra submodule to services members (@eevans, @mobrovac, myself). This would eliminate the second ops review, and we can test merged changes in the submodule with the puppet compiler before asking for +2 for the submodule update in puppet proper.

Services is currently handling most of the administrative tasks around the RESTBase cassandra cluster. In that capacity, we often need to tweak the cassandra submodule. Currently the development process for these changes is less than ideal, as each change requires two +2s from ops, one for the puppet/cassandra repository change & one for the submodule update. The other issue is that we can't use the puppet compiler to check changes until a change is merged in the submodule. @eevans created a patch to eliminate the submodule at https://gerrit.wikimedia.org/r/#/c/196335/, but this met resistance from Andrew because it would complicate the reuse of this submodule in Vagrant. Instead, we I think we should consider granting +2 rights on the cassandra submodule to services members (@eevans, @mobrovac, myself). This would eliminate the second ops review, and we can test merged changes in the submodule with the puppet compiler before asking for +2 for the submodule update in puppet proper.

Services is currently handling most of the administrative tasks around the RESTBase cassandra cluster. In that capacity, we often need to tweak the cassandra submodule. Currently the development process for these changes is less than ideal, as each change requires two +2s from ops, one for the submodulepuppet/cassandra repository change & one for the submodule update. The other issue is that we can't use the puppet compiler to check changes until a change is merged in the submodule. @eevans created a patch to eliminate the submodule at https://gerrit.wikimedia.org/r/#/c/196335/, but this met resistance from Andrew because it would complicate the reuse of this submodule in Vagrant. Instead, we I think we should consider granting +2 rights on the cassandra submodule to services members (@eevans, @mobrovac, myself). This would eliminate the second ops review, and we can test merged changes in the submodule with the puppet compiler before asking for +2 for the submodule update in puppet proper.