Feng Ruohang

What about using a series of a predefined files instead of if-else templates. Just like `pg_conf`? And we may get a list of combinations such as : * centos7 *...

brilliant idea. so we got one template file for each OS Name. and distinguish different repos by `os_major_build` & `os_region`. What if we make os_name & os_major_build as config parameters....

当 `vip_mode: l2' 时，`service` role中 会为集创建一个 L2 VIP。 使用前提条件是，集群位于同一二层网络中。

Sorry for keeping you waiting. I'm available for local testing and validating in 2 days. It looks great since the default configuration file works perfectly. I wonder if there could...

e.g a config template file in https://github.com/Vonng/pigsty/blob/master/files/conf/pigsty-dcs3.yml which enables all security features by default? :D

I made some modifications to ca & certs [refactor role ca](https://github.com/Vonng/pigsty/commit/372a364535019f12b3c8571771a32a1d693e3f45) * now ca are execute on meta nodes only * generate self-signed ca on primary meta node (meta_ip) *...

That would be great and thank you, (I'm still occupied by some chores >_

Thanks for your feedback. It is a reasonable feature (though I didn't use that in production...) I'll try adding some sort of basic ssl support in next minor release. >...

* That really make sense. I think using ascii characters instead in next release is a good idea. * There's a docker image since v0.5, so I guess embeded configuration...

That would be a great feature for testing & introspection. Maybe I could have some draft implementation in next release