Re: [Openstack-operators] Cinder attach volume

2016-07-22 Thread Delatte, Craig 
Without knowing your environment, it is hard to say specifically how it should 
look.  But to give an example.

Here I have a ceph_ssd backend defined.  It contains all the information I 
would need to connect and use the backend

[ceph_ssd]
volume_backend_name=ceph_ssd
volume_driver=cinder.volume.drivers.rbd.RBDDriver
rbd_ceph_conf=/etc/ceph/ceph.conf
rbd_user=volumes
rbd_pool=ssd_volumes
rbd_max_clone_depth=2
rbd_flatten_volume_from_snapshot=True
rbd_secret_uuid=
backend_host=


After you have this up, you will see the volume service go active in your 
cinder-volume.log.  At that point you can define your volume type and then add 
the extra specs tying that volume type to the backend.  Something like this

volume_backend_name ceph-ssd

Also, you can always use your cinder service-list to find out the status of 
your backend you defined.

In my lab I would see this:

|  cinder-volume   |   @ceph_ssd  | nova | enabled  |   up  | 
2016-07-22T14:02:59.00 |-|

Craig DeLatte
Cloud Engineering & Operations – OpenStack DevOps
Charter
704-731-3356
610-306-4816


From: Alexandra Kisin
Date: Wednesday, July 20, 2016 at 9:47 AM
To: Time Warner Cable
Cc: 
"openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>"
Subject: Re: [Openstack-operators] Cinder attach volume

Thank you for the prompt respond.
How should  [SATA] section look in /etc/cinder/cinder.conf file ?

Regards,

Alexandra Kisin
Servers & Network group, IBM R Labs in Israel
Unix & Virtualization Team


Phone: +972-48296172 | Mobile: +972-54-6976172 | Fax: +972-4-8296111
[cid:_2_0EC6EFE80EC6ED7C004AB8FCC2257FF6]
[IBM]









From:"Delatte, Craig" 
<craig.dela...@twcable.com<mailto:craig.dela...@twcable.com>>
To:Alexandra Kisin/Haifa/IBM@IBMIL, 
"openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>"
 
<openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>>
Date:20/07/2016 04:13 PM
Subject:Re: [Openstack-operators] Cinder attach volume




So the volume type error will require a copy of your cinder.conf.  Or you can 
just verify you have a [SATA] section in it.

Also, volume type to my knowledge won’t change how libvirt presents the volume 
to the instance.  I am not sure it can be changed, or at least never had to 
explore trying to do what you are needing to do.


Craig DeLatte
Cloud Engineering & Operations – OpenStack DevOps
Charter
704-731-3356
610-306-4816


From: Alexandra Kisin
Date: Wednesday, July 20, 2016 at 9:02 AM
To: 
"openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>"
Subject: [Openstack-operators] Cinder attach volume
Resent-From: Time Warner Cable

Hello.
I'm working on Liberty Openstack environment using 
ibm.storwize_svc.StorwizeSVCDriver as volume_drivert.
When I'm creating a new volume and attaching it to the VM - by default it will 
be /dev/vdX on the instance using virtio driver.
And this way everything is working fine.

But I need it to be /dev/sdX for my application needs.
I tried to create a new type of the volume by running :
   cinder type-create SATA
   cinder type-key SATA set volume_backend_name=sata
But when I start a volume create process , it fails - the new volume has error 
state and the error in cinder-scheduler.log is :
ERROR cinder.scheduler.flows.create_volume Failed to run task 
cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No 
valid host was found. No weighed hosts available

Please advise how a volume can be attached as /dev/sdX device and not /dev/vdX.
The solution of stop the VM first and only then attach a volume can also be 
taken in account.

Thank you.

Regards,

Alexandra Kisin
Servers & Network group, IBM R Labs in Israel
Unix & Virtualization Team


Phone:+972-48296172 | Mobile:+972-54-6976172 | Fax:+972-4-8296111
[cid:_2_0EC757A40EC944C4004AB8FCC2257FF6]
[IBM]









This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
[attachment "ATT00

Re: [Openstack-operators] Cinder attach volume

2016-07-20 Thread Delatte, Craig 
So the volume type error will require a copy of your cinder.conf.  Or you can 
just verify you have a [SATA] section in it.

Also, volume type to my knowledge won’t change how libvirt presents the volume 
to the instance.  I am not sure it can be changed, or at least never had to 
explore trying to do what you are needing to do.


Craig DeLatte
Cloud Engineering & Operations – OpenStack DevOps
Charter
704-731-3356
610-306-4816


From: Alexandra Kisin
Date: Wednesday, July 20, 2016 at 9:02 AM
To: 
"openstack-operators@lists.openstack.org"
Subject: [Openstack-operators] Cinder attach volume
Resent-From: Time Warner Cable

Hello.
I'm working on Liberty Openstack environment using 
ibm.storwize_svc.StorwizeSVCDriver as volume_drivert.
When I'm creating a new volume and attaching it to the VM - by default it will 
be /dev/vdX on the instance using virtio driver.
And this way everything is working fine.

But I need it to be /dev/sdX for my application needs.
I tried to create a new type of the volume by running :
cinder type-create SATA
cinder type-key SATA set volume_backend_name=sata
But when I start a volume create process , it fails - the new volume has error 
state and the error in cinder-scheduler.log is :
 ERROR cinder.scheduler.flows.create_volume Failed to run task 
cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No 
valid host was found. No weighed hosts available

Please advise how a volume can be attached as /dev/sdX device and not /dev/vdX.
The solution of stop the VM first and only then attach a volume can also be 
taken in account.

Thank you.

Regards,

Alexandra Kisin
Servers & Network group, IBM R Labs in Israel
Unix & Virtualization Team


Phone: +972-48296172 | Mobile: +972-54-6976172 | Fax: +972-4-8296111
[cid:_2_0731BB300731B8C4004795A8C2257FF6]
[IBM]









This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Storage error

2015-03-04 Thread Delatte, Craig 
So it looks like you have pretty much everything commented out.

You need to define what you are using.  So:
[database] section
Rabbit
Auth-stratedgy
Host
volume_driver

And so on.  This is typically tailored to each environment.  If you are testing 
this out using vagrant, I am sure there is a lot of good documentation and 
possibly puppet modules to stand up a base openstack cluster and you can see 
what it did to get cinder up and functional.


Craig DeLatte
OpenStack DevOps
Time Warner Cable
704-731-3356
610-306-4816

From: Anwar Durrani durrani.an...@gmail.commailto:durrani.an...@gmail.com
Date: Wednesday, March 4, 2015 at 7:46 AM
To: Time Warner Cable 
craig.dela...@twcable.commailto:craig.dela...@twcable.com
Cc: openstack-operators 
openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] Storage error

Hi Delatte,

I have installed cinder on controller node server, do i need to install 
separate storage for Cinder Volume Management or controller server will be ok ?

Please find configuration file attached.



Thanks

On Tue, Mar 3, 2015 at 7:48 PM, Delatte, Craig 
craig.dela...@twcable.commailto:craig.dela...@twcable.com wrote:
What does your cinder.conf look like?  What are you using for storage?
Craig DeLatte
OpenStack DevOps
Time Warner Cable
704-731-3356
610-306-4816

From: Anwar Durrani durrani.an...@gmail.commailto:durrani.an...@gmail.com
Date: Tuesday, March 3, 2015 at 5:28 AM
To: openstack-operators 
openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org
Subject: [Openstack-operators] Storage error

Hello Team,

I have setup icehouse with following nodes in test environment

1.) Controller node
2.) Compute Node
3.) Network Node

I have basic setup on it, when i was trying to create a volume to tenant called 
demo or admin i am able to create but with status error, i don't why it is so ? 
do i need to configure storage as a separate node to create cinder volume ? 
where i am missing ?

Thanks

--
Thanks  regards,
Anwar M. Durrani
+91-8605010721tel:%2B91-8605010721
http://in.linkedin.com/pub/anwar-durrani/20/b55/60b



This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.



--
Thanks  regards,
Anwar M. Durrani
+91-8605010721
http://in.linkedin.com/pub/anwar-durrani/20/b55/60b

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Storage error

2015-03-03 Thread Delatte, Craig 
What does your cinder.conf look like?  What are you using for storage?
Craig DeLatte
OpenStack DevOps
Time Warner Cable
704-731-3356
610-306-4816

From: Anwar Durrani durrani.an...@gmail.commailto:durrani.an...@gmail.com
Date: Tuesday, March 3, 2015 at 5:28 AM
To: openstack-operators 
openstack-operators@lists.openstack.orgmailto:openstack-operators@lists.openstack.org
Subject: [Openstack-operators] Storage error

Hello Team,

I have setup icehouse with following nodes in test environment

1.) Controller node
2.) Compute Node
3.) Network Node

I have basic setup on it, when i was trying to create a volume to tenant called 
demo or admin i am able to create but with status error, i don't why it is so ? 
do i need to configure storage as a separate node to create cinder volume ? 
where i am missing ?

Thanks

--
Thanks  regards,
Anwar M. Durrani
+91-8605010721
http://in.linkedin.com/pub/anwar-durrani/20/b55/60b



This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators