Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2016-07-05

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

All times shown according to UTC.

Time Nick Message
00:27 code-R joined #fuel
02:02 code-R_ joined #fuel
03:11 code-R joined #fuel
04:59 veena_ I'm facing an issue while deploying openstack using odl plugin
04:59 veena_ (/Stage[main]/Opendaylight::Service/Exec[wait-until-odl-ready]/returns) change from notrun to 0 failed: curl -o /dev/null --fail --silent --head -u admin:admin http://192.168.0.2:8282/restconf/operational/network-topology:network-topology/topology/netvirt:1 returned 22 instead of one of [0]
05:01 veena_ I'm using fuel 8.0 as suggested by mskalski and have built the odl plugin to support SFC. In settings odl plugin shows SFC features and I have selected Netvirt as Classifier used by SFC
05:28 xarses joined #fuel
05:29 xarses joined #fuel
05:39 code-R joined #fuel
05:41 xarses joined #fuel
05:42 xarses joined #fuel
05:51 vkulanov joined #fuel
05:51 vkulanov joined #fuel
05:54 vkulanov joined #fuel
05:55 maestropandy joined #fuel
05:56 code-R_ joined #fuel
06:02 maestropandy hi, I would like to keep Ceph as backend for all my block, object, and images. Created New Openstack Environment in Fuel Dashboard, while adding nodes showing warning messages as "Cinder LVM should be enabled in settings  ceph RBD cannot be used with cinder "
06:05 vkulanov joined #fuel
06:20 code-R joined #fuel
06:28 maestropandy joined #fuel
06:56 maestropandy While deploying fuel setup got error "Error Provision has failed. Failed to execute hook 'shell' Failed to run command" http://paste.openstack.org/show/525861/ please help to resolve and deploy
07:08 maestropandy I gone through this same error "https://bugs.launchpad.net/fuel/+bug/1460653"
07:08 maestropandy Is it fixed ?
07:09 maestropandy May I know why am getting, Is ISO broken with ubuntu ?
07:10 maestropandy COuld not find images under "cd /var/www/nailgun/targetimages/"
07:24 dancn joined #fuel
07:32 gongysh joined #fuel
07:35 w00t joined #fuel
07:36 zhsj joined #fuel
07:46 maestropandy Can someone plesase reply my query, which is similar as "https://bugs.launchpad.net/fuel/+bug/1460653""
07:46 maestropandy am using fuel
07:47 maestropandy 8.0
07:47 maestropandy where redoplyment of master fuel node doesnt help
07:50 maestropandy manaully checked to access URL "http://10.20.0.2:8080/targetimages/env_39_ubuntu_1404_amd64-boot.img.gz" 404 page not found
07:53 hkominos joined #fuel
08:17 noshankus joined #fuel
08:49 bgaifullin joined #fuel
08:50 bgaifullin joined #fuel
09:11 aglarendil I guess you entered incorrect IP addresses when first configuring fuel node. maestropandy - can you check it in /etc/fuel and /etc/nailgun ?
09:12 aglarendil veena_: what was the HTTP error code? was it 404 ?
09:13 veena_ aglarendil, I loggedin to the node where odl was installed and tried running the services, it gave error as openjdk 1.8 is needed
09:14 veena_ so I installed openjdk-8 and deploying it again, it seems to be going fine, deployment is not complete yet
09:14 aglarendil I suggest you file a bug for opendaylight plugin. I guess it is community-based thing
09:21 veena_ aglarendil, again got the same error. ERR (/Stage[main]/Opendaylight::Service/Exec[wait-until-odl-ready]/returns) change from notrun to 0 failed: curl -o /dev/null --fail --silent --head -u admin:admin http://192.168.0.2:8282/restconf/operational/network-topology:network-topology/topology/netvirt:1 returned 22 instead of one of [0]
09:21 aglarendil maestropandy: I suggest that this is simply due to slow access to repos from your site. you can change ubuntu repos to use your local geographic mirror in environment configuration
09:22 veena_ aglarendil, so it might not be a bug
09:22 aglarendil @veena_ I am not subject matter expert on odl plugin, but I suggest that you check corresponding web services logs and run the command manually to see the full error message
09:22 aglarendil well if it does not work, it must be a bug :-)
09:24 ekosareva joined #fuel
09:25 veena_ aglarendil, sure, will try it and check the logs
09:28 aglarendil @mskalski ^^
09:31 maestropandy joined #fuel
09:32 maestropandy aglarendil: I cant able to reach that URL from fuel node itself
09:33 mskalski veena_: can you please join #opnfv-fuel - this channel is more related to your issues
09:35 maestropandy veena_: yes my error code is 404, which s same from fuel node host as well, where rest of URL can able to reach
09:35 aglarendil maestropandy: can you check for fuel-agent logs in /var/log?
09:37 veena_ mskalski, I joined
09:38 maestropandy aglarendil: under log can see bootsrap and fuelmenu, couldnt find fuel agent log
09:38 aglarendil check this path /var/log/fuel-agent-env-*
09:39 aglarendil like /var/log/fuel-agent-env-1.log which is log for the first environment
09:40 maestropandy aglarendil: could not find similar log
09:41 maestropandy ls /var/log/fuel
09:41 maestropandy fuel-bootstrap-image-build.log  fuelmenu.log
09:42 maestropandy Now completed new fuel setup in another machine where its shows "There is no active bootstrap. Bootstrap image building is in progress. Usually it takes 15-20 minutes. It depends on your internet connection and hardware performance. Please reboot failed to discover nodes after bootstrap image become available." in dash board for long time
09:43 maestropandy Where all my bootstrap images are up as triggered by virtual box scripts
10:36 maestropandy left #fuel
10:37 bgaifullin joined #fuel
10:40 LanceHaig joined #fuel
10:45 kaliya joined #fuel
10:56 vkulanov joined #fuel
11:02 DavidRama joined #fuel
11:14 aglarendil maestropandy: are you sure you do not have /var/log/fuel-agent-env-38.log file?
12:00 tosc_fiberdata joined #fuel
12:08 maestropandy joined #fuel
12:12 tosc_fiberdata mwhahaha, yo man, did you check the NFS-plugin?
12:17 maestropandy Still error "There is no active bootstrap. Bootstrap image building is in progress. Usually it takes 15-20 minutes. It depends on your internet connection and hardware performance. Please reboot failed to discover nodes after bootstrap image become available." in dash board for long time"
12:30 DavidRama left #fuel
12:54 kaliya joined #fuel
12:59 maestropandy can someone help to resolve this raised bug in launcpad "https://bugs.launchpad.net/fuel/+bug/1599152"
13:00 asvechnikov aroma, nurla review/merge please https://review.openstack.org/#/c/333774/
13:07 Egyptian joined #fuel
13:09 Egyptian hi - i need help i set up an environment with 3 controllers and the vnc would only show up 1 in 3 refresh/tried. i found an old bug that said it was memcached_server settings in nova.conf but i verified i have that on all 3 controllers and the IPs are correct. any ideas?
13:24 tosc_fiberdata Egyptian, do you use IP or dns in nova.conf?
13:25 penguinolog joined #fuel
13:30 code-R joined #fuel
13:34 Egyptian tosc_fiberdata: ip .. and they ping .. its on the management vlan
13:34 code-R_ joined #fuel
13:41 maestropandy Hi all, after vry long time and multiple tries "https://bugs.launchpad.net/fuel/+bug/1599152", resolved
13:43 Sketch does anyone know if i have to have a networking template to use vlan segmentation?  i did modify the libvirt template, but get an error when starting libvirt
13:43 Sketch https://ask.openstack.org/en/question/94181/cant-start-initial-vms-for-reduced-footprint-setup/
13:43 Sketch or any other ideas would be great ;)
13:44 mwhahaha tosc_fiberdata: i looked into it, it's not compatible with the newer versions and would require a rewrite.  it's not the most complex plugin but it would still take some time to do
13:47 code-R joined #fuel
13:49 DavidRama joined #fuel
13:56 code-R_ joined #fuel
13:56 Julien-zte joined #fuel
13:59 gardlt joined #fuel
14:13 code-R joined #fuel
14:18 cr0wrx joined #fuel
14:21 dmellado joined #fuel
14:23 aglarendil @maestropandy what if you try to run the command in your pastebin manually ? does it work? which error would it through to the output?
14:25 agordeev dear fuelers, fuel-agent CI is slightly broken, so, please don't expect any merges into fuel-agent today. https://bugs.launchpad.net/fuel/+bug/1599155
14:30 dmellado joined #fuel
14:30 denghui joined #fuel
14:37 rmoe_ joined #fuel
14:41 maestropandy aglarendil: didn't get your question sorry, can u again pls
14:45 aglarendil maestropandy: there is a log output that you sent with log of command that was run to build a base image for provisioning
14:45 aglarendil http://paste.openstack.org/show/525861/ here
14:46 rmoe joined #fuel
14:52 aglarendil okay, I got it. you have containers
14:52 aglarendil so image building logs should be somewhere inside docker-lots
14:52 aglarendil *docker-logs directory
14:53 aglarendil so you need to check /var/log/docker-logs/nailgun for particular fuel-agent logs
14:53 GamesofCODE joined #fuel
14:55 maestropandy aglarendil: hmm
14:55 aglarendil if you do not find it in nailgun - check mcollective
14:58 mwhahaha ikalnitsky, evgenyl can you please review these fuel-plugin reviews that have been sitting for over a month now https://review.openstack.org/#/c/320059/ and https://review.openstack.org/#/c/318250/
15:00 code-R joined #fuel
15:01 xarses joined #fuel
15:04 dmburmistrov joined #fuel
15:34 agordeev guys, please help to review https://review.openstack.org/#/c/337682/ it should fix the CI for fuel-agent.
15:37 code-R joined #fuel
15:41 hkominos_home joined #fuel
15:42 code-R_ joined #fuel
15:46 denghui joined #fuel
15:52 LanceHaig joined #fuel
15:56 koma left #fuel
16:23 aarefiev joined #fuel
16:25 bgaifullin joined #fuel
16:27 code-R joined #fuel
17:09 permalac joined #fuel
17:22 Sketch is there somewhere i can change the PXE settings outside of the fuel menu?  it comes up pre-populated and won't let me change them, even though i haven't even logged into the web UI yet.
17:24 Sketch (also oddly, installing fuel in a VM seems to have resulted in it skipping the initial fuelmenu run?)
17:24 aglarendil Sketch: you might want to check this out http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_change_network_interface.html
17:25 aglarendil Sketch: did you install with vbox script or something otherwise?
17:25 itsjustme joined #fuel
17:25 Sketch nope, just via ISO into a (non-openstack) kvm virtual image
17:26 Sketch same ISO i used when I installed it on real hardware, it brought up the fuel menu on first boot.   but in a VM, that didn't happen.
17:26 itsjustme hey guys, i have liberty installed using fuel8. there's an inconsistency with regards to available disk space being reported. the hypervisors page lists 1.3tb - this only accounts for storage on six out of nine nodes.
17:27 itsjustme i have three controller+cinder nodes and six computer+cinder nodes.
17:27 Sketch unless it's somehow finding the other physical machine...it didn't clone the settings from it though.
17:28 Sketch heh, i can't disable it in fuelmenu because it's the only interface.
17:28 aglarendil itsjustme: which cinder backend are you  using?
17:29 itsjustme aglarendil: Cinder LVM over iSCSI for volumes
17:29 aglarendil Sketch: well, there is 15 seconds timeout unless you interrupt it, AFAIK
17:29 Sketch ahh
17:29 aglarendil Sketch: also, if you do not have any nodes provisioned yet, it should be safe just to change PXE network and rerun bootstrap_admin_node.sh command
17:30 aglarendil itsjustme: you might want to check for the list of alive cinder-volume services
17:30 aglarendil may be 3 of 9 have not registered properly
17:30 aglarendil e.g. they do not have network connectivity to controllers
17:30 aglarendil can you ping those 3 by there management ip addresses?
17:32 itsjustme aglarendil: cinder service-list shows everything is up, three scheduler processes on the three controllers, and nine volume processes, one per node. enabled and up.
17:34 itsjustme i should have 196gb*9=1,7-ish tb available for ephemeral storage but only 1.3tb is reported on the hypervisor page
17:34 Sketch aglarendil: even from there, fuel setup complains that i can't change the dhcp range after deployment
17:35 itsjustme so this is in line with those three servers not being accounted for
17:36 Sketch and it looks like it's doing the bootstrap process again, so i doubt it will be any different afterwards.
17:41 rkum joined #fuel
17:50 itsjustme ok - i figured it out. controllers have cinder and _image_ storage. compute nodes have cinder and _virtual_ storage.
18:40 cr0wrx anyone know how to verify where glance images are if using a ceph backend? I'm trying to learn ceph and get a little more familiar with how all this works under the hood that fuel set up. I see an 'images' pool in ceph, but it's empty. I have 11 images though and glance-api.conf is configured to use swift / everything was set to use ceph in fuel
18:45 aglarendil than I guess you have all 11 images stored in swift
18:45 thiagolib joined #fuel
18:45 aglarendil did you mean 'everything [else] was set  to use ceph in fuel' ?
18:46 cr0wrx nope
18:46 cr0wrx When I look in fuel it shows ceph RBD for images
18:47 cr0wrx now, ceph radosgw for objects (swift API) is also selected - does that mean glance is using swift but swift is backed by ceph?
18:48 cr0wrx thus glance is still ceph
18:48 aglarendil so what you mean is that you asked Fuel to configure everything for ceph, UI says that it is true, but glance-api is actually configured to work with swift
18:48 aglarendil okay, which version of Fuel are you using ?
18:48 cr0wrx 8
18:48 cr0wrx MOS 8.0 to be exact
18:48 aglarendil I guess, for 8 we need help of iberezovskiy or degorenko here ^^
18:50 cr0wrx I'm thinking it's in ceph, somewhere, I'm just having trouble following it :/ I don't have any mapped file systems that seem to point to storage it could be other than ceph osd
18:52 thiagolib Hello installed mirantis fuel 8, did deploy successfully mirantis OpenStack environment however needed to reboot my controller to return to the original settings and how the machine rebooted the fuel returns status overdraft rather than ready.
18:52 mwhahaha both of which are on vacation i believe
18:53 mwhahaha glance maybe configured to use radosgw or something
19:03 cr0wrx default_store = swift
19:03 mwhahaha are you using ironic?
19:04 mwhahaha https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack_tasks/manifests/glance/glance.pp#L117-L130
19:04 cr0wrx I do have ironic enabled
19:04 cr0wrx but no nodes currently
19:05 mwhahaha so it looks like it won't let you use rbd if ironic is enabled
19:05 cr0wrx that last else matches my settings
19:05 cr0wrx hrm, well fuel didn't complain. Oh wells. So then the question is, where is swift storing these raw files on disk? I don't see anything useful in /etc/swift/swift.conf
19:06 mwhahaha well swift proxy may still be shoving them into ceph
19:06 mwhahaha let me look
19:07 cr0wrx I'm thinking so, because I don't have any mapped file systems that seem to hold data somewhere. Maybe .rgw.buckets? Sorry I'm a bit slow at figuring all this out. ceph/swift/openstack/fuel all new here, interesting stuff though
19:07 mwhahaha so it's probably configured to use radowsgw as swift won't be enabled if images_ceph is enabled, https://github.com/openstack/fuel-library/blob/stable/8.0/deployment/puppet/osnailyfacter/modular/swift/swift.pp#L54
19:07 code-R joined #fuel
19:08 mwhahaha https://github.com/openstack/fuel-library/blob/stable/8.0/deployment/puppet/osnailyfacter/modular/ceph/radosgw.pp#L17-L22
19:08 mwhahaha so glance uses swift via radowsgw to put it into ceph
19:09 mwhahaha so that ironic could still use it i guess
19:11 cr0wrx so if I do a `ceph df` I'm guessing all the radosgw stuff goes into one of the .rgw.* pools
19:11 mwhahaha yea
19:11 cr0wrx the only one with significant data for me is .rgw.buckets, which I guess is where images are going
19:12 mwhahaha https://github.com/openstack/fuel-library/blob/stable/8.0/deployment/puppet/osnailyfacter/modular/ceph/ceph_pools.pp
19:12 mwhahaha the pools
19:12 mwhahaha compute has a different one
19:12 cr0wrx yea, but images is empty for me. That must be if you don't use ironic or go through swift
19:15 aglarendil thiagolib: I am really surprised - there is no such status 'overdraft' for node in Fuel
19:15 aglarendil is it a typo?)
19:16 aglarendil and which procedure do you mean by 'returning to original settings' ?
19:20 kaliya joined #fuel
19:23 thiagolib sorrsorry not is 'overdraft', is discovered
19:46 bgaifullin joined #fuel
20:06 cr0wrx is there ever a need to use the default fuel created ~/openrc file on controller node? For me, I thought it used to work, but now it tosses 'resource cannot be found' errors. It's set to use internalurls. If I export client config from horizon for admin user (same user as in that default ~/openrc file), I get public URLs and commands seem to work using that
20:06 mwhahaha it's used by puppet
20:07 cr0wrx so I shouldn't be expected to be able to use it? How would it work for puppet then? For me, it doesn't work at all if I source that file. pretty much all commands fail
20:08 mwhahaha you can use it on the controllers to operate with the openstack cluster
20:09 cr0wrx that's what I'm trying but it's failing. Resource cannot be found 404 for any openstack commands I run now (it used to work, I'm pretty sure)
20:09 mwhahaha might be a keystone v2 vs v3 thing
20:10 kaliya_ joined #fuel
20:10 cr0wrx not sure what's up. `ip netns exec haproxy netstat -tanup | grep LISTEN` shows services listening on those internal urls
20:12 cr0wrx ah, well, sounds like keystone version I bet
20:13 cr0wrx my openrc file had `OS_AUTH_URL=172.16.2.2:5000/`, if I copy that openrc file and change to 172.16.2.2:5000/v2.0, everything seems to work again
20:13 cr0wrx is that expected? I guess puppet will still work if in puppet commands it manually specifies version somewhere?
20:15 cr0wrx or, did I accidentally break my openrc file and puppet won't work next time it's needed :P
20:15 cr0wrx hrm well it works fine in another cluster without v2.0 on OS_AUTH_URL, so prob some other env variable got set sometime somewhere, maybe
20:28 mwhahaha thiagolib: so you deployed and want to reset the environment so you can redeploy? You can use the reset enviroment via the UI which should revert it back
20:30 cr0wrx don't provisioned nodes start up as discovered prior to flipping to ready? Or are they discovered if they aren't part of environment?
20:31 mwhahaha i believe they are discovered if not part of an environment
20:31 maestropandy joined #fuel
20:32 mwhahaha or prior to that, usually it says 'ready' after deployment
20:32 mwhahaha thiagolib: and by revert it back, I meant back to an un-provisioned state (aka delete everything)
20:34 cr0wrx yea mine are ready. Was just wondering if they are discovered (connecting to fuel) but then go through some other checks / process before going to ready (usable), so if they don't go to ready it means something got messed up maybe. Or, maybe when thiagolib said 'original settings' he already removed node from environment and nuked it and just needs to add back to environment
20:34 maestropandy deploying single node setup taking place more than 7 hours, is it usual or i have to check somthing
20:34 cr0wrx not usual would be my guess. physical? VM? your fuel node and hardware specs prob have something to do with it
20:35 maestropandy I am running on my Virtual box. so its VM
20:35 cr0wrx I have deployed 3-4 node environments in a couple hours about 30 times now (still don't have a clue what I'm doing), on some fairly cheap hardware, takes me a couple hours
20:35 mwhahaha 7 hours is not normal
20:36 mwhahaha you can check the astute.log for the status of what's its currently working on
20:36 maestropandy me also thinking same, but its still going on without issues so whether let it go or do something
20:38 maestropandy 2016-07-05 17:08:07INFO[748] Provision summary: time was spent 01:00:12 was astute log recent INFO
20:38 mwhahaha so it provisioned
20:38 mwhahaha did you do just provisioning or did you do provisioning+deploy?
20:39 maestropandy but in dashboard its showing 57 %
20:39 maestropandy and status is deploying
20:39 mwhahaha which version of fuel?
20:40 maestropandy its 8
20:40 maestropandy and my node statistics Node Statistics Controller1, Compute1, Storage - Ceph OSD3
20:42 GamesofCODE joined #fuel
20:43 maestropandy mwhahaha: installation is going on and it was 80 %  can see it under Nodes tab
20:43 mwhahaha oh ceph
20:44 mwhahaha might take a while depending on the hardware
20:44 mwhahaha you can check the puppet logs on the nodes to see what its currently configuring
20:44 mwhahaha or tail -f /var/log/remote/node*/puppet-apply.log from the master
20:44 maestropandy yes, u right when using LVM it was done quicker
20:45 cr0wrx still seems long to me unless VM specs aren't too beefy. My 3-4 node deploys were all ceph
20:45 mwhahaha yea it depends on the underlying hardware, and if you're in virtualbox it may take longer
20:46 maestropandy could not find puppet logs under mentioned, pls confirm again
20:50 maestropandy cr0wrx: My host is 8 GB and i have tuned virtual box scripts to comfort with my hardware like 1 GB each node
20:53 mwhahaha oh that's a problem
20:53 mwhahaha oh on 8 it's under /var/log/docker/remote/node*/puppet-apply.log
20:53 mwhahaha so that's not enough ram for those it's going to take hours. its recommended to have at least 16 gigs
20:54 mwhahaha if you're doing a single host otherwise it's going to probably error out at some point
20:54 maestropandy yes, found its under docker, but no puppet apply log, here the list under it astute.log                      cobbler.log   mcollective-hiera.log  nailgun.log  ostf.log      rabbitmq.log
20:54 maestropandy cobbler-dhcp-default-range.log  keystone.log  mcollective.log        nginx.log    postgres.log
20:54 mwhahaha no that's a different set of logs
20:55 mwhahaha under /var/log/docker/remote/node*/ should be the node logs unless you're sending your logs to an external syslog server
20:56 v1k0d3n joined #fuel
20:56 maestropandy path is /var/log/docker-logs/puppet/
20:56 mwhahaha no
20:56 mwhahaha that's the puppet logs from within the docker container(s)
20:57 maestropandy there is no docker/remote in master, it was docker-logs in fuel 8
20:57 mwhahaha is there /var/log/docker-logs/remote then?
20:58 mwhahaha i've been working on 9+ too long to remember
20:58 maestropandy mwhahaha: please see this http://paste.openstack.org/show/526081/
20:58 mwhahaha yes that's not the logs i'm refering to
20:58 mwhahaha those are the logs from the docker containers
20:59 maestropandy how to  see remote logs of puppert apply
20:59 mwhahaha so /var/log/docker-logs/remote/node*
21:01 mwhahaha tail -f /var/log/docker-logs/remote/node*/puppet*
21:01 mwhahaha should work
21:04 maestropandy here the list of file under /docker-logs/remote http://paste.openstack.org/show/526083/
21:04 mwhahaha yea so those node-* folders have the logs for the remote nodes
21:07 maestropandy No puppet logs found, see the explored files under remote http://paste.openstack.org/show/526084/
21:08 mwhahaha so if they only have bootstrap then nothing has been deployed there yet
21:08 mwhahaha not sure what to tell you, i would recommend deploying on a system with more ram
21:09 maestropandy ok, I will destroy deployment and try with LVM
21:09 maestropandy by removing ceph
21:09 maestropandy Shall i do revamp or wait ?
21:09 mwhahaha if you only have 8 gigs you realistically should only deploy a max of like 3 nodes
21:10 mwhahaha i wouldn't wait, i doubt it'll complete
21:11 maestropandy My host laptop is  8 GB RAM and tuned virtual box scripts launch_8G.sh with all nodes (5) each 1 GB RAM + Fuel 1.2 GB so in total it was 6.5 used for deployment out of 8 GB RAM
21:12 mwhahaha yea i know, i'm just saying it may not work well
21:13 maestropandy sad, what shall i do, would like to deploy fuel 8 with ceph in this 8GB hardware pls suggest
21:13 mwhahaha get more ram
21:13 mwhahaha or deploy 1 controller + 2 ceph/compute
21:14 maestropandy fuel 8 not allowing with 2 ceph node
21:14 maestropandy i have tried that
21:14 mwhahaha 1 controller/ceph + 2ceph/compute
21:15 maestropandy didnt get 1 controller/ceph + 2ceph/compute ??
21:15 mwhahaha put ceph on the controller and on the compute nodes
21:17 mwhahaha mmalchuk, holser_, aglarendil: fix for noop tests https://review.openstack.org/#/c/337845/
21:18 maestropandy I have destroyed existing deployment
21:44 veena__ joined #fuel
21:45 Vijayendra joined #fuel
21:52 xarses maestropandy: deploy controller + ceph-osd on same node and compute + ceph-osd on second node, go to settings page and change ceph object replica from 3 to 2. deployment will work then
21:52 xarses compute and controller node should have 2GB ram, fuel can have ~1.5G
22:01 HeOS joined #fuel
22:17 Bomfunk joined #fuel
22:26 Julien-zte joined #fuel
22:27 DavidRama joined #fuel
22:42 gongysh joined #fuel
22:44 DavidRama left #fuel
22:56 fatdragon joined #fuel
23:38 xarses joined #fuel

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