Do we have a plan to enable CI for this repositories? Tests to run on commits, nightly builds, integration with nightly system tests? Should it be part of Fuel CI or completely independent? On Thu, Jan 29, 2015 at 11:55 AM, Alexander Kislitsky <akislitsky at mirantis.com> wrote: > Hi, guys > > All our plugins repositories are moved to stackforge. Each plugin has > separate repo and now can be maintained independently from core product > cycle and without core-team attraction. > > Here is a map of migration: > > https://github.com/stackforge/fuel-plugins/tree/master/external_glusterfs -> > https://github.com/stackforge/fuel-plugin-external-glusterfs > > https://github.com/stackforge/fuel-plugins/tree/master/external_nfs -> > https://github.com/stackforge/fuel-plugin-external-nfs > > https://github.com/stackforge/fuel-plugins/tree/master/ha_fencing -> > https://github.com/stackforge/fuel-plugin-ha-fencing > > https://github.com/stackforge/fuel-plugins/tree/master/lbaas -> > https://github.com/stackforge/fuel-plugin-neutron-lbaas > > https://github.com/Mirantis/fuel-plugins/tree/master/cinder_netapp -> > https://github.com/stackforge/fuel-plugin-cinder-netapp > > https://github.com/Mirantis/fuel-plugins/tree/master/vpnaas -> > https://github.com/stackforge/fuel-plugin-neutron-vpnaas > > > Now external_glusterfs, external_nfs, ha_fencing, lbaas can be removed from > the https://github.com/stackforge/fuel-plugins: > https://review.openstack.org/#/c/151143/ > > Repository https://github.com/Mirantis/fuel-plugins/ is not required and can > be removed or made private. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Aleksandra Fedorova Fuel Devops Engineer bookwar