I am using Foreman for deployment of multiple instances of test-platforms
for test and integration purposes. My typical platform consists of 14
heavily inter-dependent applications and every team needs its own
test/integration copy. Foreman helps me a lot: i scripted my deployment, so
i can create an environment from scratch by demand in no time.
There are 2 things that would be extremely helpful for me, and i wonder if
there any plans for that:
Users and Quotas
I would really like to give my users (developers and integrator) more
freedom, or even propose a self-service. But still it would be great to
limit them with some quotas.
Management of Hosts in Platform (Environment)
In OpenStack there is a cool project called Heat<https://github.com/openstack/heat>.
Basically it takes a YAML file that describes a number of Hosts in a
Platform. You need to specify all your hosts and Heat will create them one
by one. Simple and stupid. I would really love to have some thing like this
in Foreman GUI, so i could create a Platform as easy as I create single
Host now.
> 1. Users and Quotas
> I would really like to give my users (developers and integrator) more
> freedom, or even propose a self-service. But still it would be great to
> limit them with some quotas.
Right, one solution of that is to use oVirt virtualization project which
allows you to define quotas and Foreman can work with them to some
degree (you can select quotas when provisioning).
Unfortunately we do not provide any quotas in the Foreman itself. But we
have this feature request. Just vote it up, or even better provide us
some former descriptions with more ideas. Currently this is not our
priority.
> 2. Management of Hosts in Platform (Environment)
> In OpenStack there is a cool project called Heat<https://github.com/openstack/heat>.
> Basically it takes a YAML file that describes a number of Hosts in a
> Platform. You need to specify all your hosts and Heat will create them one
> by one. Simple and stupid. I would really love to have some thing like this
> in Foreman GUI, so i could create a Platform as easy as I create single
> Host now.
We do not support Heat itself, but folks are implementing orchestration
engine called Dynflow and OpenStack installer Staypuft which do provide
similar. It will be integrated with Foreman. It has very similar use
case, so take a look on it.
Note this is early stage of development, but if you ask on this list (or
better foreman-dev) we will provide you with answers. The plan is to
orchestrate (OpenStack) deployments from the Foreman GUI. And this is
real code, not just on a paper:
You can build your own Actions and Plans, we would love to hear some
feedback.
