Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-10-14

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

All times shown according to UTC.

Time Nick Message
00:15 sbog_ joined #fuel
00:54 eliqiao joined #fuel
01:05 EinstCrazy joined #fuel
01:08 lawrancejing joined #fuel
01:18 eliqiao joined #fuel
01:24 hezhiqiang joined #fuel
01:28 sbog_ joined #fuel
01:28 zhangjn joined #fuel
02:00 sbfox joined #fuel
03:17 rmoe joined #fuel
03:23 sbfox joined #fuel
03:24 sbog_ joined #fuel
03:37 sbog_ joined #fuel
03:47 az__ joined #fuel
04:36 cartik joined #fuel
04:52 cartik need help on instance level HA, are there any solutions available?
04:54 sbog_ cartik: shared file system + corosync & pacemaker, cause libvirtd doesn't have such functionality. Or using vmware as a hypervisor.
04:55 cartik sbog_, im looking for kvm hypervisor only, thanks
04:56 cartik are there any documentation available on shared file system corosync
04:57 sbog_ No, corosync + pacemaker used for application level HA. For FS level ha you should use some other solution, like glusterfs, lustre, drbd or something similar
05:09 cartik sbog_, all my instance are non ephemiral/ persistnace volume
05:09 cartik in such case do i need to look for FS
05:09 cartik will corosync and pacemaker do the job for me?
05:13 kozhukalov_ joined #fuel
05:19 sbog_ cartik: in case of persistence volumes - no, they won't, you will need to place distributed fs to volumes on your instances. If I remember right, cinder guys started work on shared volumes, but I don't know it state now.
05:21 cartik intresting, let me take a look @ shared volumes too
05:21 sbog_ Also, it highly depend on your HA application. If you want to work with some REST stuff and DB like galera - for some cases corosync and pacemaker can do your job. But if you want to support consistent FS for some random files - they definetely won't
05:22 eliqiao left #fuel
05:24 cartik ok
05:46 az__ joined #fuel
06:07 Miouge joined #fuel
06:20 Miouge joined #fuel
06:36 vsedelnik joined #fuel
06:37 xarses joined #fuel
06:45 neilus1 joined #fuel
06:54 mkwiek joined #fuel
06:57 mkwiek_ joined #fuel
06:58 subscope joined #fuel
07:24 sbfox joined #fuel
07:33 sbfox Cinder doenst support shared volumes, Manila is the shared filesystem openstack project. I think its pretty mature but isnt part of fuel. Alternatively you could run gluster between the nodes you want HA
07:46 hyperbaba joined #fuel
07:58 mojo joined #fuel
07:59 plasticnoise joined #fuel
08:26 bapalm joined #fuel
08:28 devvesa joined #fuel
08:30 zhangjn joined #fuel
08:33 neilus joined #fuel
08:35 vsedelnik joined #fuel
08:38 cartik joined #fuel
08:41 sbfox joined #fuel
08:43 alrick joined #fuel
08:51 mkwiek1 joined #fuel
08:52 adanin joined #fuel
08:54 subscope joined #fuel
08:56 zhangjn joined #fuel
09:00 macjack joined #fuel
09:01 subscope joined #fuel
09:17 HeOS joined #fuel
09:30 cartik joined #fuel
09:41 Miouge joined #fuel
09:46 pradiprw_ joined #fuel
10:14 vsedelnik joined #fuel
10:14 kozhukalov_ joined #fuel
10:20 vsedelnik joined #fuel
10:22 subscope joined #fuel
10:31 vsedelnik joined #fuel
10:44 kozhukalov_ joined #fuel
10:56 cartik joined #fuel
10:56 e0ne joined #fuel
10:57 cartik_ joined #fuel
11:00 cartik_ joined #fuel
11:23 cartik joined #fuel
11:37 EinstCrazy joined #fuel
11:37 zhangjn joined #fuel
11:42 vsedelnik joined #fuel
11:46 ddmitriev joined #fuel
11:57 subscope joined #fuel
12:14 lawrancejing joined #fuel
12:20 gongysh joined #fuel
12:24 neilus joined #fuel
12:40 vsedelnik joined #fuel
12:43 subscope joined #fuel
12:52 alrick joined #fuel
13:00 Miouge joined #fuel
13:19 subscope joined #fuel
13:29 evkonst joined #fuel
13:39 subscope joined #fuel
13:44 subscope joined #fuel
13:53 ppradhan joined #fuel
14:18 rgowrishankar joined #fuel
14:19 claflico joined #fuel
14:22 sbog_ joined #fuel
14:25 krogon_ joined #fuel
14:25 krogon__ joined #fuel
14:33 nihilifer joined #fuel
14:34 weihan joined #fuel
14:35 ppradhan When I configure public network on my nodes does it have to be Untagged? I did Tagged and having some issues
14:45 kozhukalov_ joined #fuel
14:50 alrick joined #fuel
15:08 sbfox joined #fuel
15:23 weihan joined #fuel
15:25 weihan joined #fuel
15:27 e0ne joined #fuel
15:46 vsedelnik joined #fuel
15:47 vsedelnik joined #fuel
15:47 kozhukalov_ joined #fuel
15:52 lanakars joined #fuel
15:52 sbog_ joined #fuel
16:17 karume joined #fuel
16:23 sbog_ joined #fuel
16:27 scolby joined #fuel
16:28 alrick joined #fuel
16:49 sbfox joined #fuel
16:49 e0ne_ joined #fuel
16:57 adanin joined #fuel
16:59 blahRus joined #fuel
16:59 bapalm joined #fuel
16:59 sigurdga joined #fuel
17:07 igorbelikov joined #fuel
17:07 jaypipes joined #fuel
17:07 prmtl joined #fuel
17:07 kozhukalov_ joined #fuel
17:08 omolchanov joined #fuel
17:08 xenolog13 joined #fuel
17:08 mwhahaha joined #fuel
17:09 dkaigarodsev joined #fuel
17:10 blahRus joined #fuel
17:10 bapalm joined #fuel
17:10 sigurdga joined #fuel
17:25 vsedelnik joined #fuel
17:43 Lyncos left #fuel
17:43 karume joined #fuel
17:51 thumpba joined #fuel
17:54 a_mac joined #fuel
18:20 e0ne joined #fuel
18:53 sbog_ joined #fuel
19:04 thumpba joined #fuel
19:12 wholetthestackou joined #fuel
19:25 HeOS joined #fuel
19:26 sergmelikyan joined #fuel
19:27 v1k0d3n joined #fuel
19:33 karume joined #fuel
19:47 xarses joined #fuel
19:49 vsedelnik joined #fuel
20:09 angdraug joined #fuel
20:26 vsedelnik joined #fuel
20:33 karume joined #fuel
21:05 thumpba joined #fuel
21:08 sbog_ joined #fuel
21:36 vsedelnik joined #fuel
21:36 sbog__ joined #fuel
21:43 willw joined #fuel
21:44 willw anyone have a link to something useful about fixing Instance Console with an error of Unable to resolve the server's DNS address.
21:44 sbog__ Yes
21:45 sbog__ Couple minutes, I'll find it
21:45 willw sweet
21:49 sbog__ Here, look on https://bugs.launchpad.net/fuel/+bug/1495466 - it contains problem and solution.
21:52 willw so what happens when replacing the public.fuel.local with the horizon IP doesnt work?
21:52 xarses you don't have a dns name for public.fuel.local in your resolver
21:53 willw nope
21:53 xarses if you did, that would work as well
21:53 willw hmmm
21:55 xarses also, if you disable TLS, then it won't be configured to use domain names and will send you IP address
21:55 willw ok I like that idea
21:55 willw im reseting the environment
22:10 xarses sbog__: I updated the bug, its a valid UX issue
22:13 sbog__ You propose to set public TLS hostname to blank value?
22:13 xarses yes
22:13 xarses user must set it to a value that is correct for them
22:13 willw I just unchecked both httpd and TLS
22:13 xarses sbog__: otherwise we have to add the page to the wizard
22:14 sbog__ hmm, @mihgen, what do you think about it? I know that you very sensitive to such kind of bugs
22:14 xarses eitherway we have to have the user see this value and set it (with the domain name)
22:15 sbog__ I also think that set default values which are wrong is also bad idea
22:16 sbog__ You can't create SSL certificate with blank CN, so we need place something into this field - or we MUST force user to do it by himself
22:16 mihgen we need to target for a production use case, so use FQDN / https
22:16 mihgen but let people know what problems they will have if they don't do fqdn
22:16 sbog__ It is what we do now
22:16 mihgen and suggest ugly possible solution
22:16 sbog__ Okay, I'll create documentation bug about it
22:17 mihgen like try this IP
22:17 mihgen ideally system should say that out loud
22:17 mihgen not to be hidden in 100 pages of docs
22:17 sbog__ Hmm, I'll think what we could do about it
22:21 mihgen sbog__: if we can't put a message in Horizon about it, then we must put it in Fuel success deployment message
22:21 mihgen so that guys, if you don't have DNS configured, you won't be able to access console of VMs using just IP
22:22 mihgen even though you will be able to connect to the horizon
22:22 sbog__ Yes, I writing comment in bug about it right now. Will schedule a talk with Vitaly about it.
22:22 mihgen thank you
22:25 xarses mihgen: no we need a fqdn to support proper CN. The field should be required, but with no default value
22:28 sbog__ @xarses: thereby we will ship master node with wrong default values
22:28 xarses wrong default values?
22:29 az__ joined #fuel
22:29 sbog__ If field will be blank - you cannot create valid certificate. So by default if user will try to deploy something without change any setting - it won't work.
22:30 xarses like i said, make the field required
22:30 xarses but empty by default
22:30 xarses that will make the settings page invalid and require the user to provide a value before they can save the page or deploy
22:31 sbog__ It cost high, as for me. How much required fields we have right now? One - for environment name, that's all?
22:32 xarses We can't just create a default here, the value is wrong for the end user, its only correct in CI
22:32 xarses the user must provide their own value
22:32 xarses and understand what / why they need to set it
22:32 sbog__ I suppose we could talk about it with other guys by schedule a meeting or by writing a letter to openstack-dev
22:33 xarses the user must be required to see the setting if tls is configured
22:33 xarses we either mess around with the setting (make it blank but value required) or add it to the wizard
22:34 sbog__ It means that he must be required every time - we ship TLS by default
22:34 xarses yes
22:34 xarses it needs to be configured every time
22:34 xarses a cluster is created
22:34 xarses because services use this name as responses
22:34 xarses the user must have this value configured or those services don't work
22:35 xarses using a default of public.fuel.local is just wrong
22:35 xarses their client will never have dns records for public.fuel.local
22:35 sbog__ They will, actually. Have something work and don't have proper access due to your own settings is different
22:36 sbog__ Their client will never have dns records for anything, actually
22:36 sbog__ We cannot suppose their settings
22:36 xarses which is why they need to configure this value, every time
22:36 xarses and why we can't make a default
22:37 sbog__ But it still costs much, as for me.
22:37 xarses it costs CI
22:37 xarses because it will need to configure a value
22:37 xarses otherwise it costs nothing
22:37 xarses deployment can't start without a value
22:37 xarses I don't want to allow empty values to cert generation
22:37 xarses I want to force the user to provide a value
22:40 sbog__ Okay, I'll schedule a meeting with UI guys to see what options we have to add such field to wizard. Will update bug after that (probably, it will happen tomorrow, cause most of UI is GMT+3)
22:40 xarses sbog__: yep, I understand
22:41 xarses Will you have an update by the time of the IRC meeting? I can put it on the agenda
22:43 sbog__ Which one of IRC's?
22:43 xarses fuel irc meeting tomorrow
22:44 sbog__ got it, weekly one. Yes, I will try to update before meeting
22:44 xarses ok
23:00 jobewan joined #fuel
23:17 zhangjn joined #fuel
23:38 sbog_ joined #fuel
23:43 xarses joined #fuel

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