
Added solar internal architecture diagram. Fixed doc generation errors. Change-Id: I0be39d9dbae7c19c633d6378f332bd8a14db3997 Closes-bug: #1538168
90 lines
2.3 KiB
ReStructuredText
90 lines
2.3 KiB
ReStructuredText
.. _faq:
|
|
|
|
|
|
FAQ
|
|
===
|
|
|
|
|
|
.. _faq_hardcoded_params:
|
|
|
|
Why nodes/transports have hardcoded keys, ips and other inputs ?
|
|
--------------------------------------------------------------
|
|
|
|
This is temporary situation, we will improve it in near future.
|
|
|
|
I want to use different SSH keys
|
|
----------------------------
|
|
|
|
Just update resource for example::
|
|
|
|
solar resource update ssh_transport1 '{"ssh_key": "/path/to/some/key"}'
|
|
|
|
I want to use passwords not keys
|
|
--------------------------------
|
|
|
|
Just update resource::
|
|
|
|
solar resource update rsync1 '{"password": "vagrant", "key": null}'
|
|
|
|
.. _faq_running_celery_worker:
|
|
|
|
.. note::
|
|
|
|
You need to change it for all transport resources (ssh and rsync by default).
|
|
|
|
|
|
How can I run solar celery worker ?
|
|
-----------------------------------
|
|
|
|
- If you use `vagrant` then you can just `service solar-celery start|restart`
|
|
as `vagrant` user.
|
|
- If you have `gevent` installed then you can use utils/solar-celery script.
|
|
You may need to adjust log files etc.
|
|
- You can spawn celery by hand too:
|
|
|
|
.. code-block:: bash
|
|
|
|
celery multi start 2 -A solar.orchestration.runner -P prefork -c:1 1 -c:2 2 -Q:1 scheduler,system_log -Q:2 celery
|
|
|
|
.. note::
|
|
|
|
We're currently working on removing celery completely.
|
|
|
|
How can I configure solar ?
|
|
---------------------------
|
|
|
|
There are several places where we search for config values:
|
|
|
|
1. `.config` file in CWD or in path from `SOLAR_CONFIG` env variable
|
|
2. if env `SOLAR_CONFIG_OVERRIDE` contains valid path then it override previous
|
|
values
|
|
3. `.config.override` in CWD
|
|
4. You can also set upper-cased env variable which matches one of those in
|
|
config
|
|
|
|
.. _faq_using_sqlbackend:
|
|
|
|
Why do you use celery with SQL backend instead of X ?
|
|
-----------------------------------------------------
|
|
|
|
For simplicity, but nothing stops you from changing these defaults::
|
|
|
|
celery_broker: sqla+sqlite:////tmp/celery.db
|
|
celery_backend: db+sqlite:////tmp/celery.db
|
|
|
|
.. _faq_what_database:
|
|
|
|
What database can I use with solar ?
|
|
------------------------------------
|
|
|
|
By default for simplicity we use `sqlite`. On our vagrant environment we use
|
|
single node `riak`.
|
|
You can also use multiple nodes `riak`, with some strong consistent buckets.
|
|
|
|
|
|
Where can I find solar examples ?
|
|
---------------------------------
|
|
|
|
Example resources, composer templates and examples itself are located:
|
|
https://github.com/Mirantis/solar-resources
|