7c0485eb1a
Connection between node and Astute can be lost some times, so we need more tries to get info about task status on node. Two changes: - instead of 1 try Astute will run 6 tries with 10 timeout for every attempt; - it will process such behavior for puppet using separately retries: puppet_undefined_retries Instead of full puppet retry status retry is safety because it is idempotent. Puppet undefined retries can be setup using Astute config or sending undefined_retries in puppet task parameters same way as for usual retries. Most important thing: it will refresh to original value every time when Astute get defined answer. Change-Id: Ie86576a3400be5a6b11041c8e6acf89abf3bbd51 Related-Bug: #1653210 Closes-Bug: #1653737 |
||
---|---|---|
bin | ||
debian | ||
examples | ||
lib | ||
mcagents | ||
spec | ||
specs | ||
tests | ||
.gitignore | ||
.gitreview | ||
.rspec | ||
.ruby-version | ||
astute.gemspec | ||
astute.service | ||
astute.sysconfig | ||
Gemfile | ||
LICENSE | ||
MAINTAINERS | ||
Rakefile | ||
README.md | ||
run_tests.sh |
Astute is orchestrator, which is using data about nodes and deployment settings performs two things:
- provision
- deploy
Provision
OS installation on selected nodes.
Provisioning is done using Cobbler. Astute orchestrator collects data about nodes and creates corresponding Cobbler systems using parameters specified in engine section of provision data. After the systems are created, it connects to Cobbler engine and reboots nodes according to the power management parameters of the node.
Deploy
OpenStack installation in the desired configuration on the selected nodes.
Astute uses data about nodes and deployment settings and recalculates parameters needed for deployment. Calculated parameters are passed to the nodes being deployed by use of nailyfact MCollective agent that uploads these attributes to /etc/astute.yaml
file of the node. Then puppet parses this file using Facter plugin and uploads these facts into puppet. These facts are used during catalog compilation phase by puppet. Finally catalog is executed and Astute orchestrator passes to the next node in deployment sequence. Fuel Library provides puppet modules for Astute.
Using as library
require 'astute'
class ConsoleReporter
def report(msg)
puts msg.inspect
end
end
reporter = ConsoleReporter.new
orchestrator = Astute::Orchestrator.new(log_parsing=false)
# Add systems to cobbler, reboot and start installation process.
orchestrator.provision(reporter, environment['engine'], environment['nodes'])
# Observation OS installation
orchestrator.watch_provision_progress(reporter, environment['task_uuid'], environment['nodes'])
# Deploy OpenStack
orchestrator.deploy(reporter, environment['task_uuid'], environment['nodes'])
Example of using Astute as library: lib/astute/server/dispatcher.rb
Using as CLI
CLI interface in Astute no longer supported. Please use new Fuel-CLI. More details you can get by link: https://github.com/openstack/fuel-docs/blob/master/pages/user-guide/cli.rst
- ISO, other materials: http://fuel.mirantis.com/
- User guide: http://docs.mirantis.com/
- Development documentation: http://docs.mirantis.com/fuel-dev/
License
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.