Re: [openstack-dev] [nova][docker][powervm] out of tree virt driver breakage

2016-01-19 Thread Andrew Thorstensen
Thanks Daniel.  We will be proposing an update to the powervm driver today 
to
handle this change.

Appreciate you reaching out about this!


Thanks.

Drew Thorstensen



From:   "Daniel P. Berrange" 
To: openstack-dev@lists.openstack.org
Date:   01/19/2016 06:31 AM
Subject:[openstack-dev] [nova][docker][powervm] out of tree virt 
driver  breakage



This is an alert for anyone who maintains an out of tree virt driver
for Nova (docker & powervm are the 2 I know of).

The following change has just merged changing the nova/virt/driver.py
API, and as such it will break any out of tree virt drivers until they
are updated

  commit fbe31e461ac3f16edb795993558a2314b4c16b52
  Author: Daniel P. Berrange 
  Date:   Mon Jun 8 17:58:09 2015 +0100

compute: convert manager to use nova.objects.ImageMeta
 
Update the virt driver API so that all methods with an
'image_meta' parameter take a nova.objects.ImageMeta
instance instead of a dict.
 
NB, this will break out of tree virt drivers until they
convert their code to use the new object.
 
Blueprint: mitaka-objects
Change-Id: I75465a2029b53aa4d338b80619ed7380e0d19e6a

Anywhere in your virt driver impl that uses the 'image_meta' parameter
should be updated to use the nova.objects.ImageMeta instance rather
than assuming it has a dict.

If you have any trouble understanding how to update the code, reply
to this message or find me on IRC for guidance, or look at changes
made to the libvirt/xenapi/vmware drivers in tree.

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron] [networking-powervm] Please createnetworking-powervm on PyPI

2015-11-04 Thread Andrew Thorstensen
Hi Kyle,

My team owns the networking-powervm project.  When we moved from the 
StackForge to OpenStack namespace we changed the name from neutron-powervm 
to networking-powervm.  There is no reason for the PyPI project to have a 
different name and we were planning to publish an update shortly with the 
networking-powervm name.

We were planning to do this sometime next week.  Do we need it done 
sooner?


Thanks!

Drew Thorstensen
Power Systems / Cloud Software



From:   Kyle Mestery 
To: "OpenStack Development Mailing List (not for usage questions)" 

Date:   11/03/2015 10:09 PM
Subject:[openstack-dev] [neutron] [networking-powervm] Please 
create  networking-powervm on PyPI



I'm reaching out to whoever owns the networking-powervm project [1]. I 
have a review out [2] which updates the PyPI publishing jobs so we can 
push releases for networking-powervm. However, in looking at PyPI, I don't 
see a networking-powervm project, but instead a neutron-powervm project. 
Is there a reason for the PyPI project to have a different name? I believe 
this will not allow us to push releases, as the name of the projects need 
to match. Further, the project creation guide recommends naming them the 
same [4].

Can someone from the PowerVM team look at registering networking-powervm 
on PyPI and correcting this please?

Thanks!
Kyle

[1] https://launchpad.net/neutron-powervm
[2] https://review.openstack.org/#/c/233466/
[3] https://pypi.python.org/pypi/neutron-powervm/0.1.0
[4] http://docs.openstack.org/infra/manual/creators.html#pypi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev