Re: [Openstack] Cinder iscsi

2013-07-18 Thread John Griffith
On Thu, Jul 18, 2013 at 4:55 PM, Remo Mattei  wrote:

> Hello everyone I was reading the code of cinder and I want to check if
> this is correct
>
> 1 vm will get a instruction to mount the drive using the iscsi
>

It's actually more like the compute node gets the iSCSI attach, and the
local-dev is passed in to
the instance.

> 2 on the back end I can have any time of drive type net app,emc etc.
>

To a point, yes; assuming the device of interest has a driver integrated in
Cinder.

> 3 once the vm has mount the drive it goes direct
>

See points on note 1.. but yes, I think you're kinda on the right page

>
> Thanks
>
> Remo
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [cinder] Proposal for Ollie Leahy to join cinder-core

2013-07-18 Thread John Griffith
On Thu, Jul 18, 2013 at 10:30 AM, thingee  wrote:

> On Wed, Jul 17, 2013 at 8:09 AM, Duncan Thomas wrote:
>
>> Hi Everybody
>>
>> I'd like to propose Ollie Leahy for cinder core. He has been doing
>> plenty of reviews and bug fixes, provided useful and tasteful negative
>> reviews (something often of far higher value than a +1) and has joined
>> in various design discussions.
>>
>
> I do find Ollie's reviews insightful, but given the current review stats
> [0], I'd like to see that more near average with the rest of core.
>
> Besides numbers in reviews I'm mostly looking at bug triaging/fixes and
> involvement in the ML and IRC with Cinder.
>
> With that in mind, given the discussions that have been going on and the
> direction [1], I'm going to have to give a -1.
>
> I absolutely welcome Ollie to self nominate or be nominated by myself if
> that improves after 30 days. [2]
>
> Thanks,
> Mike Perez
>
> [0] - http://russellbryant.net/openstack-stats/cinder-reviewers-30.txt
> [1] -
> http://lists.openstack.org/pipermail/openstack-dev/2013-July/012079.html
> [2] - https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> While I think Ollie provides fantastic detailed reviews (and he's a cool
dude), I'd like to see more of them as well. So for now I'm going to have
to vote with a -1.

As Cinder grows I think we need to be taking a closer look at the review
activity by ALL of the core team members.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder Storage Server Statistics

2013-07-17 Thread John Griffith
Understood, and completely agree.  I'll look at opening a bug to get this
and run it by you when I have a patch to make sure we're meeting your needs
here.


On Wed, Jul 17, 2013 at 5:04 PM, Ray Sun  wrote:

> John,
> Thanks. I will look into that extension today. The requirement is ​
> ​as an administrator, I want to know how many real resources I have in my
> cloud pool.
>
> If we don't have such interface in client side, I would be a contributor
> to add the code in cinder client.
>
> Best Regards
> -- Ray
>
>
> On Wed, Jul 17, 2013 at 2:50 AM, John Griffith <
> john.griff...@solidfire.com> wrote:
>
>>
>>
>>
>> On Tue, Jul 16, 2013 at 12:47 PM, Doug Hellmann <
>> doug.hellm...@dreamhost.com> wrote:
>>
>>> When I said, "we", I meant "the ceilometer team". If the auditing app
>>> isn't finding any volumes, it's not going to notify us.
>>>
>>> If you just want to know how much data is being used by cinder, there
>>> may be a way to get that from their admin API, but I'm not sure.
>>>
>>>
>>> On Mon, Jul 15, 2013 at 7:08 PM, Ray Sun  wrote:
>>>
>>>> D
>>>> ​oug,
>>>> Thanks. I tried it in grizzly, here's the return:
>>>> sysadmin@demo:/opt/stack/cinder/bin$ cinder-volume-usage-audit
>>>> Starting volume usage audit
>>>> Creating usages for 2013-06-01 00:00:00 until 2013-07-01 00:00:00
>>>> Found 0 volumes
>>>> Volume usage audit completed​
>>>>
>>>> ​Actually, I want to get some data like this:
>>>> Total Cinder Storage on Physical Machine: 100G
>>>> Used Cinder Storage on Physical Machine: 10G​
>>>>
>>>> Is there any way to get this?
>>>>
>>>>
>>>> Best Regards
>>>> -- Ray
>>>>
>>>>
>>>> On Tue, Jul 16, 2013 at 6:27 AM, Doug Hellmann <
>>>> doug.hellm...@dreamhost.com> wrote:
>>>>
>>>>> We rely on a similar audit program to get the "exists" notifications
>>>>> about cinder volumes. Look for "cinder-volume-usage-audit".
>>>>>
>>>>> Doug
>>>>>
>>>>>
>>>>> On Sun, Jul 14, 2013 at 11:04 AM, Ray Sun  wrote:
>>>>>
>>>>>> Yes, it should be, but seems not at least in grizzly. Any update of
>>>>>> Ceilometer?
>>>>>>
>>>>>> Best Regards
>>>>>> -- Ray
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 14, 2013 at 11:04 AM, Haomai Wang >>>>> > wrote:
>>>>>>
>>>>>>> I think Statistics should be find in Ceilometer. Ceilometer may
>>>>>>> provide with
>>>>>>> enough information you need.
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Haomai Wang, UnitedStack Inc.
>>>>>>>
>>>>>>> 在 2013-7-14,上午8:09,Ray Sun  写道:
>>>>>>>
>>>>>>> In nova, we have a period task to report the usage of the physical
>>>>>>> server, including CPU, Memory and Local Disk, but I don't think I can 
>>>>>>> find
>>>>>>> the same strategy in cinder service. Is there any way to do this or is
>>>>>>> there any blueprint for this?
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> Best Regards
>>>>>>> -- Ray
>>>>>>>  ___
>>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>>> Post to : openstack@lists.launchpad.net
>>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Mailing list: https://launchpad.net/~openstack
>>>>>> Post to : openstack@lists.launchpad.net
>>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>> ​there is an os-hosts extension that gives things like volume-count and
>> GB/used on a cinder volume-service node, however it's not currently exposed
>> from the client.  Not sure if that's the sort of thing you're looking for
>> or not.​
>>
>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack-dev] [cinder] Proposal for Ollie Leahy to join cinder-core

2013-07-17 Thread John Griffith
On Wed, Jul 17, 2013 at 12:19 PM, Avishay Traeger wrote:

> -1
>
> I'm sorry to do that, and it really has nothing to do with Ollie or his
> work (which I appreciate very much).  The main reason is that right now
> Cinder core has 8 members:
> 1. Avishay Traeger (IBM)
> 2. Duncan Thomas (HP)
> 3. Eric Harney (RedHat)
> 4. Huang Zhiteng (Intel)
> 5. John Griffith (SolidFire)
> 6. Josh Durgin (Inktank)
> 7. Mike Perez (DreamHost)
> 8. Walt Boring (HP)
>
> Adding another core team member from HP means that 1/3 of the core team is

from HP.  I believe that we should strive to have the core team be as
> diverse as possible, with as many companies as possible represented (big
> and small alike).  I think that's one of the keys to keeping a project
> healthy and on the right track (nothing against HP - I would say the same
> for IBM or any other company).  Further, we appointed two core members
> fairly recently (Walt and Eric), and I don't feel that we have a shortage
> at this time.
>
> Again, nothing personal against Ollie, Duncan, HP, or anyone else.
>
> Thanks,
> Avishay
>
>
>
> From:   Duncan Thomas 
> To: "Openstack (openstack@lists.launchpad.net)
> (openstack@lists.launchpad.net)"
> , OpenStack Development Mailing
> List ,
> Date:   07/17/2013 06:18 PM
> Subject:[openstack-dev] [cinder] Proposal for Ollie Leahy to join
> cinder-core
>
>
>
> Hi Everybody
>
> I'd like to propose Ollie Leahy for cinder core. He has been doing
> plenty of reviews and bug fixes, provided useful and tasteful negative
> reviews (something often of far higher value than a +1) and has joined
> in various design discussions.
>
> Thanks
>
> --
> Duncan Thomas
> Cinder Core, HP Cloud Services
>
> ___
> OpenStack-dev mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
Just to point out a few things here, first off there is no guideline that
states a company affiliation should have anything to do with the decision
on voting somebody as core.  I have ABSOLUTELY NO concern about
representation of company affiliation what so ever.

Quite frankly I wouldn't mind if there were 20 core members from HP, if
they're all actively engaged and participating then that's great.  I don't
think there has been ANY incidence of folks exerting inappropriate
influence based on their affiliated interest, and if there ever was I think
it would be easy to identify and address.

As far as "don't need more" I don't agree with that either, if there are
folks contributing and doing the work then there's no reason not to add
them.  Cinder IMO does NOT have an excess of reviewers by a very very long
stretch.

The criteria here should be review consistency and quality as well as
knowledge of the project, nothing more nothing less.  If there's an
objection to the individuals participation or contribution that's fine, but
company affiliation should have no bearing.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Cinder] Loading cinder.conf

2013-07-16 Thread John Griffith
On Tue, Jul 16, 2013 at 12:41 AM, zan tosh  wrote:

> Thanks for all your responses. I didn't realize that stack.sh actually
> copies the cinder.conf.sample instead of cinder.conf to /etc/cinder every
> time it runs. So, it was overwriting my entries. I fixed it by making
> changes to the script. The issue is resolved.
>
>
> On Mon, Jul 15, 2013 at 4:54 PM, Unmesh Gurjar wrote:
>
>> Hi,
>>
>> AFAIK, there are no additional changes required (other than restarting
>> the service so that it loads the new conf settings). Assuming you have done
>> that, can you check what is the 'volume_driver' from the service start up
>> logs?
>>
>>
>> ~Unmesh.
>>
>> On Mon, Jul 15, 2013 at 10:44 AM, zan tosh  wrote:
>>
>>> Ray
>>>
>>> I am wondering why I see the default driver even after I changed the
>>> entry in cinder.conf. I un-commented the line for volume_driver and changed
>>> the driver name. I tried to print volume driver in the __init__ and I see
>>> it still pointing to LVMISCSIDriver. It seems I am missing something
>>> and its not loading values from cinder.conf.
>>>
>>> ~z
>>>
>>>
>>> On Mon, Jul 15, 2013 at 10:33 AM, Ray Sun  wrote:
>>>
 Yes, that's the default driver. See cinder/volume/manager.py
 volume_manager_opts = [
 cfg.StrOpt('volume_driver',
default='cinder.volume.drivers.lvm.LVMISCSIDriver',
help='Driver to use for volume creation'),
 ]

 Best Regards
 -- Ray


 On Mon, Jul 15, 2013 at 12:51 PM, zan tosh  wrote:

> I use devstack (Grizzly/stable). I have been trying to use a different
> volume driver by muncommenting and modifying the below line in cinder.conf
> under etc/cinder
> # Driver to use for volume creation (string value)
> #volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
>
> But when VolumeManager is loaded I see it still refers to the default
> LVMISCSIDriver. Is there any other change to load cinder.conf?
>
> Any suggestions?
>
> Tahnks
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>

>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Yes, devstack will overwrite each time your run stack.sh.  You can also
modify your cinder.conf file and then just resart the cinder-volume service
(use screen -x to access the service).
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder Storage Server Statistics

2013-07-16 Thread John Griffith
On Tue, Jul 16, 2013 at 12:47 PM, Doug Hellmann  wrote:

> When I said, "we", I meant "the ceilometer team". If the auditing app
> isn't finding any volumes, it's not going to notify us.
>
> If you just want to know how much data is being used by cinder, there may
> be a way to get that from their admin API, but I'm not sure.
>
>
> On Mon, Jul 15, 2013 at 7:08 PM, Ray Sun  wrote:
>
>> D
>> ​oug,
>> Thanks. I tried it in grizzly, here's the return:
>> sysadmin@demo:/opt/stack/cinder/bin$ cinder-volume-usage-audit
>> Starting volume usage audit
>> Creating usages for 2013-06-01 00:00:00 until 2013-07-01 00:00:00
>> Found 0 volumes
>> Volume usage audit completed​
>>
>> ​Actually, I want to get some data like this:
>> Total Cinder Storage on Physical Machine: 100G
>> Used Cinder Storage on Physical Machine: 10G​
>>
>> Is there any way to get this?
>>
>>
>> Best Regards
>> -- Ray
>>
>>
>> On Tue, Jul 16, 2013 at 6:27 AM, Doug Hellmann <
>> doug.hellm...@dreamhost.com> wrote:
>>
>>> We rely on a similar audit program to get the "exists" notifications
>>> about cinder volumes. Look for "cinder-volume-usage-audit".
>>>
>>> Doug
>>>
>>>
>>> On Sun, Jul 14, 2013 at 11:04 AM, Ray Sun  wrote:
>>>
 Yes, it should be, but seems not at least in grizzly. Any update of
 Ceilometer?

 Best Regards
 -- Ray


 On Sun, Jul 14, 2013 at 11:04 AM, Haomai Wang 
 wrote:

> I think Statistics should be find in Ceilometer. Ceilometer may
> provide with
> enough information you need.
>
> Best regards,
> Haomai Wang, UnitedStack Inc.
>
> 在 2013-7-14,上午8:09,Ray Sun  写道:
>
> In nova, we have a period task to report the usage of the physical
> server, including CPU, Memory and Local Disk, but I don't think I can find
> the same strategy in cinder service. Is there any way to do this or is
> there any blueprint for this?
>
> Thanks.
>
> Best Regards
> -- Ray
>  ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


>>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> ​there is an os-hosts extension that gives things like volume-count and
GB/used on a cinder volume-service node, however it's not currently exposed
from the client.  Not sure if that's the sort of thing you're looking for
or not.​
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Volume Success Create But No Volume in its Path

2013-07-15 Thread John Griffith
On Mon, Jul 15, 2013 at 10:01 PM, Mahardhika
wrote:

>  Hi all, i have investigate this issue, since i am successful in create
> volume with cinder, but volume is not create on it's own volumes_dir that's
> in /var/lib/cinder/volumes
> and in cinder-volumes.log it said success when creating no error or warn
> appear.
> lvm (with /dev/loop) is show that lvm is used for volume .
>
> please help
> thanks
> --
> Regards,
> Mahardhika Gilang
>
> *PT. Andalabs Technology *
> Gedung Gravira
> Jl. Cideng Barat no. 54
> Jakarta Pusat 10150
>
> HP : 0852 139 55861
> Email : mahardika.gil...@andalabs.com
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Mahardhika,

The cinder volumes directory is actually used just for specifying the
location of the iscsi target persistence files.

Your volume is actually an LVM/Volume that you should see by running "sudo
lvs".

As far as the persistence file, are you runing devstack?  If so it will be
in /opt/stack/data/cinder/volumes...  If not perhaps you could provide your
cinder.conf file and we could get a better idea of what you're setup is and
where things might be.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Path Cinder Volume

2013-07-13 Thread John Griffith
On Fri, Jul 12, 2013 at 6:52 AM, Haomai Wang  wrote:

> Hi Mahardhika,
>
> Could you provide more info about your configuration? And the steps what
> you did?
>
> The more info can help us solve your problem, thank you
>
> Best regards,
> Haomai Wang, UnitedStack Inc.
>
> 在 2013-7-12,下午4:38,Mahardhika  写道:
>
>  Hello, in my configuration at cinder.conf
> volumes_dir is on* **/var/lib/cinder/volumes*. but when i create new
> volume it isn't there,
> on cinder-volume.log not said much, it's just successful
> kindly help
> thanks
>  ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> ​Hi Mahardhika,​
​The file you're looking at is the iscsi target persistence file, as Haomai
said, it would be useful to provide more info about your environment,
including what version of OpenStack and the cinder.conf file.

If you're using LVM and the create reported success, do a "sudo lvs" and
see if the volume is there.  I suspect that it is, and you're just not
using a driver/version that has persistent iscsi targets.

John​
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] why did openstack choose ceph (and not glusterfs)

2013-07-11 Thread John Griffith
On Thu, Jul 11, 2013 at 6:27 PM, Tom Fifield  wrote:

> Hi,
>
> Community Manager here - just confirming - "OpenStack" has not "chosen
> Ceph". Not sure where that information is coming from - got a blog link so
> we can fix any confusion? :)
>
>
> Regards,
>
> Tom
>
>
> On 12/07/13 10:23, Zippy Zeppoli wrote:
>
>> Hello,
>> I apologize if this email causes some kind of subjective ruckus, but
>> frankly I don't care (sorry etiquette) since it will resolve a
>> reasonable question that isn't clearly answered on the web.
>>
>> Why did openstack choose ceph and not glusterfs. There doesn't seem to
>> be a lot of (good) information on how/why to choose one over the other,
>> and I'm sure most folks do a proof-of-concept to figure this out, but it
>> doesn't seem like a lot of information has been shared on the matter.
>>
>> That being said, OpenStack is a large open source project that has
>> decided to use this storage platform (big decision). Why and how did the
>> technical architects for OpenStack come to this decision (blog post
>> would be awesome, wasn't able to find one Googling).
>>
>> CheerZ
>>
>>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>

Hi Zippy,

To be clear, OpenStack doesn't really "choose" at all.  In terms of Cinder
you have a choice, that could be the base LVM implementation, Ceph-RBD,
Gluster or any choice from a long list of supported/integrated backend
storage devices.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] cinder api list volumes very slow and inefficient.

2013-07-08 Thread John Griffith
On Sun, Jul 7, 2013 at 5:43 PM, Sam Morrison  wrote:

> Hi,
>
> I'm wondering if anyone is using cinder and is having issue with the list
> volumes API call.
>
> We have a grizzly install and we're at about 160 active volumes in cinder
> at the moment.
>
> To do "cinder list" with a tenant that has about 140 volumes it takes
> about 6 seconds.
> API calls on a specific volume are done in about 0.1 seconds so I'm happy
> with the API servers, it's the code I'm worried about.
>
> Doing a "cinder list --all-tenants" as an admin it takes about 20 seconds.
>
> Looking at the code it seems as an admin it will iterate over every volume
> 3 times and do a db requests on each volume.
> As a normal user it iterates over every volume once.
>
> The for loops are for adding glance image information and as an admin it
> also adds host and tenant information which is in the same table so it's a
> bit strange that it's doing more DB calls.
>
> Does anyone use cinder with more that just a couple of active volumes and
> if so how do they when requests are so slow?
> We have 36 cinder-api servers handling requests and they aren't under
> significant load. Also our DB cluster is handling things fine.
>
> Cheers,
> Sam
>
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Hi Sam,
Definitely some things in this area that cause problems at scale, I'm not
sure exactly where you're looking at in terms of the loops?

We did recently submit a bug fix [1] related to some of this, but I don't
think it covers the case you're describing and it has NOT been backported
to Grizzly.

If you'd like to point me specifically to the loops your describing I'm
happy to take a look and see if we can fix this up.

Thanks,
John

[1] http://tinyurl.com/jwgpxpr
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Shared Storage with cinder ?

2013-07-05 Thread John Griffith
On Fri, Jul 5, 2013 at 10:31 AM, Clint Byrum  wrote:

> Excerpts from Heiko Krämer's message of 2013-07-05 09:24:03 -0700:
> > Heyho guys,
> >
> > I'm searching for a solution to share storage over more then one
> instance.
> >
> > Normally you attach a block device with cinder directly via iscsi or
> > glusterfs or whatever to one instance and that's it. Multi attachments
> > are not present.
> >
> >
> > Use case:
> >
> > I've an application on 4 application instances and a database instance.
> > Now you have static file like images, movies, css ... but this files
> > should be available on each application instance.
>
> This use case is best served by object storage like swift and CEPH's
> radosgw.
>
> > Now you need to fire up an "storage" instance and attach a volume. After
> > that you can with nfs or what ever share your stuff to the application
> > instances but i think this is a very big ressource overhead for small
> > projects. You need a instance only to share your data on each project
> > and this n times :(
> >
>
> If you only have one small app with 5 instances, running your own
> OpenStack is quite overkill.  However, I suspect you have OpenStack so
> you can have many small apps with a few instances, and thus you'll find
> many of them can benefit from a good solid object store.
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Cinder does not offer multi-attach currently, we're hoping to change that
for the Havana release:
https://blueprints.launchpad.net/cinder/+spec/shared-volume
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] To run Openstack, stack.sh is required to execute after every reboot ?

2013-06-17 Thread John Griffith
On Mon, Jun 17, 2013 at 6:06 PM, Aaron Rosen  wrote:

> If you run rejoin-stack.sh it should start all the openstack processes
> that were running before reboot.
>
> Aaron
>
>
> On Mon, Jun 17, 2013 at 12:15 PM, Vivek Satpute 
> wrote:
>
>> Hi,
>>
>> I recently setup a openstack on one node, which is hosting all the
>> services
>> like keystone, nova, glance, cinder, etc. Using Dashboard, I could create
>> the VM instances and volumes too. But if I rebooted my host machine where
>> openstack is configured, once machine comes up, horizon cannot
>> retrieve any data.
>>
>> I realised that, there is no services running on host setup. (Checked
>> using ps -ef command).
>> I again did ./stack.sh and then I could create new instances, volumes,
>> etc.
>>
>> How can I configure openstack such a that it would get started after
>> reboot automatically ?
>> Or Am I missing something here ?
>>
>>
>> Thanks in advance,
>> Vivek Satpute
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> As Aaron pointed out, rejoin works with the exception of Cinder (the loop
back files devstack sets up for VG's aren't persistent across reboot),
you'd need to recreate them via script yourself, or make them persistent.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] volumeId is not in proper format

2013-06-05 Thread John Griffith
Not exactly sure what it's tripping up on when using the volume name there,
but I would suggest using the volume-id rather than the name.


On Wed, Jun 5, 2013 at 9:46 AM, Greg Chavez  wrote:

> So I'm happily spinning virts on my new Grizzly installation (Ubuntu
> 13.04, per tenant routers, vm config network via GRE, and Ceph block
> storage on the compute nodes).
>
> Suddenly, we have encountered the following problem attaching the
> following volume:
>
> root@kcon-gen-01i:~l# nova volume-attach maps-cs-vm-01u
> maps-cs-vm-01u_vol0 /dev/vdc
> ERROR: Bad volumeId format: volumeId is not in proper format
> (maps-cs-vm-01u_vol0) (HTTP 400) (Request-ID:
> req-1205e592-8e96-4874-a7a0-1f7117859f84)
>
> I've several other volumes with similar names and have had no trouble
> attaching them.  Any idea what's wrong here?  Thanks!
>
> --
> \*..+.-
> --Greg Chavez
> +//..;};
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] How add an iScsi Storage with devstack

2013-05-16 Thread John Griffith
On Thu, May 16, 2013 at 9:12 AM, Alexandre De Carvalho <
alexandre7.decarva...@gmail.com> wrote:

> Hi !
>
> I would like to know how to add an iscsi storage for my instances. I used
> devstack to install openstack.
> I think i need to modify my localrc in my controller node but what ! i
> don't know.
>
> Can you help me, please ? If you have some documents or a localrc conf it
> would be nice.
>
> Thanks !
>
> --
> regards,
> Alexandre
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Alexandre,

If you used devstack you already have the base LVM storage that we export
via iSCSI by defult.  If you want to add some external iSCSI storage device
the way to go about that is going to depend upon what device it is,
assuming there's a driver available from there it's just a matter of making
some modifications to your cinder.conf file and restarting the volume
service.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder's LVM vg creation when installing Grizzly

2013-05-14 Thread John Griffith
On Tue, May 14, 2013 at 9:06 AM, Chris Bartels  wrote:

> Hi,
>
> ** **
>
> I have questions regarding this part of the Grizzly install guide that’s
> up on github:
>
> ** **
>
> **· **Finally, don't forget to create a volumegroup and name it
> cinder-volumes:
>
> **· **dd if=/dev/zero of=cinder-volumes bs=1 count=0 seek=2G
>
> **· **losetup /dev/loop2 cinder-volumes
>
> **· **fdisk /dev/loop2
>
> **· **#Type in the followings:
>
> **· **n
>
> **· **p
>
> **· **1
>
> **· **ENTER
>
> **· **ENTER
>
> **· **t
>
> **· **8e
>
> **· **w
>
> **· **Proceed to create the physical volume then the volume group:
> 
>
> **· **pvcreate /dev/loop2
>
> **· **vgcreate cinder-volumes /dev/loop2
>
> *Note:* Beware that this volume group gets lost after a system reboot.
> (Click 
> Hereto
>  know how to load it after a reboot)
> 
>
> ** **
>
> First, I don’t know what all those commands are doing, in particular with
> the dd stuff, and I’m reluctant to be doing stuff with that which I don’t
> understand, so if someone could explain what that’s all about I’d
> appreciate it. If that’s how it _*must*_ be done, I’d like to know.
>
> ** **
>
> Secondly, I’m wondering if I could make life easier and not have to bother
> with the extra stuff regarding making the vg come back after reboot, which
> the instructions link to how to do, if I were to simply do the cinder vg
> with the installer & install Ubuntu with 100GB (out of 1000GB) of the disk
> made available to the guided LVM partitioning during the initial install,
> and use the rest as a cinder-volumes vgcreate’d group that gets mounted
> normally at each boot like everything else does.
>
> ** **
>
> Wouldn’t that work? Seems easier to me.
>
> ** **
>
> Please advise.
>
> ** **
>
> Thanks,
>
> Chris
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hey Chris,

What's listed above is standard unix commands to build a loop-back device
file that can be used as a Physical Volume to build Volume Groups.  To be
honest, this isn't really how you should deploy Cinder in a real
environment, but it really just for testing and things like Devstack.

For a production setup, you'd actually want to have a raw disk or two on
the system, add them as an LVM Physical Volume.  The create the Volume
Group, in other words the only steps you would need are:

pvcreate /dev/sdc (or some disk or partition that you have available)
vgcreate cinder-volumes /dev/sdc

That's about it, that will give you dedicated partitions/volume groups and
it will persist over reboots.  I'd also suggest you read up a big on LVM to
get a better idea of what those commands do and how all of this works.

Hope that helps,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Help About The Documentation

2013-04-30 Thread John Griffith
On Tue, Apr 30, 2013 at 9:44 AM, Sylvain Bauza
wrote:

>  Indeed. There is room for improvement : should the 2 disks be RAID1 or
> parts of the same VG, as said ?
>
> As it is recommended hardware, it would be interesting to know which kind
> of setup with 2 SATA disks is optimal ?
>
> Of course, it does depend a lot of the usage : if you need to boot from
> volume, I would say having 2 physical PVs is better, but if you need to
> store critical data, then the RAID one is fine.
>
> -Sylvain
>
> Le 30/04/2013 14:35, Alexandre De Carvalho a écrit :
>
> Here the link :
> http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-system-requirements.html
>
>  regards,
> Alexandre
>
> 2013/4/30 Razique Mahroua 
>
>> Hi,
>> can you provide us the link ?
>> I think that means create an LVM VG made of two disks (so two PV) that
>> you will call "nova-volume"
>> Regards,
>>
>>  *Razique Mahroua** - **Nuage & Co*
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15 <%2B33%209%2072%2037%2094%2015>
>>
>>
>>  Le 30 avr. 2013 à 09:49, Alexandre De Carvalho <
>> alexandre7.decarva...@gmail.com> a écrit :
>>
>>   Hi everyone !
>>
>>  I found these ones in the documentation : "Volume storage: two disks
>> with 2 TB (SATA) for volumes attached to the compute nodes". And I don't
>> understand this sentence. Someone can explain to me this sentence, please ?
>>
>>  Thanks !
>>
>>  Have a good day !
>>
>>  --
>> regards,
>> Alexandre
>>
>>
>>   ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Sylvain,

This doc is a bit outdated and references Nova Volumes etc, however the
problem I think you're having is that it makes some assumptions regarding
knowledge of how all the components tie together and what they do.  They're
simply guidelines for possible configurations, however given the
flexibility of OpenStack and the numerous use cases I've always thought
this was sort of a difficult task (recommended hardware configs).

That being said, the Volume Group and disk portion of that doc that's being
discussed is in relation to your block-storage through Cinder.  This is the
back-end storage that you're configuring Cinder to use.  The preference
regarding RAID, Size etc are completely up to you, but you can make some of
those decisions based upon how you intend to use your OpenStack deployment.

For example you can just take any free disks/partitions on your Cinder
node, create one big LVM VG out of them (cinder-volumes) and the default
Cinder set up would then allocate space from this VG any time you do a
"cinder create".  The recommendations in the doc are geared toward what
would typically be required to have a functional setup, the size,
configuration and type of disks you use is going to vary depending upon how
many tenants you plan to have, how much block storage you suspect they'll
deploy and what kind of performance they're going to require.

The other thing to keep in mind is OpenStack is fully scale-out, so you can
start with something and as you need more storage for Cinder you can add
Cinder nodes with more disks/VG's.

I hope that helps.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder restarting every second with cryptic error

2013-04-29 Thread John Griffith
Hi Drew,

I think the gist listed here [1], will address the issue.  I'm going to
need to spin things up and test it though.

Thanks,
John

[1] https://gist.github.com/j-griffith/5485632


On Mon, Apr 29, 2013 at 5:24 PM, John Griffith
wrote:

>
> On Mon, Apr 29, 2013 at 3:59 PM, Drew Weaver wrote:
>
>> Child 4300 exited with status 2
>
>
> Hi Drew,
>
> I think I know what's going on here.  In the Folsom release we had to add
> some conversion work to deal with migrating from iet to tgt.  One of the
> things we did here was added a kwarg to create_iscsi_target (old_name),
> this is handled by tgtadm just fine, however iet is not stripping this out
> before trying to just pass it in directly to the iet command.  The iet
> command sees this and  pukes.
>
> I'm looking for a clean way to get around this, other than just say "use
> tgtadm" for your iscsi helper.
>
> John
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder restarting every second with cryptic error

2013-04-29 Thread John Griffith
On Mon, Apr 29, 2013 at 3:59 PM, Drew Weaver  wrote:

> Child 4300 exited with status 2


Hi Drew,

I think I know what's going on here.  In the Folsom release we had to add
some conversion work to deal with migrating from iet to tgt.  One of the
things we did here was added a kwarg to create_iscsi_target (old_name),
this is handled by tgtadm just fine, however iet is not stripping this out
before trying to just pass it in directly to the iet command.  The iet
command sees this and  pukes.

I'm looking for a clean way to get around this, other than just say "use
tgtadm" for your iscsi helper.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OpenStack Training

2013-04-25 Thread John Griffith
On Thu, Apr 25, 2013 at 2:15 PM, Chris Bartels  wrote:

> Hi,
>
> ** **
>
> My experience with virtualization has been limited to the ProxmoxVE
> platform, and with it I’m quite adept after working with it for a few
> years, however I’m looking forward to migrating to OpenStack & would like
> to find a way to learn as much about it as I can, in as efficient a manner
> as possible.
>
> ** **
>
> I’m currently in the process of selling my laptop on eBay so that I can
> buy a cheap used server with which to tinker with the new OpenStack Grizzly
> release so I can start to learn first-hand about working with the software,
> so I have that to look forward to, but I’m also on the lookout for more
> opportunities to soak up information.
>
> ** **
>
> Today I found the ‘OpenStack Foundation’ YouTube channel, and have been
> watching videos all morning. I’m happy with this to a degree. One in
> particular entitled “Solving The OpenStack Talent Gap” turned me on to a
> resource called ‘Cloud Academy’, which seemed promising at first, but after
> getting registered with them- as far as I can tell they don’t have training
> content up & available yet, as their project is in its infancy apparently.
> 
>
> ** **
>
> So I come to you all here on the list for suggestions as to whether there
> exists reputable formal online training that I can sign up for somewhere-
> free is better however I don’t mind spending a thousand dollars for
> top-notch training if it provides an industry recognized certification at
> the end such as the CompTIA A+ (which I’m signed up for this fall, btw-
> because it’s the closest I can get to what I’m after at the local community
> college).
>
> ** **
>
> What do people here know that I don’t know about OpenStack learning &
> training? Do any programs stand out as being great that you know of?
>
> ** **
>
> Please advise.
>
> ** **
>
> ** **
>
> Kindest Regards,
>
> -Chris
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hey Chris,

Welcome, I don't have much input regarding your questions on the best
training resources other than docs and diving in to OpenStack.

That being said, you might want to reconsider selling your laptop, you can
run OpenStack in a VM on your laptop just fine, and in fact checkout:
http://devstack.org for a very easy way to get started and experimenting
with OpenStack.

Good Luck,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder Multi-Backend Documentation

2013-03-15 Thread John Griffith
Jerome,

I would love for you to assign it to yourself :)  You've already done quite
a bit of work here with Tempest etc, so as long as hubcap has no objections
I say go for it.  Just make sure you put him on the review since he's the
master-mind.

John

On Fri, Mar 15, 2013 at 8:03 AM, Jérôme Gallard wrote:

> Hi John, Michael,
>
> I would like to help for the Cinder documentation.
>
> I have noticed that there is no open bug for the multi-backend
> documentation.
> Anne allowed me to open a bug (
> https://lists.launchpad.net/openstack/msg21938.html ).
> Is it OK for you if I assign this bug to me or do you have any other
> plans for the writing of this documentation?
>
> If it's OK for you, I will write this documentation with the help of:
> https://wiki.openstack.org/wiki/Cinder-multi-backend
>
> Thanks a lot,
> Jérôme
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Suggestions for shared-storage cluster file system

2013-02-15 Thread John Griffith
On Fri, Feb 15, 2013 at 1:08 PM, JR  wrote:

> Is there anyone using GPFS (General Parallel Filesystem) from IBM.  It's
> high performing, posix compliant, can do internal replication, etc...?
>
> To make it work, would one simply have to modify the nova-volume (or
> cinder) code that creates a volume-group using the corresponding GPFS
> commands?  Or, are there other complexities?  Which code would I look in
> to see what's involved?
>
> JR
>
>
> On 2/15/2013 2:54 PM, Samuel Winchenbach wrote:
> > Thanks,
> >
> > I think I will go with GlusterFS.   MooseFS looks interesting, but
> > maintaining a package outside the repo/cloud archive is not something I
> > want to deal with.
> >
> > Along the same lines...   is it possible to mount a GlusterFS volume in
> > pacemaker?  I have tried both ocf:heartbeat:Filesystem and
> > ocf:redhat:netfs.sh without much luck.   I have managed to get the
> > service started with upstart though.
> >
> > Thanks,
> > Sam
> >
> >
> > On Fri, Feb 15, 2013 at 2:29 PM, Sébastien Han  > > wrote:
> >
> > Hi,
> >
> >
> > Important: Mount the CephFS filesystem on the client machine,
> > not the cluster machine.
> >
> >
> > It's just like NFS, if you mount an NFS export on the NFS server,
> > you get kernel locks.
> >
> > Unfortunately even if love Ceph far more than the other, I won't go
> > with CephFS, at least not know. But if are in a hurry and looking
> > for a DFS then GlusterFS seems to be a good candidate. NFS works
> > pretty well too.
> >
> > Cheers.
> >
> > --
> > Regards,
> > Sébastien Han.
> >
> >
> > On Fri, Feb 15, 2013 at 4:49 PM, JuanFra Rodriguez Cardoso
> >  > > wrote:
> >
> > Another one:
> >
> >  - MooseFS
> > (
> http://docs.openstack.org/trunk/openstack-compute/admin/content/installing-moosefs-as-backend.html
> )
> >  - GlusterFS
> >  - Ceph
> >  - Lustre
> >
> > Regards,
> > JuanFra
> >
> >
> > 2013/2/15 Samuel Winchenbach  > >
> >
> > Hi All,
> >
> > Can anyone give me a recommendation for a good
> > shared-storage cluster filesystem?   I am running
> > kvm-libvirt and would like to enable live migration.
> >
> > I have a number of hosts (up to 16) each with 2xTB drives.
> >  These hosts are also my compute/network/controller nodes.
> >
> > The three I am considering are:
> >
> > GlusterFS - I have the most experience with this, and it
> > seems the easiest.
> >
> > CephFS/RADOS - Interesting because glance supports the rbd
> > backend.  Slightly worried because of this though "Important:
> > Mount the CephFS filesystem on the client machine, not the
> > cluster machine."
> > (I wish it said why...)  and "CephFS is not quite as stable
> > as the block device and the object storage gateway."
> > Lustre - A little hesitant now that Oracle is involved with
> it.
> >
> >
> > If anyone has any advice, or can point out another that I
> > should consider it would be greatly appreciated.
> >
> > Thanks!
> >
> > Sam
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
Don't know about folks that might have their own implementation, but
currently nothing in Cinder.  The closest thing to use to get an idea of
the driver is the pending Gluster work:
https://review.openstack.org/#/c/21342/

John
___
Mailing list: https://launchpad.net/~openstack
Post to

Re: [Openstack] Cinder-volume doesn't start anymore...

2013-02-02 Thread John Griffith
On Sat, Feb 2, 2013 at 1:34 PM, Martinx - ジェームズ
wrote:

> No one can help me with this?
> My cinder-volume process is completely down.
> I don't know what I can do to fix this issue...
>
> Thanks!
> Thiago
>
>
> On 1 February 2013 19:49, Martinx - ジェームズ wrote:
>
>> Guys,
>>
>>  At first, tgt was running after one "controller.teste.com" reboot but,
>> I know I'm using ietd, so, I stop tgt and remove the init script of if and
>> started ietd manually...
>>
>>  But cinder doesn't start up anymore...   :(
>>
>>  I really appreciate any kind of help here...
>>
>>  Someone on IRC channel told me that Cinder is trying to use
>> "_get_target" function in the TargetAdmin class but, how can Cinder use tgt
>> if "iscsi_helper = ietadm" ?
>>
>> Best,
>> Thiago
>>
>> On 1 February 2013 19:20, Martinx - ジェームズ wrote:
>>
>>> Guys,
>>>
>>>  At my Cinder logs, I'm seeing this when I run
>>> "/etc/init.d/cinder-volume start":
>>>
>>> 
>>> 2013-02-01 18:16:20 1075 AUDIT cinder.service [-] Starting cinder-volume
>>> node (version 2012.2.1-LOCALBRANCH:LOCALREVISION)
>>> 2013-02-01 18:16:21 DEBUG cinder.utils
>>> [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Running cmd
>>> (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs
>>> --noheadings -o name execute
>>> /usr/lib/python2.7/dist-packages/cinder/utils.py:163
>>> 2013-02-01 18:16:22 DEBUG cinder.utils
>>> [req-1ebb9638-2300-456a-995e-382c96f6632d None None] backend >> 'cinder.db.sqlalchemy.api' from
>>> '/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.pyc'>
>>> __get_backend /usr/lib/python2.7/dist-packages/cinder/utils.py:477
>>> 2013-02-01 18:16:23 DEBUG cinder.volume.manager
>>> [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Re-exporting 1 volumes
>>> init_host /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:98
>>> 2013-02-01 18:16:23 1075 CRITICAL cinder [-] Got unknown keyword args to
>>> utils.execute: {'old_name': None}
>>> 2013-02-01 18:16:23 1075 TRACE cinder Traceback (most recent call last):
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File "/usr/bin/cinder-volume",
>>> line 48, in 
>>> 2013-02-01 18:16:23 1075 TRACE cinder service.wait()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/service.py", line 422, in wait
>>> 2013-02-01 18:16:23 1075 TRACE cinder _launcher.wait()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/service.py", line 127, in wait
>>> 2013-02-01 18:16:23 1075 TRACE cinder service.wait()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in
>>> wait
>>> 2013-02-01 18:16:23 1075 TRACE cinder return self._exit_event.wait()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait
>>> 2013-02-01 18:16:23 1075 TRACE cinder return hubs.get_hub().switch()
>>>  2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch
>>> 2013-02-01 18:16:23 1075 TRACE cinder return self.greenlet.switch()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in
>>> main
>>> 2013-02-01 18:16:23 1075 TRACE cinder result = function(*args,
>>> **kwargs)
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/service.py", line 88, in run_server
>>> 2013-02-01 18:16:23 1075 TRACE cinder server.start()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/service.py", line 159, in start
>>> 2013-02-01 18:16:23 1075 TRACE cinder self.manager.init_host()
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 101, in
>>> init_host
>>> 2013-02-01 18:16:23 1075 TRACE cinder
>>> self.driver.ensure_export(ctxt, volume)
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/volume/driver.py", line 352, in
>>> ensure_export
>>> 2013-02-01 18:16:23 1075 TRACE cinder old_name=old_name)
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 198, in
>>> create_iscsi_target
>>> 2013-02-01 18:16:23 1075 TRACE cinder self._new_target(name, tid,
>>> **kwargs)
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 211, in
>>> _new_target
>>> 2013-02-01 18:16:23 1075 TRACE cinder **kwargs)
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 60, in _run
>>> 2013-02-01 18:16:23 1075 TRACE cinder self._execute(self._cmd,
>>> *args, run_as_root=True, **kwargs)
>>> 2013-02-01 18:16:23 1075 TRACE cinder   File
>>> "/usr/lib/python2.7/dist-packages/cinder/utils.py", line 142, i

Re: [Openstack] (no subject)

2013-02-02 Thread John Griffith
On Sat, Feb 2, 2013 at 9:49 AM, Thierry Carrez wrote:

> Xiazhihui (Hashui, IT) wrote:
> > 1.I want to know if grizzly-3 is the last of Grizzly? Will it have a
> > grizzly-4?
>
> No there won't be another milestone. The release schedule appears at:
> http://wiki.openstack.org/GrizzlyReleaseSchedule
>
> The release cycle is explained at:
> http://wiki.openstack.org/ReleaseCycle
>
> The developer section of this page contains a few other useful pointers:
> http://wiki.openstack.org/HowToContribute
>
> > 2.I hava a cinder driver, if I want to commit it in grizzly-3. What's
> > the deadline of the codes committing? Should the code be approved by PTL
> > before 2013-02-21 ?
>
> The proposed change needs to be merged before the end of the day on
> February 19 (when we branch for grizzly-3 delivery). That means
> gathering necessary code review approvals before then. This can take
> time, so code should be submitted asap.
>
> > 3.Grizzly will public in April 2013, can I commit my blueprint codes
> > from 2013-02-21 to April 2013?
>
> No, Feb 19 is Feature Freeze, so if you don' tmake it by then, your
> feature will be part of the next release (Havana) instead.
>
> Engaging early with the developer community (and the project PTL) is the
> key to success. Ideally features would be presented to the design summit
> and implemented in the months after, to be integrated in the release at
> the end of the 6-month cycle.
>
> Regards,
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
In addition to everything that Thierry pointed out, I'd also like to
mention that Cinder is a bit unique.  Cinder is a bit different than other
projects because there's a constant flow of vendors wishing to implement
new drivers.  The result is we typically get to the final week or two of
the last feature milestone in a release cycle and suddenly half a dozen new
blue-prints for drivers are submitted.  This makes for a very troubling
week of trying to get reviews, tests etc while still getting all the
*normal* back-log of things in.

We're planning to have a session at the summit to agree upon and formalize
some policies around driver submissions.  Of course we still want to
encourage folks to contribute and participate, we just want to avoid the
trend of everything showing up in the last week of the milestone if
possible.

If you want to get a driver added to Cinder in time for Grizzly, please get
a BP submitted and get the patch in as soon as possible (ideally early this
coming week).  Also feel free to grab me on IRC and we can talk more about
where you're at and how we can make this happen for the Grizzly release.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova ceph integration

2013-01-31 Thread John Griffith
On Thu, Jan 31, 2013 at 11:43 AM, Sébastien Han wrote:

> Try to have a look at the boot from volume feature. Basically the disk
> base of your instance is an RBD volume from Ceph. Something will be
> remain in /var/lib/nova/instances but it's only the kvm xml file.
>
> http://ceph.com/docs/master/rbd/rbd-openstack/?highlight=openstack
>
> Cheers!
> --
> Regards,
> Sébastien Han.
>
>
> On Thu, Jan 31, 2013 at 7:40 AM, Wolfgang Hennerbichler
>  wrote:
> > Hi,
> >
> > I'm sorry if this has been asked before. My question is: can I integrate
> ceph into openstack's nova & cinder in a way, that I don't need
> /var/lib/nova/instances anymore? I'd like to have EVERYTHING in ceph,
> starting from glance images to nova-disk-images and volumes (cinder). And
> more important: Can this be done in a way so that my horizon-users can
> still use horizon (including snapshotting) without the need of abusing the
> command-line? :)
> > I've read that cinder and glance are supported, but I didn't find much
> information on nova-disk-images and ceph.
> >
> > thanks for a reply
> > wolfgang
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Boot from volume is one good option, another is to setup ceph and point
nova's insances_path to point to it.  I haven't done it with Ceph but I've
done this sort of thing using iSCSI mounts on the compute node.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] List of Cinder compatible devices

2013-01-31 Thread John Griffith
On Thu, Jan 31, 2013 at 8:56 AM, Koert van der Veer wrote:

>  In that case, it is probably best to transpose the table, with series
> included, the number of products will yield too many columns to be workable.
>
> Also: Do blank spaces indicate "not supported" or "unknown"?
>
> koert
>
>
> On 01/31/2013 04:47 PM, Shake Chen wrote:
>
> I think need add Vendor storage series.
>
> like not all the EMC storage would support Cinder.
>
>
>
>  On Thu, Jan 31, 2013 at 11:19 PM, Sébastien Han 
> wrote:
>
>> Just added some stuff about RBD where E refers to Essex.
>>
>> --
>> Regards,
>> Sébastien Han.
>>
>>
>> On Thu, Jan 31, 2013 at 11:20 AM, Avishay Traeger 
>> wrote:
>> > openstack-bounces+avishay=il.ibm@lists.launchpad.net wrote on
>> > 01/31/2013 12:37:07 AM:
>> >> From: Tom Fifield 
>> >> To: openstack@lists.launchpad.net,
>> >> Date: 01/31/2013 12:38 AM
>> >> Subject: Re: [Openstack] List of Cinder compatible devices
>> >> Sent by: openstack-bounces+avishay=il.ibm@lists.launchpad.net
>> >>
>> >> Here's a starting point:
>> >>
>> >> http://wiki.openstack.org/CinderSupportMatrix
>> >>
>> >> Regards,
>> >>
>> >> Tom
>> >
>> > Tom,
>> > Thanks for doing this.  I recommend that instead of "Y", we should put
>> the
>> > letter of the version in which the feature first appeared.  So for
>> example,
>> > "E", "F", "G", ...
>> >
>> > Thanks,
>> > Avishay
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to : openstack@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Shake Chen
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> So thanks for putting this together but this brings something up that I've
been meaning to raise on the dev-list anyway.  In my opinion it should be a
requirement that for a driver to be accepted in Cinder it implements all of
the functionality of the base LVM driver (ie all of the rows listed in the
matrix here).

Having to go through and determine what feature is or is not supported per
driver is EXACTLY what I want to avoid. If we go down the path of building
a matrix and allowing partial integration it's going to create a huge mess
and IMO the user experience is going to suffer greatly.  Of course a driver
can do more than what's on the list, but I think this is the minimum
requirement and I've been pushing back on submissions based on this.

The only exceptions have been some of the newer Grizzly features, but
that's only because we're moving those up to generalized cases that folks
can inherit from if they use iSCSI.  For those that want to do FC or AOE
drivers however they're going to need to have a solution of their own.

My thought is there should be a simple list of back-end device and version
and whether it's supported in Grizzly or Folsom or .  All API features
should be assumed available.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Copy glance image to cinder bootable volumes - "copy_image_to_volume"

2013-01-30 Thread John Griffith
On Wed, Jan 30, 2013 at 7:39 AM, Lei Zhang  wrote:

> I also have a question. What's the requirement for the image? I found
> nothing int the doc.
>
>
> On Tue, Jan 29, 2013 at 5:38 PM, Benoit ML  wrote:
>
>> Hello,
>>
>> Thank you ! nice :)
>> I'm really impatient to test cinder with NetApp device (soon it will be).
>>
>> In the documentation :
>>
>> http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html
>> The process is quite painful   ...
>>
>> Regards,
>>
>> 2013/1/29 Avishay Traeger :
>> > Benoit,
>> >
>> > openstack-bounces+avishay=il.ibm@lists.launchpad.net wrote on
>> > 01/29/2013 10:56:33 AM:
>> >> Hello,
>> >>
>> >> I have an openstack installation with 1 controller node, 1 network
>> >> node and 2 compute node, configured with GRE tunnel for the network,
>> >> and NFS backend for volumes.
>> >>
>> >> I'd like to create a bootable cinder volume from a glance image to
>> >> have persistant disque for VMs, and tests live migration in this
>> >> setup.
>> >>
>> >> But when I ask cinder to create a volume from a image, cinder report
>> >> "not supported" ... And I have look into the code, it's seems to be
>> >> supportend only with Ceph/Rados or Iscsi driver.
>> >>
>> >> So I have many questions :
>> >> - Any plan to support it for other driver/setupe like :  NetAppIscsi
>> >> (or netappNFS Driver) ; NFS driver   ?
>> >
>> > I have a patch submitted that will implement this for all iSCSI drivers:
>> > https://review.openstack.org/#/c/19808/
>> > I don't know about NetApp's plans for other drivers.
>> >
>> >> - Any simple way to create a bootable cinder volume from the
>> >> controller node shell ?  (In the doc I must mount the volume on a VM
>> >> ... create partition .. copy data and so on ; lots of manipulation..)
>> >
>> > I don't understand this question.
>> >
>> >> And of course, I have the same question for cinder snapshot.
>> >>
>> >> Thank you in advance !
>> >>
>> >> Regards,
>> >>
>> >> --
>> >> --
>> >> Benoit
>> >
>> > Thanks,
>> > Avishay
>> >
>>
>>
>>
>> --
>> --
>> Benoit
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Lei Zhang
>
> Blog: http://jeffrey4l.github.com
> twitter/weibo: @jeffrey4l
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> In Grizzly you can add an image-id to the create call.  The create will do
a conversion on the image to raw and write it to the volume directly, then
you can boot it in Nova.

The sequence is something like this:
cinder create --image-id  --display-name mybootable-vol 10
nova boot --image  --flavor 
--block-device-mapping vda= --key-name
 my-test-instance

The implementatio in Folsom isn't quite as far along.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] which is the level of unit test cases should be covered

2013-01-22 Thread John Griffith
On Mon, Jan 21, 2013 at 8:58 PM, Robert Collins
wrote:

> On 22 January 2013 16:37, Xiazhihui (Hashui, IT) 
> wrote:
> > Hi friends,
> >
> >
> >
> >  I want to upload a volume driver, right now I’m writing unit
> test
> > case code ( it’s also need to be uploaded).
> >
> >
> >
> >  And I do not know the requirements of the unit test code. Which
> is
> > the level of unit test cases in my unit test code should be covered:
> > Function Coverage, Condition coverage, Decision Coverage, Statement
> Coverage
> > or others? Or should I write what I think needs?
>
> Pragmatically speaking, code should be tested such that if either:
>  - some precondition it has is changed (either elsewhere in the same
> code base or in the behaviour of some other code base) that we find
> out
>  - if someone changes the code itself and breaks an existing use case,
> we find out.
>
> Exactly what that means may be different for different routines :).
>
> My general rule is to start with testing each entry and exit path and
> any domain or range corner cases.
>
> -Rob
> --
> Robert Collins 
> Distinguished Technologist
> HP Cloud Services
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
You can use some of the other back-end driver tests as a starting point or
reference, and submit a review and go from there.  Also feel free to grab
somebody on IRC in #openstack-cinder and maybe we can help answer more
detailed questions you have there.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Fwd: [Cinder]

2013-01-11 Thread John Griffith
On Fri, Jan 11, 2013 at 3:47 AM, Sajid Akhtar  wrote:

> Hi Yonny,
>
> OpenStack modules such as Cinder are dependent on the Vendor driver on
> Openstack to achieve LUN provisioning and maintenance operations on the
> respective storage controller.
>
> Object Storage (Swift)
>
> OpenStack Object Storage 
> (Swift) is
> a massively scalable redundant storage system. Objects and files are
> written to multiple disk drives spread throughout servers in the data
> center, with the OpenStack software responsible for ensuring data
> replication and integrity across the cluster. Storage clusters scale
> horizontally simply by adding new servers. Should a server or hard drive
> fail, OpenStack replicates its content from other active nodes to new
> locations in the cluster. Because OpenStack uses software logic to ensure
> data replication and distribution across different devices, inexpensive
> commodity hard drives and servers can be used.
>
> In Aug 2009, Rackspace started the development of Swift, which is a
> complete replacement for the *Cloud Files* product. The initial
> development team consists of nine developers. 
> [14]
>  
> [edit
> ]Block Storage (Cinder)
>
> OpenStack Block Storage 
> (Cinder) provides
> persistent block level storage devices for use with OpenStack compute
> instances. The block storage system manages the creation, attaching and
> detaching of the block devices to servers. Block storage volumes are fully
> integrated into OpenStack Compute and the Dashboard allowing for cloud
> users to manage their own storage needs. In addition to using simple Linux
> server storage, it has unified storage support for numerous storage
> platforms including Ceph , 
> NetApp
> , Nexenta  and 
> SolidFire.
> Block storage is appropriate for performance sensitive scenarios such as
> database storage, expandable file systems, or providing a server with
> access to raw block level storage. Snapshot management provides powerful
> functionality for backing up data stored on block storage volumes.
> Snapshots can be restored or used to create a new block storage volume.
>
> For more information you may refer to
> https://en.wikipedia.org/wiki/OpenStack
>
> http://docs.openstack.org/developer/swift/#
>
> -- Forwarded message --
> From: Yonny Luis Leyva Suárez 
> Date: Fri, Jan 11, 2013 at 3:10 AM
> Subject: [Openstack] [Cinder]
> To: openstack@lists.launchpad.net
>
>
>  Hello,
>
> I have a big doubt.
>
> Cinder and Swift, are 2 separated services, but openstack talk about
> Storage controller.
>
> What Cinder and Switft does ?
> Can i use two NAS iSCSI with separated LUN for those services or need
> servers for Swift?
>
> Thanks a lot
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> --
> With Regards
> Sajid Akhtar
> Twitter: @mail2fashion
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Just to add a little to Sajid's response, there is of course a default LVM
implementation for Cinder/Block Storage in addition to the supported back
ends that were mentioned.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Cinder] cinder-agent

2013-01-05 Thread John Griffith
On Fri, Jan 4, 2013 at 11:39 AM, Akira Yoshiyama
wrote:

> Hi all,
>
> JOSUG (Japanese OpenStack User Group) had a regular hackathon in Tokyo
> last month.
> We discussed about Quantum and Cinder, and got an idea about
> 'cinder-agent'.
>
> Now Cinder has many server-side drivers for volume service and
> nova-compute has
> client-side drivers to use it. If other software like CloudStack,
> OpenNebula and so on use
> Cinder, they will have to implement their own client-side drivers for
> Cinder. But they don't
> have to do it for Quantum because it has a client service
> 'quantum-agent' and others.
>
> I think Cinder should have its own client service 'cinder-agent'.
> There are many benefits:
>
> * We can remove volume-related drivers (server/client side) from Nova
> perfectly.
>   * Nova can be used with newer/older Cinder.
>   * Both-side volume drivers can be added or updated with one patch for
> Cinder.
> * Attaching/detaching volume API can be simple because Cinder can use
> RPC to do them.
>   For example:
> Attaching volume request:
>   POST
> /v2/{tenant_id}/servers/{server_id}/os-volume_attachments_with_agent
>   {'volume'] '{volume_id}', 'host': '{host_name}'}
> Response body:
>   {'volume': '{volume_id}', 'host': '{host_name}', 'path':
> '{device_path}'}
> # {host_name}: the host name with nova-compute and cinder-agent
> * Of course, any software can use Cinder without client-side volume
> drivers.
>
> Any comments?
>
> Regards,
>Akira YOSHIYAMA 
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
Hi Akira,

This is something I've thought about a little bit but to be honest it's
been very low on my priority list.  I've be very interested in pursuing the
idea further and getting more input/feedback from the community.  I think
there are some significant benefits to this for NTT and a few other end
users as well as obvious wins for those vendors with storage drivers in
Cinder.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] two or more NFS / gluster mounts

2012-12-20 Thread John Griffith
On Thu, Dec 20, 2012 at 9:37 AM, JuanFra Rodriguez Cardoso <
juanfra.rodriguez.card...@gmail.com> wrote:

> Yes, I'm really agree with Diego.
> It would be a good choice for submitting a blueprint with this storage
> feature based on tenants.
>
> According to current quotas control, it limits the:
>
>-
>
>Number of volumes which may be created
>-
>
>Total size of all volumes within a project as measured in GB
>-
>
>Number of instances which may be launched
>-
>
>Number of processor cores which may be allocated
>- Publicly accessible IP addresses
>
>
> Another new feature related to shared storage we had thought about, it's
> to include an option for choosing if an instance has to be replicated or
> not, i.e. in a MooseFS scenario, to indicate goal (number of replicas).
> It's useful for example in testing or demo projects, where HA is not
> required.
>
> Regards,
>
> JuanFra.
>
> 2012/12/20 Diego Parrilla Santamaría 
>
>> mmm... not sure if the concept of oVirt multiple storage domains is
>> something that can be implemented in Nova as it is, but I would like to
>> share my thoughts because it's something that -from my point of view-
>> matters.
>>
>> If you want to change the folder where the nova instances are stored you
>> have to modify the option in nova-compute.conf  'instances_path':
>>
>> If you look at that folder (/var/lib/nova/instances/ by default) you will
>> see a structure like this:
>>
>> drwxrwxr-x   2 nova nova   73 Dec  4 12:16 _base
>> drwxrwxr-x   2 nova nova5 Oct 16 13:34 instance-0002
>> ...
>> drwxrwxr-x   2 nova nova5 Nov 26 17:38 instance-005c
>> drwxrwxr-x   2 nova nova6 Dec 11 15:38 instance-0065
>>
>> If you have a shared storage for that folder, then your fstab entry looks
>> like this one:
>> 10.15.100.3:/volumes/vol1/zone1/instances /var/lib/nova/instances nfs
>> defaults 0 0
>>
>> So, I think that it could be possible to implement something like
>> 'storage domains', but tenant/project oriented. Instead of having multiple
>> generic mountpoints, each tenant would have a private mountpoint for
>> his/her instances. So the /var/lib/nova/instances could look like this
>> sample:
>>
>> /instances
>> +/tenantID1
>> ++/instance-X
>> ++/instance-Y
>> ++/instance-Z
>> +/tenantID2
>> ++/instance-A
>> ++/instance-B
>> ++/instance-C
>> ...
>> +/tenantIDN
>> ++/instance-A
>> ++/instance-B
>> ++/instance-C
>>
>> And in the /etc/fstab something like this sample too:
>> 10.15.100.3:/volumes/vol1/zone1/instances/tenantID1
>> /var/lib/nova/instances/tenantID1 nfs defaults 0 0
>> 10.15.100.3:/volumes/vol1/zone1/instances/tenantID2 
>> /var/lib/nova/instances/tenantID2 nfs
>> defaults 0 0
>> ...
>> 10.15.100.3:/volumes/vol1/zone1/instances/tenantIDN
>> /var/lib/nova/instances/tenantIDN nfs defaults 0 0
>>
>> With this approach, we could have something like per tenant QoS on shared
>> storage to resell differente storage capabilities on a tenant basis.
>>
>> I would love to hear feedback, drawback, improvements...
>>
>> Cheers
>> Diego
>>
>>  --
>> Diego Parrilla
>> *CEO*
>> *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
>> skype:diegoparrilla*
>> * 
>> *
>>
>> *
>>
>>
>>
>>
>> On Thu, Dec 20, 2012 at 4:32 PM, Andrew Holway wrote:
>>
>>> Good plan.
>>>
>>>
>>> https://blueprints.launchpad.net/openstack-ci/+spec/multiple-storage-domains
>>>
>>>
>>> On Dec 20, 2012, at 4:25 PM, David Busby wrote:
>>>
>>> > I may of course be entirely wrong :) which would be cool if this is
>>> achievable / on the roadmap.
>>> >
>>> > At the very least if this is not already in discussion I'd raise it on
>>> launchpad as a potential feature.
>>> >
>>> >
>>> >
>>> >
>>> > On Thu, Dec 20, 2012 at 3:19 PM, Andrew Holway 
>>> wrote:
>>> > Ah shame. You can specify different storage domains in oVirt.
>>> >
>>> > On Dec 20, 2012, at 4:16 PM, David Busby wrote:
>>> >
>>> > > Hi Andrew,
>>> > >
>>> > > An interesting idea, but I am unaware if nova supports storage
>>> affinity in any way, it does support host affinity iirc, as a kludge you
>>> could have say some nova compute nodes using your "slow mount" and reserve
>>> the "fast mount" nodes as required, perhaps even defining separate zones
>>> for deployment?
>>> > >
>>> > > Cheers
>>> > >
>>> > > David
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > On Thu, Dec 20, 2012 at 2:53 PM, Andrew Holway <
>>> a.hol...@syseleven.de> wrote:
>>> > > Hi David,
>>> > >
>>> > > It is for nova.
>>> > >
>>> > > Im not sure I understand. I want to be able to say to openstack;
>>> "openstack, please install this instance (A) on this mountpoint and please
>>> install this instance (B) on this other mountpoint." I am planning on
>>> having two NFS / Gluster based stores, a fast one and a slow one.
>>> > >
>>> > > I probably will not want to say please every time :)
>>> > >
>>> > > Thanks,
>>> > >
>>> > > Andrew
>>> 

Re: [Openstack] Cinder-Volume installer for Windows Storage Server 2012

2012-12-12 Thread John Griffith
On Wed, Dec 12, 2012 at 11:02 AM, Alessandro Pilotti  wrote:

>  Hi guys, we just released an installer for Cinder Volume on Windows
> Server 2012:
>
> http://www.cloudbase.it/cinder-volume-on-windows-storage-server-2012/
>
> One of the great advantages of integrating Windows solutions in the
> OpenStack ecosystem is the ease of management and deployment, and Cinder is
> no exception.
> All you need to start is a physical or virtual host running Windows Server
> 2012 or Windows Storage Server 2012 and a copy of our Cinder volume
> installer.
>
> Thanks in advance for your feedback and testing! :-)
>
>
> Alessandro Pilotti
>   Cloudbase Solutions | CEO
> -
> MVP ASP.Net / IIS
> Windows Azure Insider
> Red Hat Certified Engineer
> -
>
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Nicely done Alessandro!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Duplication of code in nova and cinder

2012-12-11 Thread John Griffith
On Tue, Dec 11, 2012 at 6:34 PM, Joshua Harlow wrote:

> Isn't that a lets fix the slowness instead of continue bad behavior.
>
> Fix the root problem and don't bypass it in the first place?
>
> Then said root problem is solved for everyone and isn't pushed into the
> future (as is typically done).
>
> On 12/11/12 5:31 PM, "Huang Zhiteng"  wrote:
>
> >On Wed, Dec 12, 2012 at 8:56 AM, Joshua Harlow 
> >wrote:
> >> Related to this, how do we in the future stop such code-copying from
> >> happening in the first place?
> >>
> >> Is it just that there needs to be a place for this (oslo?) that can be
> >> updated more quickly, or something similar?
> >>
> >> I'm always sorta 'weirded out' when people say that they copied some
> >>code in
> >> the name of 'it was quicker' or we are just 'borrowing it'.
> >But you have to admit 'it is quicker'.  My experience is getting
> >common code into Oslo and then port to project usually take two times
> >longer time to merge, in best case.
> >>
> >> From: John Griffith 
> >> Date: Tuesday, December 11, 2012 3:36 PM
> >> To: Sam Morrison 
> >> Cc: OpenStack mailing list 
> >> Subject: Re: [Openstack] Duplication of code in nova and cinder
> >>
> >>
> >>
> >> On Tue, Dec 11, 2012 at 4:24 PM, Sam Morrison 
> >>wrote:
> >>>
> >>> I attempted to create a volume from an image in cinder and was getting
> >>> this strange error, turns out it was because I had my glance servers
> >>> specified as https://glanceserver:9292
> >>>
> >>> In cinder the version of images/glance.py is older than the one in nova
> >>> and is missing the ssl support additions.
> >>> https://bugs.launchpad.net/cinder/+bug/1089147
> >>>
> >>> My real question is why is there one version is nova and one version in
> >>> cinder. I also think there is quite a bit more unnecessary duplication.
> >>> Should it all go into oslo?
> >>>
> >>> Cheers,
> >>> Sam
> >>>
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~openstack
> >>> Post to : openstack@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~openstack
> >>> More help   : https://help.launchpad.net/ListHelp
> >>
> >> Hi Sam,
> >>
> >> Short answer is "yes".  Need to check scoping etc and make sure that it
> >>does
> >> in fact fit within the parameters of OSLO.  It's something I thought of
> >>a
> >> couple weeks ago but to be honest it's been low on my list personally
> >>and
> >> nobody else that I know of has shown an interest in picking it up.
> >>
> >> You'll notice another image related item we're *borrowing* from Nova
> >> (cinder.image.image_utils).  In both cases there are slight
> >>modifications to
> >> fit Cinder's use case that given a bit of work could easily be shared.
> >>
> >> John
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : openstack@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> >
> >
> >--
> >Regards
> >Huang Zhiteng
>
> The reality is that sometimes copying (or borrowing) code from another
project is in fact that best way to go.  Personally my opinion is that in
some cases, if there's a module that's needed that exists in another
OpenStack project but is not available in OSLO then by all means it should
be used (as it has here).  At the same time there are cases where a major
component (for example the filter scheduler patch in Cinder) should be held
up until the common code is in fact available in OSLO.  There's also a
third case where the patch should move forward as is, but a BP should be
submitted against OSLO (IMO).

With respect to how to address "bad behavior", I think that's a bit strong
of a term (especially since I'm guilty of copying/borrowing files from
Nova).  Keep in mind that Cinder started as a *copy* of Nova, and while
it's growing and we're making adjustments and corrections as we go, the
reality is there's going to be things like this that come up, especially
for the first release cycle or two of Cinder.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Duplication of code in nova and cinder

2012-12-11 Thread John Griffith
On Tue, Dec 11, 2012 at 4:36 PM, John Griffith
wrote:

>
>
> On Tue, Dec 11, 2012 at 4:24 PM, Sam Morrison  wrote:
>
>> I attempted to create a volume from an image in cinder and was getting
>> this strange error, turns out it was because I had my glance servers
>> specified as https://glanceserver:9292
>>
>> In cinder the version of images/glance.py is older than the one in nova
>> and is missing the ssl support additions.
>> https://bugs.launchpad.net/cinder/+bug/1089147
>>
>> My real question is why is there one version is nova and one version in
>> cinder. I also think there is quite a bit more unnecessary duplication.
>> Should it all go into oslo?
>>
>> Cheers,
>> Sam
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
> Hi Sam,
>
> Short answer is "yes".  Need to check scoping etc and make sure that it
> does in fact fit within the parameters of OSLO.  It's something I thought
> of a couple weeks ago but to be honest it's been low on my list personally
> and nobody else that I know of has shown an interest in picking it up.
>
> You'll notice another image related item we're *borrowing* from Nova
> (cinder.image.image_utils).  In both cases there are slight modifications
> to fit Cinder's use case that given a bit of work could easily be shared.
>
> John
>

BTW, we can update to include the SSL changes your bug references right
away.  Long term, I'd like to go with the OSLO approach.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Duplication of code in nova and cinder

2012-12-11 Thread John Griffith
On Tue, Dec 11, 2012 at 4:24 PM, Sam Morrison  wrote:

> I attempted to create a volume from an image in cinder and was getting
> this strange error, turns out it was because I had my glance servers
> specified as https://glanceserver:9292
>
> In cinder the version of images/glance.py is older than the one in nova
> and is missing the ssl support additions.
> https://bugs.launchpad.net/cinder/+bug/1089147
>
> My real question is why is there one version is nova and one version in
> cinder. I also think there is quite a bit more unnecessary duplication.
> Should it all go into oslo?
>
> Cheers,
> Sam
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
Hi Sam,

Short answer is "yes".  Need to check scoping etc and make sure that it
does in fact fit within the parameters of OSLO.  It's something I thought
of a couple weeks ago but to be honest it's been low on my list personally
and nobody else that I know of has shown an interest in picking it up.

You'll notice another image related item we're *borrowing* from Nova
(cinder.image.image_utils).  In both cases there are slight modifications
to fit Cinder's use case that given a bit of work could easily be shared.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Volume types

2012-12-10 Thread John Griffith
On Mon, Dec 10, 2012 at 10:05 AM, Daniel Oliveira wrote:

> Hello.
>
> I've been "playing" around with OpenStack, when I noticed a section in the
> Dashboard where you can create/delete volume types. The problem is, I
> didn't understand their purpose, as when you create a new type, you only
> specify its name. Can anyone tell me what are volume types used for?
>
> Thanks in advance
>
> --
> My best regards,
>
> Daniel Oliveira.
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Daniel,

The primary idea behind volume-types is a method to deal with multiple
back-ends.  The volume-type corresponds to a specific back-end, or perhaps
enables different characteristics of a back-end.  Hopefully that helps a
bit.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Basic Devstack question

2012-12-07 Thread John Griffith
On Fri, Dec 7, 2012 at 11:27 AM, Marco Bravo  wrote:

> Maybe is not the place to ask this but I'm sorry if is not
>
>
> I have this problem. *Couldn't find stack-screenrc *when I try to start
> Openstack after a reboot.
>
>
>- What I've losted?
>- How can I repair this?
>- Why sometimes happens and others , no?
>
>
> *
> *
> Tks Marco.
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hey Marco,
Not completely sure I follow your question, but the OpenStack services
don't restart on their own after a reboot.  You can try rejoin.sh if you
want to kick everything back off again without making any changes.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] LVM over LVM is acceptable?

2012-11-27 Thread John Griffith
On Tue, Nov 27, 2012 at 7:19 PM, Matt Joyce wrote:

> other hazard to mention.
>
> live fs resizes tend to be sketchy.  the growing of a live filesystem is
> possible and tends to work.  but shrinking for obvious reasons is very
> dangerous and can be wrought with peril.  also cannot be done live as far
> as I know for any ext filesystem.
>
> -matt
>
> On Tue, Nov 27, 2012 at 6:13 PM, Lei Zhang wrote:
>
>>  Got it.
>>
>> Could Cinder can check the created volume? I can not find any command
>> like cinder update. I try to extends the volume by lvextend, but data in
>> the cinder db doesn't update. So when I delete the changed volume, it raise
>> error.
>>
>> On Tue, Nov 27, 2012 at 12:34 PM, Dean Troyer  wrote:
>>
>> On Mon, Nov 26, 2012 at 8:04 PM, Lei Zhang 
>>> wrote:
>>> > Another question. If the vm treat the vol-0 as a normal block device,
>>> is it
>>> > necessary to partition? If not, the fdisk will show Disk /dev/vdb
>>> doesn't
>>> > contain a valid partition table. If yes, how can I extend the volume
>>> on the
>>> > vm? It seems that treat the volume as a normal block device is not a
>>> good
>>> > idea.
>>>
>>> It is not necessary to partition the device (vdb) inside com-0.  If
>>> you use it as an LVM physical device (PV) inside com-0 then pvresize
>>> will update the metadata o recognize the new size inside com-0 after
>>> you lvextend the vol-0 in the host.
>>>
>>> If you do partition /dev/vdb and don't use LVM in com-0 it is still
>>> possible to grow a partition, but you'll have to delete and re-create
>>> the last partition to get com-0 to recognize the additional space.
>>> And you'd also need to do the filesystem resize too.
>>>
>>> Nested LVM can be tricky but if you are careful to keep the layers
>>> separated it can work.
>>>
>>> dt
>>>
>>> --
>>>
>>> Dean Troyer
>>> dtro...@gmail.com
>>>
>> --
>> Lei Zhang
>>
>> Blog: http://jeffrey4l.github.com
>> twitter/weibo: @jeffrey4l
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
There is no functionality to re-size a Cinder Volume.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Volume handling

2012-11-16 Thread John Griffith
On Fri, Nov 16, 2012 at 3:17 AM, Nicolae Paladi  wrote:

> Hi,
>
> this is likely an RTFM question, but I haven't found any relevant 'FM' so
> I decided
> to ask on the mailing list before digging into the code:
>
> How are volumes mapped to the instances after they are restarted?
>

In terms of a reboot of the instance, I believe this is handled via the BDM
table in the DB, it's checked on a reboot and the attach is verified.


>
> How can a volume created earlier be identified to be attached to a newly
> spawned intance?
>

Not sure I see the question here, use the same process "nova volume-attach
  

>
> Are the IQNs created during volume creation exposed anywhere
> else than the compute nodes?
>

Nope, not really.  You can find what they are either by checking the DB or
checking the persistence file info for the volume
(/var/lib/cinder/volumes/xxx, or devstack:
/opt/stack/data/cinder/volumes/)


> Thanks,
> /Nico.
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cannot start "nova-api" service

2012-11-12 Thread John Griffith
On Mon, Nov 12, 2012 at 7:34 PM, Ahmed Al-Mehdi  wrote:

>
>
> From: John Griffith 
> Date: Monday, November 12, 2012 7:17 PM
> To: Jian Hua Geng 
> Cc: Ahmed Al-Mehdi , "
> openstack-bounces+gengjh=cn.ibm@lists.launchpad.net" <
> openstack-bounces+gengjh=cn.ibm@lists.launchpad.net>, "
> openstack@lists.launchpad.net" 
>
> Subject: Re: [Openstack] Cannot start "nova-api" service
>
>
>
> On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng  wrote:
>
>> By default both cinder and nova-api are listening on the same port 8776
>> (this should be a bug I think), you can try to change the default value in
>> the cinder.conf like: osapi_volume_listen_port = 8777 if you are running
>> the cinder and nova-api on the same machine.
>>
>> --
>> Best regard,
>> David Geng
>>
>> --
>>
>> [image: Inactive hide details for Ahmed Al-Mehdi ---11/13/2012 09:32:21
>> AM---Ahmed Al-Mehdi ]Ahmed Al-Mehdi ---11/13/2012
>> 09:32:21 AM---Ahmed Al-Mehdi 
>>
>>
>>*Ahmed Al-Mehdi *
>>Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.net
>>
>>11/13/2012 09:32 AM
>>
>>
>> To
>>
>>
>>Vishvananda Ishaya ,
>>
>>
>> cc
>>
>>
>>"openstack@lists.launchpad.net" 
>>
>>
>> Subject
>>
>>
>>Re: [Openstack] Cannot start "nova-api" service
>>
>>
>> Hello,
>>
>> Can someone please help me with a nova-api issue.  After install all the
>> nova services, all seem to be running fine, except for nova-api.  I even
>> reboot my controller node, no luck.  After reboot all services are running,
>> except nova-api.  When I manually start nova-api, nova-api crashes with the
>> following error "*error: [Errno 98] Address already in use*".  I
>> installed nova-volume earlier during the install process, but later on
>> installed cinder, and made the necessary modifications (as far as I can
>> tell) to nova-api.conf to use cinder for block storage.  Should I uninstall
>> nova-volume?
>>
>> 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting
>> keystone auth_token middleware
>> 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using
>> /var/lib/nova/keystone-signing as cache directory for signing certificate
>> 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use
>> 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last):
>> 2012-11-12 14:46:24 TRACE nova   File "/usr/bin/nova-api", line 50, in
>> 
>> 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api)
>> 2012-11-12 14:46:24 TRACE nova   File
>> "/usr/lib/python2.7/dist-packages/nova/service.py", line 584, in __init__
>> 2012-11-12 14:46:24 TRACE nova port=self.port)
>> 2012-11-12 14:46:24 TRACE nova   File
>> "/usr/lib/python2.7/dist-packages/nova/wsgi.py", line 72, in __init__
>> 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host,
>> port), backlog=backlog)
>> 2012-11-12 14:46:24 TRACE nova   File
>> "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in
>> listen
>> 2012-11-12 14:46:24 TRACE nova sock.bind(addr)
>> 2012-11-12 14:46:24 TRACE nova   File "/usr/lib/python2.7/socket.py",
>> line 224, in meth
>> 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args)
>> 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use
>> 2012-11-12 14:46:24 TRACE nova
>> 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died
>> unexpectedly, exiting
>> 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died
>> unexpectedly, exiting
>> 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server.
>> 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server.
>>
>> Would highly appreciate any pointers to understanding or resolving the
>> issue.
>>
>> Regards,
>> Ahmed.
>>
>>
>> *From: *Ahmed Al-Mehdi <*ah...@coraid.com* >*
>> Date: *Friday, November 9, 2012 12:45 AM*
>> To: *Vishvananda Ishaya <*vishvana...@gmail.com* >
>> *
>> Cc: *"*openstack@lists.launchpad.net* " <*
>> openstack@lists.launchpad.net* >*
>> Subject: *Re: [Openstack] Cannot start "nova-api" service
>>
>>
>>
>>*From: *Vishvananda Ishaya <*vishvana...@gmai

Re: [Openstack] Cannot start "nova-api" service

2012-11-12 Thread John Griffith
On Mon, Nov 12, 2012 at 6:57 PM, Jian Hua Geng  wrote:

> By default both cinder and nova-api are listening on the same port 8776
> (this should be a bug I think), you can try to change the default value in
> the cinder.conf like: osapi_volume_listen_port = 8777 if you are running
> the cinder and nova-api on the same machine.
>
> --
> Best regard,
> David Geng
>
> --
>
> [image: Inactive hide details for Ahmed Al-Mehdi ---11/13/2012 09:32:21
> AM---Ahmed Al-Mehdi ]Ahmed Al-Mehdi ---11/13/2012
> 09:32:21 AM---Ahmed Al-Mehdi 
>
>
>*Ahmed Al-Mehdi *
>Sent by: openstack-bounces+gengjh=cn.ibm@lists.launchpad.net
>
>11/13/2012 09:32 AM
>
>
> To
>
>
>Vishvananda Ishaya ,
>
>
> cc
>
>
>"openstack@lists.launchpad.net" 
>
>
> Subject
>
>
>Re: [Openstack] Cannot start "nova-api" service
>
>
> Hello,
>
> Can someone please help me with a nova-api issue.  After install all the
> nova services, all seem to be running fine, except for nova-api.  I even
> reboot my controller node, no luck.  After reboot all services are running,
> except nova-api.  When I manually start nova-api, nova-api crashes with the
> following error "*error: [Errno 98] Address already in use*".  I
> installed nova-volume earlier during the install process, but later on
> installed cinder, and made the necessary modifications (as far as I can
> tell) to nova-api.conf to use cinder for block storage.  Should I uninstall
> nova-volume?
>
> 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Starting
> keystone auth_token middleware
> 2012-11-12 14:46:24 INFO keystone.middleware.auth_token [-] Using
> /var/lib/nova/keystone-signing as cache directory for signing certificate
> 2012-11-12 14:46:24 CRITICAL nova [-] [Errno 98] Address already in use
> 2012-11-12 14:46:24 TRACE nova Traceback (most recent call last):
> 2012-11-12 14:46:24 TRACE nova   File "/usr/bin/nova-api", line 50, in
> 
> 2012-11-12 14:46:24 TRACE nova server = service.WSGIService(api)
> 2012-11-12 14:46:24 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/nova/service.py", line 584, in __init__
> 2012-11-12 14:46:24 TRACE nova port=self.port)
> 2012-11-12 14:46:24 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/nova/wsgi.py", line 72, in __init__
> 2012-11-12 14:46:24 TRACE nova self._socket = eventlet.listen((host,
> port), backlog=backlog)
> 2012-11-12 14:46:24 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in
> listen
> 2012-11-12 14:46:24 TRACE nova sock.bind(addr)
> 2012-11-12 14:46:24 TRACE nova   File "/usr/lib/python2.7/socket.py", line
> 224, in meth
> 2012-11-12 14:46:24 TRACE nova return getattr(self._sock,name)(*args)
> 2012-11-12 14:46:24 TRACE nova error: [Errno 98] Address already in use
> 2012-11-12 14:46:24 TRACE nova
> 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died
> unexpectedly, exiting
> 2012-11-12 14:46:24 INFO nova.service [-] Parent process has died
> unexpectedly, exiting
> 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server.
> 2012-11-12 14:46:24 INFO nova.wsgi [-] Stopping WSGI server.
>
> Would highly appreciate any pointers to understanding or resolving the
> issue.
>
> Regards,
> Ahmed.
>
>
> *From: *Ahmed Al-Mehdi <*ah...@coraid.com* >*
> Date: *Friday, November 9, 2012 12:45 AM*
> To: *Vishvananda Ishaya <*vishvana...@gmail.com* >*
> Cc: *"*openstack@lists.launchpad.net* " <*
> openstack@lists.launchpad.net* >*
> Subject: *Re: [Openstack] Cannot start "nova-api" service
>
>
>
>*From: *Vishvananda Ishaya <*vishvana...@gmail.com*
>>*
>Date: *Thursday, November 8, 2012 8:18 PM*
>To: *Ahmed Al-Mehdi <*ah...@coraid.com* >*
>Cc: *"*openstack@lists.launchpad.net* "
><*openstack@lists.launchpad.net* >*
>Subject: *Re: [Openstack] Cannot start "nova-api" service
>
>   On Nov 8, 2012, at 7:01 PM, Ahmed Al-Mehdi 
> <*ah...@coraid.com*>
>   wrote:
>   Vish,
>
>  I am running cinder-api.   The following two lines are present
>  in nova.conf.
>
>  volume_api_class=nova.volume.cinder.API
>  enabled_apis=ec2,osapi_compute,metadata
>
>  Do I need to re-sync the db, or add any additional lines to
>  nova.conf?
>
>   No that is it. Are you sure a) you don't have another nova-api or
>   nova-metadata or nova-api-os-compute process running? and b) that your
>   nova.conf is being read properly?
>
>   Vish
>
>As far as I can tell, no other nova-api, nova-metadata,
>nova-api-os-compute is running.   If there another way to confirm besides
>running "ps aux".  And how can I tell if nova.conf is being read properly?
>
>root@bodega:~# ps aux | grep nova
>nova   914  0.0  0.0  37952  1312 ?Ss   16:01   0:00 su -s
>/bin/sh -c exec nova-novncproxy --config-file=/etc/nova/nova.conf nova
>nova   916  0.0  0.2 1

Re: [Openstack] [Cinder] Cinder snapshots

2012-11-11 Thread John Griffith
On Sun, Nov 11, 2012 at 6:30 AM, Avishay Traeger  wrote:

> John Griffith  wrote on 08/11/2012 19:58:39:
> > Hi Avishay,
> >
> > So we have plans to improve some of this in the Grizzly release,
> > here's a few thoughts:
> > >> a. Why is a snapshot a fundamentally different entity than a volume?
> > I've asked this question a number of times myself :)  There are a
> > number of different ideas/definitions of what a snapshot is, versus
> > a clone, versus a backup, etc etc
> >
> > I've proposed that we leave snapshots as they are today and
> > introduce a clone option to just directly get a new volume to work
> > with and move on, as well as the ability to restore a volume to a
> > specific snapshot (the originating volume, not a new one).  I don't
> > know how popular this idea is though, there were a number of folks
> > at the Summit that seemed to think that was crazy talk.
> >
> > >> c. Is this what the snapshot-to-volume operation was meant to achieve?
> > Yep
>
> > >> d. If a back-end supports nested snapshots, each snapshot will need to
> > >> be converted to volume before a nested snapshot can be taken?
> > >> e. And in this case, will the back-end driver simply do nothing for
> the
> > >> snapshot-to-volume operation?
> > Not sure I follow here...
> >
> > >>2) Why can't you take snapshots of attached volumes?  I think most/all
> > >>back-ends will be fine with it (of course they will be crash-consistent
> if
> > >>the OS/application doesn't sync to disk).
> > Worth investigating for those back-ends that support it
> >
> > >>3) Most back-ends support various types of snapshots - e.g., read-only,
> > >>read-write, full copy, etc.  How can we better support this notion?
> > Not sure how I feel about trying to match up to every option every
> > vendor might have.  The reality also is that there are differences
> > in definitions from vendor A to vendor B on these sorts of things.
> >
> > The direction I was going with snapshots, clones would *kinda* give
> > at least part of what you're talking about here.
> >
> > I started a blueprint for this sort of thing here: https://
> > blueprints.launchpad.net/cinder/+spec/add-cloning-support-to-cinder,
> > feel free to add suggestions or give me feed-back if you like.  It's
> > by no means complete, but I should be working on it week after next.
> >
> > Thanks,
> > John
>
> Hi John,
> Thanks for your reply.  I guess I'm still confused about what a snapshot is
> in OpenStack.  Currently you can't really do anything with them via
> OpenStack.  I think every back-end supports reads, so at the very minimum,
> why not allow attaching a snapshot to a VM in read-only mode?  Further, I
> think all current back-ends support writable snapshots, so we could
> consider attaching read-write, or making that a capability.
>
> The way I'm thinking about it now is that volumes are stand-alone (i.e.,
> full copies with no CoW mappings or any other dependencies), while
> snapshots may depend on their respective source volumes.  I guess clones,
> then, would be a full copy of the original volume, and would basically be a
> shortcut for snapshot + create_volume_from_snapshot.  Do you agree?
>
> And finally, with regard to supporting various types of snapshots - maybe
> we can do something similar as with volume types?
>
> Thanks,
> Avishay
>
> Hey Avishay,

>>I guess I'm still confused about what a snapshot is
>>in OpenStack.  Currently you can't really do anything with them via
>>OpenStack.
Sure you can, you can use them to create a new volume.  They make a good
backup mechanism IMO.

I guess my question to you in your definition then is 'what's the
difference between a snapshot and a clone'?

Also, it Seems to me if we go with the idea of adding snapshot-restore, and
a true "clone" feature you get everything that you're asking for here and
more... so I'm not sure of the problem?  Maybe you could help me understand
why defining snapshot and clone in the manner described doesn't seem
appropriate?

FWIW, I think a R/O attach is something that would be good to have as an
option regardless.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Cinder] Cinder snapshots

2012-11-08 Thread John Griffith
On Thu, Nov 8, 2012 at 2:02 AM, Avishay Traeger  wrote:

>
> Hi all,
> I had a few questions about snapshot support in Cinder:
> 1) a. Why is a snapshot a fundamentally different entity than a volume?
>b. Is it because some back-ends don't support the same set of operations
> on snapshots?
>c. Is this what the snapshot-to-volume operation was meant to achieve?
>d. If a back-end supports nested snapshots, each snapshot will need to
> be converted to volume before a nested snapshot can be taken?
>e. And in this case, will the back-end driver simply do nothing for the
> snapshot-to-volume operation?
> 2) Why can't you take snapshots of attached volumes?  I think most/all
> back-ends will be fine with it (of course they will be crash-consistent if
> the OS/application doesn't sync to disk).
> 3) Most back-ends support various types of snapshots - e.g., read-only,
> read-write, full copy, etc.  How can we better support this notion?
>
> Thanks,
> Avishay
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Hi Avishay,

So we have plans to improve some of this in the Grizzly release, here's a
few thoughts:
>> a. Why is a snapshot a fundamentally different entity than a volume?
I've asked this question a number of times myself :)  There are a number of
different ideas/definitions of what a snapshot is, versus a clone, versus a
backup, etc etc

I've proposed that we leave snapshots as they are today and introduce a
clone option to just directly get a new volume to work with and move on, as
well as the ability to restore a volume to a specific snapshot (the
originating volume, not a new one).  I don't know how popular this idea is
though, there were a number of folks at the Summit that seemed to think
that was crazy talk.

>> c. Is this what the snapshot-to-volume operation was meant to achieve?
Yep

>> d. If a back-end supports nested snapshots, each snapshot will need to
>> be converted to volume before a nested snapshot can be taken?
>> e. And in this case, will the back-end driver simply do nothing for the
>> snapshot-to-volume operation?
Not sure I follow here...

>>2) Why can't you take snapshots of attached volumes?  I think most/all
>>back-ends will be fine with it (of course they will be crash-consistent if
>>the OS/application doesn't sync to disk).
Worth investigating for those back-ends that support it

>>3) Most back-ends support various types of snapshots - e.g., read-only,
>>read-write, full copy, etc.  How can we better support this notion?
Not sure how I feel about trying to match up to every option every vendor
might have.  The reality also is that there are differences in definitions
from vendor A to vendor B on these sorts of things.

The direction I was going with snapshots, clones would *kinda* give at
least part of what you're talking about here.

I started a blueprint for this sort of thing here:
https://blueprints.launchpad.net/cinder/+spec/add-cloning-support-to-cinder,
feel free to add suggestions or give me feed-back if you like.  It's by no
means complete, but I should be working on it week after next.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack][cinder] cinder create gives an error

2012-11-06 Thread John Griffith
On Tue, Nov 6, 2012 at 3:44 PM, Ahmed Al-Mehdi  wrote:

> John,
>
> I reboot my controller node, and things seem to be working a bit better.
> I followed the steps in "OpenStack Deploy and Install – Ubuntu", section
> Appendix B (
> http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-cinder.html
>  ).
>  All the three cinder-api/volume/scheduler services are running.
>
> root@bodega:/var/log/cinder# ps aux | grep cinder
> cinder1329  0.0  0.0  37952  1312 ?Ss   12:01   0:00 su -s
> /bin/sh -c exec cinder-scheduler --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-scheduler.log cinder
> cinder1331  0.0  0.4 182508 34424 ?S12:01   0:07
> /usr/bin/python /usr/bin/cinder-scheduler
> --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-scheduler.log
> cinder2289  0.0  0.0  37952  1308 ?Ss   12:08   0:00 su -s
> /bin/sh -c exec cinder-api --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-api.log cinder
> cinder2290  0.0  0.5 213864 46872 ?S12:08   0:01
> /usr/bin/python /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-api.log
> cinder2537  0.0  0.0  37952  1312 ?Ss   12:22   0:00 su -s
> /bin/sh -c exec cinder-volume --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-volume.log cinder
> cinder2538  0.0  0.4 184644 36812 ?S12:22   0:06
> /usr/bin/python /usr/bin/cinder-volume
> --config-file=/etc/cinder/cinder.conf
> --log-file=/var/log/cinder/cinder-volume.log
>
> VG "cinder-volumes" is present:
>
> root@bodega:/var/log/cinder# vgdisplay  cinder-volumes
>   --- Volume group ---
>   VG Name   cinder-volumes
>   System ID
>   Formatlvm2
>   Metadata Areas1
>   Metadata Sequence No  6
>   VG Access read/write
>   VG Status resizable
>   MAX LV0
>   Cur LV1
>   Open LV   0
>   Max PV0
>   Cur PV1
>   Act PV1
>   VG Size   2.00 GiB
>   PE Size   4.00 MiB
>   Total PE  511
>   Alloc PE / Size   256 / 1.00 GiB
>   Free  PE / Size   255 / 1020.00 MiB
>   VG UUID   VhxQZx-fB8K-36V9-L0sB-ImVO-oVFw-LNOLM0
>
>
> However, when I create a 1GB test volume (as per the instructions), I run
> into a failure.
>
> root@bodega:~/ahmed/cinder# date; cinder create --display_name test 1
> Tue Nov  6 12:57:39 PST 2012
> +-+--+
> |   Property  |Value |
> +-+--+
> | attachments |  []  |
> |  availability_zone  | nova |
> |  created_at |  2012-11-06T20:57:39.538245  |
> | display_description | None |
> | display_name| test |
> |  id | ab719d8d-42a4-44bc-b627-96b30e3f5002 |
> |   metadata  |  {}  |
> | size|  1   |
> | snapshot_id | None |
> |status   |   creating   |
> | volume_type | None |
> +-+--+
> root@bodega:~/ahmed/cinder#
> root@bodega:~/ahmed/cinder#
> root@bodega:~/ahmed/cinder#
> root@bodega:~/ahmed/cinder# date; cinder list
> Tue Nov  6 13:06:46 PST 2012
>
> +--++--+--+-+-+
> |  ID  | Status | Display Name | Size |
> Volume Type | Attached to |
>
> +--++--+--+-+-+
> | ab719d8d-42a4-44bc-b627-96b30e3f5002 | error  | test |  1   |
>   None| |
>
> +--++--+--+-----+-+
> root@bodega:~/ahmed/cinder#
>
> I am attaching text file containing the log entries from the three cinder
> log files.   Can you please help me understand why the volume creation is
> failing?  I really appreciate your help.
>
> Regards,
> Ahmed.
>
>
> From: John Griffith 
> Date: Tuesday, November 6, 2012 11:41 AM
>
> To: Ahmed Al-Mehdi 
> Cc: "openstack@lists.launchpad.net" 
> Subject: Re: [

Re: [Openstack] [openstack][cinder] cinder create gives an error

2012-11-06 Thread John Griffith
On Tue, Nov 6, 2012 at 11:28 AM, Ahmed Al-Mehdi  wrote:

> John,
>
> Thank you for your response.  When you stay start from scratch, do you
> mean re-install everything (all services) from scratch, as in a fresh
> install of Ubuntu?   And then not install nova-volume and don't create
> endpoint for nova-volume?
>
> Not to impose on you, but can you help me understand what does the
> following error mean:
> *ERROR: Malformed request url (HTTP 400) (Request-ID:
> req-8cff9608-598b-4618-bdc1-1068a1227781)*
> *
> *
> Is there an issue with how the REST command (Get/Put) is formed?
> Is the service not listening on the expected port, or the service is not
> even up and running?
>
> Regards,
> Ahmed.
>
>
> From: John Griffith 
> Date: Tuesday, November 6, 2012 11:19 AM
> To: Ahmed Al-Mehdi 
> Cc: "openstack@lists.launchpad.net" 
> Subject: Re: [Openstack] [openstack][cinder] cinder create gives an error
>
>
>
> On Tue, Nov 6, 2012 at 11:10 AM, Ahmed Al-Mehdi  wrote:
>
>> Hello,
>>
>> I just installed installed cinder, however, I am getting the following
>> error.
>>
>> root@bodega:~/ahmed/cinder# cinder create --display_name test 1
>> ERROR: Malformed request url (HTTP 400) (Request-ID:
>> req-a488154b-37f8-47e8-ae5f-8e7a73f6637b)
>> root@bodega:~/ahmed/cinder#
>>
>>
>> Can someone please help me understand what this error means.  I don't see
>> any logs being generated in any of the cinder log files - cinder–api.log,
>> cinder-scheduler.log, cinder-volume.log.
>>
>> Any pointers to debug this issue would be greatly appreciated.
>>
>> Regards,
>> Ahmed.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>> Ahmed,
>
> It looks like there's still a problem with your endpoint configuration?
>  If your conf files are in fact set up correctly as advised earlier there
> is also a potential that you didn't clean up the nova-volume settings you
> had in keystone and the CS.  Depending on your system, you might want to
> consider dropping the tables from your DB and starting from scratch and
> install cinder only.
>
> Thanks,
> John
>
> Ahmed,

No... sorry, I didn't mean re-install the OS, just reconfigure OpenStack
from scratch (drop the databases [NOT the mysql and other defaults]) and
step back through the config without the nova-volume piece in the mix.

The malformed request is telling you that there's something that the
receiving end does not like about the call you've made.  The reason I
suspect the endpoint or catalog service issue is that I've made the same
mistake and seen the same error myself :)

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack][cinder] cinder create gives an error

2012-11-06 Thread John Griffith
On Tue, Nov 6, 2012 at 11:10 AM, Ahmed Al-Mehdi  wrote:

> Hello,
>
> I just installed installed cinder, however, I am getting the following
> error.
>
> root@bodega:~/ahmed/cinder# cinder create --display_name test 1
> ERROR: Malformed request url (HTTP 400) (Request-ID:
> req-a488154b-37f8-47e8-ae5f-8e7a73f6637b)
> root@bodega:~/ahmed/cinder#
>
>
> Can someone please help me understand what this error means.  I don't see
> any logs being generated in any of the cinder log files - cinder–api.log,
> cinder-scheduler.log, cinder-volume.log.
>
> Any pointers to debug this issue would be greatly appreciated.
>
> Regards,
> Ahmed.
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Ahmed,

It looks like there's still a problem with your endpoint configuration?  If
your conf files are in fact set up correctly as advised earlier there is
also a potential that you didn't clean up the nova-volume settings you had
in keystone and the CS.  Depending on your system, you might want to
consider dropping the tables from your DB and starting from scratch and
install cinder only.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] "nova boot" errors while attaching a volume to an instance

2012-10-31 Thread John Griffith
On Wed, Oct 31, 2012 at 1:29 PM, Bontala, Vibhuvardhan <
vibhuvardhan.bont...@emc.com> wrote:

> Hi,
>
> ** **
>
> I am running GA bits of Folsom. I am running a two node setup where the
> first node is the controller+compute node that has Cinder running as well.
> The second node is merely a compute node. I am seeing an issue while
> booting an instance from Cinder volume on both the nodes. The “nova boot”
> operation fails while spawning the instance with the following error.
>
> ** **
>
> [00mProcessExecutionError: Unexpected error while running command.
>
> [00mCommand: sudo nova-rootwrap /etc/nova/rootwrap.conf iscsiadm -m node
> -T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p
> 192.168.150.96:3260 --rescan
>
> [00mExit code: 255
>
> [00mStdout: ''
>
> [00mStderr: 'iscsiadm: No portal found.\n'
>
> [00m
>
> ** **
>
> I had successfully created a Cinder volume with a valid image on it.
>
> ** **
>
>
> +--+---+--+--+-+-+
> 
>
> |  ID  |   Status  | Display Name | Size |
> Volume Type | Attached to |
>
>
> +--+---+--+--+-+-+
> 
>
> | 3ac4b027-905e-4318-a74e-2bdf94f5d887 | available |   Volume1|  2
> | None| |
>
>
> +--+---+--+--+-+-+
> 
>
> ** **
>
> I even tried to discover the iSCSI targets. But it returns with “no
> records found”.
>
> ** **
>
> I then looked into to MySQL database for Cinder and looked at the entries,
> specifically “provider_location” and it looked just fine. 192.168.150.96
> is the node where I have controller and cinder running.
>
> ** **
>
>
> +---+
> 
>
> |
> provider_location
> |
>
>
> +---+
> 
>
> |
> NULL
> |
>
> | 192.168.150.96:3260,1
> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 1 |*
> ***
>
> ** **
>
> I manually tried to discover the iSCSI targets and it couldn’t find any.**
> **
>
> ** **
>
> stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m discovery -t
> sendtargets -p 192.168.150.96:3260 192.168.150.96:3260,1
> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887
>
> iscsiadm: Connection to Discovery Address 192.168.150.96 closed
>
> iscsiadm: Login I/O error, failed to receive a PDU
>
> iscsiadm: retrying discovery login to 192.168.150.96
>
> stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T
> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p
> 192.168.150.96:3260iscsiadm: no records found!
>
> stack@esg-dell-c4-s08:/etc/cinder$ sudo iscsiadm -m node -T
> iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -p
> 192.168.150.96:3260 --rescan
>
> iscsiadm: No portal found.
>
> stack@esg-dell-c4-s08:/etc/cinder$
>
> ** **
>
> I am not sure what’s wrong with my setup. Any help is greatly appreciated.
> 
>
> ** **
>
> Thanks
>
> Vibhu
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Vibnu,

Strange, you're unable to see the target on either of the nodes?  I'm
assuming your using the default LVM storage back-end.

Something to look at:

"sudo tgtadm --lld iscsi --op show --mode target" - Make sure your target
is present (on the cinder node)


You shouldn't *need* to do this, but to trouble-shoot you could also try:

"sudo iscsiadm -m discovery -p 192.168.150.96:3260 -t st"

followed by trying to login.

"sudo iscsiadm -m node
-T iqn.2010-10.org.openstack:volume-3ac4b027-905e-4318-a74e-2bdf94f5d887 -l"

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Nova compute fails to start

2012-10-30 Thread John Griffith
On Tue, Oct 30, 2012 at 6:02 AM, Johannes Baltimore  wrote:

> Hello.
>
> Whenever I try to start the compute module, it seems not to start at all.
> I'm pasting the log entry for when I try to do it:
>
> http://paste.ubuntu.com/1317755
>
> If someone wants to help and needs to know anything else, just let me
> know. Thanks in advance
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Johannes,

Looks like something amiss in nova.conf, do you have the following in your
nova.conf file:

`compute_driver=libvirt.LibvirtDriver`


John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Possible upgrade bug in nova-volume (& cinder)?

2012-10-25 Thread John Griffith
On Thu, Oct 25, 2012 at 5:03 PM, Jonathan Proulx  wrote:

> On Wed, Oct 24, 2012 at 6:32 PM, John Griffith
>  wrote:
>
> > Hey Jon,
> >
> > Cool... Yeah, I had intended for that patch to be a stable/folsom patch
> but
> > shouldn't have submitted it to master :(  The real problem isn't just
> > normalizing the lvm names, but also the provider_location information
> that
> > is stored in the DB for when you try to attach to your compute node.
>
> Yup, I had understood that.  We only have about 10 active volumes so
> it was easy enough in my case to copy and paste the ids/uuids around
> for mysql updates and lvrenames.  So I can now attach both old and new
> volumes at my site.
>
> > The cinder version is the same (https://review.openstack.org/#/c/14790/)
> and
> > depending on the feedback it's a candidate for back-port.
> >
> > The other possible issues that I've seen people run in to:
> > 1. volumes directory not being specified correctly
> > 2. not restarting tgtadm
> > 3. not having the include statement in /etc/tgt/conf.d
> >
> > I think you and I covered most of these in our chat on IRC earlier
> today...
>
> I tripped over a couple more steps that I didn't know about but
> managed to discover on my own as well, like 'cinder-manage db sync' to
> set up the tables in the cinder database, which I'm sure are so
> obvious as to be nearly invisible to people working on the code and
> enough like any other openstack service it wasn't too hard to guess.
> I collected up my notes and expanded migration section of the release
> notes by a few steps
>
> http://wiki.openstack.org/ReleaseNotes/Folsom#OpenStack_Block_Storage_.28Cinder.29
>
> Thanks again,
> -Jon
>
Thanks for putting this together Jon!  I'll see about fixing what we have
against the extra info you've provided.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Possible upgrade bug in nova-volume (& cinder)?

2012-10-24 Thread John Griffith
On Wed, Oct 24, 2012 at 3:20 PM, Jonathan Proulx  wrote:

> On Wed, Oct 24, 2012 at 3:01 PM, John Griffith
>  wrote:
>
> > Hey Jon,
> >
> > Couple of things going on, one is the volume naming (in progress here:
> > https://review.openstack.org/#/c/14615/).  I'll take a closer look at
> some
> > of the other issues you pointed out.
>
> Hi John,
>
> On this issue I think the issue you link to above covers my problem
> (even if that exact implementation now seems abandoned).  So "the
> right thing" is to normalize all the naming on UUID in my case using
> lvrename (or symlinks as the patchset above does) and updating the
> cinder db provider_location.  What other issues did you see to look
> into?  Seems this covers everything I brought up here and the issues
> you helped me with on IRC earlier (thanks) seem like documentation
> issues (which I hope to get into the docs once I clean up my notes)
>
> -Jon
>
Hey Jon,

Cool... Yeah, I had intended for that patch to be a stable/folsom patch but
shouldn't have submitted it to master :(  The real problem isn't just
normalizing the lvm names, but also the provider_location information that
is stored in the DB for when you try to attach to your compute node.

The cinder version is the same (https://review.openstack.org/#/c/14790/)
and depending on the feedback it's a candidate for back-port.

The other possible issues that I've seen people run in to:
1. volumes directory not being specified correctly
2. not restarting tgtadm
3. not having the include statement in /etc/tgt/conf.d

I think you and I covered most of these in our chat on IRC earlier today...

One other thing that Vish pointed out is I made an assumption about
attached volumes that may result in you having to detach/reattach after the
upgrade.  I'm looking into that one now.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Possible upgrade bug in nova-volume (& cinder)?

2012-10-24 Thread John Griffith
On Wed, Oct 24, 2012 at 12:57 PM, Jonathan Proulx  wrote:

> On Wed, Oct 24, 2012 at 2:45 PM, Jonathan Proulx 
> wrote:
>
> > To fix this for me I can look up the volumes by ID in the database and
> > then lvrename the logical volumes (I don't have too many and all on
> > one volume server right now).
>
> That maybe the wrong answer as the database (both cinder and the older
> nova leavings) has a provider_location that implies the "right"
> logical volume name:
>
>
> +--++---+
> | id   | ec2_id | provider_location
>
>   |
>
> +--++---+
> | 25cb6abc-1938-41da-b4a4-7639fa122117 | NULL   | 128.52.x.x:3260,9
> iqn.2010-10.org.openstack:volume-001c 1
>   |
> | 60cd2c0e-6d61-4010-aee2-df738adb3581 | NULL   | 128.52.x.x:3260,4
> iqn.2010-10.org.openstack:volume-001a 1
>   |
> | 67ba5863-9f92-4694-b639-6c9520e0c6f3 | NULL   | 128.52.x.x:3260,2
> iqn.2010-10.org.openstack:volume-0016 1
>   |
> | 7397daa1-f4a7-47d4-b0dc-0b306defdf62 | NULL   | 128.52.x.x:3260,14
> iqn.2010-10.org.openstack:volume-0014 1
>  |
> | 7d8c51bc-9cac-4edf-b1e6-1c37d5a8256f | NULL   | 128.52.x.x:3260,10
> iqn.2010-10.org.openstack:volume-7d8c51bc-9cac-4edf-b1e6-1c37d5a8256f
> 1 |
> | 86426e77-e396-489d-9e66-49f0beef46bb | NULL   | 128.52.x.x:3260,16
> iqn.2010-10.org.openstack:volume-0019 1
>  |
> | 98ac28f5-77d8-476b-b3e1-c90a0fd3e880 | NULL   | 128.52.x.x:3260,1
> iqn.2010-10.org.openstack:volume-0010 1
>   |
> | a6e68eae-23a9-483e-bd42-e4b8a7f47dc4 | NULL   | 128.52.x.x:3260,24
> iqn.2010-10.org.openstack:volume-a6e68eae-23a9-483e-bd42-e4b8a7f47dc4
> 1 |
> | a89b9891-571c-43be-bc1b-0c346a161d38 | NULL   | 128.52.x.x:3260,9
> iqn.2010-10.org.openstack:volume-a89b9891-571c-43be-bc1b-0c346a161d38
> 1  |
> | cbd32221-7794-41d1-abf2-623c49f4ff03 | NULL   | 128.52.x.x:3260,6
> iqn.2010-10.org.openstack:volume-001b 1
>   |
>
> +--++---+
>
> so I'm also open to suggestions on the "right" resolution to this.
> Should I rename the logical volume sand update the provider_location
> or should I make the  /var/lib/cinder/volumes/* files match what is in
> the database and LVM (and if I do the latter will something come along
> and undo that)?
>
> -Jon
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
Hey Jon,

Couple of things going on, one is the volume naming (in progress here:
https://review.openstack.org/#/c/14615/).  I'll take a closer look at some
of the other issues you pointed out.

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] using cinder to create volumes error

2012-10-21 Thread John Griffith
On Sun, Oct 21, 2012 at 9:24 PM, livemoon  wrote:

> When I create volumes by cinder, error occurs in cinder-volume.log
>
> 2012-10-22 10:58:25 DEBUG cinder.volume.manager
> [req-f51ade4d-5bed-4f24-b492-528b9baca625 cd7e95086cfc4693945f37e59c1b7206
> 67456c69ae074be4b4ba0af7048b5ceb] volume
> volume-e224dfdb-913c-4135-811d-eb075a551de8: creating export create_volume
> /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:155
> 2012-10-22 10:58:25 28674 ERROR cinder.openstack.common.rpc.amqp [-]
> Exception during message handling
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp Traceback
> (most recent call last):
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py",
> line 276, in _process_data
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp rval
> = self.proxy.dispatch(ctxt, version, method, **args)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py",
> line 145, in dispatch
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> return getattr(proxyobj, method)(ctxt, **kwargs)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 163, in
> create_volume
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> volume_ref['id'], {'status': 'error'})
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> self.gen.next()
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 156, in
> create_volume
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> model_update = self.driver.create_export(context, volume_ref)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/volume/driver.py", line 380, in
> create_export
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> volume_path)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 112, in
> create_iscsi_target
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> utils.ensure_tree(FLAGS.volumes_dir)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/utils.py", line 1049, in
> ensure_tree
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> os.makedirs(path)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/os.py", line 157, in makedirs
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
> mkdir(name, mode)
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp OSError:
> [Errno 13] Permission denied: '/usr/lib/python2.7/dist-packages/volumes'
> 2012-10-22 10:58:25 28674 TRACE cinder.openstack.common.rpc.amqp
>
> Then I manually create directory "volumes" in
> /usr/lib/python2.7/dist-packages" and give 777 to it
> but error again:
>
> 2012-10-22 11:21:43 ERROR cinder.volume.iscsi
> [req-d965ffd6-aff8-4c2d-b3c0-c6aaca4cebf0 cd7e95086cfc4693945f37e59c1b7206
> 67456c69ae074be4b4ba0af7048b5ceb] Failed to create iscsi target for volume
> id:volume-a430f00e-53fa-44e9-9470-f604d63b88b8. Please ensure your tgtd
> config file contains 'include /usr/lib/python2.7/dist-packages/volumes/*'
> 2012-10-22 11:21:43 28674 ERROR cinder.openstack.common.rpc.amqp [-]
> Exception during message handling
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp Traceback
> (most recent call last):
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py",
> line 276, in _process_data
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp rval
> = self.proxy.dispatch(ctxt, version, method, **args)
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py",
> line 145, in dispatch
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp
> return getattr(proxyobj, method)(ctxt, **kwargs)
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 163, in
> create_volume
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp
> volume_ref['id'], {'status': 'error'})
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
> 2012-10-22 11:21:43 28674 TRACE cinder.openstack.common.rpc.amq

Re: [Openstack] Cinder Improvement for Grizzly

2012-10-09 Thread John Griffith
On Tue, Oct 9, 2012 at 8:35 PM, Akira Yoshiyama wrote:

> Hi all,
>
> I want to join the next design summit but I can't because of the current
> job.
> So I wrote my ideas for cinder improvement to etherpad.
> I hope someone will take up them (or a part of them) at the summit.
>
> http://etherpad.openstack.org/CinderImprovementsForGrizzly
>
> Table of contents:
>
> * New features
> * Shared volumes for instances
>
> * APIs
> * Validation for all parameters
> * Validation for state transitions
> * Keeping previous state for rollback
>
> * Drivers
> * VolumeDriver as the real base class
> * Unification of create_volume()+create_export() and
> remove_export()+delete_volume()
> * Zeroing volumes not at deleting but at creating
> * Common FileDriver
> * Post function of nova-side drivers for terminate_connection()
> * One driver per module file
> * Checking whether commands work in check_for_setup_error()
>
>
> Any comments will be gratefully appreciated.
>
> Thank you,
> Akira Yoshiyama 
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
Hi Akira,

Thanks for putting this list together.  A number of things on your list
have been mentioned at different weekly meetings etc so you definitely
targeted some good ideas.

I'm sure that we'll cover a number of these during various sessions at the
summit.  We'll sync up via session etherpads, but don't hesitate to add
some items to the weekly cinder meeting agenda [1], and be sure to drop in
and present some of these ideas.

There's always the blue-print process as well.

Thanks,
John

[1] http://wiki.openstack.org/NovaVolumeMeetings
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Horizon Bug 1004412 Details

2012-10-06 Thread John Griffith
On Sat, Oct 6, 2012 at 7:09 PM, Gabriel Hurley wrote:

>  All of what you said is correct. Those filtering issues (which applied
> to volumes, keypairs, and security groups at least) were tracked in
> separate tickets in Nova and all got fixed towards the tail end of Folsom.
> I don’t have the commits handy, sorry. The proper fix was filtering the
> results returned from Nova correctly on that end; the fix on the ticket you
> listed was only a defense against the problem on Horizon’s end.
>
> ** **
>
> **-  **Gabriel
>
> ** **
>
> *From:* 
> openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
> openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
> Behalf Of *Joe Topjian
> *Sent:* Saturday, October 06, 2012 11:19 AM
> *To:* openstack
> *Subject:* [Openstack] Horizon Bug 1004412 Details
>
> ** **
>
> Hello,
>
> ** **
>
> I've been aware of Bug 1004412 (
> https://bugs.launchpad.net/horizon/+bug/1004412) in my Essex deployments
> for a while and finally had some time to look into it in detail.
>
> ** **
>
> I believe I have found the cause and wanted to discuss what I found vs how
> it was fixed in the patch.
>
> ** **
>
> From what I can see, when an admin requests a list of volumes, all volumes
> in the cloud are returned. But when an admin requests a list of instances,
> only instances owned by the admin are returned -- unless an option to
> return all instances is specified.
>
> ** **
>
> Because of these two distinct actions, the chances of a KeyError happening
> when visiting /nova/instances_and_volumes is extremely high once other
> projects begin working in the OpenStack environment: all volumes from all
> projects are returned but only admin instances are returned, so any volume
> attached in another project cannot find its corresponding instance.
>
> ** **
>
> I see two proper solutions to this issue: either only return volumes owned
> by the admin or return all instances in all projects by default. I was
> unable to figure out (without doing too many changes) how to filter
> volumes, so I decided on the latter solution. In views.py, I modified the
> call to get a list of instances to be:
>
> ** **
>
> if self.request.user.is_admin():
>
> self._instances_list = api.server_list(self.request,
> all_tenants=True)
>
> else:
>
> self._instances_list = api.server_list(self.request)
>
> ** **
>
> Without looking at the implementation details, but instead what the
> implementation is trying to achieve, I do not see this same issue being
> resolved in the patch (
> https://github.com/openstack/horizon/commit/155bfb72c1b5f866236928f4ffd0c2567dc556f3
> ). 
>
> ** **
>
> My question is if I have incorrectly assessed the issue or if the patch is
> taking other things into account that I'm not aware of? 
>
> ** **
>
> Thanks,
>
> Joe
>
>
> 
>
> ** **
>
> --
> Joe Topjian
>
> Systems Administrator
>
> Cybera Inc.
>
> ** **
>
> www.cybera.ca
>
> ** **
>
> Cybera is a not-for-profit organization that works to spur and support
> innovation, for the economic benefit of Alberta, through the use
> of cyberinfrastructure.
>
> ** **
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Joe and Gabriel,

The changes were in fact merged to Folsom as Gabriel mentioned.  The
specific patches were:
Cinder-Volume: 
Ie9d74e9c09fa0c192ab6257b5fb02d65b593cbfb
Cinder-Snapshot:
I2a8338d77badc70201bb315198183f2091df43fb

Further details can be viewed (including the Nova-Volume version of the
patches) in the bug: https://bugs.launchpad.net/horizon/+bug/967882

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] mailing list for nova-volume / Cinder

2012-09-26 Thread John Griffith
On Wed, Sep 26, 2012 at 8:18 PM, Ahmed Al-Mehdi  wrote:

> Hello,
>
> Is there a specific mailing list for nova-volume / Cinder?
>
> Thank you,
> Ahmed.
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hello Ahmed,

Nope, no individual mail list.  Depending on your context you can use
openstack-...@lists.openstack.org and just add [openstack-dev][Cinder] in
the subject.

Take a look here at[1] for the different lists available depending on your
context.

Thanks,
John

[1] http://wiki.openstack.org/MailingLists
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] TC candidacy

2012-09-14 Thread John Griffith
On Fri, Sep 14, 2012 at 12:59 PM, Thierry Carrez wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Anne Gentle wrote:
> > I'd like to propose myself as a Technical Committee candidate for
> > one of the open seats in the current election.
>
> As an election official, I confirm that you're eligible to this position.
>
> - --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJQU36pAAoJEFB6+JAlsQQj/KIQAKYY5Jsa2hUdQrid8p/sDkL/
> K0Np7yCKjlyOnJAdBxBs6SrfUyJvZYCxAAOt1s1oeEC8lBbx7ubZaUkZjVy5ZvOj
> sEgizIsO8wVOQ4pzHE/2t3BUZWOgSY05zOl0hlrSpGK1OupYvIR9brw+81SsCe92
> op2HfoAXKibDXtnXUi6dtwClZ+jxKSNeqSw8iMfvnBsesRLrrOELZO5753cN9dxA
> 31pb8u0DG/wYbXmx9e59yfNomNwbamNsF/JjgGwZgwWuiu5C86xJBRCzOmQTKL3l
> uT9OUbTMI5N1KQK/xjrkBIrVr5YRcmgMUOXAfHRv5fKn4w4ZT7XVrBFwP+B/jAlJ
> L1hwlxjePEa46hAuvS9wEK48PTvC4zwhOsQW05IIEVvYZ3Kr3oMqG0bWt7Rr+nLX
> Y2vn6Z0MXV7AVKp7bbjzKLfDhGm6ygLki9HO8Fryl6lRIEktn1wC4fX0EqjX8Ruo
> rGa5lhHR+VABx/GikOU/00yeEdr3KI1dmtRiHBna6SEQOOCys1Iu6mX1hDXb0G/N
> pC2vCEs/md1yYr2ToL4hqfbKv5E0TqO/2JzfYEK4MI+Lba3tOK+zqR7wl0m2KEAL
> KRxAvRV/wI7mA9EXLVAbOvZUyXCfRnvkKq9eiAennYdjis0z/V6Qw09WWJK/MCxl
> mvS8eMpXiCMSGAmRMzdO
> =ON9e
> -END PGP SIGNATURE-
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
+1
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Fwd: Cinder PTL candidacy

2012-09-12 Thread John Griffith
Hi Rob,

Thanks, initial thoughts regarding your questions are inline below.

John

On Wed, Sep 12, 2012 at 10:43 AM, Esker, Robert wrote:

>  Hi John,
>
>  Good to see you running and thanks for your efforts thus far...  I do
> have a few questions about your thoughts on Cinder's future:
>
>  • We (NetApp) have heard from folks looking to potentially use Cinder
> independently of Nova, et cetera (as a generalized storage backend
> abstraction layer).  Where do you stand on retaining the option to do so?
>
> I would strongly agree with this mindset.  This was in fact part of a
number of discussions at the Folsom summit last spring.  Ideally I would
like to see Cinder mature to a point where it could be used exactly in this
sort of manner.  Plugged in to different architectures and used as it's own
entity with or without Nova, but obviously working with Nova is the main
charter and first priority.

 • We've also been asked by several in the operator (or soon to be)
> community to look at expanding the role of Cinder beyond block storage
> only.  This was touched upon a bit at the last summit.  Given the
> significant effort associated with breaking out Cinder it wasn't a focus at
> the time though.  We're planning talks on this at the Grizzly design summit
> next month, but more significantly have prototyped Cinder support for
> accommodating shared filesystems.  We've specifically avoided submitting
> most of it while Folsom is in play, but will do so as soon as Grizzly revs
> up.  Could you please comment on your philosophy for the future of Cinder
> as it applies to extending the API for such?
>

I don't think my opinion regarding this has ever been much of a secret
(regardless of how unpopular it may be) :)  During the initial proposals to
start the Cinder project I shared my opinion that the idea was to provide
an independent block storage service that would be consumed by Nova and
possibly others.  I've never been a big fan of the idea of shoe horning in
all sorts of extras (network shares, file systems etc.).  My experience has
been that if you don't have a very clear and focused definition regarding
what your purpose is you tend to not be very good at anything.  I'd like to
keep Cinder focused on being a Block Storage service, not an NFS service or
other shared file system service etc.

That being said, I also understand the needs/desires from folks in the
community.  As you know NetApp submitted changes to Cinder to enable NFS
support and they were accepted and merged.  I would never object to
something that the majority of team members and especially end users ask
for. I would just like to avoid trying to be everything to everyone and in
turn not being very good at any of it.  In my opinion if changes are
somewhat isolated and the only real impact is things like new drivers (such
as the NFS addition) without impacting the API etc then I'm all for it.

I also think that this is a philosophy that can evolve over time as the
project matures.  Right now I see a significant need for improvements to
block storage and that's where I would like to focus efforts.  Down the
road when Cinder is the *best* block storage service that it can be, that
opens up the door to a change in philosophies and focus.


>
Thanks!
>
>  Rob Esker
> NetApp, Inc.
>
>
>  On Aug 31, 2012, at 3:27 PM, John Griffith 
>  wrote:
>
>  Hello,
>
> For the many folks that don't know me, my name is John Griffith and I'd
> like to announce my candidacy for Cinder PTL.
>
> Qualifications:
>
> I've been an active contributor to Nova since November of 2011, starting
> out as many by adding a driver, but then began helping out anywhere and
> everywhere I could. IRC questions/conversations, assigning bugs to myself
> etc.  In addition I've been involved in multiple conversations with
> customers interested in OpenStack and have been acting as an OpenStack
> evangelist to a number of both small and large companies looking to deploy
> OpenStack in public and private clouds.
>
>
> Contribution over the last six months:
>
> During the last summit I lead conversations around the idea of Cinder and
> organized the effort to kick off the project. Since then I've been acting
> as interim PTL for the Cinder project and have successfully driven the
> effort to promote Cinder to core status as an OpenStack project. I'm
> continually learning, and absolutely love doing the work!
>
> While it's been a learning experience I have been fulfilling the
> responsibilities or PTL, and dedicated every day to the success of the
> project. I'm passionate about the success of Cinder and believe it has vast
> potential and is critically important to OpenStack as a whole.
>
>
> Most c

Re: [Openstack] Which volume API in Nova ?

2012-09-11 Thread John Griffith
On Tue, Sep 11, 2012 at 10:07 AM, Day, Phil  wrote:

>  Thanks Vish,
>
> ** **
>
> So are both maintained at present – for example if there was a bug fix to
> volume creation would it be applied to the VolumeController in both places ?
> 
>
> ** **
>
> I’m just trying to work out how best to provide compatibility as we roll
> forwards – seems like for some period we may need to have both the compute
> extension and the Volume API server running.
>
> ** **
>
> Phil
>
> ** **
>
> *From:* Vishvananda Ishaya [mailto:vishvana...@gmail.com]
> *Sent:* 10 September 2012 18:08
> *To:* Day, Phil
> *Cc:* openstack@lists.launchpad.net (openstack@lists.launchpad.net) (
> openstack@lists.launchpad.net)
> *Subject:* Re: [Openstack] Which volume API in Nova ?
>
> ** **
>
> Prior to creating our own endpoint for volumes inside of nova (one of the
> first steps in the transition that happened right before the essex
> release), volume control was done by compute extensions. We left these
> extensions in case anyone was using them. They should be roughly
> functionally equivalent, but the compute extension is located at:
>
> http://host:8774/os-volumes (host and port of the compute endpoint)
>
> and the volume api is at:
>
> http://host:8776/volumes (host and port of the volume endpoint)
>
> ** **
>
> Vish
>
> ** **
>
> On Sep 10, 2012, at 8:34 AM, "Day, Phil"  wrote:
>
>
>
> 
>
> Hi Folks,
>
>  
>
> I know things are in transition right now from Nova to Cinder, but can
> someone shed light on the difference between
> “api.openstack.compute.contrib.volumes” and “api.openstack.volume” ?**
> **
>
>  
>
> Thanks
>
> Phil
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> ** **
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hey Phil,

You would probably want to move off of the extensions if you're in a
position to make that sort of change.  Also keep in mind the switch to the
Cinder volume service after Folsom.  It may be worth looking at this now
rather than waiting.

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] reservation of CPU cores?

2012-09-03 Thread John Griffith
On Mon, Sep 3, 2012 at 7:57 AM, Alex Glikson  wrote:

> Dear all,
>
> I wonder whether there is an easy way to configure how many cores
> nova-compute is supposed to use (or alternatively refrain from using) for
> provisioning of instances on a certain host, out of the total number of
> cores on that host? E.g., if I know that there are other things running on
> the host, and I want to dedicate some of the CPU capacity to them (such as
> OpenStack services themselves). I am thinking of KVM right now, but the
> general approach is probably platform-independent. Would appreciate your
> insights.
>
> Thanks,
> Alex
>
> P.S. trivial solution is to dedicate entire host(s) to those other
> "things", and assume that nova-compute is running on hosts used *only* to
> run VMs (and that nova-compute itself does not need much CPU cycles). but I
> am looking for a more fine-grained approach.
>
>
> 
> Alex Glikson
> Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
> http://w3.haifa.ibm.com/dept/stt/cloud_sys.html |
> https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml
> Email: glik...@il.ibm.com | Phone: +972-4-8281085 | Mobile:
> +972-54-647 | Fax: +972-4-8296112
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> Hi Alex,

You might have a look at the max_cores setting in your nova.conf file.  I
think this will do what you have in mind.  You can find some documentation
on it here:
http://docs.openstack.org/essex/openstack-compute/admin/content/compute-options-reference.html

John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Fwd: Cinder PTL candidacy

2012-08-31 Thread John Griffith
Hello,

For the many folks that don't know me, my name is John Griffith and I'd
like to announce my candidacy for Cinder PTL.

Qualifications:

I've been an active contributor to Nova since November of 2011, starting
out as many by adding a driver, but then began helping out anywhere and
everywhere I could. IRC questions/conversations, assigning bugs to myself
etc.  In addition I've been involved in multiple conversations with
customers interested in OpenStack and have been acting as an OpenStack
evangelist to a number of both small and large companies looking to deploy
OpenStack in public and private clouds.


Contribution over the last six months:

During the last summit I lead conversations around the idea of Cinder and
organized the effort to kick off the project. Since then I've been acting
as interim PTL for the Cinder project and have successfully driven the
effort to promote Cinder to core status as an OpenStack project. I'm
continually learning, and absolutely love doing the work!

While it's been a learning experience I have been fulfilling the
responsibilities or PTL, and dedicated every day to the success of the
project. I'm passionate about the success of Cinder and believe it has vast
potential and is critically important to OpenStack as a whole.


Most critical aspects for Cinder in the next 6 months:

The next six months are going to be defining for Cinder. The most important
thing is going to be showing a smooth transition from Nova-Volume to Cinder
is possible. There's a lot of concern regarding this subject and it's
something that I keep in mind with any change/fix or addition to the code.
Aside from the initial release, the critical aspects for Grizzly are going
to be gain momentum in terms of visibility and participation, focus on
quality and provide new features. Quality is my number one priority, and I
think there is a lot of potential to harden the core code in the project
and greatly improve the user experience as well as capabilities.


Philosophical ideas regarding being a PTL:

There are of course all of the items listed in the being a PTL guide. In
addition however I think it is very important for a PTL to be accessible in
a multitude of ways. This includes questions, helping people that want to
get involved with OpenStack and most of all listening to ideas/input. One
of the things that makes Open Source work is the vast pool of ideas and
suggestions from various views and backgrounds, keeping an open mind and
constantly challenging existing paradigms leads to a better project.
I believe it's crucial to build a strong core team, listen to input from
users, storage vendors and other developers and make something that is
truly better than anything else that's out there. I don't believe we should
strive to offer the *same* functionality as other cloud platforms, but
offer something that is MUCH better!



If you have any questions or there are any further details I can provide
don't hesitate to ask.

Thanks,
John

email:john.griff...@solidfire.com
irc:jgriffith
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack-dev] [nova] Disk attachment consistency

2012-08-13 Thread John Griffith
On Mon, Aug 13, 2012 at 10:16 PM, Nathanael Burton
 wrote:
> On Aug 13, 2012 11:37 PM, "Vishvananda Ishaya" 
> wrote:
>> The second proposal I have is to use a feature of kvm attach and set the
>> device serial number. We can set it to the same value as the device
>> parameter. This means that a device attached to /dev/vdb may not always be
>> at /dev/vdb (with old kvm guests), but it will at least show up at
>> /dev/disk/by-id/virtio-vdb consistently.
>
> What about setting the serial number to the volume_id? At least that way you
> could be sure it was the volume you meant, especially in the case where vdb
> in the guest ends up not being what you requested. What about other
> hypervisors?
>
>> (review coming soon)
>>
>> First question: should we return this magic path somewhere via the api? It
>> would be pretty easy to have horizon generate it but it might be nice to
>> have it show up. If we do return it, do we mangle the device to always show
>> the consistent one, or do we return it as another parameter? guest_device
>> perhaps?
>>
>> Second question: what should happen if someone specifies /dev/xvda against
>> a kvm cloud or /dev/vda against a xen cloud?
>> I see two options:
>> a) automatically convert it to the right value and return it
>> b) fail with an error message
>>
>> Third question: what do we do if someone specifies a device value to a kvm
>> cloud that we know will not work. For example the vm has /dev/vda and
>> /dev/vdb and they request an attach at /dev/vdf. In this case we know that
>> it will likely show up at /dev/vdc. I see a few options here and none of
>> them are amazing:
>>
>> a) let the attach go through as is.
>>   advantages: it will allow scripts to work without having to manually
>> find the next device.
>>   disadvantages: the device name will never be correct in the guest
>> b) automatically modify the request to attach at /dev/vdc and return it
>>   advantages: the device name will be correct some of the time (kvm guests
>> with newer kernels)
>>   disadvantages: sometimes the name is wrong anyway. The user may not
>> expect the device number to change
>> c) fail and say, the next disk must be attached at /dev/vdc:
>>   advantages: explicit
>>   disadvantages: painful, incompatible, and the place we say to attach may
>> be incorrect anyway (kvm guests with old kernels)
>>
>> The second proposal earlier will at least give us a consistent name to
>> find the volume in all these cases, although b) means we have to check the
>> return value to find out what that consistent location is like we do when we
>> don't pass in a device.
>>
>> I hope everything is clear, but if more explanation is needed please let
>> me know. If anyone has alternative/better proposals please tell me. The last
>> question I think is the most important.
>>
>> Vish
>>
>>
>> ___
>> OpenStack-dev mailing list
>> openstack-...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> ___
> OpenStack-dev mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

I've wondered about using the mount by device-uuid as long term
solutions, ie just mount using libvirt mount by /dev/disk/by-uuid
(don't even take a device parameter).  Although I guess there are some
issues here.

As far as my input to your questions:
> What about setting the serial number to the volume_id? At least that way you
> could be sure it was the volume you meant, especially in the case where vdb
> in the guest ends up not being what you requested. What about other
> hypervisors?

+1

>First question: should we return this magic path somewhere via the api? It 
>would be >pretty easy to have horizon generate it but it might be nice to have 
>it show up. If we >do return it, do we mangle the device to always show the 
>consistent one, or do we >return it as another parameter? guest_device perhaps?

I think returning a distinct parameter would be best in this case.

>Second question: what should happen if someone specifies /dev/xvda against a 
>>kvm cloud or /dev/vda against a xen cloud?
>I see two options:
>a) automatically convert it to the right value and return it
>b) fail with an error message

I would vote for option a (auto convert and return)

With respect to the third question:
> (b) automatically modify the request to attach at /dev/vdc and return it)

Seems the best choice we have given a balance between compatibility
and reliability.
The only way to get better reliability given the scenarios creates a
mess compatibility wise in my opinion.  I also think that if we add a
field to volume show that includes the *real* path it alleviates some
of the problem here.

John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~open

Re: [Openstack] devstack + exercise.sh failures

2012-08-09 Thread John Griffith
On Thu, Aug 9, 2012 at 1:57 PM, Joe Gordon  wrote:
> Did you turn off rate limiting in devstack?  I have hit that in the past
>
> On Aug 9, 2012 12:36 PM, "Thomas Gall"  wrote:
>>
>> Hi!
>>
>> I'm working on some code for scheduler_hints to be used during migration
>> and was running devstack/exercise.sh on the latest greatest git.  Without
>> any of my changes installed I see on a 12.04 install the following failures:
>>
>> =
>> SKIP quantum
>> SKIP swift
>> PASS aggregates
>> PASS bundle
>> PASS client-args
>> PASS client-env
>> PASS sec_groups
>> FAILED boot_from_volume
>> FAILED euca
>> FAILED floating_ips
>> FAILED volumes
>> =
>>
>> I'm new so certainly possible I've missed an email/bug that documents
>> this.  I did also try on f17 but the results were exactly the same.  Not
>> that it should matter but I have devstack running inside of a kvm partition.
>> Nothing obvious seems amiss.
>>
>> localrc has nothing in it but the settings for MYSQL_PASSWORD,
>> RABBIT_PASSWORD, SERVICE_TOKEN, SERVICE_PASSWORD, ADMIN_PASSWORD
>>
>> Known problem or ?
>>
>> Regards,
>> Tom
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Sadly the boot from volume tests haven't worked for a while, and I
suspect the following failures you're seeing are aftermath.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Nova Volume and provisionning on iSCSI SAN

2012-08-02 Thread John Griffith
On Thu, Aug 2, 2012 at 10:21 AM, Vishvananda Ishaya
 wrote:
> You will likely have to write a nova-volume/cinder backend to talk to the
> dell SAN directly. You could probably base it on the HP lefthand san code
> and get something working pretty quickly:
>
>
> https://github.com/openstack/nova/blob/master/nova/volume/san.py
>
> Vish
>
> On Aug 2, 2012, at 2:31 AM, Bilel Msekni  wrote:
>
> Hi all,
> I have a question relating to nova-volume, and provisioning block devices as
> storage for VMs. As I understand it from the documentation, nova-volume will
> take a block device with LVM on it, and then become an iSCSI target to share
> the logical volumes to compute nodes. I also understand that there is
> another process for using an HP lefthand SAN or solaris iSCSI setup, whereby
> nova-volume can interact with APIs for volume creation on the SAN itself.
>
> I have a dell iSCSI SAN, and I can see that I'd be able to mount a LUN from
> the SAN on my nova-volume node, then go through the documented process of
> creating an LVM on this LUN and having nova-volume re-share it over iSCSI to
> the compute nodes, but what I'm wondering is whether I can have the compute
> nodes simple connect to the iSCSI SAN to access these volumes (which would
> be created and managed by nova-volume still), rather than connect each
> compute node to the iSCSI target which nova-volume presents? I imagine with
> this setup, I could take advantage of the SAN's HA and performance benefits.
>
> Hope that makes sense..
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Bilel,

If you need some help with this let me know.  I'll be back from
vacation tomorrow and can point a few things out to you if needed.

John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] When are the IRC meetings for Nova, Glance and Swift?

2012-07-20 Thread John Griffith
On Fri, Jul 20, 2012 at 8:34 AM, Jay Pipes  wrote:
> Glance does not have any regular weekly IRC meetings.
>
> Not sure about Swift or Nova.
>
> Best,
> -jay
>
> On 07/20/2012 02:40 AM, Sheng Bo Hou wrote:
>> Hi OpenStackers,
>>
>> From this link http://wiki.openstack.org/Meetings/, I cannot find when
>> the IRC meetings for Nova, Glance and Swift will be.
>> Can someone tell me when these meetings take place?
>> Thank you in advanced.
>>
>>
>> Best wishes.
>> Vincent Hou (侯胜博)
>>
>> Software Engineer, Standards Growth Team, Emerging Technology Institute,
>> IBM China Software Development Lab
>>
>> Tel: 86-10-82450778 Fax: 86-10-82453660
>> Notes ID: Sheng Bo Hou/China/IBM@IBMCNE-mail: sb...@cn.ibm.com
>> Address:3F Ring, Building 28 Zhongguancun Software Park, 8 Dongbeiwang
>> West Road, Haidian District, Beijing, P.R.C.100193
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Hey Vincent,

You can look at the meetings wiki page to see if there's an applicable
meeting or sub-group meeting.  Not sure if all of these are up to date
but they seem to be.

http://wiki.openstack.org/Meetings/

John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Cinder] Wiki update

2012-07-14 Thread John Griffith
Hi Everyone,

In light of the "lively" email threads the past couple of days I
thought it would be good to update the Cinder wiki page and point out
that it exists.  In no way does it answer all of the
questions/concerns, however it does at least give a bit of an
introduction and at least offer some general answers to a few of the
questions that have come up.  If you're interested you can check out
the general run down here [1].

Feel free to offer any CONSTRUCTIVE feedback, I'm more than open to
taking suggestions or input and working with folks. Also in light of
the concerns raised, I'm working on a regular communication/update
plan to keep folks who are interested in the loop on how Cinder is
shaping up.

Thanks,
John

[1]: http://wiki.openstack.org/Cinder

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread John Griffith
On Thu, Jul 12, 2012 at 1:14 PM, George Reese
 wrote:
> So if Im not coding, I should shut up?
>
> I think you answered your own question.
>
> Sent from my iPhone
>
> On Jul 12, 2012, at 14:10, Brian Waldon  wrote:
>
> What exactly was so offensive about what I said? Communities like OpenStack
> are built on top of people *doing* things, not *talking* about things. I'm
> just asking you to contribute code or design help rather than slanderous
> commentary.
>
> Brian " "Offensive" " Waldon
>
> On Jul 12, 2012, at 11:59 AM, George Reese wrote:
>
> You evidently have not had to live with the interoperability nightmare known
> as OpenStack in the same way I have. Otherwise, you would find responses
> like Brian's much more offensive.
>
> -George
>
> On Jul 12, 2012, at 1:48 PM, Christopher B Ferris wrote:
>
> This level of response is unnecessary.
>
> That said, the perspectives which influenced the decision seemed somewhat
> weighted to the development community. I could be wrong, but I did not see
> much input from the operations community as to the impact.
>
> Clearly, going forward, we want to be more deliberate about changes that may
> have impact on operations and he broader ecosystem that bases its efforts on
> assumptions established at the start of a release cycle, rather than on
> changes introduced late in the cycle.
>
> Cheers
>
> Chris
>
> Sent from my iPad
>
> On Jul 12, 2012, at 2:24 PM, "George Reese" 
> wrote:
>
> Well, I think overall OpenStack has done an absolute shit job of
> compatibility and I had hoped (and made a huge point of this at the
> OpenStack conference) Diablo -> Essex would be the end of this compatibility
> bullshit.
>
> But the attitudes in this thread and with respect to the whole Cinder
> question in general suggest to me that this cavalier attitude towards
> forward migration hasn't changed.
>
> So you can kiss my ass.
>
> -George
>
> On Jul 12, 2012, at 12:11 PM, Brian Waldon wrote:
>
> We actually care a hell of a lot about compatibility. We also recognize
> there are times when we have to sacrifice compatibility so we can move
> forward at a reasonable pace.
>
> If you think we are handling anything the wrong way, we would love to hear
> your suggestions. If you just want to make comments like this, I would
> suggest you keep them to yourself.
>
> Have a great day!
> Brian Waldon
>
> On Jul 12, 2012, at 9:32 AM, George Reese wrote:
>
> This community just doesn't give a rat's ass about compatibility, does it?
>
> -George
>
> On Jul 11, 2012, at 10:26 AM, Vishvananda Ishaya wrote:
>
> Hello Everyone,
>
> Now that the PPB has decided to promote Cinder to core for the Folsom
> release, we need to decide what happens to the existing Nova Volume
> code. As far as I can see it there are two basic strategies. I'm going
> to give an overview of each here:
>
> Option 1 -- Remove Nova Volume
> ==
>
> Process
> ---
> * Remove all nova-volume code from the nova project
> * Leave the existing nova-volume database upgrades and tables in
>   place for Folsom to allow for migration
> * Provide a simple script in cinder to copy data from the nova
>   database to the cinder database (The schema for the tables in
>   cinder are equivalent to the current nova tables)
> * Work with package maintainers to provide a package based upgrade
>   from nova-volume packages to cinder packages
> * Remove the db tables immediately after Folsom
>
> Disadvantages
> -
> * Forces deployments to go through the process of migrating to cinder
>   if they want to use volumes in the Folsom release
>
> Option 2 -- Deprecate Nova Volume
> =
>
> Process
> ---
> * Mark the nova-volume code deprecated but leave it in the project
>   for the folsom release
> * Provide a migration path at folsom
> * Backport bugfixes to nova-volume throughout the G-cycle
> * Provide a second migration path at G
> * Package maintainers can decide when to migrate to cinder
>
> Disadvantages
> -
> * Extra maintenance effort
> * More confusion about storage in openstack
> * More complicated upgrade paths need to be supported
>
> Personally I think Option 1 is a much more manageable strategy because
> the volume code doesn't get a whole lot of attention. I want to keep
> things simple and clean with one deployment strategy. My opinion is that
> if we choose option 2 we will be sacrificing significant feature
> development in G in order to continue to maintain nova-volume for another
> release.
>
> But we really need to know if this is going to cause major pain to existing
> deployments out there. If it causes a bad experience for deployers we
> need to take our medicine and go with option 2. Keep in mind that it
> shouldn't make any difference to end users whether cinder or nova-volume
> is being used. The current nova-client can use either one.
>
> Vish
>
>
> ___
> Mailing list: https://launchpad.net/~

[Openstack] Some clarifications about Cinder

2012-07-12 Thread John Griffith
Hi Everyone,

Throughout the email thread regarding how to proceed with
cinder/nova-volumes and a number of IRC conversations I thought I
should try and clarify a few things about Cinder.

First, it should be clear that Cinder is literally a direct copy of
the existing nova-volume code.  This was intentional in order to
maintain compatibility and provide a 'sane' transition.  The goal for
Folsom from the very start was clearly stated as providing a
functional equivalent and as near compatible version as possible (I
won't say 100% because there's always room for interpretation with
regard to what compatibility means).  There are a number of things
that were considered and done to make things better for the community:

1. For the most part it's the same code
2. The usage semantics are the same
3. You can still use novaclient just as you did before
4. You can use euca2ools to the same extent that you did before
5. You can also use the new cinderclient

The only thing we're really changing at this point is that now the
volume service is it's own project.  This of course means that there
is some up front configuration regarding a different end point etc,
but that really is the bulk of it.  You'll notice for example that all
of the existing devstack tests etc work exactly the same with cinder
as they do with nova-volume, we're not suggesting anybody replace
nova-volume with an incompatible interface.

I want to be very clear that myself and just about everybody else I've
talked with and worked with DO in fact care about compatibility as
well as customer impacts.  I know one concern is migration, that's
something that is critical and if Cinder doesn't have a robust and
clean migration mechanism in place by F3 I don't think we would ask
anybody to switch from what they already have.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread John Griffith
On Thu, Jul 12, 2012 at 9:28 AM, Jay Pipes  wrote:
> On 07/12/2012 10:36 AM, Thomas, Duncan wrote:
>> We’ve got volumes in production, and while I’d be more comfortable with
>> option 2 for the reasons you list below, plus the fact that cinder is
>> fundamentally new code with totally new HA and reliability work needing
>> to be done (particularly for the API endpoint), it sounds like the
>> majority is strongly favouring option 1…
>
> Actually, I believe Cinder is essentially a bit-for-bit copy of
> nova-volumes. John G, is that correct?
>

Yes, that's correct, and as you state it's really the only reason that
option 1 is feasible and also why in my opinion it's the best option.

> It's this similarity that really makes option 1 feasible. If the
> codebases (and API) were radically different, removal like this would be
> much more difficult IMHO.
>
> Best,
> -jay
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-11 Thread John Griffith
On Wed, Jul 11, 2012 at 11:38 AM, Sean Dague  wrote:
> Before we completely pile on option 1, can we get devstack changed to run
> this way? I think the amount of pain / ease that transition is for users and
> the OpenStack CI team will greatly inform this decision, and give us some
> good data points on how tough this is for people to convert.

Yes, you can do this currently by adding the following to your localrc
in devstack:

ENABLED_SERVICES+=",-n-vol,c-api,c-sch,c-vol"

I'm also planning to propose a patch for devstack to make Cinder the
default, here this afternoon (of course this can be configured back to
use Nova Volume if desired).

>
> -Sean
>
>
> On 07/11/2012 12:22 PM, Mike Perez wrote:
>>
>> +1 for option 1
>>
>> --
>> Mike Perez
>> DreamHost.com
>>
>> On Wednesday, July 11, 2012 at 8:26 AM, Vishvananda Ishaya wrote:
>>
>>> Option 1 -- Remove Nova Volume
>>> ==
>>
>>
>>
>> This body part will be downloaded on demand.
>>
>
>
> --
> Sean Dague
> IBM Linux Technology Center
> email: sda...@linux.vnet.ibm.com
> alt-email: slda...@us.ibm.com
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Cinder] Weekly meeting reminder

2012-07-10 Thread John Griffith
All,

Just a reminder that we'll have our weekly Nova-Volume/Cinder meeting
tomorrow (Wed July 11) at 16:00 UTC.  You can find the agenda, and add
to it here: http://wiki.openstack.org/NovaVolumeMeetings

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Folsom-2 milestone available for Cinder

2012-07-05 Thread John Griffith
Hi everyone,

As a follow up to the F2 announcement from Thierry, I'd also like to
point out that there is an F2 release of Cinder that went out today as
well.  As Cinder is not currently a core Openstack project it was not
included in the announcement.  That being said, the Cinder project is
currently following the same release cycles and processes on the road
to achieving core project status.

You can see the full list of new features and fixed bugs, as well as
tarball downloads, at:

https://launchpad.net/cinder/folsom/folsom-2

Many of you have already noticed, but Cinder is also now integrated
into devstack.  You can select the use of cinder instead of
nova-volume in devstack by adding the following line to your localrc
file:

ENABLED_SERVICES+=",-n-vol,c-api,c-sch,c-vol"



Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Git Commit Messages

2012-06-28 Thread John Griffith
On Thu, Jun 28, 2012 at 11:38 AM, Brian Waldon
 wrote:
> I've written up a short guide in Nova's HACKING.rst on how to write useful
> commit messages: https://review.openstack.org/#/c/9118/.
>
> The driving factor here is the amount of time I've personally spent coaching
> people through the process of composing a commit message. I believe we would
> all benefit from writing better commit messages, so I'm taking the first
> step by getting a common guide written up. All feedback is appreciated!
>
> Brian Waldon
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

I like it... one possible enhancement, for visual folks like myself,
would it be of any value to include and example?  Or pointer to a
dummy commit message in gerrit, on a wiki, or wherever?  Even a
template perhaps.

Just looking in gerrit on your own is fine of course too, but who
knows, maybe you'll come across one that's incorrect :(

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [metering] Cinder usage data retrieval

2012-06-20 Thread John Griffith
On Wed, Jun 20, 2012 at 12:15 PM, Nick Barcet  wrote:
> On 06/20/2012 07:26 PM, John Griffith wrote:
>> On Wed, Jun 20, 2012 at 10:53 AM, Nick Barcet  
>> wrote:
>>> Hello John (or anyone else working on cinder),
>>>
>>> As part of the ceilometer project¹, we're working on usage data
>>> retrieval from various OpenStack components. One of them is Cinder.
>>> We're targeting Folsom for the first release, therefore it seems
>>> important for both projects to be able to work together, this is why
>>> we're bringing ceilometer to your attention and asking for advices. :)
>>>
>>> What we want is to retrieve the maximum amount of data, so we can meter
>>> things, to bill them in the end. For now and for Cinder, this would
>>> first include (per user/tenant):
>>> - the amount of reserved volume space
>>> - the amount of used volume space
>>> - the number of volumes
>>> but we'll need probably more in a near future.
>>>
>>> Do you have any advice regarding integration of Ceilometer and Cinder
>>> together? What would be a stable interface we could rely on that would
>>> be independent of the backend?
>>>
>>> Thanks in advance,
>>>
>>> Regards,
>>>
>>> ¹  http://launchpad.net/ceilometer
>>> --
>>> Nick Barcet 
>>> aka: nijaba, nicolas
>>>
>>
>> Hi Nick,
>>
>> We should chat about how things are shaping up so far and how you're
>> implementing things on the other sides (consistency where
>> practical/possible).  Also, it sort of depends on the architecture and
>> use model details of Ceilometer, which I hate to admit but I'm not
>> really up to speed on.
>>
>> My first reaction/thought is the best most appropriate place to tie in
>> is via the python-cinderclient.  There would be a number of ways to
>> obtain some of this info, whether deriving it or maybe some extensions
>> to obtain things directly.
>
> Sounds great.  We have our weekly meeting on Thurdays at 4PM UTC [1]
> which you would be welcome to join, or I can set up a bridge for us a
> phone chat.  Let me know what you would prefer.
>
> [1] http://wiki.openstack.org/Meetings/MeteringAgenda
>
> Cheers,
> Nick
>
>

I'll drop in on irc tomorrow...

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [metering] Cinder usage data retrieval

2012-06-20 Thread John Griffith
On Wed, Jun 20, 2012 at 10:53 AM, Nick Barcet  wrote:
> Hello John (or anyone else working on cinder),
>
> As part of the ceilometer project¹, we're working on usage data
> retrieval from various OpenStack components. One of them is Cinder.
> We're targeting Folsom for the first release, therefore it seems
> important for both projects to be able to work together, this is why
> we're bringing ceilometer to your attention and asking for advices. :)
>
> What we want is to retrieve the maximum amount of data, so we can meter
> things, to bill them in the end. For now and for Cinder, this would
> first include (per user/tenant):
> - the amount of reserved volume space
> - the amount of used volume space
> - the number of volumes
> but we'll need probably more in a near future.
>
> Do you have any advice regarding integration of Ceilometer and Cinder
> together? What would be a stable interface we could rely on that would
> be independent of the backend?
>
> Thanks in advance,
>
> Regards,
>
> ¹  http://launchpad.net/ceilometer
> --
> Nick Barcet 
> aka: nijaba, nicolas
>

Hi Nick,

We should chat about how things are shaping up so far and how you're
implementing things on the other sides (consistency where
practical/possible).  Also, it sort of depends on the architecture and
use model details of Ceilometer, which I hate to admit but I'm not
really up to speed on.

My first reaction/thought is the best most appropriate place to tie in
is via the python-cinderclient.  There would be a number of ways to
obtain some of this info, whether deriving it or maybe some extensions
to obtain things directly.

Thanks,
John

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Deleting a volume stuck in "attaching" state?

2012-06-19 Thread John Griffith
On Tue, Jun 19, 2012 at 7:40 PM, Lars Kellogg-Stedman
 wrote:
> I attempted to attach a volume to a running instance, but later
> deleted the instance, leaving the volume stuck in the "attaching"
> state:
>
>  # nova volume-list
>  ++---+--+--+-+-+
>  | ID |   Status  | Display Name | Size | Volume Type | Attached to |
>  ++---+--+--+-+-+
>  | 9  | attaching | None         | 1    | None        |             |
>  ++---+--+--+-+-+
>
> It doesn't appear to be possible to delete this with "nova
> volume-delete":
>
>  # nova volume-delete
>   nova volume-delete 9
>   ERROR: Invalid volume: Volume status must be available or error (HTTP 400)
>
> Other than directly editing the database (and I've had to do that an
> awful lot already), how do I recover from this situation?
>
> --
> Lars Kellogg-Stedman        |
> Senior Technologist                                | 
> http://ac.seas.harvard.edu/
> Academic Computing                                 | 
> http://code.seas.harvard.edu/
> Harvard School of Engineering and Applied Sciences |
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Hi Lars,

Unfortunately manipulating the database might be your best bet for
now.  We do have plans to come up with another option in the Cinder
project, but unfortunately that won't help you much right now.

If somebody has a better method, I'm sure they'll speak up and reply
to this email, but I think right now that's your best bet.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Cinder status update

2012-06-19 Thread John Griffith
On Tue, Jun 19, 2012 at 3:29 PM, Gabriel Hurley
 wrote:
> Nice work.
>
> When you've got the rest of the API bits ironed out (particularly 
> attach/detach) I'll help work on making sure Horizon is fully functional 
> there. Note that there's also an F3 Horizon blueprint for splitting volumes 
> into its own optional panel: 
> https://blueprints.launchpad.net/horizon/+spec/nova-volume-optional
>
> We should coordinate on these things. ;-)
>
>    - Gabriel
>
>> -Original Message-
>> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
>> [mailto:openstack-
>> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of John
>> Griffith
>> Sent: Tuesday, June 19, 2012 2:10 PM
>> To: openstack@lists.launchpad.net
>> Subject: [Openstack] Cinder status update
>>
>> For those of you that don't know Cinder is the new project intended to
>> separate block storage out of Nova and provide it via it's own service.  The
>> goal is to have a functional replacement for Nova-Volumes by Folsom 2
>> (don't worry, you'll be able to select which service to use).  So far things 
>> have
>> gone fairly well, we're at a stage now where we have a beta version that's
>> ready for use in devstack environments for folks that might be curious or
>> interested in doing some testing/fixing :)
>>
>> I haven't done anything fancy like packaging it all up in vagrant, but
>> depending on the level of interest we can look into that.  Currently the
>> needed patches are in Gerrit as Drafts, so rather than mess with adding a ton
>> of people who are just a little curious, I've created a github fork that can 
>> be
>> used just for initial looking around/testing.
>>
>> In order to get an install up and running all you need to do is clone the
>> following version of devstack:
>> https://github.com/j-griffith/devstack.git (you should also be able to just
>> modify your vagrant attributes file to point to this version of devstack of
>> course).
>>
>> The stackrc in the version of devstack on j-griffith is hard coded for the 
>> cinder
>> service and the special repos in order to make it as easy as possible to 
>> check
>> out the beta.
>>
>> Run stack.sh and you should be in business...
>>
>> Please note that this is a hack to get things up and running for folks that 
>> have
>> expressed interest in testing and seeing where things are at.  There are
>> surely issues/bugs and things that "aren't done yet", but this is suitable 
>> to be
>> called beta.
>>
>> What to expect:
>>    * Create/List/Delete volumes on the cinder service via:
>>              cinderclient ('cinder'), euca2ools
>>    * Create/List/Delete volume-snapshots on the cinder service via:
>>              cinderclient ('cinder'), euca2ools
>>    * Attach/Detach needs some work but it can be done via euca-attach-
>> volume
>>
>> What's in progress:
>>    * Attach/Detach for cinderclient
>>    * Seems to be something not working in horizon any longer, need to
>>       look at this
>>    * Lots of cleanup and unused nova code to strip out of cinder project 
>> still
>>    * Tests (unit tests, as well as devstack tests)
>>
>> Note there are a fixes/changes on a daily basis so it's very much a moving
>> target.  Official repos should all be updated and ready for consumption no
>> later than the end of this week.
>>
>>
>> Give it a try, if you find an issue or something missing let me know, or 
>> better
>> yet fix it up and send me a pull request :)
>>
>> Thanks,
>> John
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Looks like most of these issues are taken care of.  I have a few
things to button up elsewhere, but should be pushing changes tonight
or tomorrow that will enable alot of this.

Also won't need to use my personal github any longer :)

I'll send an update to everyone on what to add to localrc to make this
work when everything is in place.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Cinder status update

2012-06-19 Thread John Griffith
For those of you that don't know Cinder is the new project intended to
separate block storage out of Nova and provide it via it's own
service.  The goal is to have a functional replacement for
Nova-Volumes by Folsom 2 (don't worry, you'll be able to select which
service to use).  So far things have gone fairly well, we're at a
stage now where we have a beta version that's ready for use in
devstack environments for folks that might be curious or interested in
doing some testing/fixing :)

I haven't done anything fancy like packaging it all up in vagrant, but
depending on the level of interest we can look into that.  Currently
the needed patches are in Gerrit as Drafts, so rather than mess with
adding a ton of people who are just a little curious, I've created a
github fork that can be used just for initial looking around/testing.

In order to get an install up and running all you need to do is clone
the following version of devstack:
https://github.com/j-griffith/devstack.git (you should also be able to
just modify your vagrant attributes file to point to this version of
devstack of course).

The stackrc in the version of devstack on j-griffith is hard coded for
the cinder service and the special repos in order to make it as easy
as possible to check out the beta.

Run stack.sh and you should be in business...

Please note that this is a hack to get things up and running for folks
that have expressed interest in testing and seeing where things are
at.  There are surely issues/bugs and things that "aren't done yet",
but this is suitable to be called beta.

What to expect:
   * Create/List/Delete volumes on the cinder service via:
 cinderclient ('cinder'), euca2ools
   * Create/List/Delete volume-snapshots on the cinder service via:
 cinderclient ('cinder'), euca2ools
   * Attach/Detach needs some work but it can be done via euca-attach-volume

What's in progress:
   * Attach/Detach for cinderclient
   * Seems to be something not working in horizon any longer, need to
  look at this
   * Lots of cleanup and unused nova code to strip out of cinder project still
   * Tests (unit tests, as well as devstack tests)

Note there are a fixes/changes on a daily basis so it's very much a
moving target.  Official repos should all be updated and ready for
consumption no later than the end of this week.


Give it a try, if you find an issue or something missing let me know,
or better yet fix it up and send me a pull request :)

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Cinder] Weekly meeting reminder

2012-06-12 Thread John Griffith
Just a reminder, we will have our weekly team meeting in
openstack-meeting tomorrow June 13 at 16:00 UTC.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Cinder] Weekly meeting reminder

2012-06-05 Thread John Griffith
Just a reminder, our weekly meeting will take place tomorrow (Wed, June 6)
at 16:00 UTC.

Agenda:
* status update
* outstanding items for F2
* outstanding reviews
* unassigned blueprints
* open discussion

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Volume creation stuck at status "Creating"

2012-05-31 Thread John Griffith
On Thu, May 31, 2012 at 5:58 AM, Alisson Soares Limeira Pontes <
apon...@cpqd.com.br> wrote:

> Something changed in the nova-volume ubuntu packages instalation.
> I'd never had problems with nova-volume, but in my last two setups i
> cannot attach volume and vm. Logs do not show any problem, so no clue why
> this problem.
>
>
> 2012/5/31 Milind 
>
>> Thanks,
>>
>> Any one know what is the problem or it is another bug?
>>
>> REgards,
>> Milind
>>
>> On Thu, May 31, 2012 at 12:22 PM, William Herry <
>> william.herry.ch...@gmail.com> wrote:
>>
>>> I can't tell what's wrong about your config, let others help you
>>>
>>> On Thu, May 31, 2012 at 2:50 PM, Milind  wrote:
>>>
 Hi Just ran command... here is the output...

 root@ucmaster:/var/log/upstart# nova --debug  volume-create
 --display_name=novavol5 --display_description=volumenova5 1
 connect: (ucmaster, 5000)
 send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
 ucmaster:5000\r\nContent-Length: 117\r\ncontent-type:
 application/json\r\naccept-encoding: gzip, deflate\r\naccept:
 application/json\r\nuser-agent: python-novaclient\r\n\r\n{"auth":
 {"tenantName": "openstackDemo", "passwordCredentials": {"username":
 "adminUser", "password": "secretword"}}}'
 reply: 'HTTP/1.1 200 OK\r\n'
 header: Content-Type: application/json
 header: Vary: X-Auth-Token
 header: Date: Thu, 31 May 2012 06:42:50 GMT
 header: Transfer-Encoding: chunked
 connect: (ucmaster, 8776)
 send: u'POST /v1/68124ec3a778447093eba446aa896105/volumes
 HTTP/1.1\r\nHost: ucmaster:8776\r\nContent-Length:
 131\r\nx-auth-project-id: openstackDemo\r\naccept-encoding: gzip,
 deflate\r\naccept: application/json\r\nx-auth-token:
 b0b433d2506145d0b4f5ab8e1fcb6478\r\nuser-agent:
 python-novaclient\r\ncontent-type: application/json\r\n\r\n{"volume":
 {"snapshot_id": null, "display_name": "novavol5", "volume_type": null,
 "display_description": "volumenova5", "size": 1}}'
 reply: 'HTTP/1.1 200 OK\r\n'
 header: X-Compute-Request-Id: req-58d480c3-f729-4670-8c86-74ef9991993a
 header: Content-Type: application/json
 header: Content-Length: 274
 header: Date: Thu, 31 May 2012 06:42:50 GMT
 root@ucmaster:/var/log/upstart# clear






 On Thu, May 31, 2012 at 12:12 PM, Milind wrote:

>
>
>
> On Thu, May 31, 2012 at 12:08 PM, William Herry <
> william.herry.ch...@gmail.com> wrote:
>
>> I can't see any unusual log
>>
>> try:
>>
>>  nova --debug volume-create --display_name=novavol4
>> --display_description=volumenova4 1
>>
>>
>> On Thu, May 31, 2012 at 2:33 PM, Milind wrote:
>>
>>> I did that and issued following command.
>>>
>>> nova volume-create --display_name=novavol4
>>> --display_description=volumenova4 1
>>>
>>> I have attached relevant part of log.
>>>
>>> Regards,
>>> Milind
>>>
>>>
>>> On Thu, May 31, 2012 at 11:48 AM, William Herry <
>>> william.herry.ch...@gmail.com> wrote:
>>>
 add debug=true to /etc/nova/nova.conf and restart
 service(nova-volume I think)

 On Thu, May 31, 2012 at 2:16 PM, Milind wrote:

> In which config file?
>
>
> On Thu, May 31, 2012 at 11:43 AM, William Herry <
> william.herry.ch...@gmail.com> wrote:
>
>> have you add debug=true to config file
>>
>> On Thu, May 31, 2012 at 2:11 PM, Milind 
>> wrote:
>>
>>> There is nothing in the logs :(
>>>
>>>
>>>
>>> On Thu, May 31, 2012 at 11:37 AM, William Herry <
>>> william.herry.ch...@gmail.com> wrote:
>>>
 you should check logs to see what's going on

 On Thu, May 31, 2012 at 1:50 PM, Milind >>> > wrote:

> Hi,
>
> I am not able to resolve this error quite frustrated :(, it
> gets stuck at volume creation with status as "Creating"
>
>
>
>
> Regards,
> Milind
>
 --
> *Alisson Pontes*
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
Hi Milind,

Sorry if you've already answered this, but what sort of setup is this?  Are
you using Essex, or latest from Trunk?  Is this a devstack install or
other?  This is something I've seen before as well and it had to do with
issues in my configuration for the scheduler.  Let me know a bit more about
your setup if you have a chance.  Perhaps I can try to recreate and have a
closer look.

Thanks,
John
___
Mailing list: https

[Openstack] [Cinder] Weekly team meeting reminder

2012-05-30 Thread John Griffith
Just a reminder, we will have our weekly team meeting in
openstack-meeting today at 16:00 UTC.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [cinder] weekly meeting reminder

2012-05-21 Thread John Griffith
Just a reminder, we've changed our weekly meeting time to Wednesdays
at 16:00 UTC effective this week (Wed May 23, 2012).  Also keep in
mind this is still a nova-volume meeting as well, so if you have
topics please join us.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Essex horizon dashboard - volume snapshot issue

2012-05-18 Thread John Griffith
On Fri, May 18, 2012 at 7:54 PM, Vijay  wrote:
> Hello,
> On Essex Dashboard, I am able to create a snapshot of a volume successfully. 
> However, when I click on the volume snapshot to look at the details, I get 
> "Error: Unable to retrieve volume details". This error occurs only when 
> retrieving the details of volume snapshots only. The volume details of the 
> volume created from the scratch shows up correctly.
>
> Also, on the horizon dashboard, there is no option to attach the volume 
> snapshot to any running instance. I see only delete snapshot option. If it is 
> by design, then, how is volume snapshot is going to be used?
>
> Any help is appreciated.
>
> Thanks,
> -vj
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Hi VJ,

I believe you may have discovered a bug in the current version of
code.  Are you using the latest Folsom version (ie devstack)?  Check
your Horizon logs and you'll notice a number of errors when trying to
perform this operation.  Perhaps some Horizon folks here have some
knowledge of this, otherwise I can look into it further next week and
file a bug if necessary.

Meanwhile, you can use python-novaclient to perform a 'nova
volume-snapshot-show' which is the information that would be reported
from the Horizon details page you're trying to retrieve.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] not able to attach a volume to a running instance

2012-05-17 Thread John Griffith
Hey Vijay,

You might want to verify that /etc/iscsi/initiatorname.iscsi in fact
does not exist.  If that is actually the case, then something appears
to have gone wrong in your iscsi setup/install on that node I believe.

You can try running 'sudo iscsi-iname' and using the output to create
the file manually.

John

On Thu, May 17, 2012 at 3:12 PM, Vijay  wrote:
> Hello,
> I am not able to attach a volume to a running instance.
>
> I am able to create volume but attaching it to the running instance is 
> failing. Using Essex release.
> I am getting the following error:
>
> File /etc/iscsi/initiatorname.iscsi could not be found.
>
> Detailed nova-compute log:
>
> 2012-05-17 13:50:28 ERROR nova.rpc.amqp 
> [req-301e50a2-3238-4924-b7f0-477be7e0ffa8 75899f2562cc44d9aa0f120ff1d246be 
> 6672d2141fe4454e87fad2ba19223327] Exception during message handling
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp Traceback (most recent call last):
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/rpc/amqp.py",
>  line 252, in _process_data
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp rval = node_func(context=ctxt, 
> **node_args)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/exception.py",
>  line 114, in wrapped
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp return f(*args, **kw)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py",
>  line 153, in decorated_function
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp function(self, context, 
> instance_uuid, *args, **kwargs)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py",
>  line 177, in decorated_function
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp sys.exc_info())
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp self.gen.next()
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py",
>  line 171, in decorated_function
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp return function(self, context, 
> instance_uuid, *args, **kwargs)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py",
>  line 1717, in attach_volume
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp 
> self.volume_api.unreserve_volume(context, volume)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp self.gen.next()
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py",
>  line 1708, in attach_volume
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp connector = 
> self.driver.get_volume_connector(instance_ref)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/virt/libvirt/connection.py",
>  line 479, in get_volume_connector
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp self._initiator = 
> libvirt_utils.get_iscsi_initiator()
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/virt/libvirt/utils.py",
>  line 42, in get_iscsi_initiator
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp contents = 
> utils.read_file_as_root('/etc/iscsi/initiatorname.iscsi')
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp   File 
> "/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/utils.py", 
> line 1635, in read_file_as_root
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp raise 
> exception.FileNotFound(file_path=file_path)
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp FileNotFound: File 
> /etc/iscsi/initiatorname.iscsi could not be found.
> 2012-05-17 13:50:28 TRACE nova.rpc.amqp
>
> I appreciate any help.
> Thanks,
> -vj
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [cinder] Proposed meeting time change

2012-05-17 Thread John Griffith
To help out some of our friends in Europe, there's a proposal to move
the weekly nova-volume/cinder team meetings to Wednesdays at 16:00
UTC.  Most of the regulars were present at today's meeting and agreed
so I'm going to change this unless I get a ton of objections.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] nova volume creation problem

2012-05-07 Thread John Griffith
On Mon, May 7, 2012 at 7:17 PM, Shashi Kanth Boddula
 wrote:
> I tried creating from Dashboard as well as command, but both are not
> creating volumes.
>
> nova volume-create --display_name v1 2
>
> " specifically, what zone are you passing?"
>
> Please can you tell me what is a zone here, where to define and how to pass
> zone information ?
>
>
>
> On Tue, May 8, 2012 at 12:24 AM, Joshua Tobin 
> wrote:
>>
>> On May 7, 2012, at 11:14, Shashi Kanth Boddula 
>> wrote:
>>
>> > Ubuntu 12.04 LTS Essex.
>> >
>> > I am not able to create nova volumes, the command never ends up, and the
>> > volume status will be always "creating".
>> >
>> > # nova volume-list
>> > ++--+---+--+-+-+
>> > | ID |  Status  |    Display Name   | Size | Volume Type | Attached to |
>> > ++--+---+--+-+-+
>> > | 1  | creating | OpenStack Volume1 | 16   | None        |             |
>> > | 2  | creating | shashi            | 1    | None        |             |
>> > | 3  | creating | v1                | 2    | None        |             |
>> > | 4  | creating | v1                | 2    | None        |             |
>> > ++--+---+--+-+-+
>> >
>> > The nova volume service is running.
>> >
>> > # nova-manage service list | grep volume
>> > 2012-05-07 23:40:30 DEBUG nova.utils
>> > [req-0f8aa0b7-fa77-4e5b-93de-fc1621b575c9 None None] backend > > 'nova.db.sqlalchemy.api' from
>> > '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from
>> > (pid=9641) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658
>> > nova-volume      OpenStack                            nova
>> > enabled    XXX   2012-05-06 08:40:57
>> >
>> >
>> > In the nova.conf the volume is defined.
>> >
>> > # Volumes
>> > --volume_group=nova-volumes
>> > --volume_name_template=volume-%08x
>> > --iscsi_helper=tgtadm
>> >
>> >
>> > And in the system nova VG is already created, but no logical volumes are
>> > getting created whenever i issue "nova volume-create" command.
>> >
>> > # vgdisplay | grep nova
>> >   VG Name               nova-volumes
>> >
>> >
>> >
>> >
>> > --
>> > Thanks & Regards,
>> > Shashi Kanth
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to     : openstack@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> What command are you issuing to create the volume, specifically, what zone
>> are you passing?
>
>
>
>
> --
> Thanks & Regards,
> Shashi Kanth
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Hello Sashi,

Along with the zone info requested, would it be possible to get a look
at the nova-volume logs and possibly the nova-compute logs?  If you
look in these two places one of them is likely to contain some more
information that would help isolate the problem.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Cinder] Status updates and proposals

2012-05-01 Thread John Griffith
All,

For those folks that have expressed an interest in contributing to the
Cinder project we've made some minor progress.

We've grabbed the wiki page: http://wiki.openstack.org/Cinder

Note that currently we're keeping track of updates and what folks are
working on via etherpad:
http://etherpad.openstack.org/cinder-worksheet

Please check it out, and feel free to jump in.

John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [Openstack:Volume] Block Storage Naming Poll

2012-04-19 Thread John Griffith
On Wed, Apr 18, 2012 at 11:53 PM,   wrote:
> If you have trouble viewing or submitting this form, you can fill it out
> online:
> https://docs.google.com/spreadsheet/viewform?formkey=dG5hOVpKZ3lFY3RTcE4yU0lxa1I3VkE6MQ
>
> Block Storage Naming Poll
>
> Suggested names are listed below, cast your vote. We'll take the top results
> and find the one that isn't already associated with an existing project. If
> you have other suggestions you'd like to add to this list add them or shoot
> me an email. I'd like to close out this process in the next day or so if
> possible.
>
> Name for the new block storage service
>
> cinder
> decibel
> eleven
> litre
> arcade
> ensemble
> fount
> reservoir
> lego
> jenga
> volterre
> severance
> bolide
> corona
>
>
> Sample Question 2
>
> Powered by Google Docs Report Abuse - Terms of Service - Additional Terms
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

It looks like we have a pretty clear winner

With 10 votes "cinder" was the leading choice with the closest
alternative being "lego" at 4 votes.  Based on a total of 25 votes I
think it's safe to say the majority of folks have had an opportunity
to vote.

So... we have a project name!

I talked with Thierry last nigh regarding official repos, process etc
and will keep moving to get that all set up.  I'll keep everyone
updated via email, it shouldn't take long to get an official repo at
least.  Also in the meantime I'll create a cinder project on my own
personal github account (https://github.com/j-griffith/).

Might be a bit busy today, but hope to have something to work off of next week.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [Openstack:Summit] Nova Volume Unconference sessions

2012-04-16 Thread John Griffith
All,
For those of you that attended the Volume sessions at the summit this
morning (and those who may have missed it but would like to attend),
I'd like to continue our discussion tomorrow afternoon using the
Unconference sessions.

We've reserved 14:00 - 15:00 for continuation of the Volume spin out
discussion and 15:00 - 16:00 for Boot From Volume.  I'm working on a
specific set of goals/decisions to make during this time slots so that
we can begin moving forward and will have the etherpads updated
tomorrow.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Removal of VSA Code

2012-03-15 Thread John Griffith
On a sort of side note, I was sort of surprised that given all the
discussion on volumes, VSA etc in IRC and on email lately that there
were ZERO attendees in the weekly meeting today.

So, maybe just a reminder, there is a weekly volume meeting in
openstack-meeting on Thursdays at 18:00 (UTC).  Also the meetings page
is updated and open for folks to add topics.

John


On Thu, Mar 15, 2012 at 11:33 AM, Vishvananda Ishaya
 wrote:
>
> On Mar 15, 2012, at 10:08 AM, Ghe Rivero wrote:
>
>> I think is time (after essex release) to rethink the way plugins are 
>> integrated into "mainline code". This problem, an outdated plugin, it's not 
>> new  (Hyper-V), and with the increasing numbers of them (storage like 
>> Zadara, Nexenta... network with Nicira, BigSwitch, Citrix...) we need a 
>> policy to deal with this. From the vendor point of view, it's not easy to 
>> follow the development release cycle that OpenStack has now days, with so 
>> many changes day after day. Maybe plugins should be out of OpenStack code, 
>> and let vendors to publish them after the release.
>
> +1
>
> We are going to discuss a plan at the summit for making this easier.
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Volume team meeting reminder

2012-02-22 Thread John Griffith
Just another reminder for folks in addition to the one Robert sent out
earlier this evening.  Along with the proposed agenda in the original
email I sent out, I've also updated the meetings wiki page with
current information.
http://wiki.openstack.org/NovaVolumeMeetings

Look forward to catching up with everyone tomorrow.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Any block storage folks interested in getting together?

2012-02-22 Thread John Griffith
Hi Robert,

I had forogt that I intended to send out a reminder this afternoon.  I
had intended to continue with the standard process of using
#openstack-meeting.  The standing volume team meeting is still posted
on the meetings wiki page:
http://wiki.openstack.org/Meetings

There was a link to an .ics file to download all Openstack meetings to
your calendar, but it's easy enough to enter this one individually and
make it recurring weekly.

Talk to you tomorrow.

John

On Wed, Feb 22, 2012 at 9:19 PM, Robert Esker  wrote:
> We (NetApp) would be interested in participating.  Was #openstack-meeting or 
> #openstack-volumes decided upon?  Does anyone perhaps own a recurring 
> calendar invite for this?
>
> Thanks,
> Rob Esker
>
>
> On Feb 13, 2012, at 12:06 PM, John Griffith  
> wrote:
>
>> There's been a lot of new work going on specific to Nova Volumes the
>> past month or so.  I was thinking that it's been a long time since
>> we've had a Nova-Volume team meeting and thought I'd see if there was
>> any interest in trying to get together next week?  I'm open to
>> suggestions regarding time slots but thought I'd propose our old slot,
>> Thursday Feb 23, 18:00 - 19:00 UTC.
>>
>> Here's a proposed agenda:
>>
>>    * Quick summary of new blueprints you have submitted and completed
>> (or targeting for completion) in Essex
>>    * Any place folks might need some help with items they've targeted
>> for Essex (see if we have any volunteers to help out if needed)
>>    * Any updates regarding BSaaS
>>    * Gauge interest in resurrecting a standing meeting, perhaps every 2 
>> weeks?
>>
>> If you have specific items that you'd be interested in
>> sharing/discussing let me know.
>>
>> Thanks,
>> John
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Problem in nova/volume/driver.py

2012-02-21 Thread John Griffith
Hey Folks,

I was trying to work on bug #917245 today and had troubles connecting
my iSCSI devices.  After a bit of poking around I found the culprit in
nova/volume/driver.py


results = location.split(" ")
properties['target_portal'] = results[0].split(",")[0]
properties['target_iqn'] = results[1]
try:
properties['target_lun'] = int(results[2])
except (IndexError, ValueError):
if FLAGS.iscsi_helper == 'tgtadm':
properties['target_lun'] = 1
else:
properties['target_lun'] = 0

Unfortunately this doesn't work out very well.  First, I don't know
how to derive the lun number from the discovery (perhaps devices with
multi lun support and multiple luns reported from "report luns"
populate something here that I'm not familiar with, or maybe newer
version of iscsiadm give us some additional info), but the other
problem is how do we pick the correct default value to revert to?  In
the case of my particular device everything is Lun 0, and only Lun 0.
Looking at a wireshark trace you can see that report luns responds
with one lun and it's id is '0'.

So what happens in my case is when libvirt later goes through and
tries to attach the volume to an instance, it fails because the entry
it checks in /dev/disk/by_id has a mismatch in lun numbers.  I'm
planning to file a bug on this and assign it to myself, but I wanted
some input first.  I'm thinking that maybe there's a way to call
report luns or something and actually get the definitive value that
should be used here?  Or maybe there's another iscsiadm command that
will give us the info we need?

I'm wondering if anybody knows the logic here and perhaps would like
to educate me on the special case that I am not familiar with?  I also
figure I should make sure this wasn't changed by somebody to handle
their case where there device only support "Lun 1".  :)

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Any block storage folks interested in getting together?

2012-02-13 Thread John Griffith
Hi Bob,
Just pop into IRC: #openstack-meeting

John

On Mon, Feb 13, 2012 at 3:17 PM, Bob Van Zant  wrote:
> I'm interested in joining in. I've never joined one of the calls before,
> where do I get more information on how to join?
>
>
> On Mon, Feb 13, 2012 at 12:06 PM, Diego Parrilla
>  wrote:
>>
>> Sounds great. We will try to join the meeting.
>>
>> Enviado desde mi iPad
>>
>> El 13/02/2012, a las 19:06, John Griffith 
>> escribió:
>>
>> > There's been a lot of new work going on specific to Nova Volumes the
>> > past month or so.  I was thinking that it's been a long time since
>> > we've had a Nova-Volume team meeting and thought I'd see if there was
>> > any interest in trying to get together next week?  I'm open to
>> > suggestions regarding time slots but thought I'd propose our old slot,
>> > Thursday Feb 23, 18:00 - 19:00 UTC.
>> >
>> > Here's a proposed agenda:
>> >
>> >    * Quick summary of new blueprints you have submitted and completed
>> > (or targeting for completion) in Essex
>> >    * Any place folks might need some help with items they've targeted
>> > for Essex (see if we have any volunteers to help out if needed)
>> >    * Any updates regarding BSaaS
>> >    * Gauge interest in resurrecting a standing meeting, perhaps every 2
>> > weeks?
>> >
>> > If you have specific items that you'd be interested in
>> > sharing/discussing let me know.
>> >
>> > Thanks,
>> > John
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to     : openstack@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Any block storage folks interested in getting together?

2012-02-13 Thread John Griffith
There's been a lot of new work going on specific to Nova Volumes the
past month or so.  I was thinking that it's been a long time since
we've had a Nova-Volume team meeting and thought I'd see if there was
any interest in trying to get together next week?  I'm open to
suggestions regarding time slots but thought I'd propose our old slot,
Thursday Feb 23, 18:00 - 19:00 UTC.

Here's a proposed agenda:

* Quick summary of new blueprints you have submitted and completed
(or targeting for completion) in Essex
* Any place folks might need some help with items they've targeted
for Essex (see if we have any volunteers to help out if needed)
* Any updates regarding BSaaS
* Gauge interest in resurrecting a standing meeting, perhaps every 2 weeks?

If you have specific items that you'd be interested in
sharing/discussing let me know.

Thanks,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Development ML

2012-02-07 Thread John Griffith
I would find this helpful for managing/organizing email traffic for sure...
+1

On Tue, Feb 7, 2012 at 8:25 AM, Jay Pipes  wrote:

> On 02/07/2012 04:49 AM, Thierry Carrez wrote:
>
>> Jay Pipes wrote:
>>
>>> So, the topic of multiple mailing lists has come up before and we've
>>> even tried topical mailing lists before, but the amount of traffic on
>>> them tends to be too low for it to be worth the extra ML subscription.
>>> I've also made the argument before that with a general mailing list
>>> (this one), you get a wider audience and people that may not always get
>>> excited about distribution specifics may be exposed to important
>>> discussions, learn something new, and in general just be made aware of
>>> the state of a particular subcommunity by scanning/skimming emails.
>>>
>>
>> I agree that topical development MLs are not worth it...
>>
>> That said, I think it's time to split development discussions from
>> user/operations questions. Over the recent months with more people using
>> OpenStack the volume of non-development-related emails has reached a
>> level that makes it difficult to parse. As an example, I read all the
>> development emails, while I only read the rest of the emails based on
>> topic -- separating the lists would be a great help for me. The
>> audiences are slightly different too.
>>
>> The risks are that (1) non-development topics end up in the development
>> mailing-list anyway, and (2) developers ignore the non-development ML.
>> In order to mitigate those risks, I propose that we create a new
>> openstack-dev mailing-list, only for development discussions (new deps,
>> blueprint discussion, FFEs, packaging, core-dev proposals...).
>> Everything else should remain on the usual list, including governance
>> discussions, usage discussions, community events etc.
>>
>> Creating a new list should avoid most of risk (1), and we should just be
>> careful to redirect non-development-related topics to the other ML if it
>> still happens. Developers should still be subscribed to the usual ML to
>> catch up with all the other openstack topics, which should avoid most of
>> risk (2).
>>
>> What do you think ?
>>
>
> I'm not a fan of multiple mailing lists given our experience in the past
> with fragmented discussions... I still don't think the amount of traffic on
> the mailing list is particularly cumbersome, but maybe I'm a minority in
> that regard. I appreciate having all my OpenStack ML threads in a single ML.
>
> Best,
> -jay
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] SolidFireSanISCSIDriver - FF-Exception request

2012-01-25 Thread John Griffith
All,

I rant into some problems with my LaunchPad accounts that prevented me from
getting everything submitted/approved before the deadline.

This change is simply the addition of a SAN-ISCSI driver for SolidFire
block storage devices.  It was on it's way to approval until something went
wrong with my LaunchPad ID.

Anyway, here's the link to the applicable gitweb review:


https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commit;h=47a357bd2b46a2279a98ed726facd2b12fe0a0f5

Thanks,
John
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problems with run_tests.sh on 11.10

2012-01-02 Thread John Griffith
Thanks Soren, that did the trick!!

On Mon, Jan 2, 2012 at 4:50 AM, Soren Hansen  wrote:

> 2011/12/30 John Griffith :
> > Oops, sorry about that.  Forgot to check it in the venv, which reveals
> the
> > issue:
> >
> >  % tools/with_venv.sh
> > jdg@grumpy ~/Projects/OpenStack/nova
> >  % python
> > Python 2.7.2+ (default, Oct  4 2011, 20:06:09)
> > [GCC 4.6.1] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> >>>> import M2Crypto
> > Traceback (most recent call last):
> >   File "", line 1, in 
> >   File "/usr/local/lib/python2.7/dist-packages/M2Crypto/__init__.py",
> line
> > 22, in 
> > import __m2crypto
> > ImportError:
> /usr/local/lib/python2.7/dist-packages/M2Crypto/__m2crypto.so:
> > undefined symbol: SSLv2_method
> >>>>
>
> Ah, yes. That's because M2Crypto hasn't kept up wit the removal of
> SSLv2 from OpenSSL.
>
> It's fixed in the Ubuntu packages, so if you remove the M2Crypto line
> from pip-requires and put this instead:
>
> -e bzr+
> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/m2crypto/precise/#egg=M2Crypto
>
> You should be fine. (Yes, the line in pip-requires should start with
> "-e")
>
> --
> Soren Hansen| http://linux2go.dk/
> Ubuntu Developer| http://www.ubuntu.com/
> OpenStack Developer | http://www.openstack.org/
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problems with run_tests.sh on 11.10

2011-12-30 Thread John Griffith
Oops, sorry about that.  Forgot to check it in the venv, which reveals the
issue:

 % tools/with_venv.sh
jdg@grumpy ~/Projects/OpenStack/nova
 % python
Python 2.7.2+ (default, Oct  4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import M2Crypto
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python2.7/dist-packages/M2Crypto/__init__.py", line
22, in 
import __m2crypto
ImportError: /usr/local/lib/python2.7/dist-packages/M2Crypto/__m2crypto.so:
undefined symbol: SSLv2_method
>>>


Looking in .venv M2Crypto was NOT installed, I ran things on a clean 11.10
install last night and the results were the same.  Repeat on a clean 11.04
and everything is fine. Looking at the venv setup script to see if I can
figure out why this failed.  Seems odd I've reproduced on multiple machines
but nobody else has seen this?  Maybe there's a step I'm missing still?

John



On Fri, Dec 30, 2011 at 12:13 PM, Jay Pipes  wrote:

> On Thu, Dec 29, 2011 at 11:27 AM, John Griffith
>  wrote:
> > jdg@grumpy /tmp % python
> > Python 2.7.2+ (default, Oct  4 2011, 20:06:09)
> > [GCC 4.6.1] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> >>>> import M2Crypto
>
> What does this result in, though?
>
> $> tools/with_venv.sh python
> >>>> import M2Crypto
>
> -jay
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problems with run_tests.sh on 11.10

2011-12-29 Thread John Griffith
Hi Monty,

Thanks for the response, performed the steps you recommended and pastes the
output from run_tests.sh on pastebin:

http://paste.openstack.org/show/4018/

Let me know if this is useful.  Also, I'm going to try running on a "fresh"
11.10 install, I suspect there's some config on my existing laptop that's
messing things up.

Thanks,
John

On Thu, Dec 29, 2011 at 1:10 PM, Monty Taylor  wrote:

> Well, we're running tests in Jenkins on 11.10, so there is certainly
> something that we're doing that you're not... let's see if we can track
> that down so that we can document it properly.
>
> Ensure that you have the following packages installed via apt:
>
> build-essential python-all-dev libssl-dev swig python-setuptools openssl
>
> And then re-build your venv.
>
> If that doesn't work, please take the entire traceback/log of what
> happens when you create the venv and put it somewhere
> (paste.openstack.org would work) and send it here so that we can take a
> look at where things might be going south for you.
>
> Sorry for the troubles, but that's for working with us to get it sorted!
>
> Monty
>
> On 12/29/2011 08:27 AM, John Griffith wrote:
> > Hi,
> > I'm trying to learn how the testing framework is set up and write my own
> > unit tests for the driver I've been working on.  Unfortunately I'm not
> > making much progress, on my Ubuntu 11.10 system I keep running into
> > problems with M2Crypto.
> >
> > I picked up the change to use apt-get instead of pip, but still no luck.
> >
> > During virtualenv setup I recieved an error at install of M2Crypto that
> > the source couldn't be verified, so I ran 'sudo apt-get install -y
> > --force-yes python-m2crypto', deleted the .venv directory and ran
> > run_tests.sh again.
> >
> > This time the environment setup completed, but again the tests fail for
> > 'ImportError: No module named M2Crypto'.
> >
> > Running in the python cli I can do 'import M2Crypto' with no
> > ImportError.  I've spun up a VM for now with 11.04 and things are
> > working, but I would like to understand what's going on with 11.10 and
> > not have to use the VM if I don't have to.  Has anybody seen anything
> > along these lines?  There seems to be quite a bit on Google about 11.10
> > and M2Crypto, but not finding a resolution.
> >
> > Thanks,
> > John
> >
> >
> ``
> >
> > Nova development environment setup is complete.
> >
> > Nova development uses virtualenv to track and manage Python
> dependencies
> > while in development and testing.
> >
> > To activate the Nova virtualenv for the extent of your current shell
> > session you can run:
> >
> > $ source .venv/bin/activate
> >
> > Or, if you prefer, you can run commands in the virtualenv on a case
> > by case
> > basis by running:
> >
> > $ tools/with_venv.sh 
> >
> > Also, make test will automatically use the virtualenv.
> >
> > ERROR
> >
> > ==
> > ERROR: 
> > --
> > Traceback (most recent call last):
> >   File
> >
> "/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/suite.py",
> > line 208, in run
> > self.setUp()
> >   File
> >
> "/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/suite.py",
> > line 291, in setUp
> > self.setupContext(ancestor)
> >   File
> >
> "/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/suite..py",
> > line 314, in setupContext
> > try_run(context, names)
> >   File
> >
> "/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/util.py",
> > line 478, in try_run
> > return func()
> >   File "/home/jdg/Projects/OpenStack/nova/nova/tests/__init__.py", line
> > 48, in setup
> > from nova.tests import fake_flags
> >   File "/home/jdg/Projects/OpenStack/nova/nova/tests/fake_flags.py",
> > line 28, in 
> > flags.DECLARE('auth_driver', 'nova.auth.manager')
> >   File "/home/jdg/Projects/OpenStack/nova/nova/flags.py", line 224, in
> > DECLA

[Openstack] Problems with run_tests.sh on 11.10

2011-12-29 Thread John Griffith
Hi,
I'm trying to learn how the testing framework is set up and write my own
unit tests for the driver I've been working on.  Unfortunately I'm not
making much progress, on my Ubuntu 11.10 system I keep running into
problems with M2Crypto.

I picked up the change to use apt-get instead of pip, but still no luck.

During virtualenv setup I recieved an error at install of M2Crypto that the
source couldn't be verified, so I ran 'sudo apt-get install -y --force-yes
python-m2crypto', deleted the .venv directory and ran run_tests.sh again.

This time the environment setup completed, but again the tests fail for
'ImportError: No module named M2Crypto'.

Running in the python cli I can do 'import M2Crypto' with no ImportError.
 I've spun up a VM for now with 11.04 and things are working, but I would
like to understand what's going on with 11.10 and not have to use the VM if
I don't have to.  Has anybody seen anything along these lines?  There seems
to be quite a bit on Google about 11.10 and M2Crypto, but not finding a
resolution.

Thanks,
John

``

Nova development environment setup is complete.

Nova development uses virtualenv to track and manage Python dependencies
while in development and testing.

To activate the Nova virtualenv for the extent of your current shell
session you can run:

$ source .venv/bin/activate

Or, if you prefer, you can run commands in the virtualenv on a case by
case
basis by running:

$ tools/with_venv.sh 

Also, make test will automatically use the virtualenv.

ERROR

==
ERROR: 
--
Traceback (most recent call last):
  File
"/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/suite.py",
line 208, in run
self.setUp()
  File
"/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/suite.py",
line 291, in setUp
self.setupContext(ancestor)
  File
"/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/suite.py",
line 314, in setupContext
try_run(context, names)
  File
"/home/jdg/Projects/OpenStack/nova/.venv/local/lib/python2.7/site-packages/nose/util.py",
line 478, in try_run
return func()
  File "/home/jdg/Projects/OpenStack/nova/nova/tests/__init__.py", line 48,
in setup
from nova.tests import fake_flags
  File "/home/jdg/Projects/OpenStack/nova/nova/tests/fake_flags.py", line
28, in 
flags.DECLARE('auth_driver', 'nova.auth.manager')
  File "/home/jdg/Projects/OpenStack/nova/nova/flags.py", line 224, in
DECLARE
__import__(module_string, globals(), locals())
  File "/home/jdg/Projects/OpenStack/nova/nova/auth/manager.py", line 34,
in 
from nova import crypto
  File "/home/jdg/Projects/OpenStack/nova/nova/crypto.py", line 36, in

import M2Crypto
ImportError: No module named M2Crypto

--
Ran 0 tests in 0.002s

FAILED (errors=1)

jdg@grumpy ~/Projects/OpenStack/nova
 % cd /tmp

jdg@grumpy /tmp % python
Python 2.7.2+ (default, Oct  4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import M2Crypto

jdg@grumpy /tmp %
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


  1   2   >