Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-06-09

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

All times shown according to UTC.

Time Nick Message
06:12 designated joined #fuel
06:25 al_ex joined #fuel
06:47 vkozhukalov joined #fuel
07:16 e0ne joined #fuel
07:16 sbog joined #fuel
07:39 sbog joined #fuel
07:42 sbog joined #fuel
08:02 sbog joined #fuel
08:11 ykotko joined #fuel
08:24 mattymo joined #fuel
08:26 mattymo joined #fuel
08:31 mattymo joined #fuel
08:42 mattymo joined #fuel
08:52 mattymo joined #fuel
08:52 aedocw joined #fuel
08:54 mattymo joined #fuel
08:56 mattymo joined #fuel
08:58 mattymo joined #fuel
09:00 mattymo joined #fuel
09:02 mattymo joined #fuel
09:04 mattymo joined #fuel
09:06 mattymo joined #fuel
09:14 mattymo joined #fuel
09:15 odyssey4me joined #fuel
09:18 taj joined #fuel
09:19 mattymo joined #fuel
09:23 AndreyDanin joined #fuel
09:55 e0ne joined #fuel
11:00 e0ne joined #fuel
11:06 e0ne joined #fuel
11:40 lromagnoli joined #fuel
12:11 lromagnoli hallo my company is going to test fuel solution, i see on running mirantis openstack on virtualbox that script are tested on Ubuntu 12.10 there will some know problem if i use ubuntu 14.4 I'm starting developing test solution now
12:11 lromagnoli so i can choose the right testing solution, which one u suggest?
12:38 book` joined #fuel
12:57 jp joined #fuel
13:02 evg lromagnoli: hi, it should work well on 14.4.
13:04 evg lromagnoli: btw, what is vbox's version in 14.4?
13:19 jaypipes joined #fuel
13:28 jaypipes joined #fuel
13:35 jaypipes joined #fuel
13:37 lromagnoli evg I will tell u on 30 minutes becouse i'm deploing now 14.4
13:38 jaypipes joined #fuel
13:45 evg lromagnoli: don't worry
13:46 jaypipes joined #fuel
13:46 melodous_away joined #fuel
13:49 jaypipes joined #fuel
13:51 e0ne joined #fuel
13:52 georgem2 joined #fuel
14:16 lromagnoli evg: virtualbox Version: 4.3.10-dfsg-1
14:22 georgem2 I'm trying Fuel 5.0 in VMWare and the VM nodes are not discovered by Fuel; my Fuel-master has two vNICs connected, one to Fuel-Admin net and one to my lab network; the nodes have vNICs connected to Fuel-Admin, Fuel-mgnt, Fuel-private, Fuel-storage and Fuel-public; I was expected the nodes to get a DHCP from the Fuel-admin network when PXE booting, but no luck
14:24 georgem2 I installed Fuel-master from the ISO giving it a static address in the lab network, any idea what should I check or do different to get it working?
14:35 evg lromagnoli: thanks
14:38 MiroslavAnashkin georgem2: Do you use Workstation/Player or vCenter/ESXi?
14:39 georgem2 MiroslavAnashkin:ESXi
14:40 MiroslavAnashkin OK, one more question - with or without vSwitch?
14:41 georgem2 MiroslavAnashkin:ESXi uses their own vswitch, in my case I created one where all Fuel networks connect and it has to uplink ports, it's internal to the ESXi host only
14:41 georgem2 MiroslavAnashkin:it has NO uplink ports
14:42 MiroslavAnashkin georgem2: Then, most of the settings questions are addressed here: http://vbyron.com/blog/deploy-openstack-on-vsphere-with-fuel/
14:44 MiroslavAnashkin 5.0 has additional option - to select vCenter as hypervisor. Please consult the docs on it first, http://docs.mirantis.com/fuel/fuel-5.0/user-guide.html#hypervisor
14:45 georgem2 MiroslavAnashkin:thanks, I'll take a look at that blog
14:47 MiroslavAnashkin And general VMWare tips:
14:47 MiroslavAnashkin 1. Use 'vlance' network card if possible. e1000 works in selected VMware versions (mostly enterprise ones) and may not work with others.
14:47 MiroslavAnashkin You may open .VMX file of your machine (OK, all machines) and check the following string for each network adapter:
14:47 MiroslavAnashkin `ethernetXXX.virtualDev = "vlance"`.
14:47 MiroslavAnashkin If there is no vlance (old AMD) support in your distribution - use e1000.
14:47 MiroslavAnashkin 2. Allow promiscuous mode for each network card. Again, check VMX file of your VM, the following string:
14:47 MiroslavAnashkin `ethernetXXX.noPromisc = "false"`
14:47 MiroslavAnashkin 3. Check you network card PXE boot is not turned off  (affects all cards that use selected driver and should be on by default).
14:47 MiroslavAnashkin `vlance.noOprom = "false"`
14:47 MiroslavAnashkin 4. In case you use ESXi/vSphere with vSwitch as networking solution:
14:47 MiroslavAnashkin Create separate port group or even separate vSwitch instance with port group for each virtual network.
14:47 MiroslavAnashkin Allow promiscuous mode for each port group.
14:47 MiroslavAnashkin Please note: some kinds of multicast/broadcast traffic does not go outside the port group, so always use port groups for Neutron.
14:47 MiroslavAnashkin vSwitch does not support Native VLAN for Trunk ports and removes all VLAN tags from traffic, going through Access ports. So you cannot mix VLAN tagged and untagged traffic and have to create different port groups for Trunk and Access ports.
14:52 georgem2 MiroslavAnashkin: I had a similar setup working last week and I deployed using Centos, now I was trying Ubuntu; the difference is that last week my Fuel-master had interfaces on all Fuel networks (Public, private, storage, admin and mgnt) but the nodes' interfaces were re-ordered during discoveryl this time I'm trying to deploy on Ubuntu and with Fuel-master connected only to the the fuel-admin network where PXE and DHCP should be provided
14:53 e0ne joined #fuel
14:56 rongze joined #fuel
15:04 angdraug joined #fuel
15:21 jaypipes joined #fuel
15:46 Protux joined #fuel
15:54 e0ne joined #fuel
16:30 albionandrew joined #fuel
16:34 jobewan joined #fuel
16:40 albionandrew On Fuel 4.1 I have /dev/mapper/image-glance showing 100% on a controller - We use glance with Ceph and there is space on the 2 ceph nodes. How should I resolve?
16:42 blahRus joined #fuel
16:46 albionandrew MiroslavAnashkin: ^ On our cluster in production.
16:47 rmoe joined #fuel
16:51 vkozhukalov joined #fuel
16:57 MiroslavAnashkin albionandrew: Do you mean volume has no free space or it does not point to Ceph?
16:57 MiroslavAnashkin Please also check this bug https://bugs.launchpad.net/fuel/+bug/1262313
16:59 albionandrew MiroslavAnashkin: http://pastebin.com/gqFLywCg node-18 is a controller . service ceph restart on node-18 does not start. The logs show http://pastebin.com/xwSHC0v3
17:02 albionandrew MiroslavAnashkin: I suppose my question really is why is the glance mount on the contoller showing 100% when there’s space on ceph?
17:07 MiroslavAnashkin Nova uses this partition to download images from Ceph, expand these images to full size (if these were RAW) and store them back to Glance backend.
17:08 MiroslavAnashkin If you have no images, currently being downloaded/uploaded - you may try to clean up this volume from obsolete data.
17:10 albionandrew Nothing being downloaded. By Uploaded you mean uploaded to a ceph node? How would I identify what is obsolete?
17:11 MiroslavAnashkin Glance should delete all successfully iploaded/downloaded data automatically.
17:12 MiroslavAnashkin If it has not removed something - then it is probably remains of failed operation
17:12 albionandrew Should there be anything in image-cache?
17:13 albionandrew images is empty
17:13 albionandrew on the controller
17:13 MiroslavAnashkin Image-cache is temporary storage space. /var/lib/glance
17:13 MiroslavAnashkin On the controller
17:14 albionandrew http://pastebin.com/RdrWCuij
17:15 MiroslavAnashkin It is safe to remove all from /invalid and /incomplete
17:16 albionandrew Those are empty
17:16 albionandrew but theres a good 4G in image-cache
17:17 albionandrew This is what I’m looking at http://pastebin.com/RdrWCuij
17:17 albionandrew Could  36da2280-a475-4213-a412-4fe69ab371f2 for example be deleted?
17:17 angdraug joined #fuel
17:20 BillTheKat joined #fuel
17:21 xarses joined #fuel
17:21 BillTheKat I wanted to remove some nodes from fuel DB and in 4.1 I did it via postgres  - no postgres DB in 5.0? It not are there documented instructions to remove old nodes from DB?
17:27 MiroslavAnashkin BillTheKat: Everything in 5.0 is in its own Docker container. To get the shell to the postgres container please run `dockerctl shell postgres`
17:29 BillTheKat MiroslavAnashkin: Ah yes - docker - duh - I forgot - thanks for for the specific docker instance....
17:30 MiroslavAnashkin albionandrew: Please check if this ID exist in Nova with `glance image-list` and `nova image-list`
17:30 albionandrew Thanks I will check. If its not listed is that ok to go?
17:30 MiroslavAnashkin Yes,
17:31 albionandrew Great Thnaks again
17:35 BillTheKat When doing a "fuel node" on 5.0 - some nodes are listed twice (not all). Hmm - some are in discovered state and some are in ready state. Does not seem to make any specific sense to see exactly why. I would like to issue a bug report. Do I just show output of fuel node. Would that be sufficient?
17:42 MiroslavAnashkin Fuel output would be sufficient. Diagnostic snapshot - even more sufficient, as it includes postgred DB dump.
17:43 derrickb joined #fuel
17:44 BillTheKat MiroslavAnashkin: Specific command to do a diagnostic snapshot?
17:48 MiroslavAnashkin Click Support in Fuel web UI, click Generate Diagnostic Snapshot, wait until it get ready and link to the new snapshot appears near the button.
17:48 BillTheKat k thanks
17:58 xarses BillTheKat: you want to delete a Node from the db?
18:01 e0ne joined #fuel
18:02 BillTheKat xarses: yes - you actually gave me specific postgres commandas to do that in 4.1 - I assume once I get into docker postres instance they are the same for 5.0?
18:15 jaypipes joined #fuel
18:21 xarses you can 'curl -X DELETE http://<nailgun>:8080/api/nodes/<node id>' where node id is the first colum from the output of 'fuel nodes'
18:22 xarses there is a bug somewhere on LP that talks about adding it as a command for the fuel client
18:26 e0ne joined #fuel
18:26 BillTheKat xarses:  I did a "curl -X DELETE http://localhost:8080/api/nodes/16" on the fuel master node and I got a 405 "Not Allowed" error.
18:26 xarses try singular node
18:27 xarses instead of plural
18:27 BillTheKat xarses: same thing
18:27 xarses hmm
18:28 BillTheKat xarses:  I believe this was the same behaviour we saw in 4.1 and you gave me a specific list of postgres commands to remove the node.
18:30 xarses you can 'curl -X DELETE http://<nailgun>:8080/api/v1/nodes/<node id>' where node id is the first colum from the output of 'fuel nodes'
18:30 xarses should work, was missing v1
18:31 xarses https://bugs.launchpad.net/bugs/1326116
18:34 xarses BillTheKat: ^ This worked last week, should work on 4.1 and 5.0. Sorry, the command line earlier was from memory
18:34 BillTheKat xarses:  Ah worked with port = 8000 not 8080
18:34 xarses doh
18:35 xarses yep, thats my bad
18:35 BillTheKat xarses: np - lol
18:35 vkozhukalov left #fuel
18:35 xarses I should have known better. Too many ports
18:40 e0ne joined #fuel
18:46 albionandrew xarses MiroslavAnashkin I’m back trying to rebuild the ISO with the patches preparing the env. test_run_with_retries (fuel_upgrade.tests.test_docker_upgrader.TestDockerUpgrader) ... ERROR etc  http://pastebin.com/JKwCgvD8 what do I need to fix those. Sorry as ever for asking so many questions!
19:02 MiroslavAnashkin albionandrew: This question is rather to bookwar or dburmistrov... BTW, this or next week we hope to migrate our ISO build server to 14.04 and update developer docs properly.
19:03 bookwar MiroslavAnashkin: albionandrew i am not sure this one is related to 14.04 version
19:04 bookwar albionandrew: do you apply patches to current master?
19:14 albionandrew bookwar: Thursday/Friday last week Miroslav and xarses were helping with a new test deployment. We are having an issue where we cant get the nodes to pxe boot. We still cant PXE boot so I thought the idea of burning an ISO with all the patches might be the way to go ? Thats why I’m trying to build the ISO.
19:15 aedocw joined #fuel
19:22 bookwar albionandrew: do you build 4.1 or 5.0 version? docker_upgrader - is a work in progress feature for 5.1 release i think, thus you are not supposed to run its tests during iso build
19:25 albionandrew bookwar: I’m trying to build 5.0
19:27 albionandrew bookwar: http://pastebin.com/bryvzL9w I know you’re in the process of updating the documentation ..
19:27 albionandrew bookwar: the above is the output from step 7 http://docs.mirantis.com/fuel-dev/develop/nailgun/development/env.html
19:28 albionandrew are you saying I should ignore? Its all docker errors
19:29 bookwar i think you can move on with the procedure, those are upgrader tests errors which you can skip for now
19:30 Protux joined #fuel
19:32 bookwar but i'll file a bug to check, if there is something wrong with our default tests setup
19:33 bookwar albionandrew: to clarify, do you use master, or stable/5.0 branch?
19:35 e0ne joined #fuel
19:37 albionandrew bookwar: From this doc - http://docs.mirantis.com/fuel-dev/develop/env.html git clone https://github.com/stackforge/fuel-web; git clone https://github.com/stackforge/fuel-astute; git clone https://github.com/stackforge/fuel-ostf; git clone https://github.com/stackforge/fuel-library; git clone https://github.com/stackforge/fuel-docs
19:37 albionandrew and I’m using 14.04
19:37 albionandrew ubuntu on a vm
19:38 bookwar albionandrew: it's master branch then, thanks
19:38 albionandrew bookwar: Thanks
19:38 albionandrew If I get this working I should go a git pull each night to get the latest?
19:39 xarses albionandrew: it won't work on 14.04, there is an issue with multistrap, should use 12.04, otherwise you have to get multistrap from 12.04 repo
19:40 albionandrew xarses thanks. I will start again
19:40 skul1 joined #fuel
19:40 xarses you don't need to do all of the development deps. You should only need to do fuel-main requirements.
19:57 BillTheKat joined #fuel
20:07 albionandrew xarses so your saying I should only need to pull down git clone https://github.com/stackforge/fuel-main nothing else?
20:11 boris-42 joined #fuel
20:17 christopheraedo albionandrew two things - I have had better success building fuel dev environment on 12.10.  Also, after git clone in each of those, do a "git checkout tags/5.0" in each repo to make sure you're building from stable branch
20:17 albionandrew christopheraedo: Thanks
20:19 christopheraedo No problem.  Only other consideration is that the docs say you can skip the "build nailgun dev" part, but that is no longer correct - it will be removed (or corrected) in the next update
20:45 xarses albionandrew: if you git clone fuel-main, and then run "make repos" from the root it will pull each of the other repos into build/repos for you, you can checkout stable/5.0 from there
21:10 jues joined #fuel
21:17 albionandrew xarses - Can you just clarify for me what I need to do. I’ve done the git clone of the fuel main, done a make repos. One of the devs here made sure I pulled the stable 5.0 now …I need to do the nailgun tests? and all of 3.2 ? then 3.3 .. Sorry but I’ve never built anything like this so it gets a bit confusing if I have to follow some things but ignore other bits..
21:23 christopheraedo albionandrew - do 3.1, and in 3.2 go through 4.1.1.2, you can stop at "running nailgun in fake mode" then do 3.3 and 3.4 (ignoring step 3.4.3)
21:23 albionandrew christopheraedo: great thanks
21:24 christopheraedo no prob, and share here if you have any problems, we should be able to get you sorted out quickly.
21:43 albionandrew christopheraedo: should I only be doing 4.1.1.2, nothing before or after?
21:44 christopheraedo Do all the steps up to and including 4.1.1.2
21:45 christopheraedo (and soon hopefully, this will all be resolved with something like "make dev_environment" https://bugs.launchpad.net/fuel/+bug/1324723 )
21:46 albionandrew christopheraedo: at step 7 I see http://pastebin.com/kJt86pju someone said it should fail is that correct?
21:46 albionandrew Failed tests: upgrade_system_tests
21:46 christopheraedo yes you can ignore that
21:47 albionandrew christopheraedo: I can ignore because its related to docker? Or for some other reason?
21:49 christopheraedo are you in the 5.0 branch?
21:49 albionandrew christopheraedo: I believe so yes.
21:51 christopheraedo What does "git show -s --pretty=%d HEAD" show?
21:51 albionandrew christopheraedo on 4.1.1.2. Setup for Web UI Tests -  http://pastebin.com/Q6DUFNRN
21:52 albionandrew christopheraedo: I’m guessing I’m on master - http://pastebin.com/UsXLErHH
21:53 albionandrew One of the guys here said I was on 5.0
21:53 albionandrew sorry.
21:53 christopheraedo no prob - get to the base of each of the fuel repos and do "git checkout tags/5.0" and you should be good
21:54 christopheraedo Glad you verified whether or not you should see an error.  If you're on 5.0 branch, you should be able to run those tests without errors.
21:55 albionandrew christopheraedo: http://pastebin.com/6UzNBz1B
21:55 albionandrew is that what I should be seeing?
21:56 christopheraedo I think so, you can verify "git show -s --pretty=%d HEAD" gives you  (HEAD, 5.0, origin/stable/5.0)
21:57 albionandrew christopheraedo:  (grafted, HEAD, 5.0, origin/stable/5.0)
21:57 albionandrew will now do in all the repos
21:57 albionandrew thanks
22:02 christopheraedo no problem at all
22:05 albionandrew christopheraedo: http://pastebin.com/K2RX6bvk What am I missing?
22:08 albionandrew christopheraedo: everything forward of 4.1.1.2 http://pastebin.com/DK8r5bqP
22:09 christopheraedo after switching to 5.0 tag, do make deep_clean to start fresh.  Also, which Ubuntu are you doing this under?
22:10 albionandrew christopheraedo 12.10
22:11 albionandrew so change into every directory and run deep_clean  ?
22:11 christopheraedo ok that's good - try a make deep_clean at the base of fuel-main and then go through the nailgun steps again ..
22:11 christopheraedo only need to deel clean in fuel-main
22:11 albionandrew will do thanks
22:37 albionandrew christopheraedo: http://pastebin.com/fygUsxhF
22:42 christopheraedo Hmm, looks like you might be building this in the wrong place.  Try going to fuel-web and try running the steps from there.  I think the build directory you are in under fuel-main is meant only for make to touch during the build iso/build img process
22:44 albionandrew christopheraedo: 4.1.1.1. Setup for Nailgun Unit Tests ?
22:44 christopheraedo (sorry, I didn't notice that earlier, I would have mentioned sooner) ..  Yes, "4.1.1.1. Setup for Nailgun Unit Tests
22:44 christopheraedo Nailgun can be found in fuel-web/nailgun"
22:45 christopheraedo Pastebin shows you in /fuel-main/build/repos/nailgun
22:51 albionandrew christopheraedo: Thanks. running step 7 again
23:00 albionandrew christopheraedo: I’ve got to shoot off but will try running this tonight, Thanks again for your help
23:02 christopheraedo no prob, I'll be around tomorrow (and even tonight), will keep an eye out. Definitely want to get you rolling with making your own ISO
23:19 Kupo24z1 Anyone run Fuel nodes in ubuntu? Trying to install guestfish and having no luck
23:34 xarses Kupo24z1: "Fuel nodes in ubuntu" what do you mean?
23:34 Kupo24z1 compute/controller nodes in ubuntu rather than centos 6
23:35 xarses Should work fine, I deploy it all the time
23:36 Kupo24z1 I do 'apt-get install guestfish' and it tells me 'You will have to enable the component called 'universe''
23:36 Kupo24z1 however in the apt sources i see its using the fuel master for its repository
23:36 Kupo24z1 im not sure where i can go from here to install it
23:37 xarses Fuel errored out trying to install guestfish? Or is this something you want to enable?
23:38 Kupo24z1 something post-install i want to setup on each of the compute nodes manually to run a few scripts
23:38 Kupo24z1 since its not installed by default it looks like
23:39 xarses ok, so we ship packages on this iso, its not a full clone of upstream, just what we expect to use and some utilities
23:40 xarses so you'd have to add a source for the package, preferably create one with what you need in it so it won't create unnecessary conflicts with the ones we provide
23:42 Kupo24z1 hmm well dpkg -i worked from this version http://www.ubuntuupdates.org/package/core/precise/universe/base/guestfish

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