@Bibmaster you do *not* want to use volumes as that is not enabled. The parameters you have provided do not have backing storage support which means the cinder volumes that would be provisioned have no backend to provision from.
To make it a bit easier, let’s just remove the cinder service from your service catalog. To do this,run:
microstack.openstack service delete cinderv2
microstack.openstack service delete cinderv3
Log out of horizon interface
sudo snap restart microstack.horizon-uwsgi
Log back into horizon. There should not be any volume options available.
Now you can create an instance and it should spawn. If you can’t access, you’ll want to check to make sure you provided ssh keys when you launched it and it has a floating up assigned. You access it via the floating up.
@Bibmaster you do *not* want to use volumes as that is not enabled. The parameters you have provided do not have backing storage support which means the cinder volumes that would be provisioned have no backend to provision from.
To make it a bit easier, let’s just remove the cinder service from your service catalog. To do this,run:
microstack. openstack service delete cinderv2 openstack service delete cinderv3
microstack.
Log out of horizon interface horizon- uwsgi
sudo snap restart microstack.
Log back into horizon. There should not be any volume options available.
Now you can create an instance and it should spawn. If you can’t access, you’ll want to check to make sure you provided ssh keys when you launched it and it has a floating up assigned. You access it via the floating up.