Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-10-27

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

All times shown according to UTC.

Time Nick Message
00:02 Wida joined #fuel
00:04 ppradhan joined #fuel
00:43 angdraug joined #fuel
00:44 zhangjn joined #fuel
00:59 EinstCrazy joined #fuel
01:00 EinstCrazy joined #fuel
01:05 Verilium Sesso:  Yeah, thankfully, interface configs don't change, but still, shoudn't disk configs also stay the same as they were set?
01:05 sbog_ joined #fuel
01:06 e0ne joined #fuel
01:14 ppradhan joined #fuel
01:17 xarses_ joined #fuel
01:18 xarses_ joined #fuel
01:19 xarses_ joined #fuel
01:20 sbog_ joined #fuel
01:20 xarses_ joined #fuel
01:53 angdraug joined #fuel
01:56 e0ne joined #fuel
02:00 fedexo joined #fuel
02:00 e0ne_ joined #fuel
02:25 ppradhan joined #fuel
02:41 angdraug joined #fuel
03:04 ppradhan joined #fuel
03:28 aleksandr_null joined #fuel
03:30 rmoe joined #fuel
03:34 Sesso Verilium: I dont think disks stay from what I remember. I always had to reset my ceph cluster journal drive lol
03:52 rmoe joined #fuel
04:15 ppradhan joined #fuel
04:39 cartik joined #fuel
04:53 ppradhan joined #fuel
05:15 zhangjn joined #fuel
05:16 zhangjn joined #fuel
05:19 az joined #fuel
05:28 zhangjn joined #fuel
05:30 zhangjn joined #fuel
05:33 vsedelnik joined #fuel
05:46 cartik Hi team,
05:47 cartik not able to update the vrouter ip using the yaml file
05:47 cartik when i try downloading the fine and update and upload it is not reflecting
05:47 cartik pls. help
05:47 cartik im using MOS 7.0
05:49 Sesso wouldnt you have to restart the neutron service?
06:01 cartik Sesso, was it to me?
06:02 Sesso sorry
06:02 Sesso yea
06:03 cartik sorry, im trying to update the network.yaml file for changing the management vrouter, as the first ip is configured in the firewall, it is creating ipconflict
06:03 cartik in order to prevent that thought would update the network config prior to deployment by updating the network config of the env
06:04 cartik i did downloaded and update the same and uploaded it but after uploading when i try downloading the changes are not reflecting
06:08 Sesso not sure.  I have never had to change any of that in my deployments
06:11 cartik Sesso, np
06:19 sergmelikyan joined #fuel
06:26 ppradhan joined #fuel
06:31 sergmelikyan joined #fuel
06:40 sergmelikyan joined #fuel
06:45 sergmelikyan joined #fuel
06:50 prmtl joined #fuel
06:51 tuvenen joined #fuel
06:54 sergmelikyan joined #fuel
06:55 ppradhan joined #fuel
07:02 ppradhan joined #fuel
07:15 adanin joined #fuel
07:20 mkwiek1 joined #fuel
07:20 neouf joined #fuel
07:22 Guest78532 joined #fuel
07:25 xarses joined #fuel
07:30 xarses magicboiz: did you get your question for LBaaS answered?
07:39 JoeStack joined #fuel
07:41 tkhno joined #fuel
07:42 rlu joined #fuel
07:44 rlu joined #fuel
07:55 Gary joined #fuel
07:59 neilus1 joined #fuel
08:05 cartik joined #fuel
08:12 cartik xarses, i have two queries, one wrt to the lbaas plugin for MOS7.0, and regarding management vrouter ip update during deployment, can you pls. guide me on that
08:13 xarses cartik: I can try
08:16 cartik xarses, thanks
08:23 xarses cartik: sorry, I don't have scroll-back, can you re-iterate your questions?
08:25 cartik xarses, 1- Fuel plugin for lbaas in MOS7.0, when is it expected, in the dev branch i still see 6.1 and there is no update for 7.0. i tried updating the metadata.yaml file and when i compiled it throwed error
08:25 cartik also would like to understand if there is a major change wrt lbaas in kilo?
08:26 xarses lbaas via haproxy basicly hasn't changed
08:26 xarses afaiu there are more backend drivers and thats about it
08:27 cartik 2- Update management vrouter ip before deployment, I used fuel --env <id> network --download
08:27 cartik and updated the generated yaml file and uploaded it and the change is not reflecting
08:28 vsedelnik joined #fuel
08:28 cartik is it enough or am i missing something
08:29 xarses the LBaaS plugin is maintained mostly by another team in Mirantis. So I dont know when they will provide the update. It may be delayed because I heard that they are tasked with a re-design of some parts of it, not just updating from 6.1 -> 7.0
08:30 cartik xarses, thanks
08:31 cartik in general are there any timelines for the GA of 7.0 plugins
08:31 xarses no, there isn't a strong timeline
08:31 cartik ok
08:32 xarses I will poke some internal people again about this lack of information
08:32 xarses they aren't part of the team that works on the fuel codebase
08:32 cartik thanks xarses, thankyou very much
08:32 xarses so there is some disconnect
08:32 cartik ok
08:32 xarses there is a verification api that you have to call for results from the upload. There is either a) an error with what you tried to upload and it's rejecting it because of it b) the patch to allow updating the VIP IP didn't land in 7.0 but is in master (you could back port it in this case)
08:33 cartik i did also checked using the --verify
08:33 cartik how do we track the patch option
08:38 xarses I asked akasatkin who wrote the patch to reach out to you he's in EU so he should be around
08:38 xarses I don't think I'll have time to track it down for you as I'm at the summit and am probably moving to another session shortly
08:39 xarses if you don't get a response please let me know or follow up on the openstack-dev ML
08:45 hyperbaba joined #fuel
08:46 akasatkin joined #fuel
08:46 HeOS joined #fuel
08:47 akasatkin cartik, Hi, xarses said you need help with API
08:48 cartik akasatkin, hi
08:50 ppradhan joined #fuel
08:51 cartik akasatkin, i would like to update the management vrouter ip created by fuel during deployment
08:52 cartik i tried downloading the network yaml file update it and when i tried uploading it same and the changes are not reflecting
08:52 akasatkin do you use Fuel CLI ?
08:52 cartik xarses, thanks
08:52 cartik akasatkin, yes
08:53 cartik fuel --env 9 network --download
08:53 cartik and im getting the yaml file and i modified the yaml and did fuel --env 9 network --upload
08:53 cartik and it dint work
08:54 cartik is there a option to change the management vrouter ip from gui?
08:54 akasatkin so, you've just changed VIP address and uploaded it back, true?
08:54 cartik i havent noticed it
08:54 akasatkin no, it is not in UI
08:54 cartik yes very true
08:54 cartik ya, i dint find it
08:55 akasatkin please try upload with "--debug" option. it should print response then
08:57 alrick joined #fuel
09:14 JoeStack Hi ! One of my deployments has a flapping control-node. I took a look into nailgun-agent.log of that specific node and found hundreds of "
09:14 JoeStack /usr/lib/ruby/vendor_ruby/ohai/mash.rb:91: [BUG] Segmentation fault
09:15 JoeStack and
09:15 JoeStack /usr/lib/ruby/vendor_ruby/ohai/mash.rb:91: [BUG] rb_gc_mark(): unknown data type 0x18(0x12cfaa0) non object
09:15 JoeStack ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
09:16 xarses joined #fuel
09:16 JoeStack It is a plugin enabled 6.1 deployment
09:22 subscope joined #fuel
09:29 c0by joined #fuel
09:29 akasatkin cartic: one of the problems can be that the address is in use already by some of the nodes
09:34 adanin joined #fuel
09:38 adanin_ joined #fuel
09:48 adanin_ joined #fuel
09:50 asaprykin joined #fuel
09:51 magicboiz Hi, I have a lab running MOS6.1(Juno/2014.2.2). Is there any way to update the Juno version to the latest Juno release(2014.2.3)?
09:55 magicboiz there are some security issues fixed in [2014.2.3].....
09:59 ppradhan joined #fuel
10:07 Chlorum joined #fuel
10:15 Damjanek magicboiz: There's no 2014.2.3 available in MOS6.1 at the moment. Please consult https://docs.mirantis.com/openstack/fuel/fuel-6.1/release-notes.html#maintenance-updates to check if those security fixes are delivered in Maintenance Updates.
10:19 magicboiz <Damjanek>: thx. And would you happen to know if "cloud-archive:juno" from Ubuntu Cloud are compatible with packages released from MOS6.1?
10:33 subscope joined #fuel
10:47 Damjanek magicboiz: I'm sorry, but I don't. For sure it's not supported, so it could mean that those will not be compatible.
11:03 vsedelnik joined #fuel
11:04 EinstCrazy joined #fuel
11:12 Wida joined #fuel
11:19 vsedelnik joined #fuel
11:23 weihan joined #fuel
11:47 vsedelnik joined #fuel
11:56 subscope joined #fuel
12:03 ppradhan joined #fuel
12:06 az joined #fuel
12:13 Wida joined #fuel
12:14 sergmelikyan joined #fuel
12:15 zhangjn joined #fuel
12:22 rlljorge joined #fuel
12:25 rlljorge Hello, Is security upgrade from 6.1 to 7.0 ?
12:27 cartik joined #fuel
12:33 Damjanek rlljorge: What do you mean?
12:37 subscope joined #fuel
12:51 rlljorge Damjanek:  I have version 6.1 installed and I want to upgrade to 7.0 any known problem during the upgrade? A prerequisite to be checked?
12:51 Guest89897 left #fuel
12:53 vsedelnik joined #fuel
12:58 Wida I don't know none of true story when somebody successful upgrade 6.1 to 7.0
13:00 Wida instruction in https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#upgrade-environment-experimental have a lot of not resolved issues
13:01 vsedelnik joined #fuel
13:01 rlljorge Wida: Thank you !
13:06 claflico joined #fuel
13:06 rmoe joined #fuel
13:09 claflico1 joined #fuel
13:12 e0ne joined #fuel
13:14 Wida joined #fuel
13:18 Wida when I do: 'SEED_ID=$(octane upgrade-env $ORIG_ID)' I have error:
13:18 Wida 2015-10-27 12:53:36 ERROR    octane.util.subprocess fuel2[13587] stderr: DEPRECATION WARNING: /etc/fuel/client/config.yaml exists and will be used as the source for settings. This behavior is deprecated. Please specify the path to your custom settings file in the FUELCLIENT_CUSTOM_SETTINGS environment variable.
13:19 Wida the next step: 'octane upgrade-node --isolated $SEED_ID 12' I have new error: '2015-10-27 12:54:37 ERROR    octane '
13:20 zhangjn joined #fuel
13:20 Wida how resolve it?
13:24 zhangjn joined #fuel
13:25 zhangjn joined #fuel
13:29 jerrygb joined #fuel
13:31 Damjanek Wida: Do you have anything under $SEED_ID?
13:38 zhangjn joined #fuel
13:39 zhangjn joined #fuel
13:46 magicboiz joined #fuel
13:49 Wida Damjanek: see it please http://paste.openstack.org/show/477469/
13:49 Wida it is full log of this command
13:50 rlljorge I am using the version 6.1 2014.2.2-6.1, for update de lasted 6.1 version i will do dockerctl backup; yum update; dockerctl destroy all; dockerctl start all; this is the correct procedure ?
13:53 Damjanek Wida: Can you provide full output from octane upgrade-node command?
13:55 Wida Damjanek: see it http://paste.openstack.org/show/5QQI5gLLIGonjYcre5Qo/
13:59 vsedelnik joined #fuel
14:04 ppradhan joined #fuel
14:06 rlu joined #fuel
14:07 Damjanek Wida: I'm afraid, that your architecture is unsupported: you've got ceph-osds on controllers, and we only support ceph-osds on separate nodes or combined with computes.
14:08 Damjanek Wida: https://bugs.launchpad.net/fuel/+bug/1509243 - here you can track the progress of this issue.
14:11 Wida Damjanek: Thank you so much
14:11 Damjanek Wida: No problem.
14:16 Damjanek rlljorge: Please consult this doc: https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#upgrading-and-updating-from-earlier-releases for 6.1->7.0 upgrade procedure.
14:17 jobewan joined #fuel
14:32 ppradhan joined #fuel
14:42 ppradhan joined #fuel
15:03 e0ne joined #fuel
15:08 rmallah joined #fuel
15:09 rmallah how to change ephemeral_ceph: true to ephemeral_ceph: false post deployement?
15:09 rmallah of an openstack environment
15:17 mwhahaha I don't think you can change it after the fact
15:32 Wida joined #fuel
15:33 blahRus joined #fuel
15:33 jerrygb joined #fuel
15:50 fedexo joined #fuel
16:18 lanakars joined #fuel
16:19 scolby joined #fuel
16:22 neilus1 joined #fuel
16:34 rlljorge Damjanek: I have the plugin zabbix monitoring installed in 6.1, Can i upgrade to 7.0 with this plugin installed ?
16:39 az joined #fuel
16:52 rlljorge I have the plugin zabbix monitoring installed in 6.1, Can i upgrade to 7.0 with this plugin installed ?
16:56 scolby left #fuel
17:01 Damjanek rlljorge: I think you should be able to do that. But keep in mind that monitoring data will be lost.
17:04 rlljorge Damjanek: Ok ! thanks
17:06 John__ joined #fuel
17:07 mohmultihouse joined #fuel
17:07 mohmultihouse hi!
17:14 mohmultihouse Okay, i get the following error in Fuel: Deployment has failed. Method granular_deploy. Inspect Astute logs for the details.
17:14 mohmultihouse Does anyone know what this can relate to?
17:24 Zer0BYte__ someone there
17:24 Zer0BYte__ ?
17:27 mwhahaha mohmultihouse: you'll have to look at the astute log to see what task failed and you may have to check the puppet error log on the node that fails to find out what happened
17:27 mwhahaha Zer0BYte__: what's up?
17:27 Zer0BYte__ hey mwhahaha
17:27 Zer0BYte__ how are u
17:27 mwhahaha pretty good, yourself?
17:28 Zer0BYte__ cool getting ready for vacations
17:28 Zer0BYte__ lol
17:28 mwhahaha :D
17:28 mohmultihouse I find it very hard to read the puppet and astute logs, can you help me if i upload the logs?
17:28 mwhahaha mohmultihouse: yes
17:28 Zer0BYte__ qustion
17:28 Zer0BYte__ fuel by default have turned off cpu overcommit and memory overcommit right?
17:29 mwhahaha i don't think so
17:29 mwhahaha i'd have to check
17:29 Zer0BYte__ well on configuration file
17:29 Zer0BYte__ #cpu_allocation_ratio=16.0
17:29 Zer0BYte__ at nova.conf
17:32 Zer0BYte__ rrghrhrghrgrh my nuts will going to explode lol
17:32 Zer0BYte__ i cant make it work the overcommitment
17:32 mwhahaha gimme a minute to look for you
17:34 mwhahaha so 16 is the default and if that's commented out we're using the default
17:34 Zer0BYte__ oh
17:34 Zer0BYte__ wb memory commitment
17:35 Zer0BYte__ #dynamic_memory_ratio=1.0
17:35 mwhahaha pretty sure that's the default as well but i'm looking now
17:36 Zer0BYte__ i enable dynamic_memory_ratio=2.0
17:36 Zer0BYte__ im using windows vms .. I know i know its really sucks lol
17:37 mwhahaha are you running into issues where there are no available hosts or something?
17:37 Zer0BYte__ yes
17:37 mwhahaha there is this message from the mailing list, http://lists.openstack.org/pipermail/openstack-dev/2015-January/054652.html
17:38 mwhahaha where it seems to indicate that they didn't take that setting into account for scheduling
17:38 mwhahaha that setting seems to be be more related to hyper-v
17:39 Zer0BYte__ i want to cry
17:39 Zer0BYte__ jhahah
17:39 mwhahaha http://docs.openstack.org/openstack-ops/content/compute_nodes.html#overcommit
17:40 mwhahaha ram_allocation_ratio is the setting you want
17:42 Zer0BYte__ are u sure
17:42 Zer0BYte__ its confuse
17:42 Zer0BYte__ http://www.sebastien-han.fr/blog/2012/09/22/openstack-memory-overcommit/
17:47 mohmultihouse @mwhahaha logs still processing 😉
17:47 Zer0BYte__ im add this and enable ram_allocation_ratio
17:51 Zer0BYte__ if i check top
17:51 Zer0BYte__ the memory its complety free
17:51 Zer0BYte__ exist any manual way  to execute nova-scheduler
17:51 Zer0BYte__ ?
17:55 Zer0BYte__ no result
17:58 Wida joined #fuel
17:59 Zer0BYte__ exist any way to know
17:59 Zer0BYte__ what exactly the vm its not created
17:59 Zer0BYte__ instead of "not available hosts"
18:00 Zer0BYte__ nova.compute.resource_tracker [req-3c456b76-2801-472d-bf0d-bd39c98dbd3b - - - - -] Total usable vcpus: 4, total allocated vcpus: 4
18:00 Zer0BYte__ maybe its my problem?
18:05 Wida joined #fuel
18:06 mwhahaha yea that'd be a problem
18:07 mwhahaha but i would think the cpu_allocation_ratio would cover that
18:07 mwhahaha i'm not a nova person so i'm not sure how that specifically works
18:09 Zer0BYte__ lol
18:09 Zer0BYte__ well
18:09 Zer0BYte__ i saw the problem are not the procesors
18:09 Zer0BYte__ its the ram
18:10 Zer0BYte__ hosts really have the free ram
18:10 Zer0BYte__ i saw on top
18:10 Zer0BYte__ but openstack dont care about it
18:10 Zer0BYte__ lol
18:15 adanin_ joined #fuel
18:26 mwhahaha there is a reserved amount
18:26 mwhahaha not that you should be messing with that
18:26 e0ne joined #fuel
18:35 rlljorge I cannot open http://seed.fuel-infra.org/fuelweb-community-release/fuel-community-7.0-upgrade.tar.lrz.torrent?from=landing the link is broken ?
18:48 mwhahaha rlljorge: no i was able to open that
18:51 jerrygb joined #fuel
18:57 mugleeta joined #fuel
18:58 vsedelnik joined #fuel
19:10 John__ question for the #fuel group: is there a URL pertaining to customizing a FUEL installation to include DNS and NTP Services and be able to deploy slight changes pertaining to geogrphical different areas? Interested in deploying FUEL on a KVM Guest
19:18 mwhahaha John__: You can specify the dns/ntp services for a specific environment...
19:21 mohmultihouse @mwhahaha still processing the logs, is something wrong?
19:21 mwhahaha if you have a lot of logs it may take a while
19:24 Wida joined #fuel
19:32 vsedelnik joined #fuel
19:41 rlljorge what the correct procedure to upgrade from 6.1 to 7.0 this https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#upgrading-and-updating-from-earlier-releases or https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#upgrade-environment-experimental ?
19:42 mwhahaha the first is the fuel upgrade steps, the second is if you wanted to try and upgrade a deployed environment
19:45 adanin joined #fuel
19:47 rlljorge mwhahaha: Ok ! now I understand ... So upgrade deployed environment is a experimental feature ? Not ready for the production ?
19:51 mwhahaha yes
20:06 Wida joined #fuel
20:28 HeOS joined #fuel
20:29 Wida joined #fuel
20:31 fuel-slackbot joined #fuel
20:36 adanin_ joined #fuel
20:47 JoeStack joined #fuel
21:10 jerrygb joined #fuel
21:39 mugleeta joined #fuel
22:07 xarses joined #fuel
22:08 xarses joined #fuel
22:09 xarses joined #fuel
22:09 xarses joined #fuel
22:24 jerrygb joined #fuel
22:53 JoeStack joined #fuel
23:02 vsedelnik joined #fuel
23:40 jerrygb joined #fuel
23:44 xarses joined #fuel
23:49 xarses joined #fuel
23:50 xarses joined #fuel
23:57 xarses_ joined #fuel
23:59 xarses joined #fuel

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