Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-05-29

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:05 IlyaE joined #fuel
00:22 ilbot3 joined #fuel
00:22 Topic for #fuel is now Fuel 4.1 for Openstack: http://fuel.mirantis.com/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
00:47 thehybridtech joined #fuel
01:21 rmoe joined #fuel
01:49 crandquist joined #fuel
01:53 gleam my understanding is all you get with 5.0 is the ability to upgrade the fuel node itself. you would be able to upgrade the fuel node from 5.0 to 5.1 but actually upgrading a running openstack environment isn't possible w/5.0
01:54 gleam https://blueprints.launchpad.net/fuel/+spec/upgrade-major-openstack-environment
03:05 IlyaE joined #fuel
03:44 dmit2k gleam: this is what I was talking about
03:45 dmit2k pretty funny
03:47 dmit2k so as I can understand, FUEL is a kind of temporary solution when you need to take a brief view on OpenStack or to promote it to someone
03:50 dmit2k by this logic the lifecycle is a year or so, then you have to migrate all your VM's manually to a more up-to-date solution, with all the environment
03:50 dmit2k DISAPPOINTED
04:03 xarses joined #fuel
05:27 IlyaE joined #fuel
06:28 al_ex joined #fuel
07:03 artem_panchenko joined #fuel
07:26 bogdando joined #fuel
08:12 e0ne joined #fuel
08:59 vgonzal joined #fuel
08:59 vgonzal Hi
09:13 tatyana joined #fuel
09:21 e0ne joined #fuel
10:20 AndreyDanin joined #fuel
10:34 e0ne joined #fuel
11:02 e0ne joined #fuel
12:56 themistymay joined #fuel
13:08 e0ne_ joined #fuel
13:16 jaypipes joined #fuel
13:33 casanch1 joined #fuel
13:42 adidenko joined #fuel
13:55 IlyaE joined #fuel
13:57 tatyana_ joined #fuel
14:43 tatyana_ joined #fuel
14:46 alex_didenko joined #fuel
15:35 alex_didenko joined #fuel
15:43 b-zone joined #fuel
15:44 vkozhukalov joined #fuel
15:44 blahRus joined #fuel
15:44 vkozhukalov left #fuel
15:50 vkozhukalov joined #fuel
15:58 vkozhukalov left #fuel
16:14 angdraug joined #fuel
16:15 rmoe joined #fuel
16:16 rmoe joined #fuel
16:25 xarses joined #fuel
16:31 e0ne joined #fuel
16:37 themistymay joined #fuel
16:56 themistymay joined #fuel
17:10 angdraug joined #fuel
17:12 xarses_ joined #fuel
17:22 IlyaE joined #fuel
17:44 vogelc joined #fuel
17:46 vogelc Looking for help with Fuel 5.0.  I can pxe boot physical nodes just fine in Fuel 4.1,  when we migrated to 5.0 the dhcp requests never make it back to the client.
18:04 derrickb joined #fuel
18:06 MiroslavAnashkin vogelc: Yes, it is known issue. http://docs.mirantis.com/fuel/fuel-5.0/release-notes.html#bootstrap-kernel-issues-on-certain-hardware
18:06 derrickb joined #fuel
18:07 MiroslavAnashkin How to use workaround (online docs will be also updated soon):
18:07 MiroslavAnashkin Download kernel-2.6 based bootstrap filed from
18:07 MiroslavAnashkin http://9f2b43d3ab92f886c3f0-e8d43ffad23ec549234584e5c62a6e24.r60.cf1.rackcdn.com/bootstrap-5.0-kernel-2.6.zip
18:07 MiroslavAnashkin Copy the downloaded zip archive to the Fuel master node
18:07 MiroslavAnashkin scp bootstrap-5.0-kernel-2.6.zip root@10.20.0.2:/root/
18:07 MiroslavAnashkin Log in to Fuel master node and run the following commands to install new bootstrap:
18:07 MiroslavAnashkin cd /root/
18:07 MiroslavAnashkin yum -y install unzip
18:07 MiroslavAnashkin unzip bootstrap-5.0-kernel-2.6.zip
18:07 MiroslavAnashkin cp -b linux /var/www/nailgun/bootstrap/
18:07 MiroslavAnashkin chmod +x /var/www/nailgun/bootstrap/linux
18:07 MiroslavAnashkin chmod -w /var/www/nailgun/bootstrap/linux
18:07 MiroslavAnashkin cp -b initramfs.img /var/www/nailgun/bootstrap/
18:07 MiroslavAnashkin cobbler sync
18:07 MiroslavAnashkin Existing bootstrap files will be renamed to linux~ and initramfs.img~.
18:07 MiroslavAnashkin To apply changes to already bootstrapped nodes, simply reboot the
18:07 MiroslavAnashkin affected nodes to boot with the 2.6 kernel.
18:08 derrickb I just jumped in late..  is this a workround for the BNX drivers in 5.0?
18:08 MiroslavAnashkin Yes, if BNX drivers worked in 4.x
18:09 derrickb they did... I just was going back to 4.x on my test environment... going to apply this patch and try again! :) Thanks!
18:10 thehybridtech joined #fuel
18:21 vogelc Actually - we updated the initramfs and yes that did fix the firmware issue with the broadcom nics.  This is more about dhcp response getting picked up by the hosts.
18:21 vogelc I have 13 hosts,  6 work just fine and 7 dont.  If I reinstall fuel 4.1 all 13 with recieve DHCP and pxe boot the the boot strap image.
18:37 IlyaE joined #fuel
18:39 derrickb BNX controllers did come up....
18:40 ogelbukh hi
18:40 ogelbukh small question: which is the standard port for fuel api to listen on?
18:42 MiroslavAnashkin :8000/api/
18:42 ogelbukh MiroslavAnashkin: thanks
18:43 MiroslavAnashkin vogelc: Looks similar to this bug, while the bug was reported against the network verification failure only. https://bugs.launchpad.net/fuel/+bug/1306705
18:44 IlyaE joined #fuel
18:47 rmoe joined #fuel
18:51 IlyaE joined #fuel
19:07 e0ne joined #fuel
19:46 xarses joined #fuel
19:49 Arminder joined #fuel
20:18 IlyaE joined #fuel
20:58 rmoe joined #fuel
20:59 xarses joined #fuel
21:06 angdraug joined #fuel
21:11 xarses joined #fuel
21:11 rmoe joined #fuel
21:58 IlyaE joined #fuel
22:03 angdraug joined #fuel
22:18 IlyaE joined #fuel
22:38 xarses joined #fuel
22:54 IlyaE joined #fuel
23:05 crandquist joined #fuel

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary