-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc from openstack admin guide #1083
base: stackhpc/2023.1
Are you sure you want to change the base?
Conversation
This doc will need client specific infromation to be helpful
d9d7187
to
90a9b23
Compare
90a9b23
to
ac2cafb
Compare
The short version | ||
================= | ||
|
||
#. Create an infrastructure VM for the Wazuh manager, and add it to the wazuh-manager group | ||
#. Configure the infrastructure VM with kayobe: ``kayobe infra vm host configure`` | ||
#. Edit your config under | ||
``etc/kayobe/inventory/group_vars/wazuh-manager/wazuh-manager``, in | ||
``$KAYOBE_CONFIG_PATHinventory/group_vars/wazuh-manager/wazuh-manager``, in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
``$KAYOBE_CONFIG_PATHinventory/group_vars/wazuh-manager/wazuh-manager``, in | |
``$KAYOBE_CONFIG_PATH/inventory/group_vars/wazuh-manager/wazuh-manager``, in |
|
||
Those groups are usually defined in ``etc/kayobe/inventory/groups``. | ||
|
||
Running cephadm playbooks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
Running cephadm playbooks | |
Running Cephadm playbooks |
or
Running cephadm playbooks | |
Running ``cephadm`` playbooks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same for other uses of "cephadm"
- ``cephadm.yml`` - runs the end to end process starting with deployment and | ||
defining EC profiles/crush rules/pools and users | ||
- ``cephadm-crush-rules.yml`` - defines Ceph crush rules according | ||
- ``cephadm-deploy.yml`` - runs the bootstrap/deploy playbook without the | ||
additional playbooks | ||
- ``cephadm-ec-profiles.yml`` - defines Ceph EC profiles | ||
- ``cephadm-gather-keys.yml`` - gather Ceph configuration and keys and populate | ||
kayobe-config | ||
- ``cephadm-keys.yml`` - defines Ceph users/keys | ||
- ``cephadm-pools.yml`` - defines Ceph pools\ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The order here has changed a bit since this was written, and there are some new playbooks that run custom commands. The list is here: https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/2023.1/etc/kayobe/ansible/cephadm.yml
- ``cephadm-keys.yml`` - defines Ceph users/keys | ||
- ``cephadm-pools.yml`` - defines Ceph pools\ | ||
|
||
Running Ceph commands |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should get someone with more Ceph experience to review the rest of this file to check it for accuracy.
---------- | ||
|
||
* `Back up InfluxDB <https://docs.influxdata.com/influxdb/v1.8/administration/backup_and_restore/>`__ | ||
* `Back up ElasticSearch <https://www.elastic.co/guide/en/elasticsearch/reference/current/backup-cluster-data.html>`__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* `Back up ElasticSearch <https://www.elastic.co/guide/en/elasticsearch/reference/current/backup-cluster-data.html>`__ | |
* `Back up OpenSearch <https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore/>`__ |
|
||
.. code-block:: console | ||
|
||
monitoring0# for i in `docker ps -q`; do docker stop $i; done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should use systemctl
rather than docker
Upgrading OpenStack Services | ||
---------------------------- | ||
|
||
* Update tags for the images in ``etc/kayobe/kolla-image-tags.yml`` | ||
* Pull container images to overcloud hosts with ``kayobe overcloud container image pull`` | ||
* Run ``kayobe overcloud service upgrade`` | ||
|
||
You can update the subset of containers or hosts by | ||
|
||
.. code-block:: console | ||
|
||
kayobe# kayobe overcloud service upgrade --kolla-tags <service> --limit <hostname> --kolla-limit <hostname> | ||
|
||
For more information, see: https://docs.openstack.org/kayobe/latest/upgrading.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably just delete this section. Full version upgrades require a lot more than this. For container tag bumps, we just use service deploy. Either way, I don't think this section is really that useful
|
||
.. code-block:: console | ||
|
||
openstack server create --flavor <flavour name>--network <network name> --key-name <key> --image <Image name> --os-compute-api-version 2.74 --host <hypervisor hostname> <vm name> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
openstack server create --flavor <flavour name>--network <network name> --key-name <key> --image <Image name> --os-compute-api-version 2.74 --host <hypervisor hostname> <vm name> | |
openstack server create --flavor <flavour name> --network <network name> --key-name <key> --image <Image name> --os-compute-api-version 2.74 --host <hypervisor hostname> <vm name> |
|
||
openstack server create --flavor <flavour name>--network <network name> --key-name <key> --image <Image name> --os-compute-api-version 2.74 --host <hypervisor hostname> <vm name> | ||
|
||
Cleanup Procedures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Patch merged and backported long ago. This can be removed
It can be resolved by dropping cached content with ``docker restart | ||
memcached``. Note this will log out users from Horizon, as Django sessions are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be resolved by dropping cached content with ``docker restart | |
memcached``. Note this will log out users from Horizon, as Django sessions are | |
It can be resolved by dropping cached content with ``systemctl restart | |
kolla-memcached-container.service``. Note this will log out users from Horizon, as Django sessions are |
Moved general operation documentations from Openstack admin guide.
Removed customer specific templatings and tried to generalise.
Updated old contents
Please let me know if there are more contents that need to be updated.
Related PR on Openstack Admin Guide stackhpc/openstack-admin-guide#53