<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 1:54 PM, Clint Byrum <span dir="ltr"><<a href="mailto:clint@fewbar.com" target="_blank">clint@fewbar.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts from Mark Washenberger's message of 2014-01-30 12:41:40 -0800:<br>
<div class="im">> On Wed, Jan 29, 2014 at 5:03 PM, Zane Bitter <<a href="mailto:zbitter@redhat.com">zbitter@redhat.com</a>> wrote:<br>
</div><div class="im">> > (I'm not touching the question of whether Heat should have a Glance Image<br>
> > resource at all, which I'm deeply ambivalent about.)<br>
> ><br>
><br>
> Maybe I'm just missing the use case, but it seems like modeling anything<br>
> Glance-y in Heat doesn't quite make sense. If at all, the dependency would<br>
> run the other way (model heat-things in glance, just as we presently model<br>
> nova-things in glance). So I think we're in agreement.<br>
><br>
<br>
</div>I'm pretty sure it is useful to model images in Heat.<br>
<br>
Consider this scenario:<br>
<br>
<br>
resources:<br>
  build_done_handle:<br>
    type: AWS::CloudFormation::WaitConditionHandle<br>
  build_done:<br>
    type: AWS::CloudFormation::WaitCondition<br>
    properties:<br>
      handle: {Ref: build_done_handle}<br>
  build_server:<br>
    type: OS::Nova::Server<br>
    properties:<br>
      image: build-server-image<br>
      userdata:<br>
        join [ "",<br>
          - "#!/bin/bash\n"<br>
          - "build_an_image\n"<br>
          - "cfn-signal -s SUCCESS "<br>
          - {Ref: build_done_handle}<br>
          - "\n"]<br>
  built_image:<br>
    type: OS::Glance::Image<br>
    depends_on: build_done<br>
    properties:<br>
      fetch_url: join [ "", ["http://", {get_attribute: [ build_server, fixed_ip ]}, "/image_path"]]<br>
  actual_server:<br>
    type: OS::Nova::Server<br>
    properties:<br>
      image: {Ref: built_image}<br>
<br>
<br>
Anyway, seems rather useful. Maybe I'm reaching.<br></blockquote><div><br></div><div>Perhaps I am confused. It would be good to resolve that.</div><div><br></div><div>I think this proposal makes sense but is distinct from modeling the image directly. Would it be fair to say that above you are modeling an image-build process, and the image id/url is an output of that process? Maybe the distinction I'm making is too fine. The difference is that once an Image exists, you can pretty much just *download* it, you can't really do dynamic stuff to it like you can with a nova server instance.</div>
<div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>