Open Stack

On 17 March 2014 10:32, Steve Baker <sbaker at redhat.com> wrote:
> On 17/03/14 10:14, Robert Collins wrote:
>> On 17 March 2014 09:20, Steve Baker <sbaker at redhat.com> wrote:
>>
>>> It looks like the cert files you want to transfer are all ascii rather than
>>> binary, which is good as we have yet to implement a way to attach binary
>>> data to a heat stack create call.
>>>
>>> One way to write out these files would be using cloud-config. The
>>> disadvantages of this is that it is boot-time config only, so those keys
>>> couldn't be updated with a stack update. You would also be consuming a
>>> decent proportion of your 16k user_data limit.
>> I'm confused - why can't we include them in the template? We include
>> an SSH key in ascii form already with no issue.
>>
> You can include them in the template. That template snippet shows how to
> specify cloud-config in the template. However I would recommend just
> going with the os-apply-config templates (the second option in that
> email). I probably shouldn't have mentioned cloud-config as an option at
> all.

Righto - thats what I meant. Shove it in heat, pull it out in heat
metadata, apply via o-a-c.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud