Re: [openstack-dev] [nova]resize

[Tian, Shuangtai]

Agree with you now

-Original Message-
From: fdsafdsafd [mailto:jaze...@163.com] 
Sent: Thursday, July 24, 2014 5:26 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova]resize


No.
before L5156, we convert it from qcow2 to qcow2, in which it strips backing 
file.
I think here, we should wirte like this:
 
if info['type'] == 'qcow2' and info['backing_file']:
       if shared_storage:
             utils.execute('cp', from_path, img_path)
       else:
 tmp_path = from_path + "_rbase"
         # merge backing file
         utils.execute('qemu-img', 'convert', '-f', 'qcow2',
                              '-O', 'qcow2', from_path, tmp_path)
            libvirt_utils.copy_image(tmp_path, img_path, host=dest)
            utils.execute('rm', '-f', tmp_path)
else:  # raw or qcow2 with no backing file
         libvirt_utils.copy_image(from_path, img_path, host=dest)



At 2014-07-24 05:02:39, "Tian, Shuangtai"  wrote:
 










whether we already use like that ?

https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L5156

 

From: fdsafdsafd [mailto:jaze...@163.com]


Sent: Thursday, July 24, 2014 4:30 PM

To: openstack-dev@lists.openstack.org

Subject: [openstack-dev] [nova]resize

 





In resize, we convert the disk and drop peel backing file, should we judge 
whether we are in shared_storage? If we are in shared storage, for example, 




nfs, then we can use the image in _base to be the backing file. And the time 
cost to resize will be faster.




 




The processing in line 5132




https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py




 




 




Thanks



 



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova]resize

[Tian, Shuangtai]

whether we already use like that ?
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L5156

From: fdsafdsafd [mailto:jaze...@163.com]
Sent: Thursday, July 24, 2014 4:30 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova]resize

In resize, we convert the disk and drop peel backing file, should we judge 
whether we are in shared_storage? If we are in shared storage, for example,
nfs, then we can use the image in _base to be the backing file. And the time 
cost to resize will be faster.

The processing in line 5132
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py


Thanks

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core

[Tian, Shuangtai]

+1

-Original Message-
From: Michael Still [mailto:mi...@stillhq.com] 
Sent: Saturday, June 14, 2014 6:41 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core

Greetings,

I would like to nominate Ken'ichi Ohmichi for the nova-core team.

Ken'ichi has been involved with nova for a long time now.  His reviews on API 
changes are excellent, and he's been part of the team that has driven the new 
API work we've seen in recent cycles forward. Ken'ichi has also been reviewing 
other parts of the code base, and I think his reviews are detailed and helpful.

Please respond with +1s or any concerns.

References:

  
https://review.openstack.org/#/q/owner:ken1ohmichi%2540gmail.com+status:open,n,z

  https://review.openstack.org/#/q/reviewer:ken1ohmichi%2540gmail.com,n,z

  http://www.stackalytics.com/?module=nova-group&user_id=oomichi

As a reminder, we use the voting process outlined at 
https://wiki.openstack.org/wiki/Nova/CoreTeam to add members to our core team.

Thanks,
Michael

--
Rackspace Australia

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Xen and Libvirt.

[Tian, Shuangtai]

Hi，
   Does anyone use the latest libvirt + xen +openstack ? In my ubuntu 
environment, It can not create VM , Because the blktap2 does not work.

-Original Message-
From: Daniel P. Berrange [mailto:berra...@redhat.com] 
Sent: Tuesday, May 27, 2014 5:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Xen and Libvirt.

On Mon, May 26, 2014 at 09:45:07AM -0400, Alvin Starr wrote:
> 
> What is the status of Xen and libvirt under Openstack?
> I noticed bits of discussions about deprecating the interface but I 
> did not see any clear answers.

There is *no* intention to deprecated it. It was merely marked as being in Tier 
3 support state, primarily due to lack of any automated testing.
The lack of CI testing is being addressed, hopefully to be up & running before 
end of Juno.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] can someone help me : cannot create VM via libvirt+xen

[Tian, Shuangtai]

vailable
libxl: error: libxl_device.c:289:libxl__device_disk_set_backend: no suitable 
backend for disk sda
libxl: debug: libxl_event.c:1739:libxl__ao_complete: ao 0x7f4a380020c0: 
complete, rc=-3
libxl: debug: libxl_create.c:1370:do_domain_create: ao 0x7f4a380020c0: 
inprogress: poller=0x7f4a38000ac0, flags=ic
libxl: debug: libxl_event.c:1711:libxl__ao__destroy: ao 0x7f4a380020c0: destroy


Best regards,
Tian, Shuangtai

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] FFE Request: Adds PCI support for the V3 API （just one patch in novaclient）

[Tian, Shuangtai]

Hi，

I would like to make a request for FFE for one patch in novaclient for PCI V3 
API : https://review.openstack.org/#/c/75324/
Though the V3 API will not release in Icehouse but all the PCI patches for V3 
API have been merged, and this is the last for V3,
I think some people may use the V3 and the PCI passthrough. Hope all the 
function can be used in the V3 in Icehouse.
This patch got one +2 from Kevin L. Mitchell but I updated it because of the 
comments.

The PCI patches in V3(merged):
Addressed by: https://review.openstack.org/51135
Extends V3 servers api for pci support
Addressed by: https://review.openstack.org/52376
Extends V3 os-hypervisor api for pci support
Addressed by: https://review.openstack.org/52377
Add V3 api for pci support

BTW the PCI Patches in V2 will defer to Juno.
The Blueprint https://blueprints.launchpad.net/nova/+spec/pci-api-support

Best regards,
Tian, Shuangtai

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [oslo] can't set rules in the common policy

[Tian, Shuangtai]

Hi, Stackers

   When I init a Enforcer class with rules, I find the rules will rewrite by 
configure policy rules,  because the policy file is modified ,
the load rules always try to load the rules from the cache or configure file 
when checks the policy in the enforce function, and
force to rewrite the rules always using the configure policy.
I think this problem also exists when we use the set_rules to set rules before 
we use the enforce to load rules in the first time.
Anyone also meets this problem, or if the way I used is wrong? I proposed a 
patch to this problem : https://review.openstack.org/#/c/72848/


Best regards,
Tian, Shuangtai

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because of a nova patch

[Tian, Shuangtai]

I have posted a patch in the ceilometer to temporary solve the problem, 
https://review.openstack.org/#/c/70073/
Similar problem ,I think we should rewrite the test with faking the object 
layer instead of faking db layer.

-Original Message-
From: Joe Gordon [mailto:joe.gord...@gmail.com] 
Sent: Thursday, January 30, 2014 10:34 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [nova][ceilometer] ceilometer unit tests broke because 
of a nova patch

While looking at gate failures trying to improve our classification rate I 
stumbled across this:

http://logs.openstack.org/50/67850/5/gate/gate-ceilometer-python26/8fd55b6/console.html

It appears that ceilometer is pulling in the nova repo
(http://git.openstack.org/cgit/openstack/ceilometer/tree/test-requirements.txt#n8)
and running tests against non-contractual (private) APIs. This means that nova 
will occasionally break ceilometer unit tests.


The nova patch that broke ceilometer is:

commit 4f1318585c38d55c097ee2e03b57b65157048a2f
Merge: 5798058 50c9055
Author: Jenkins 
Date:   Thu Jan 30 01:31:31 2014 +

Merge "Adds ephemeral_key_uuid field to instance"


commit 50c9055c8ef22b59379acadd1a1efdcbc6be12b3
Author: Dan Genin 
Date:   Thu Jan 2 09:44:24 2014 -0500

Adds ephemeral_key_uuid field to instance

Patch adds a field to instance for storing the uuid of
the key used to encrypt instance's ephemeral storage.

Implements: blueprint encrypt-ephemeral-storage
Change-Id: Id5b1e272d4461875bb231839e4714d3ed0899d3f


Going forward, how can we prevent issues like this from reoccurring in the gate?



best,
Joe Gordon

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] Help to approve the pci-api-support blueprint

[Tian, Shuangtai]

Hi All

Can someone help to approve the pci-api-support bp 
https://blueprints.launchpad.net/nova/+spec/pci-api-support?
That will need to be done before we start merging code, and the patches are 
ready.
Thanks for help!

Best regards,
Tian, Shuangtai

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] Request for review ( PCI passthrough API)

[Tian, Shuangtai]

Hi Chris,
I rebased the patches again. And added realistic data to tests.
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:pci-api-support,n,z
Thanks!

From: Christopher Yeoh [mailto:cbky...@gmail.com]
Sent: Monday, November 11, 2013 4:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Request for review ( PCI passthrough API)

Hi Tian,
A couple of things that came out of the V3 API discussions which are relevant 
to your patches:
- In Icehouse we want to merge the V3 API version of patches either before the 
V2 one or in the same patch. With
  yours split its probably easiest to do that by setting the V2 patches 
dependent on the V3 ones.
- I've added this previously in the review comments for some of the patches 
that we also would
  like a specification written up for the REST API which you are adding (not 
just what data is returned,
  but the methods (GET/POST/PUT/DELETE), URLs, data format in and data format 
out).

  At this point in time in the blueprint is probably best approach with a 
summary in the commit message
  for the portion which is added (since the API changes are split up - which is 
good)
Regards,

Chris


On Mon, Nov 11, 2013 at 7:23 PM, Tian, Shuangtai 
mailto:shuangtai.t...@intel.com>> wrote:
Hi,All

PCI pass-through support has been added to nova. Now we are doing the apis to 
support PCI pass-through.
Pls review the code 
:https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:pci-api-support,n,z

Thank you very much.

Best regards,
Tian, Shuangtai


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Request for review ( PCI passthrough API)

[Tian, Shuangtai]

Hi，Chris
I will rebase the patches,and  update the bp.
Thanks !

From: Christopher Yeoh [mailto:cbky...@gmail.com]
Sent: Monday, November 11, 2013 4:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Request for review ( PCI passthrough API)

Hi Tian,
A couple of things that came out of the V3 API discussions which are relevant 
to your patches:
- In Icehouse we want to merge the V3 API version of patches either before the 
V2 one or in the same patch. With
  yours split its probably easiest to do that by setting the V2 patches 
dependent on the V3 ones.
- I've added this previously in the review comments for some of the patches 
that we also would
  like a specification written up for the REST API which you are adding (not 
just what data is returned,
  but the methods (GET/POST/PUT/DELETE), URLs, data format in and data format 
out).

  At this point in time in the blueprint is probably best approach with a 
summary in the commit message
  for the portion which is added (since the API changes are split up - which is 
good)
Regards,

Chris


On Mon, Nov 11, 2013 at 7:23 PM, Tian, Shuangtai 
mailto:shuangtai.t...@intel.com>> wrote:
Hi,All

PCI pass-through support has been added to nova. Now we are doing the apis to 
support PCI pass-through.
Pls review the code 
:https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:pci-api-support,n,z

Thank you very much.

Best regards,
Tian, Shuangtai


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Request for review ( PCI passthrough API)

[Tian, Shuangtai]

Hi,All

PCI pass-through support has been added to nova. Now we are doing the apis to 
support PCI pass-through.
Pls review the code 
:https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:pci-api-support,n,z

Thank you very much.

Best regards,
Tian, Shuangtai

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-manuals] Need some help when "mvn clean generate-sources"

[Tian, Shuangtai]

Hi guys
When do some build on openstack-manuals project,there is error when bulid 
'openstack-compute-admin' ,but others (such as openstack-user, docbkx-example 
e.g) are all SUCCESS.
Anybody know why ?
Thanks!


Cd openstack-manuals/doc/src/docbkx/openstack-compute-admin
mvn clean generate-sources

[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building OpenStack Administration Guides 1.0.0-SNAPSHOT
[INFO] 
Downloading: 
http://maven.research.rackspacecloud.com/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.3/maven-clean-plugin-2.3.pom
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.3/maven-clean-plugin-2.3.pom
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2:17.516s
[INFO] Finished at: Mon Aug 19 10:56:57 CST 2013
[INFO] Final Memory: 8M/245M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.3 or one of its 
dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-clean-plugin:jar:2.3: Could not transfer 
artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.3 from/to 
rackspace-research 
(http://maven.research.rackspacecloud.com/content/groups/public/): Connection 
to http://maven.research.rackspacecloud.com refused: Connection timed out -> 
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-manuals] Need some help when "mvn clean generate-sources"

[Tian, Shuangtai]

Hi guys
When do some build on openstack-manuals project,there is error when bulid 
'openstack-compute-admin' ,but others (such as openstack-user, docbkx-example 
e.g) are all SUCCESS.
Anybody know why ?
Thanks!


Cd openstack-manuals/doc/src/docbkx/openstack-compute-admin
mvn clean generate-sources

[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building OpenStack Administration Guides 1.0.0-SNAPSHOT
[INFO] 
Downloading: 
http://maven.research.rackspacecloud.com/content/groups/public/org/apache/maven/plugins/maven-clean-plugin/2.3/maven-clean-plugin-2.3.pom
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.3/maven-clean-plugin-2.3.pom
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2:17.516s
[INFO] Finished at: Mon Aug 19 10:56:57 CST 2013
[INFO] Final Memory: 8M/245M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.3 or one of its 
dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-clean-plugin:jar:2.3: Could not transfer 
artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.3 from/to 
rackspace-research 
(http://maven.research.rackspacecloud.com/content/groups/public/): Connection 
to http://maven.research.rackspacecloud.com refused: Connection timed out -> 
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException


Best regards,
Tian, Shuangtai (Kenneth)

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] generate_sample.sh

[Tian, Shuangtai]

Hi, I do not know why , Mybe the patch https://review.openstack.org/#/c/38418/ 
have someone else to approve ,
You can try this  ./tools/config/generate_sample.sh -b /opt/stack/nova   -o 
./etc/nova ,that’s ok to me.

From: Haomai Wang [mailto:hao...@unitedstack.com]
Sent: Friday, July 26, 2013 3:18 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [nova] generate_sample.sh

2013-7-26，3:11 pm，"Tian, Shuangtai" 
mailto:shuangtai.t...@intel.com>> Wrote:


Recently，generate_sample.sh had been changed . look the help.
For example, try run "./tools/config/generate_sample.sh -b ./ -p nova -o 
./etc/nova" and commit the changes in nova.conf.sample
I don't know why I can't run command as expected see below.

$ ./tools/config/generate_sample.sh -b ./ -p nova -o ./etc/nova
generate_sample.sh: missing project base directory
Try `generate_sample.sh --help' for more information.



From: Haomai Wang [mailto:hao...@unitedstack.com<http://unitedstack.com>]
Sent: Friday, July 26, 2013 2:50 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [nova] generate_sample.sh



2013-7-26，1:58 pm，Gary Kotton mailto:gkot...@vmware.com>> 
Wrote：



Hi,
Over the last few days I have been battling with this script (I am only human). 
Recently there was a nice change that removed the number of entries which helps 
with the merges. One thing that I have encountered over the last 2 days is that 
the pep8 passes with my environment and fails with the gaiting. Would it be 
possible that Jenkins updates the nova.sample.conf in a similar fashion to the 
way that is done with the translations?
+1, I encountered the same problem and I think the task running 
gererate_sample.sh should be given to Jenkins



Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Best regards,
Haomai Wang, UnitedStack Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Best regards,
Haomai Wang, UnitedStack Inc.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] generate_sample.sh

[Tian, Shuangtai]

Recently，generate_sample.sh had been changed . look the help.
For example, try run "./tools/config/generate_sample.sh -b ./ -p nova -o 
./etc/nova" and commit the changes in nova.conf.sample

From: Haomai Wang [mailto:hao...@unitedstack.com]
Sent: Friday, July 26, 2013 2:50 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [nova] generate_sample.sh



2013-7-26，1:58 pm，Gary Kotton mailto:gkot...@vmware.com>> 
Wrote：


Hi,
Over the last few days I have been battling with this script (I am only human). 
Recently there was a nice change that removed the number of entries which helps 
with the merges. One thing that I have encountered over the last 2 days is that 
the pep8 passes with my environment and fails with the gaiting. Would it be 
possible that Jenkins updates the nova.sample.conf in a similar fashion to the 
way that is done with the translations?
+1, I encountered the same problem and I think the task running 
gererate_sample.sh should be given to Jenkins


Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Best regards,
Haomai Wang, UnitedStack Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev