We have submitted our spec just a few days ago while I have heared that we
should have our spec to be approved before 15/11/2014 if we want our cinder
driver merged in Kilo. Just few days left!
Having our cinder driver merged into Kilo is turely important for us, so I
would be very appreciate
I have read the related article in
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers, but I still
have a little confused about the cert test:
1. Should I run the the tempest (at https://github.com/openstack/tempest) in
our own 3rd party CI test environment? Our 3rd party CI have
When our CI run devstack, it occurs error when run image create mysql. Log
is pasted as following:
22186 2014-11-29 21:11:48.611 | ++ basename
/opt/stack/new/devstack/files/mysql.qcow2 .qcow2
22187 2014-11-29 21:11:48.623 | + image_name=mysql
22188 2014-11-29 21:11:48.624 | +
Hi Mike,
Sorry to delay so long. Now we have added a mapping in
cinder/volume/manager.pyhttps://review.openstack.org/#/c/133193/25/cinder/volume/manager.py
and add a file named
We have opened a bug for document of huawei storage driver, and have posted the
document at https://review.openstack.org/#/c/143926/.
Now I have two things not very clear:
1. When will be this document merged into Kilo? At the end of K-2 or will a
little earlier?
2. What should we do if we
Hi Mike,
I received a email named “All Cinder Drivers Must Have a Third Party CI By
March 19th 2015” and I feel confused about the “*real* storage backend”.
One of the requirements is: Run Tempest [5][6] volume tests against the
devstack environment that's hooked up to your *real* storage
Our CI get the following error when build devstack, begin from service ‘g-reg’
when uploading image:
is_service_enabled g-reg
2015-02-05 03:14:54.966 | + return 0
2015-02-05 03:14:54.968 | ++ keystone token-get
2015-02-05 03:14:54.968 | ++ grep ' id '
2015-02-05 03:14:54.969 | ++ get_field 2
Our CI failed when building devstack, the error is about “Unauthorized”.
Following is the segment of the devstacklog:
2015-02-12 11:16:14.639 | + is_service_enabled c-api
2015-02-12 11:16:14.646 | + return 0
2015-02-12 11:16:14.646 | + is_service_enabled tls-proxy
2015-02-12 11:16:14.646 | +
It still can not work.
My local.conf is:
[[post-config|\$CINDER_CONF]]
[DEFAULT]
enabled_backends=huawei_18000
[huawei_18000]
volume_driver=cinder.volume.drivers.huawei.HuaweiVolumeDriver
cinder_huawei_conf_file=/etc/cinder/cinder_huawei_conf.xml
And the resulted cinder.conf is:
[DEFAULT]
Hi Abhishek,
For the error in the first line:
“mkdir: cannot create directory `/logs': Permission denied”
and the error at the end:
“ln: failed to create symbolic link `/logs/screen/screen-key.log': No such file
or directory”
The stack user does not have the permission on “/” so it can not
Hi all,
* I have commit a bug and it is not yet merged. Now I want to commit
another bug but this bug is depends on the previousapp:ds:previous one which
have not been merged?
* So how should I do? Should I commit the latterapp:ds:latter bug
directly or wait the
Hi all,
I have commit a bug-fix patch and it have passed the Jenkins check, but in
Jenkins gate it failed for
gate-cinder-python27http://logs.openstack.org/65/143765/9/gate/gate-cinder-python27/2e7afd6/.
I have dig into the error log but can not see anything wrong in my patch code.
Review page
Mine in cinder failed too.
https://review.openstack.org/#/c/143765/
Please check it, thanks.
liu
新国刘
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Phone:
Fax:
Mobile:
Email:
地址：深圳市龙岗区坂田华为基地 邮编：518129
Huawei Technologies Co., Ltd.
Bantian, Longgang
devstack and it should work again.
Bob
From: liuxinguo [mailto:liuxin...@huawei.com]
Sent: 06 February 2015 03:08
To: OpenStack Development Mailing List (not for usage questions);
openstack-in...@lists.openstack.org
Cc: Zhangli (ISSP); Fanyaohong; Chenzongliang
Subject: [openstack-dev] [OpenStack-Infra
Hi,
In Kilo the cinder driver is requested to be merged before K-1, I want to ask
that in L does the driver will be requested to be merged before L-1?
Thanks and regards,
Liu
__
OpenStack Development Mailing List (not for
your problem).
Good luck!
Peter
From: liuxinguo [mailto:liuxin...@huawei.com]
Sent: February-12-15 6:57 AM
To:
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org;
openstack-in...@lists.openstack.orgmailto:openstack-in...@lists.openstack.org
Cc: Zhangli (ISSP); Fanyaohong
Our driver have been merged into Kilo before K-1 and have implemented many
features, so I think our driver is not a new driver.
For these drivers aleady merged in Kilo and if they want add some new features,
does they should be merged before L-1 too?
Thanks,
Liu
Yes, assume NEW drivers
Hi all,
I have seen that the blueprint of Enhance iSCSI multipath support for cinder
have been approved and target in
kilo-2https://launchpad.net/cinder/+milestone/kilo-2, I want to know that
will the blueprint of Enhance iSCSI volume multipath support for nova be
implemented in Kilo?
Any
Hi Mike,
Regarding the Huawei Volume CI:
As I am dealing with the CI process of Huawei, please modify the contact person
to liuxin...@huawei.commailto:liuxin...@huawei.com, so I won't miss
important announcements from you regarding the CI.
The CI of huawei 18000 ISCSI and huawei 18000 FC
Hi Mike,
I have seen the patch at https://review.openstack.org/#/c/165990/ saying that
huawei driver will be removed because “the maintainer does not have a CI
reporting to ensure their driver integration is successful”.
But in fact we really have a CI months ago and it is really reporting to
Hi Mike,
* Maybe I have a misunderstandapp:ds:misunderstand of the
warningapp:ds:warning you said that all drivers must have a CI. I have taken
that as if the Dorado and T driver did not have a CI then the Dorado and T
driver will be removed from the community individually.
If I can't
Hi Mike,
I think what we are talking is huawei-volume-ci, not huawei-ci. It is
huawei-volume-ci that is on behalf of huawei 18000 iSCSI and huawei 18000 FC
driver.
Regarding to only report failures when a patch really does break your
integration, I think huawei-volume-ci probaly should be
[mailto:walter.bor...@hp.com]
发送时间: 2015年3月20日 23:49
收件人: openstack-dev@lists.openstack.org
主题: Re: [openstack-dev] [cinder] May you reconsider about huawei driver?
On 03/19/2015 07:13 PM, liuxinguo wrote:
Hi Mike,
I have seen the patch at https://review.openstack.org/#/c/165990/ saying that
huawei
It is huawei-volume-ci that is on behalf of huawei 18000 iSCSI and huawei 18000
FC driver, not huawei-ci. I am sorry for these two ci names so similar.
And I think the point is: Does the requirement is really a stable CI, and if
one CI is not stable, can it make a exemption like NetApp FC
Hello Cinder team,
* Huawei Volume CI has been reporting since Decemberapp:ds:December
20 th 2014. Now it runs
* two tempest jobs for Huawei 18000 iSCSI driver and Huawei 18000 FC
driver.
* Considering that our drivers have been moved for the upstream, I have
added some
I request the same consideration for Huawei 18000 iSCSI driver and 18000 FC
driver. May I also add it to the meeting agenda?
· I promise Huawei Volume CI will become stable and reporting stably
before March 31. Our CI will be moved to a more better environment
tomorrowapp:ds:tomorrow
Hi Mike,
I have fixed the patch as your comments and have committed it at
https://review.openstack.org/#/c/152116/.
Would you please have a review at it, thanks!
Best regards,
Liu
__
OpenStack Development Mailing List (not
Recently I have commit a patch in
openstack-manuals/doc/config-reference/block-storage/drivers/huawei-storage-driver.xmlhttps://review.openstack.org/#/c/150761/8/doc/config-reference/block-storage/drivers/huawei-storage-driver.xml
contains the QoS configuration and the reviewers said that I
* I have seen that the module 'oslo.config' have changed to
'oslo_config' in Kilo but in Juno it is still 'oslo.config'.
I want my code work compatibly both for Juno and Kilo so I import this module
in this way:
try:
from oslo_config import cfg
except:
from oslo.config import cfg
in
python-cinderclient and see if you could produce a more meaningful message.
Cheers.
George
On 10/04/15 06:16 AM, liuxinguo wrote:
Hi,
When we create a volume in the horizon, there may occurrs some errors at the
driver
backend, and the in horizon we just see a error in the volume status.
So
questions)
抄送: Luozhen; Fanyaohong
主题: Re: [openstack-dev] [cinder] Is there any way to put the driver backend
error message to the horizon
Alex,
Any scratch of the solution you plan to propose?
On Mon, Apr 27, 2015 at 5:57 AM, liuxinguo
liuxin...@huawei.commailto:liuxin...@huawei.com wrote
Date: 04/06/2015 01:09 AM
Subject: Re: [openstack-dev] [cinder] Report status of Huawei Volume
CI from April 1
On 12:47 Sat 04 Apr , liuxinguo wrote:
Hello Cinder team,
· Huawei Volume CI has posted to about forty cinder
reviews from April 1 to now and will keep reporting
Hi Cinder team,
Since the 80 port or our log server have some issue to be accessed from the
public, we have changed the port from 80 to 8088.
* So if you opened a link like
http://182.138.104.27/huawei-18000-iscsi-dsvm-tempest-full/70, please change
the access port to 8088,
*
Hi Duncan,
For the 80 port of our log server is blocked by some reason, I have updated my
apache configuretion to use 8088 port.
Hence, please change to access our CI logs use 8088 port.
For example, when you access
http://182.138.104.27/huawei-18000-iscsi-dsvm-tempest-full/89, please change to
Hi Mike,
Please check this patch at Patch Set 3 our CI have newly posted result:
https://review.openstack.org/#/c/170770/
· We have changed the report link to 8088 port and it can be accessed
successfully, needn’t to manuallyapp:ds:manually change the port to 8088 any
more.
Thanks
Hello Cinder team,
· Huawei Volume CI has posted to about forty cinder reviews from April
1 to now and will keep reporting stably.
·
· It now runs 304 tests, passed 293 and skipped 11.
The following are links to the cinder reviews our CI has posted results to,
please check it:
Hi,
Many FC switchs have the function of virtual fabric and sometimes we need to
manage the virtual fabric like create zone, delete zone etc.
But it seems like that there is no virtual fabric support in our zonemanager.
So can we manage virtual fabric with zonemaneger, if not, how to manage
Hi,
Our CI can not connect to port 29418 of review.openstack.org recently, possibly
because the GFW filtered the access. Now we are processing this problem as soon
as we found it.
According to the decision of Cinder Meeting 2015-06-10:
June 15th proposed drivers for Liberty without passing code
: 2015年6月12日 17:09
收件人: OpenStack Development Mailing List (not for usage questions);
openstack-in...@lists.openstack.org
抄送: Luozhen
主题: Re: [OpenStack-Infra] [openstack-dev] Need help! Zuul can not connect to
port 29418 of review.openstack.org
On 12/06/15 17:04, liuxinguo wrote:
Hi,
Recentlyour
Hi Mike,
We have solved the problem of Huawei CI, and it is running and reporting stably
now. The logs is also ok to access.
Following are the very recently patchs it have been posted to:
https://review.openstack.org/180873
https://review.openstack.org/186312
Hi Mike,
We have solved the problem of Huawei CI, and it is running and reporting stably
now. The logs is ok to access.
The very recently patchs it have been posted to isi:
https://review.openstack.org/#/c/147726/
https://review.openstack.org/#/c/147738/
We will be very appreciate if you can
Infortrend driver and Netapp driver's failure about gate-cinder-python27
caused Jenkins -1 at patch https://review.openstack.org/#/c/201578/,
log link:
http://logs.openstack.org/78/201578/22/check/gate-cinder-python27/2212cdc/console.html
Engineers of Infortrend driver and Netapp driver please
Detach a volume when it's under migration, volume status is still in-use:
1. create vol-1
2. attach vol-1 to a vm
3. migrate vol-1
4. when vol-1 is under migration, detach vol-1
5. after vol-1 is detached, command cinder list show that the Status of
vol-1 is
whether these bps are OK for Liberty or there
is something I forgot to do and need to complete.
Thanks and best regards,
--
Liuxinguo
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
Hi,
I have saw the "manage_existing" interface in cinder/contrib/volume_manager.py
but can't find the responding cli command.
Is there any cli command for "manage_existing"? If not, who will call this api?
Thanks for any input!
Wilson Liu
Hi,
Why the permission of cinder.conf is set to 640 not 600? Can we set it to 600
instead of 640 and is there any problems if we change it?
Any input will be appreciate, thanks!
Wilson Liu
__
OpenStack Development Mailing
Hi,
In a.py we have a function:
def _change_file_mode(filepath):
utils.execute('chmod', '600', filepath, run_as_root=True)
In test_xxx.py, there is a testclass:
class DriverTestCase(test.TestCase):
def test_a(self)
...
Call a. _change_file_mode
...
def test_b(self)
...
Call
Hi,
'os-initialize_connection' is a important API for Cinder to complete the volume
attach operation,
but there is no record in Cinder(Blockstorage) API Document(1).
Also some developers want to find the description for the
'os-initialize_connection' API.
So should we add this API to the
Hi hemna:
When we attach a encrypted volume and then detach it, the device path created
when the volume is attached won't be cleanup.
This is probably due to nova and cinder not work coordinately when detach a
encrypted volume.
This will cause next volume attachment fails and also cause some
Hi xinyong,
I remembered that I have seen this error times ago in my CI.
Seems like nova doesn’t need noVNC before but now it needs noVNC to complete
the installation.
You need to clone noVNC into /opt/stack/new manually, or add noVNC project to
the $PROJECTS variable in file like:
...@gmail.com]
发送时间: 2016年2月23日 20:35
收件人: OpenStack Development Mailing List (not for usage questions)
抄送: OpenStack Infra; Luozhen
主题: Re: [OpenStack-Infra] [openstack-dev] [cinder] How to configure the third
party CI to be triggered only when jenkins +1
On Mon, Feb 22, 2016 at 7:32 PM, liuxinguo
Hi,
There is no need to trigger third party CI if a patch does not pass Jenkins
Verify.
I think there is a way to reach this but I'm not sure how.
So is there any reference or suggestion to configure the third party CI to be
triggered only when jenkins +1?
Thanks for any input!
Regards,
Development Mailing List (not for usage questions)
抄送: OpenStack Infra; Luozhen
主题: Re: [OpenStack-Infra] [openstack-dev] [cinder] How to configure the third
party CI to be triggered only when jenkins +1
On Mon, Feb 22, 2016 at 6:32 PM, liuxinguo
<liuxin...@huawei.com<mailto:liuxin...@huaw
Hi Cinder team,
We are going to implement storage-assisted volume migrate in our driver between
different backend storage array or even different array of different vendors.
This is really high-efficiency than the host-copy migration between different
array of different vendors.
To implement
evelopment Mailing List (not for usage questions)
抄送: Luozhen
主题: Re: [openstack-dev] [cinder] Does the OpenStack community(or Cinder team)
allow one driver to call another driver's public method?
* liuxinguo <liuxin...@huawei.com> wrote:
> Hi Cinder team,
>
> We are going to i
Hi cinder team,
When a volume's 'migration_status' is 'migrating', we've no idea whether this
volume is able to attach to a server to use:
IF the migration way is host-copy, it is not attachable to use, but if the
migration is handling by driver, some driver's implementation can make it
56 matches
Mail list logo
