[openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

Egor Guz EGuz at walmartlabs.com
Thu Jun 11 05:22:17 UTC 2015


+1 for add it to baymodel, but I don’t see many use cases when people need to change it. And if they really need to change it they can always modify heat template.
-1 for opening it just for admins. I think everyone who create a model should be able specify it the same way as dns-nameserver for example.


From: Kai Qiang Wu <wkqwu at cn.ibm.com<mailto:wkqwu at cn.ibm.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, June 10, 2015 at 18:35
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

I’m moving this whiteboard to the ML so we can have some discussion to refine it, and then go back and update the whiteboard.


@Sdake and I have some discussion now, but may need more input from your side.

1. keep apserver_port in baymodel, it may only allow admin to have (if we involved policy) create that baymodel, have less flexiblity for other users.

2. apiserver_port was designed in baymodel, if moved from baymodel to bay, it is big change, and if we have other better ways. (it also may apply for
other configuration fileds, like dns-nameserver etc.)


Best Wishes,
Kai Qiang Wu (吴开强  Kennan)
IBM China System and Technology Lab, Beijing

E-mail: wkqwu at cn.ibm.com<mailto:wkqwu at cn.ibm.com>
Tel: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
        No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193
Follow your heart. You are miracle!

More information about the OpenStack-dev mailing list