Hi Fuelers, this is another status update. - OpenStack-CI is now running pep8 checks [1] for patches to python-fuelclient. - The script for running python tests in on review [2] and some guys are requested to test it and give some feedback - Fuel CI is now allowed to vote on python-fuelclient [3] so the next stage it to merge both run_test.sh [2] and Jenkins job to FuelCI [4] - It’s now planned to finish this migration on Tuesday next week, so it will be possible to build ISO from python-fuelclient repo Stay tuned. References: 1. Run pep8 jobs for python-fuelclient https://review.openstack.org/#/c/147801 <https://review.openstack.org/#/c/147801> 2. Run Python tests https://review.openstack.org/#/c/146950 <https://review.openstack.org/#/c/146950> 3. Allow FuelCI voting on python-fuelclient https://review.openstack.org/#/c/147429 <https://review.openstack.org/#/c/147429> 4. Add verify-python-fuelclient https://review.fuel-infra.org/#/c/1989 <https://review.fuel-infra.org/#/c/1989> - romcheg > 13 січ. 2015 о 15:58 Roman Prykhodchenko <me at romcheg.me> написав(ла): > > Folks, > > this is another status update. > > The patch for moving python-fuelclient to a separate project has been merged. At the moment Stackforge repository, a Gerrit project and all Gerrit groups have been created. There are two guys in the core group: I and Dmitri Pyzhov (dpyzhov at mirantis.com <mailto:dpyzhov at mirantis.com>). You can obtain the sources from https://github.com/stackforge/python-fuelclient <https://github.com/stackforge/python-fuelclient>. > I kindly ask authors of all changes to Fuel Client to start moving them to the new project. > At the moment I’m working on enabling the same testing process in FuelCI, testing in OpenStack CI will be enabled later because that requires some refactoring of the existing tests in python-fuelclient. > > Stay tuned. > > > - romcheg > >> 12 січ. 2015 о 12:44 Roman Prykhodchenko <me at romcheg.me <mailto:me at romcheg.me>> написав(ла): >> >> Hi folks! >> >> This is a status update. >> Right now the patch for creating a new project on Stackforge is blocked by a bug in Zuul [1] which is actually a bug in python-daemon, the patch for this is already published [2] and waiting for being approved. >> After the patch is merged and all projects and groups are created I will file a request to perform initial setup of core groups. Once they are created it will be possible to land new patches. >> Meanwhile OSCI team is working [3] on adjusting build system to use python-fuelclient from PyPi [4]. >> Stay tuned for further updates. >> >> References: >> Zuul’s tests fail with dependencies error https://storyboard.openstack.org/#!/story/2000107 <https://storyboard.openstack.org/#!/story/2000107> >> Pin python-daemon<2.0 https://review.openstack.org/#/c/146350/ <https://review.openstack.org/#/c/146350/> >> Create repositories for python-fuelclient package https://bugs.launchpad.net/fuel/+bug/1409673 <https://bugs.launchpad.net/fuel/+bug/1409673> >> python-fuelclient on PyPi https://pypi.python.org/pypi/python-fuelclient <https://pypi.python.org/pypi/python-fuelclient> >> >> >>> 9 січ. 2015 о 15:14 Roman Prykhodchenko <me at romcheg.me <mailto:me at romcheg.me>> написав(ла): >>> >>> Hi folks, >>> >>> according to the Fuel client refactoring plan [1] it’s necessary to move it out to a separate repository on Stackforge. >>> >>> The process of doing that consists of two major steps: >>> - Landing a patch [2] to project-config for creating a new Stackforge project >>> - Creating an initial core group for python-fuelclient >>> - Moving all un-merged patches from fuel-web to python-fuelclient gerrit repo >>> >>> The first step of this process has already been started so I kindly ask all fuelers to DO NOT MERGE any new patches to fuel-web IF THEY DO touch fuelclient folder. >>> After the project is set up I will let everyone know about that and will tell what to do after that so I encourage all interested people to check this thread once in a while. >>> >>> >>> # References: >>> >>> 1. Re-thinking Fuel Client https://review.openstack.org/#/c/145843 <https://review.openstack.org/#/c/145843> >>> 2. Add python-fuelclient to Stackforge https://review.openstack.org/#/c/145843 <https://review.openstack.org/#/c/145843> >>> >>> >>> - romcheg >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: OpenStack-dev-request at lists.openstack.org <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > __________________________________________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150116/12a6044f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150116/12a6044f/attachment.pgp>