e-12-15 2:22 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Discuss
configurable-coe-api-port Blueprint
Thanks for raising this for discussion. Although I do think that the
API port humber should be expresse
Thanks Adrian. Sounds good.
Best regards,
Hongbin
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: June-13-15 2:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port
Blueprint
Hongbin,
Good use
ailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port
Blueprint
Thanks for raising this for discussion. Although I do think that the API port
humber should be expressed in a URL that the local client can immediately use
for connecting a na
usage questions)
Subject: Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port
Blueprint
Thanks for raising this for discussion. Although I do think that the API port
humber should be expressed in a URL that the local client can immediately use
for connecting a native client to the
Egor makes a good point. If we have the API port number on the Baymodel, and
Magnum sets the api_address value to a URL that contains the correct protocol,
address, and port for the native API service. Here is the blueprint for that:
https://blueprints.launchpad.net/magnum/+spec/magnum-api-addre
Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: 06/11/2015 01:17 PM
Subject: Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port
Blueprint
I think that we have a similar bp before:
https://bluepri
u are miracle!
From: Jay Lau
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 06/11/2015 01:17 PM
Subject: Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port
Blueprint
I think that we have a similar b
Kai,
+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-nameserve
I think that we have a similar bp before:
https://blueprints.launchpad.net/magnum/+spec/override-native-rest-port
I have some discussion before with Larsks, it seems that it does not make
much sense to customize this port as the kubernetes/swarm/mesos cluster
will be created by heat and end user
