Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

EDIT:
After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup: 1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file 3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:
http://docs.openstack.org/trunk/openstack-compute/admin/content/cinder-install.html
http://www.mail-archive.com/openstack@lists.launchpad.net/msg22428.html
vhttp://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html

https://answers.launchpad.net/cinder/+question/229938c

That's pretty much it

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

EDIT:
After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup: 1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file 3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:
http://docs.openstack.org/trunk/openstack-compute/admin/content/cinder-install.html
http://www.mail-archive.com/openstack@lists.launchpad.net/msg22428.html
vhttp://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html

https://answers.launchpad.net/cinder/+question/229938c

That's pretty much it

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

EDIT:
After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup: 1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file 3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:
http://docs.openstack.org/trunk/openstack-compute/admin/content/cinder-install.html
http://www.mail-archive.com/openstack@lists.launchpad.net/msg22428.html
vhttp://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html
http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html
https://answers.launchpad.net/cinder/+question/229938c

That's pretty much it

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

EDIT:
After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup: 1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file 3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:
1. http://docs.openstack.org/trunk/openstack-compute/admin/content/cinder-install.html

2.
http://www.mail-archive.com/openstack@lists.launchpad.net/msg22428.html

3.
http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html

4.
https://answers.launchpad.net/cinder/+question/229938c

That's pretty much it

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

EDIT:
After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup: setup:
1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file file
3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:
1. http://docs.openstack.org/trunk/openstack-compute/admin/content/cinder-install.html
2. http://www.mail-archive.com/openstack@lists.launchpad.net/msg22428.html
3. http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html
4. https://answers.launchpad.net/cinder/+question/229938c

That's pretty much it

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.

Thanks,

EDIT:
After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup:
1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file
3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:
1. http://docs.openstack.org/trunk/openstack-compute/admin/content/cinder-install.html
2. http://www.mail-archive.com/openstack@lists.launchpad.net/msg22428.html
3. http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/add-volume-node.html
4. https://answers.launchpad.net/cinder/+question/229938c

That's pretty much it