Re: [Openstack] cinder volume weird behavior

2013-10-23 Thread Jay S Bryant
Ritesh,

I am not familiar with cgroups, so I am not sure if that could have an 
affect.  I would try re-enabling it for good measure, though the initial 
information I get when googling cgroups doesn't seem to be a smoking gun.

I think that the feedback that John Griffith provided mirrors my original 
response that the source of the problem is likely that you already have 
other volumes attached and are looking at the size information for those 
mount points rather than the new volumes you are attaching given that the 
volumes appear to be the right size on the v3700.

Can you provide more details on how you are determining the size of the 
mounted volume?



Jay S. Bryant
Linux Developer - 
OpenStack Enterprise Edition
   
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail:  jsbry...@us.ibm.com

 All the world's a stage and most of us are desperately unrehearsed.
   -- Sean O'Casey




From:   Ritesh Nanda 
To:     Jay S Bryant/Rochester/IBM@IBMUS, 
Date:   09/30/2013 02:28 PM
Subject:Re: [Openstack] cinder volume weird behavior



Hello Jay , 

I use ubuntu 12.04 for controller and compute nodes , one change i did  
which i recall is stopping  the cgroups so that it gives performance to 
the libvirt.
Can it be the issue , rest all packages are the latest version, i checked 
all. 

 is cgroups related something to iscsi + libvirt?


On Tue, Oct 1, 2013 at 12:12 AM, Jay S Bryant  wrote:
Ritesh, 

What are you running for the host operating system on the Control Node and 
Compute Nodes?   

As I Google around for the errors you are seeing it seems that there have 
been some changes to libvirt and qemu that might help to avoid the problem 
you are seeing. 

Have you tried updating libvirt and qemu?



Jay S. Bryant
Linux Developer - 
   OpenStack Enterprise Edition
  
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail:  jsbry...@us.ibm.com

All the world's a stage and most of us are desperately unrehearsed.
  -- Sean O'Casey
 



From:Ritesh Nanda  
To:Jay S Bryant/Rochester/IBM@IBMUS, 
Date:09/30/2013 01:04 PM 
Subject:Re: [Openstack] cinder volume weird behavior 



Hello Jay,

Bug there for hyperV does'nt look related to my issue , as i have been 
specifying mount point like /dev/vdb , /dev/vdc, not using the auto 
functionality ,  When i manually try to attach a created volume from the 
horizon on the compute node on which the vm resides nova-compute log shows 
the error.

libvirtError: internal error unable to execute QEMU command 'device_add': 
Duplicate ID 'virtio-disk2' for device

Given something random mount point while attaching to a vm solves like 
specifying /dev/vfg attaches the volume but the below error persists. 

Other problem which accompanies with this is volumes i create for e.g 4gb 
gets correctly created on v3700 , but when i attach to a vm , in vm 
console it shows always a different size. 
  

Giving a restart to open-iscsi on the cinder-volume node solves the issue 
for few minutes , then it comes back.

I have a multi-node grizzly with multi-host nova-network (vlan manager) 
running. 
Cinder api and scheduler, volume  running on the controller and 
cinder-volume on all the compute nodes.

  


On Mon, Sep 30, 2013 at 11:07 PM, Jay S Bryant  
wrote: 
Ritesh, 

I have noticed that the 'auto' option for the mount point is not working 
as expected right now.  There is an issue opened that seems similar:  
https://bugs.launchpad.net/nova/+bug/1153842  The bug spells out HyperV 
but I believe the same is happening for KVM.  As you have noted, it is 
pretty easy to work around.  I hope to look at the issue after I get some 
other bugs fixed. 

With regards to the size problem, what size the volume appear to be on the 
3700?  Does the size of the volume appear as expected there?  Is it 
associated with the expected host?  Are you sure you are looking at the 
right device from the compute node?  



Jay S. Bryant
Linux Developer - 
   OpenStack Enterprise Edition
  
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail:  jsbry...@us.ibm.com

All the world's a stage and most of us are desperately unrehearsed.
  -- Sean O'Casey
 



From:   

Re: [Openstack] how to submit the code for openstack-icehouse release

2013-10-15 Thread Jay S Bryant
Tom,

Thanks for the excellent response.

Dinakar,

In addition to the information Tom has shared:  If you need assistance you 
can look for help in the #openstack-cinder channel on irc.freenode.net. 
Also, I would recommend sitting in on the Weekly Cinder meeting that 
happens in #openstack-meeting at noon Eastern US time each Wednesday.

I was able to get started on the project by going through 
https://wiki.openstack.org/wiki/Cinder .  There is a lot of good 
information there.  Note, that there is now a minimum set of functionality 
that is required to be a Cinder Driver.  Please review that information as 
well.

We look forward to seeing your code!



Jay S. Bryant
Linux Developer - 
OpenStack Enterprise Edition
   
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail:  jsbry...@us.ibm.com

 All the world's a stage and most of us are desperately unrehearsed.
   -- Sean O'Casey




From:   Tom Fifield 
To: openstack@lists.openstack.org, 
Date:   10/15/2013 01:23 AM
Subject:Re: [Openstack] how to submit the code for 
openstack-icehouse  release



Hi Dinakar,

Great to hear that you want to add a driver. The Cinder team will 
hopefully add more specific information to this, but here are the 
generic hints to get started ...

Our processes and community are all very Open[1], and it should be 
fairly easy for you to get started[2] down the road to getting your code 
included in OpenStack.

The good news is, your timing is excellent, because we're just about to 
start a new release cycle[3] it's the perfect time to start talking 
about new features.

What I would suggest you do is register a blueprint[4] on launchpad for 
your driver - linking to a page explaining more about it on the wiki. 
Then, get on the openstack-dev mailing list[5] and introduce yourself 
and your implementation plan. If you can, try and get to the design 
summit[6] to meet some of the people involved.

I hope I haven't caused confusion by sharing many links - please do let 
us know if you would like further information on any aspect.

Welcome to the OpenStack community!

Regards,


Tom

[1] http://wiki.openstack.org/Open
[2] https://wiki.openstack.org/wiki/HowToContribute
[3] https://wiki.openstack.org/wiki/ReleaseCycle
[4] https://wiki.openstack.org/wiki/Blueprints
[5] http://lists.openstack.org/cgi-bin/mailman/listinfo
[6] http://www.openstack.org/summit


On 15/10/13 16:45, Dinakar Gorti Maruti wrote:
> Dear all,
>  I am planing to submit a new driver to cinder services in
> openstack-icehouse .
> I want to know the process of submitting .
>
> Thanks
> Dinakar
>
>
> ___
> Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>


___
Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


<>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack