Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-09-03

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

All times shown according to UTC.

Time Nick Message
00:01 emagana joined #fuel
00:04 ianunruh and I'm not sure where to go from there
00:18 rmoe joined #fuel
00:45 harybahh joined #fuel
01:08 xarses joined #fuel
04:07 ArminderS joined #fuel
04:30 Ch00k joined #fuel
04:34 xarses joined #fuel
04:45 harybahh joined #fuel
05:46 ToTsiroll joined #fuel
05:48 ToTsiroll Hi, anyone here knows what are the steps to cover when changing my floating ip pool including the IPs given to my baremetal servers? My external IP pool are the floating IPs for my VMs. Now, my ISP is requesting for a change of IP pools since we are drafting a new contract.
05:49 ToTsiroll I'm just making sure I cover all the steps in changing the whole floating ip pool in my cloud.
05:49 kupo24z joined #fuel
05:50 ddmitriev1 joined #fuel
06:12 adanin joined #fuel
06:44 tuvenen joined #fuel
06:46 harybahh joined #fuel
07:06 dancn joined #fuel
07:17 kaliya ToTsiroll: on which networking model?
07:17 getup- joined #fuel
07:18 ToTsiroll Nova-Network VLAN
07:19 e0ne joined #fuel
07:20 kaliya ToTsiroll: according to our blueprint https://blueprints.launchpad.net/fuel/+spec/changes-after-deployment unfortunately there is no way, at the very present
07:20 pasquier-s joined #fuel
07:24 ToTsiroll but can i do this manually? or is it a recommendation that I just backup everything and redeploy to the new settings
07:24 ToTsiroll I understand that the IP pool is all over the configs (e.g. haproxy, .confs of all the services, floating ip for clusters)
07:26 kaliya ToTsiroll: right, you should backup and redeploy
07:29 ToTsiroll oooh...i thought there was a way manually much like a tenant's network where its just a CLI command
07:38 e0ne joined #fuel
07:45 harybahh joined #fuel
07:46 HeOS joined #fuel
07:52 harybahh hello, I would like to define starting address for management and storage networks and not let Fuel determine the first IP address of the network address define in the interface
07:53 harybahh is there a way to set starting addresses or define addresses in the astute.yaml and apply to the whole environnement ?
08:01 harybahh_ joined #fuel
08:01 Ch00k joined #fuel
08:07 kaliya harybahh_: I am looking, please wait :)
08:09 harybahh_ thanks kaliya :)
08:10 harybahh_ in fact I don't find a way to work manually on environnement astute.yaml on the fuel master and apply the changes
08:10 harybahh_ i'm a bit lost with dockers also :)
08:12 kaliya harybahh_: what happens with docker?
08:13 harybahh_ i don't understand how files are separated between the host and the container
08:14 hyperbaba helo there
08:14 hyperbaba I have a problem with api call to get quota information on 5.0
08:14 kaliya harybahh_: docker allows us to cointainarize services
08:14 harybahh_ is astute.yaml file for the openstack env I want to deploy present and the fuel master node ?
08:15 harybahh_ *on
08:15 hyperbaba I have a problem with api call to obtain quota info on 5.0. The query is :
08:15 harybahh_ I find it on openstack nodes (/etc/astute.yaml), but how to change some values (storage and management address plan) and apply them ?
08:16 hyperbaba http://A.B.C.D:8774/v2/9e3d61ba44164417a1063d22ca4dc67c/os-quota-sets/ac73c49114d247d9ba77a5105d472016
08:16 harybahh_ didn't find any options in the fuel cli
08:17 hyperbaba the response is :  "The server could not comply with the request since it is either malformed or otherwise incorrect."
08:18 hyperbaba the first hash is from admin, the second is tenant
08:18 kaliya hyperbaba: for the mgmt network settings, please look here http://docs.mirantis.com/openstack/fuel/fuel-5.0/user-guide.html#configuring - there are some CLI options for networks. You can download, modify the YAML and then upload to nailgun
08:19 kaliya there is specified the IP range
08:19 ArminderS kaliya: that shall be for harybahh_, not hyperbaba
08:20 kaliya harybahh_: for the mgmt network settings, please look here http://docs.mirantis.com/openstack/fuel/fuel-5.0/user-guide.html#configuring - there are some CLI options for networks. You can download, modify the YAML and then upload to nailgun
08:20 kaliya thanks ArminderS
08:20 ArminderS sure no worries, they both kindda look similar, I can understand :)
08:21 harybahh_ thank kaliya, how to uplaod and apply YAML changes?
08:22 harybahh_ in some documentation the astute command is used but I can't find it my fuel master
08:22 harybahh_ we have to work with fuel cli now exclusively ?
08:22 kaliya harybahh_: you go with `fuel --env 1 network download`, edit the file, and `fuel --env 1 network upload` should work
08:23 harybahh_ oki !
08:23 harybahh_ i'll try that
08:23 kaliya harybahh_: I reccomend using `fuel` :)
08:23 harybahh_ thank you ! :)
08:26 ddmitriev joined #fuel
08:38 Longgeek joined #fuel
08:53 Longgeek joined #fuel
09:05 DaveJ__ joined #fuel
09:27 Longgeek joined #fuel
09:31 geekinut1h joined #fuel
09:41 e0ne joined #fuel
10:09 adanin joined #fuel
10:32 Longgeek joined #fuel
10:32 ddmitriev joined #fuel
10:36 Longgeek_ joined #fuel
10:39 e0ne joined #fuel
10:58 getup- joined #fuel
11:42 harybahh joined #fuel
11:51 harybahh hello again
11:52 harybahh I tried what kaliya told me about downloading network YAML file, modify the IP range for mgmt and storage networks, then uploaded the configuration
11:52 harybahh but if I download again or deploy the environnment, Fuel doesn't take my changes
11:52 harybahh any hint ?
11:54 Longgeek joined #fuel
11:54 Longgeek_ joined #fuel
12:00 mattymo harybahh, you have to upload your modified yaml
12:01 harybahh yep, did it
12:01 harybahh fuel network --env 15 -d
12:01 harybahh Network configuration for environment with id=15 downloaded to /root/network_15.yaml
12:02 harybahh I modify the yaml file with vi, IP ranges for mgmt and storage
12:03 harybahh fuel --env 15 network --upload --dir /root/
12:04 harybahh but when I redownload network conf, changes are not applied
12:05 rsFF joined #fuel
12:05 pasquier-s joined #fuel
12:06 rsFF joined #fuel
12:30 Longgeek joined #fuel
12:34 e0ne joined #fuel
12:34 kaliya harybahh: which Fuel version are you working on?
12:48 harybahh I as looking for updates, I'm with a 5.0 build_id: 2014-05-27_05-51-41
12:48 harybahh I'll try the last one
13:07 kaliya joined #fuel
13:42 Ch00k joined #fuel
13:44 mattgriffin joined #fuel
13:45 harybahh joined #fuel
13:50 e0ne joined #fuel
13:58 e0ne joined #fuel
13:59 mpetason joined #fuel
14:07 manashkin_ joined #fuel
14:12 manashkin_ ToTsiroll: With Nova-Network you'll be able to add new floating IP pool and then, remove the floating IPs from the obsolete segment. http://docs.openstack.org/admin-guide-cloud/content/nova-associate-public-ip.html
14:14 manashkin_ ToTsiroll: And you still have to change the host floating IPs manually, alongside with configuration files.
14:22 manashkin_ hyperbaba: Please remove admin hash from your request. Anyway, only admin may manage quotas. http://docs.openstack.org/api/openstack-compute/2/content/os-quota-sets.html
14:42 jobewan joined #fuel
14:50 ianunruh anyone know how to add extra packages to the fuel master for use by the nodes?
14:50 ianunruh need to install some dependencies for my monitoring tools
14:57 harybahh joined #fuel
14:58 angdraug joined #fuel
15:06 ianunruh I could add the usual ubuntu sources to my /etc/apt/sources.list, but that probably would cause all sorts of version issues
15:06 xarses joined #fuel
15:10 evg ianunruh: https://help.ubuntu.com/community/Repositories/Personal here is about personal repo
15:12 ianunruh evg: thanks, I was hoping not to have to setup a separate repo, but it's looking like the easiest way
15:12 evg ianunruh: but if you used repos for 12.04 ubuntu I think you woldn't get version problems
15:12 xarses joined #fuel
15:13 evg ianunruh: no, the easiest one is using ubuntu repo
15:29 blahRus joined #fuel
15:38 ianunruh thanks, you were right, the standard ubuntu repos do not conflict
15:43 adanin joined #fuel
15:49 emagana joined #fuel
15:55 emagana joined #fuel
16:03 meow-nofer__ joined #fuel
16:04 aedocw joined #fuel
16:05 rmoe joined #fuel
16:05 obcecado joined #fuel
16:06 ianunruh_ joined #fuel
16:07 ganso_ joined #fuel
16:07 Llew_ joined #fuel
16:09 warpc__ joined #fuel
16:14 mattgriffin joined #fuel
16:39 angdraug joined #fuel
16:59 emagana joined #fuel
17:05 emagana joined #fuel
18:10 e0ne joined #fuel
18:11 kaliya_ joined #fuel
18:11 ddmitriev1 joined #fuel
18:35 emagana joined #fuel
18:36 emagana joined #fuel
19:05 e0ne joined #fuel
19:13 angdraug joined #fuel
19:19 e0ne joined #fuel
19:46 angdraug joined #fuel
20:04 kaliya__ joined #fuel
20:20 HeOS joined #fuel
20:43 emagana joined #fuel
21:00 emagana joined #fuel
21:06 adanin joined #fuel
21:10 emagana_ joined #fuel
21:13 emagana joined #fuel
21:16 emagana_ joined #fuel
21:26 xarses joined #fuel
21:49 emagana joined #fuel
22:11 emagana joined #fuel
22:13 xarses joined #fuel
22:32 kupo24z xarses: I already have an existing puppetmaster server, is there any way to run manifests from that machine or will it conflict with the Fuel stuff?
22:34 xarses we dont use puppet-master, so yes and no
22:35 xarses yes you could possibly use another server, but it won't really give you any value
22:36 xarses kupo24z: ^
22:41 kupo24z How would it not gain any value? I would be using it for ensuring configuration files/packages are setup correctly outside of what fuel does
22:42 emagana joined #fuel
22:44 xarses because we don't use the master, and re-run puppet while changing /etc/astute.yaml you may not have all of the roles applied that should be
22:45 xarses it's also verry slow to resolve the resource graph
22:45 xarses it was taking about 2-3 min for each node we added to the puppet master when we last had one (3.0.1)
22:47 kupo24z Hmm, okay
22:48 xarses its also possible that some parts of the manifest are not idempotent
22:49 kupo24z I guess ill just stick with manual scripts then
22:50 kupo24z So this Neutron DVR BP, wont it conflict with removing public addressing from compute deployments?
22:52 kupo24z https://blueprints.launchpad.net/fuel/+spec/neutron-dvr-deployment
22:57 xarses it will put them back, yes. But in that case they are needed
22:57 xarses the public addresses still won't be on storage / ceph / roles
23:32 emagana joined #fuel
23:36 emagana_ joined #fuel

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