[Openstack-operators] How do you orchestrate external tools (private cloud) ?

2016-01-12 Thread gilles . mocellin 

Hello,

I think it will be great to know how operators handle theses kind of 
orchestration :

Add, remove instances and there properties in theses SI tools :
- IPAM
- CMDB
- Monitoring
- Backup

I understand that this use case is certainly specific to private cloud, 
not public ones.


I will be so happy not to rely on an external orchestrator (from an 
OpenStack poit of view).

But I did not find any example where Heat can do these sort of thing.

For the moment, We start to use RunDeck, but I don't like the fact that 
we must use a workflow to create an instance.
If we use OpenStack Directly, we cannot handle constraints we have an 
system names and IPs : two IP addresses by instances, which are 
pre-allocated in our "IPAM" (IPPlan).


The only way I see to be able to use standard OpenStack CLI and API, is 
to handle that orchestration at instance startup.

Which is not easy, mainly if the network configuration must be handled.
There's always possibilities, like :
- a first boot with standard OpenStack DHCP
- a network config handled by cloud-init and/or a configuration 
management system
- reboot in the final good state (but Neutron config like ports will not 
be in sync)



So, how do you orchestrate beside OpenStack ?
Do you abandon OpenStack API compatibility for an orchestrator's one ?
Is there something I haven't seen in Heat ?

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] How do you orchestrate external tools (private cloud) ?

2016-01-12 Thread gilles . mocellin 

Le 2016-01-12 11:01, Christian Berendt a écrit :

On 01/12/2016 10:47 AM, gilles.mocel...@nuagelibre.org wrote:

But I did not find any example where Heat can do these sort of thing.


I think Heat is the wrong tool to directly orchestrate external 
services.


Have you tried Mistral? It is a workflow service or task orchestration
service. Some examples are available in the mistral-extra repository.
E.g.
https://github.com/openstack/mistral-extra/tree/master/examples/v2/services_registration
demonstrates how to create a new instance and how to register this
instance at an external monitoring service (zabbix) and at an external
firewall service (vyatta). Mistral is very powerful and you can do a
lot of cool things with it.

Mistral resources are available for Heat
(http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Mistral::Workflow),
this way it is possible to orchestrate external services with Heat by
using Mistral resources.

HTH, Christian.


Thanks for pointing at Mistral.
I already have read about it, but never really look into it. I will.

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators