OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|bin||2 years ago|
|debian||2 years ago|
|examples||4 years ago|
|lib||2 years ago|
|mcagents||2 years ago|
|spec||2 years ago|
|specs||2 years ago|
|tests||2 years ago|
|.gitignore||2 years ago|
|.gitreview||1 month ago|
|.rspec||5 years ago|
|.ruby-version||5 years ago|
|Gemfile||2 years ago|
|LICENSE||5 years ago|
|MAINTAINERS||2 years ago|
|README.md||2 years ago|
|Rakefile||3 years ago|
|astute.gemspec||2 years ago|
|astute.service||3 years ago|
|astute.sysconfig||3 years ago|
|bindep.txt||2 years ago|
|run_tests.sh||3 years ago|
Astute is orchestrator, which is using data about nodes and deployment settings performs two things:
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.
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.
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
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
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.