User Tools
Writing /app/www/public/data/meta/openstack/creating_new_instance.meta failed
openstack:creating_new_instance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| openstack:creating_new_instance [2020/07/16 11:05] – Updated to identify the UUID of the mount drive 10.91.130.212 | openstack:creating_new_instance [2022/01/24 15:41] (current) – 10.91.120.28 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Creating new instance ====== | ||
| + | |||
| + | Creating new instances in OpenStack fall into 3 categories | ||
| + | |||
| + | * Independent isolated instances | ||
| + | * An IDMS Cluster | ||
| + | * An RDF Cluster | ||
| + | |||
| + | |||
| + | ===== Some notes/ | ||
| + | |||
| + | ====== Adding a volume to an instance ====== | ||
| + | Reference Material [[https:// | ||
| + | |||
| + | When adding a volume to an instance, for example on a MySQL DB Instance you must manually edit the **/ | ||
| + | |||
| + | For example, as of now, the IDMS Ironman cluster has a DB instance - IronmanDB1.err | ||
| + | |||
| + | Volumes Attached | ||
| + | * Attached To 7ce1bcf3-a494-4902-9c8b-42765d3c1a12 on /dev/vda | ||
| + | * Attached To os4db1 on /dev/vdb | ||
| + | |||
| + | The os4db1 volume is defined as | ||
| + | * Name os4db1 | ||
| + | * ID db6be9ca-b8c1-454e-973d-b55f4d75693b | ||
| + | * Description snapshot created from or20-idmsdb1 | ||
| + | * Project ID 4cd57af0ccdc4827a7ffa979678943d5 | ||
| + | * Status | ||
| + | * Group. | ||
| + | * Size 650 GiB | ||
| + | |||
| + | The /etc/fstab is | ||
| + | [scotty@ironmandb1 ~]$ cat /etc/fstab | ||
| + | |||
| + | * # | ||
| + | * # /etc/fstab | ||
| + | * # Created by anaconda on Mon Jan 28 20:51:49 2019 | ||
| + | * # | ||
| + | * # Accessible filesystems, | ||
| + | * # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info | ||
| + | * # | ||
| + | * UUID=f41e390f-835b-4223-a9bb-9b45984ddf8d / | ||
| + | * #/ | ||
| + | * **UUID=51b68e38-676f-40c6-b690-c81b09c099c0 /mysql xfs defaults 0 1 | ||
| + | * ** | ||
| + | |||
| + | The UUID is established on | ||
| + | * [scotty@ironmandb1 ~]$ sudo blkid | ||
| + | * [sudo] password for scotty: | ||
| + | * /dev/vda1: UUID=" | ||
| + | * /dev/vdb1: **UUID=" | ||
| + | |||
| + | ===== Troubleshooting ===== | ||
| + | |||
| + | If volumes are stuck in a state i.e. deleting or creating, the cinder services may need a restart. Deleting or creating a volume should output to the / | ||
| + | |||
| + | < | ||
| + | sudo service cinder-scheduler restart | ||
| + | sudo service cinder-volume restart | ||
| + | </ | ||