Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting up CI

Hi Eduard, Can you put the logs or details for below comment: it seems that sometimes Zuul gets stuck (sometimes in Looking for lost > builds, sometimes doing nothing) and it misses notifications. I guess, we too have been facing the same issue with Zuul. Regards, Amit *CloudByte Inc.*

Re: [openstack-dev] 答复: [devstack] Opensatck installation issue.

Is this related to the version of Ubuntu being used ? Its 12.04 as per the email. Regards, Amit *CloudByte Inc.* On Mon, Jan 12, 2015 at 3:55 PM, Abhishek Shrivastava < abhis...@cloudbyte.com> wrote: > I tried that also but still the error is same. > > On Mon, Jan 12

Re: [openstack-dev] Problem installing devstack

Can you check the /opt/stack/requirements folder & check if thats updated (git status, git log) after doing unstack & stack. One of the *-requirements.txt has the entry which makes all the projects to fail. We had removed the /opt/stack/requirements project & then did a unstack & stack. Regards

Re: [openstack-dev] [cinder] [driver] DB operations

pdate, but I don't know if that is possible. > > > > Duncan Thomas > > On Dec 19, 2014 6:43 PM, "Amit Das" wrote: > > > > > Thanks Duncan. > > > Do you mean hepler methods in the specific driver class? > > > On 19 Dec 2014 14:51, &qu

Re: [openstack-dev] [cinder] [driver] DB operations

d > do it via a defined interface that limits what they can do to a sane set of > operations. I'd still prefer that they didn't need extra access beyond the > model update, but I don't know if that is possible. > > Duncan Thomas > On Dec 19, 2014 6:43 PM, "Amit

Re: [openstack-dev] [cinder] [driver] DB operations

ump and db call would be > better than accessing it directly from the driver. > > Duncan Thomas > On Dec 18, 2014 11:41 PM, "Amit Das" wrote: > >> Hi Stackers, >> >> I have been developing a Cinder driver for CloudByte storage and have >> come

[openstack-dev] [cinder] [driver] DB operations

Hi Stackers, I have been developing a Cinder driver for CloudByte storage and have come across some scenarios where the driver needs to do create, read & update operations on cinder database (volume_admin_metadata table). This is required to establish a mapping between OpenStack IDs with the backe

Re: [openstack-dev] [Horizon] [UX] Curvature interactive virtual network design

+1 after looking at the videos. Regards, Amit *CloudByte Inc.* On Tue, Dec 16, 2014 at 11:43 PM, Liz Blanchard wrote: > > > On Nov 7, 2014, at 11:16 AM, John Davidge (jodavidg) > wrote: > > As discussed in the Horizon contributor meet up, here at Cisco we’re > inte

Re: [openstack-dev] #PERSONAL# : Git checkout command for Blueprints submission

Hi, It is "git checkout -b bp/" Regards, Amit *CloudByte Inc.* On Wed, Dec 17, 2014 at 10:23 AM, Swati Shukla1 wrote: > > > Hi All, > > Generally, for bug submissions, we use ""git checkout -b bug/"" > > What is the similar 'git checkout' command for blueprints submis

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Hey Eduard, We posted our driver cert result by creating a new bugzilla ticket & tagging that as driver-cert. https://bugs.launchpad.net/cinder/+bug/1380126 Regards, Amit *CloudByte Inc.* On Thu, Oct 30, 2014 at 5:55 PM, Eduard Matei < eduard.ma...@cloudfounders.co

Re: [openstack-dev] [Neutron][Architecture]Suggestions for the third vendors' plugin and driver

+1 > I don't think it will be seen as punitive. Vendors can write their plugins > or drivers when a deal occurs and they do not need to submit code to > community and wait for approving. Being a third party vendor, i do not think this is punitive. OpenStack has already established through proces

Re: [openstack-dev] [devstack] [cinder] [driver] Not able to create volume on a 3rd party driver backend

stack trace. */opt/stack/cinder/cinder/scheduler/filter_scheduler.py -> _populate_retry* However, i am not sure if this is a bug or an issue of missing configuration. Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Tue, Sep 16, 2014 at 1:34 PM, Amit Das wrote: > Hi Al

[openstack-dev] [devstack] [cinder] [driver] Not able to create volume on a 3rd party driver backend

Hi All, While trying to create a volume using my cinder driver (on devstack), i get below issue w.r.t num_attempts. Am i missing any configuration here ? ^[[01;31m2014-09-16 13:20:37.837 TRACE oslo.messaging.rpc.dispatcher ^[[01;35m^[[00m File "/opt/stack/cinder/cinder/scheduler/filter_schedule

[openstack-dev] [Cinder] [Devstack] - Create Volume is called in an infinite loop

Hi All, I have been running tempest tests on my cinder driver for about a month now. However, since last week i see the create volume logic was attempted thrice by the scheduler after a failure during volume creation. However, i would like the scheduler not to attempt after a failure in volume c

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Thanks. I have done that. Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Mon, Sep 8, 2014 at 9:37 AM, Mike Perez wrote: > On 17:18 Sun 07 Sep , Amit Das wrote: > > I had submitted the "CloudByte" driver code during juno and currently > > gr

Re: [openstack-dev] [cinder] Cinder plans for kilo: attention new driver authors!

Hi, Thanks for clarification w.r.t cinder drivers. I had submitted the "CloudByte" driver code during juno and currently grappling with various aspects of setting up the CI for the same. It also requires a copy of tempest logs which also is a in progress item. Will above be automatically eligible

Re: [openstack-dev] how to provide tests environments for python things that require C extensions

I too agree this can be useful beyond openstack. It will great if one of you (experts) can explain in more details how the python virtual environment is heavyweight than docker containers. I am just a user of devstack without the nitty gritty details of its inner workings. However, I can say that

Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd party driver as default

comment (or remove) the default_volume_type > line, unless you plan to create that volume type after the services come > up. > > Andrew Kerr > OpenStack QA > Cloud Solutions Group > NetApp > > > From: Amit Das > Reply-To: "OpenStack Development Mailing List (n

Re: [openstack-dev] [Devstack] [Cinder] Registering 3rd party driver as default

With further debugging, i find that none of the configuration options present in /etc/cinder/cinder.conf are getting applied. Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Thu, Aug 14, 2014 at 11:40 AM, Amit Das wrote: > Hi folks, > > I have been trying to run d

[openstack-dev] [Devstack] [Cinder] Registering 3rd party driver as default

Hi folks, I have been trying to run devstack with my cinder driver as the default volume_driver but with no luck. Devstack seems to register the lvm driver as the default always. I have tried below approaches: 1. directly modifying the /etc/cinder/cinder.conf file 2. creating a driver fil

Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems

Hi John, I guess this is w.r.t 3rd party cinder drivers. I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the "driver cert test results" i.e. tempest tests from devstack in our environment & CI setup would be my next step. Regards, Amit

Re: [openstack-dev] [Jenkins] [Cinder] InvocationError in gate-cinder-python26 & python27

Perhaps Jenkins can display a better message to start with. Being new to openstack, i had no clue on what was happening. However, the fix was simple once understood. The current message made me to think something was wrong with jenkins environment setup. Regards, Amit *CloudByte Inc.*

Re: [openstack-dev] [Jenkins] [Cinder] InvocationError in gate-cinder-python26 & python27

Thanks a lot. The recommendations worked fine. Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Fri, Jul 4, 2014 at 3:34 PM, Yuriy Taraday wrote: > On Fri, Jul 4, 2014 at 12:57 PM, Amit Das wrote: > >> Hi All, >> >> I can see a lot of cinder gerrit

Re: [openstack-dev] [Jenkins] [Cinder] InvocationError in gate-cinder-python26 & python27

ster & rebased that to my branch before doing a gerrit review. Am i missing any steps ? Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Mon, Jun 30, 2014 at 12:17 PM, Steve Kowalik wrote: > On 30/06/14 16:37, Amit Das wrote: > > I have been facing below issues

[openstack-dev] [Jenkins] [Cinder] InvocationError in gate-cinder-python26 & python27

Hi Stackers, I have been facing below issues at gate-cinder-python26 & gate-cinder-python27 after uploading my patch. I assume this to be an infrastructure issue than an issue with my patch. Can someone please confirm ? . 2014-06-30 05:41:57.704 | check_uptodate.sh: cinder.conf.sample is not

Re: [openstack-dev] [cinder][volume/manager.py] volume driver mapping

This seems cool. Does it mean the storage vendors write their new drivers & just map it from cinder.conf ? Does it involve any changes to devstack as well ? Regards, Amit *CloudByte Inc.* On Wed, Jun 25, 2014 at 7:22 PM, Duncan Thomas wrote: > That's easy; you don

Re: [openstack-dev] [Cinder][Driver] Delete snapshot

yte.com/> On Thu, Jun 19, 2014 at 9:16 PM, John Griffith wrote: > > > > On Tue, Jun 17, 2014 at 10:50 PM, Amit Das wrote: > >> Hi Stackers, >> >> I have been implementing a Cinder driver for our storage solution & >> facing issues with below

[openstack-dev] [Cinder][Driver] Delete snapshot

Hi Stackers, I have been implementing a Cinder driver for our storage solution & facing issues with below scenario. Scenario - When a user/admin tries to delete a snapshot that has associated clone(s), an error message/log should be shown to the user stating that '*There are clones associated to

Re: [openstack-dev] Proposal to support new Cinder driver for CloudByte's Elastistor

am thinks. > No promises though that your code will make it in, there are a number of > things already in process that will take priority in terms of review time > etc. > > Thanks, > John > > > On Tue, Aug 13, 2013 at 8:42 AM, Amit Das wrote: > >>

Re: [openstack-dev] Proposal to support new Cinder driver for CloudByte's Elastistor

Thanks a lot... This should give us a head start. Regards, Amit *CloudByte Inc.* <http://www.cloudbyte.com/> On Tue, Aug 13, 2013 at 5:14 PM, Thierry Carrez wrote: > Amit Das wrote: > > We have implemented a CINDER driver for our QoS aware storage solution > >

[openstack-dev] Proposal to support new Cinder driver for CloudByte's Elastistor

Hi Team, We have implemented a CINDER driver for our QoS aware storage solution (CloudByte Elastistor). We would like to integrate this driver code with the next version of OpenStack (Havana). Please let us know the approval processes to be followed for this new driver support. Regards, Amit *C