003.png@01D028F0.E93AA0A0]
Ramy
From: Eli Qiao [mailto:ta...@linux.vnet.ibm.com]
Sent: Sunday, January 04, 2015 9:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] how to delete a volume which is in
error_deleting state
在 2015年01月05日 13:10,
Before getting into the database, try the cinder reset-state command. It’s
available in the horizon ui starting in Juno.
Otherwise use the command line [1].
Ramy
[1] http://docs.openstack.org/cli-reference/content/cinderclient_commands.html
From: Punith S [mailto:punit...@cloudbyte.com]
Sent: S
I agree with John. Option 4: one ci account for all drivers.
The only valid reasons I'm aware of to use multiple accounts for a single
vendor is if the hardware required to run the tests are not accessible from a
'central' ci system, or if the ci systems are managed by different teams.
Otherwis
odules on found error.
is there a way to get this work ?
thanks in advance
On Mon, Dec 22, 2014 at 11:10 PM, Asselin, Ramy
mailto:ramy.asse...@hp.com>> wrote:
Eduard,
A few items you can try:
1. Double-check that the job is in Jenkins
a. If not, then that’s the issue
2.
my
From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Sunday, December 21, 2014 11:01 PM
To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need help setting
up CI
Thanks Ramy,
Unfortuna
ut.yaml#L20
[2] https://github.com/openstack-dev/sandbox
From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Friday, December 19, 2014 3:36 AM
To: Asselin, Ramy
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPart
Eduard
On Wed, Dec 17, 2014 at 3:37 AM, Asselin, Ramy
mailto:ramy.asse...@hp.com>> wrote:
Manually running the script requires a few environment settings. Take a look at
the README here:
https://github.com/openstack-infra/devstack-gate
Regarding cinder, I’m using this repo to run our cinde
In this case, I see the mentoring to be more like “office hours”, which can be
done by ci operators & other volunteers spread across time zones. I think this
is a great idea.
Ramy
From: Kurt Taylor [mailto:kurt.r.tay...@gmail.com]
Sent: Tuesday, December 16, 2014 9:39 AM
To: Stefano Maffulli
Cc
#openstack-cinder. (irc# asselin)
Ramy
From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Tuesday, December 16, 2014 12:41 AM
To: Bailey, Darragh
Cc: OpenStack Development Mailing List (not for usage questions); OpenStack
Subject: Re: [openstack-dev] [OpenStack-Infra] [ThirdPartyCI] Need
Hi,
I tried this a while back and it does not work [1]. Last I looked, there was no
config option, and nothing in the code to allow it. I’m not aware of any
patches that change that.
I got mine working by getting port 29418 opened for review.openstack.org ip
address.
Ramy
[1] http://lists.ope
Looks good to me using this query: http://paste.openstack.org/show/117844/
Generated via: https://review.openstack.org/#/c/125716/
Ramy
-Original Message-
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Thursday, October 02, 2014 10:10 AM
To: OpenStack Development Mailing Li
Not sure if https://review.openstack.org/#/c/118619/ is necessary.
See if this solves your issue [1], simple update to your devstack
localrc/local.conf to create the type keys. It is merged to master.
Otherwise, consider creating a cinder backend file[1].
Ramy
[1] http://lists.openstack.org/pipe
-1 from me (non-cinder core)
It very nice to see you're making progress. I, personally, was very confused
about voting.
Here's my understanding: "Voting": it is the ability to provide an official +1
-1 vote in the gerrit system.
I don't see a "stable history" [1]. Before requesting voting, you
, Asselin, Ramy
mailto:ramy.asse...@hp.com>> wrote:
Many of us are still working on setting up and testing 3rd party ci for cinder
drivers.
None of them currently have gerrit +1/-1 voting, but I heard there’s a plan to
“disable” those that are “not working” post-J3 (Please correct m
Many of us are still working on setting up and testing 3rd party ci for cinder
drivers.
None of them currently have gerrit +1/-1 voting, but I heard there's a plan to
"disable" those that are "not working" post-J3 (Please correct me if I
misunderstood).
However, Post-J3 is a great time to work
with name * could not be found.
On Fri, Aug 15, 2014 at 10:29 AM, Asselin, Ramy
mailto:ramy.asse...@hp.com>> wrote:
John,
We’re running master on every patch set. What needs to be set in localrc?
Actually, I think I know what could be the issue (still need to confirm)
1. devstac
x27;t have to create the volume type prior to running tempest
tests?
Andrew Kerr
OpenStack QA
Cloud Solutions Group
NetApp
On 8/14/14, 5:23 PM, "Martin, Kurt Frederick (ESSN Storage MSDU)"
mailto:kurt.f.mar...@hp.com>> wrote:
>They need to be manually added.
>
>--
, for example, default_volume_type=bronze.
This allows for a volume to be created when a volume type is not selected, the
default 'None' type. This feature has been available for some time in cinder
but recently enabled in devstack.
~Kurt
-Original Message-
From: Asselin, Ramy
Hi,
Does anyone know how to configure cinder ci tests to not have these errors?
12:32:11 *** Not Whitelisted *** 2014-08-14 12:23:56.179 18021 ERROR
cinder.volume.volume_types [req-c9ec92ab-132b-4167-a467-15bd213659e8
bd1f54a867ce47acb4097cd94149efa0 d15dcf4cb3c7495389799ec849e9036d - - -]
Def
e enough, but such build cannot really report on gerrit.
David Pineau
gerrit: Joachim
IRC#freenode: joa
2014-08-13 2:28 GMT+02:00 Asselin, Ramy :
> I forked jaypipe’s repos & working on extending it to support
> nodepool, log server, etc.
>
> Still WIP but generally working.
>
&
I forked jaypipe’s repos & working on extending it to support nodepool, log
server, etc.
Still WIP but generally working.
If you need help, ping me on IRC #openstack-cinder (asselin)
Ramy
From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com]
Sent: Monday, August 11, 2014 11:33 P
Hi Nikesh,
You need to set the enabled_backends in the local.conf file.
e.g.
[[post-config|$CINDER_CONF]]
[DEFAULT]
enabled_backends=hp_msa_driver
[hp_msa_driver]
volume_driver = cinder.volume.drivers.san.hp.hp_msa_fc.HPMSAFCDriver
…
Ramy
From: Nikesh Kumar Mahalka [mailto:nikeshmaha...@vedams.
e-
From: Kerr, Andrew [mailto:andrew.k...@netapp.com]
Sent: Monday, July 07, 2014 7:31 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] 3rd party ci names for use by official
cinder mandated tests
On 7/2/14, 11:00 AM, "Anita Kuno" wrote:
3rd party ci names is currently becoming a bit controversial for what we're
trying to do in cinder: https://review.openstack.org/#/c/101013/
The motivation for the above change is to aid developers understand what the
3rd party ci systems are testing in order to avoid confusion.
The goal is to ai
Anita,
This line [1] is effectively a sub-set of tempest-dsm-full, and what we're
currently running manually now. I far as I understood, this is the current
minimum. The exact sub-set (or full set, or if additional tests are allowed) is
still under discussion.
I created a WIP reference patch
Not sure if these are “minimalist” but at least they setup automagically, so
you don’t need to do it from scratch:
You can check out these repos which automate the 3rd party ci setup:
Jay Pipe’s solution:
https://github.com/jaypipes/os-ext-testing
https://github.com/jaypipes/os-ext-testing-data
] Third-Party CI Issue: direct access to
review.openstack.org port 29418 required
Hi Asselin,
Do you had problems with other ports? Is it need to have outbound access to
other ports?
Erlon
On Mon, Jun 9, 2014 at 2:21 PM, Asselin, Ramy
mailto:ramy.asse...@hp.com>> wrote:
All,
I’ve been w
All,
I've been working on setting up our Cinder 3rd party CI setup.
I ran into an issue where Zuul requires direct access to review.openstack.org
port 29418, which is currently blocked in my environment. It should be
unblocked around the end of June.
Since this will likely affect other vendors,
Based on the discussion I'd like to propose these options:
1. Cinder-certified driver - This is an attempt to move the "certification" to
the project level.
2. CI-tested driver - This is probably the most accurate, at least for what
we're trying to achieve for Juno: Continuous Integration of Vend
I agree 'unmanage' should try to 'undo' as much as possible.
In this way, 'manage' the 2nd time will also work with the exact same command
arguments as it did the first time.
Ramy
From: Deepak Shetty [mailto:dpkshe...@gmail.com]
Sent: Thursday, April 10, 2014 1:03 AM
To: OpenStack Development Mai
Hi Shlomi,
Another solution to consider is to create a subclass per transport (iSCSI,
iSER) which reference the same shared common code.
This is the solution used for the 3PAR iSCSI & FC transports. See these for
reference:
cinder/volume/drivers/san/hp/hp_3par_common.py
cinder/volume/drivers/san
Jeremy,
Thanks for the clarification.
I found an alternative workaround that works for me and restricts the use of
the openstack pypi mirror to only be used when running tox:
1. Add PyPi mirror to tox.ini's [tox] entry:
+indexserver =
+default = http://pypi.openstack.org/openstack
e.g.
Thanks Ben! This worked for me too!
The pip.conf file wasn’t there. I created it (as root) and added the 2 lines
you suggested.
I can now run Tox without running into pypi timeout / dependency issues.
Ramy
From: Ben Nemec [mailto:openst...@nemebean.com]
Sent: Thursday, February 13, 2014 8:56 A
101 - 133 of 133 matches
Mail list logo
