openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,384 Commits 4 Branches 3 Tags 267 MiB
Go to file
Igor Zinovik 0f6abf96c3 Add 'compute-vmware' granular deployment task 
'compute-vmware' deployment task deploys nova-compute (VCDriver) on node
that got assigned 'compute-vmware' role:
- it installs nova-compute package
- prepares /etc/nova/nova-compute.conf file
- launches nova-compute service

It happens only if current node name (e.g. node-3) matches 'target_node'
attribute, it means that particuliar vSphere cluster was mapped to
current 'compute-vmware' node.

Change the way how nova-compute gets deployed on controller nodes
(vmware/manifests/compute/ha.pp): nova-compute deploys on controllers
only if 'target_node' attribute in contains 'controllers' value.

Diminish technical debt:
- remove references to 'common.libvirt_type.value'
- remove 'compute_driver' from manifests parameter list, it is inlined
  into configuration templates
- Remove useless vmware_index() invocation

Implements: blueprint compute-vmware-role
DocImpact: document new role in User Guide (VMware integration notes),
           update screenshots with VMware tab
Change-Id: I42ed40d86c5d43289fc210d426be523da545d268
 		2015-07-27 21:02:26 +03:00
debian Add new tasks for configure and deploy vms 2015-07-14 14:54:41 +02:00
deployment/puppet Add 'compute-vmware' granular deployment task 2015-07-27 21:02:26 +03:00
files Merge "Revert "Run test command against actual variables in ns_IPaddr2"" 2015-07-23 06:01:07 +00:00
specs Update openstack_version in fuel-library spec 2015-07-22 16:35:51 +03:00
tests Add 'compute-vmware' granular deployment task 2015-07-27 21:02:26 +03:00
utils Add tests for ceph module 2015-07-21 13:27:54 +00:00
.gitignore Add the task graph plotting tool 2015-03-02 17:32:04 +03:00
.gitreview Setup git-review 2013-12-11 14:31:13 +04:00
CHANGELOG Edit Changelog 2013-05-23 13:38:03 +03:00
LICENSE LICENCE added 2014-06-05 20:00:54 +00:00
README.md RabbitMQ FAQ notes prettified 2013-05-08 23:19:41 +04:00

README.md

Fuel is the Ultimate Do-it-Yourself Kit for OpenStack

Purpose built to assimilate the hard-won experience of our services team, it contains the tooling, information, and support you need to accelerate time to production with OpenStack cloud.

OpenStack is a very versatile and flexible cloud management platform. By exposing its portfolio of cloud infrastructure services – compute, storage, networking and other core resources — through ReST APIs, it enables a wide range of control over these services, both from the perspective of an integrated Infrastructure as a Service (IaaS) controlled by applications, as well as automated manipulation of the infrastructure itself.

This architectural flexibility doesn’t set itself up magically; it asks you, the user and cloud administrator, to organize and manage a large array of configuration options. Consequently, getting the most out of your OpenStack cloud over time – in terms of flexibility, scalability, and manageability – requires a thoughtful combination of automation and configuration choices.

Mirantis Fuel for OpenStack was created to solve exactly this problem.