Open Stack

A stack template defines a set of resources like VMs, networks, router..
and the relationship between them. You can create an entire cloud
 infrastructure using a template. When creating a stack these resources
will be created so that you dont need to create them individually. Suspend
means , the instances mentioned in the template will be suspended.
Similarly instances will be paused and resumed when stack is paused and
resumed respectively. Change stack template is for changing the
infrastructure created with the template, like upgrading the instances
flavour used in it.

I do not understand your second question about re running the stack.

Are you trying to create stacks using python API?

On May 14, 2017 6:02 PM, "Amit Uniyal" <auniyal61 at gmail.com> wrote:

> `Hi all,
>
> I guess I understood how heat create works. and also the meaning of
> options [ suspend, resume, check stack, change stack template ].
>
> So now whole stack is a single object.
>
> I am trying to use os_client_config to create heat stack as:
>
> *heat = os_client_config.make_client('orchestration')*
>
> now heat object has a function create_stack(**kwargs)
>
>
> I tried to use it as:
>
> template = {
>
> 'description': 'network and instances',
>  'heat_template_version': '2015-10-15',
>  'resources': {'net-a': {'properties': {'name': 'network-a'},
>    'type': 'OS::Neutron::Net'}}
>
> }
>
>
> *stack = heat.stacks.create(**template)*
>
> it throws error as  ERROR: No stack name specified
>
> so I added new key as *template.update({'stack_name': 'stack-a'})*
>
> and this time I got error as ERROR: No template specified
>
>
> what would be the proper procedure to launch stack by os_client_config.
>
>
>
>
> Regards
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Thu, May 4, 2017 at 5:53 PM, Amit Uniyal <auniyal61 at gmail.com> wrote:
>
>> Hi all,
>>
>> Please help with heat service, the only example I could find is to create
>> new stack. But how to use existing stack template which is already stored
>> by orchestration service.
>>
>> My understanding is we need to form/write a .yaml template and create new
>> stack by this template. It saves this template on orchestration and run the
>> template. According to template VMs will get launch (or other tasks) and it
>> should be finished. then whats the meaning of options [ suspend, resume,
>> check stack, change stack template ].
>>
>> How can we rerun the same template without form/creating new stack in
>> openstack.
>>
>>
>> Thanks and Regards
>>
>>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170514/488babc4/attachment.html>