On Tue, Nov 22, 2016 at 9:36 AM, Zane Bitter <[email protected]> wrote:
> On 18/11/16 16:56, Clint Byrum wrote: > >> Excerpts from Zane Bitter's message of 2016-11-18 14:24:43 -0500: >> >>> So, say that I want to create my servers in Heat so that I can use Heat >>> software deployments for orchestration. How would I go about e.g. making >>> sure that the servers are always connected to the networks I expect on a >>> variety of different clouds? Would Oaktree figure out the networks and >>> pass them in to the stack when creating it? (I don't believe shade has >>> Heat support yet, but we should definitely add it & I don't foresee any >>> great obstacle.) Or would Heat have to add Oaktree resource types? >>> >>> >> If you're wanting to use Heat, you are a) already cutting off a large >> quantity of interoperable clouds because many do not have Heat, >> > > (Roughly one third, according to the user survey.) We have a mechanism to > resolve that though (defcore), and I'm confident that that will happen in > due course. I'm less confident that we have any mechanism for resolving > these other questions. > > Perhaps we could use defcore-required Tempest tests to drive alignment on > some of those too. But we'd have to decide what we want to align on first. > > and b) >> you already have provider templates to deal with the inconsistencies >> across clouds. >> > > Indeed, and environment files and conditionals as well. > > And Shade has had Heat support in some for or another for a long time: >> >> 9922cfbb (Monty Taylor 2015-12-03 18:12:32 -0500 32)import >> heatclient.client >> > > Oh, great! I knew it had been on the agenda for a while but I didn't know > if it had actually happened or not, so I had a quick glance at > http://docs.openstack.org/infra/shade/model.html and there was no mention. > > Shade has decent heat support [1] which is behind the os_stack module available in Ansible 2.2 [2] My personal workflow involves a lot of ansible playbooks creating/updating heat stacks then doing other things, and having the os_stack module has made this much cleaner. [1] http://docs.openstack.org/infra/shade/usage.html#shade.OpenStackCloud.create_stack etc [2] https://docs.ansible.com/ansible/os_stack_module.html
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
