Looks good to me too! Chris Dell
-----Original Message----- From: crowbar-bounces On Behalf Of Terpstra, John Sent: Wednesday, July 03, 2013 8:56 AM To: [email protected]; crowbar Subject: Re: [Crowbar] Adding a public hostname attribute to each node LGTM. - John T. John H Terpstra Cloud Services Architect, Senior Principal Engineer Enterprise Solution Group +1 512 900-1654 | [email protected] -----Original Message----- From: crowbar-bounces On Behalf Of Vincent Untz Sent: Wednesday, July 03, 2013 7:32 AM To: crowbar Subject: Re: [Crowbar] Adding a public hostname attribute to each node Le mercredi 03 juillet 2013, à 07:24 -0500, [email protected] a écrit : > Vincent, > > How would $PUBLIC_HOSTNAME be set? Would this be a new field exposed in the > node edit screen? Would it be defaulted to anything? Yes, it would be a new field exposed there. There would be no default, so no change compared to current behavior. Vincent > > Thanks, > > Chris > > > -----Original Message----- > From: crowbar-bounces On Behalf Of Vincent Untz > Sent: Wednesday, July 03, 2013 4:12 AM > To: crowbar > Subject: [Crowbar] Adding a public hostname attribute to each node > > Hi, > > (this is for pebbles) > > Currently, we have nice automatic DNS entries created in bind on the admin > node for the different nodes. This means that we get, for instance, a > public.d52-54-00-fa-12-cb.$domain DNS entry for the d52-54-00-fa-12-cb. > > However, in the past, with SUSE Cloud 1.0, we realized that these DNS entries > were not always published externally and that, therefore, they cannot always > be relied on. > > This is not necessarily a big deal, except that with SSL support that we're > adding, we will want to change the endpoints registered in keystone to use > hostnames instead of IP addresses. The reason for that is simply that SSL > certificates are usually associated to hostnames, not IP addresses, and so we > want that to have the validation work fine. > > What we did in SUSE Cloud 1.0 was to add an optional attribute to each node, > which is the public hostname of the node. Simply put, this is the DNS entry > that is published externally; some people do that manually. So when this is > available, we would use $PUBLIC_HOSTNAME instead of > public.d52-54-00-fa-12-cb.$domain as endpoint. (And when no SSL is used, we > keep using the IP address for the endpoint, since that won't cause any issue > in that case). > > It's really a trivial patch to barclamp-crowbar, and then updating each > openstack barclamp registering endpoints to use that. > > Any objection? > > Vincent > > -- > Les gens heureux ne sont pas pressés. > > _______________________________________________ > Crowbar mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/ > > _______________________________________________ > Crowbar mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/crowbar > For more information: http://crowbar.github.com/ > -- Les gens heureux ne sont pas pressés. _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
