Hi Vladimir,
You could do that with Vagrant as well. Vagrant has providers e.g. for different cloud services, for local vm hosts like virtualbox or vmware or lxc, but also for managed servers (i.e. bare-metal / no VMs).
The advantage is that you can use the same descriptor (Vagrantfile) and the same cli tools (vagrant up, etc) for local, cloud and bare metal deployments.
Works well for simple deployments, e.g. few VMs, no autoscaling, etc..
Cheers,
Torben
Can I use spiceweasel for admin a localnet services or it is a overkill and spiceweasel is for deploy applications to production servers in a cloud for customer ?
I want to describe our network service i an one file, as is in spiceweasel infrastructure.yml.
And after that I want to manage our servers and virtual containers (lxc) with spiceweasel separately.
For example:
Create an lxc container1 on server1, bootstrap node with my recipes.
Delete an lxc container2 on server2, remove all about this node from chef-server
and etc actions, which is needed in real sysadmin life's
That is managed servers (most of all - virtual containers) and a bare metal linux servers and developers desktops with ubuntu.
Most of all I planned to use it for manage containers and servers instead of deplay insrastructure in a cloud.
What do you think ?
On the other hand I know about lxc cookbook and appropriate knife plugin knife-remotelxc from Heavywater company.
May be this is more useful for my local environment instead of spiceweasel.
-- Best regards, CVision Lab System Administrator Vladmir Skubriev
Archive powered by MHonArc 2.6.16.