We really should get the ruby version up to 2.x for the deployed nodes (Ubuntu and CentOS) as it will save ~30% of the run time according to the tests I ran on fuel 3.0.1 (ya a while ago now and i was testing moving to 1.9.3), then the only issue I had then was some issues with array to_s usage in l23networks.
On Fri, Apr 4, 2014 at 5:59 AM, Andrey Danin <[email protected]> wrote: > I'm doing the fastest solution right now. But we can discuss the best way > in this thread. > > > On Fri, Apr 4, 2014 at 3:22 PM, Mike Scherbakov > <[email protected]>wrote: > >> Folks, I'm for the fastest solution for now - and simultaneously creating >> bug in LP in High priority to address it properly afterwards. >> >> We really need to speed this up, as many things depend on this.. >> >> Thanks, >> >> >> On Fri, Apr 4, 2014 at 3:20 PM, Vladimir Sharshov <[email protected] >> > wrote: >> >>> Hi all! >>> >>> As many of you know we decide to move from Ruby 1.8.7 and 1.9.3 in >>> master node to Ruby 2.1 as system ruby. Also we convert all gems to >>> packages (required for docker). >>> >>> But we have a problem with make iso process, which do not expect such a >>> variance of build process with 2 versions of Ruby: 1.8.7 and 2.1 in centos >>> mirror, because yum by default try to install newest version. >>> >>> From yesterday discussion with OSCI (Sergey, Dmitry) and Andrey Danin we >>> have 3 way to solve it: >>> >>> - exclude using yum installation of new ruby in make process for >>> bootstrap process and also block it for CentOS provisioned nodes: >>> - change yum calls in make scripts ( >>> http://paste.openstack.org/show/75007/); >>> - use separate local package repository for new ruby and included >>> it when run boostrap_admin_node.sh; >>> - remove from package ruby 2.1 provider(ruby). >>> - use new ruby(2.1) for master node and bootstrap centos images. >>> Block Ruby for CentOS provisioned nodes: >>> - change kickstart profile to select special version of >>> ruby(1.8.7). >>> - use 2.1 as system Ruby for master node and provisioned nodes(both >>> for CentOS and Ubuntu) (need to fix compatibility with openstack puppet >>> recipes) >>> >>> Which way we should choose? >>> >>> Additional links: >>> >>> - https://review.openstack.org/#/c/82045/ (in progress); >>> - >>> >>> https://github.com/warpc/fuel-main/commit/fde8ca23cb5881de0b5afa8173ae113d0926dafd(in >>> progress); >>> - http://paste.openstack.org/show/75007/ >>> >>> >>> -- >>> Mailing list: https://launchpad.net/~fuel-dev >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~fuel-dev >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >> >> -- >> Mike Scherbakov >> #mihgen >> >> -- >> Mailing list: https://launchpad.net/~fuel-dev >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~fuel-dev >> More help : https://help.launchpad.net/ListHelp >> >> > > > -- > Andrey Danin > [email protected] > skype: gcon.monolake > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > > -- Andrew Mirantis Ceph community
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
