Re: [openstack-dev] [openstack][nova] Question on rollback live migration at the destination
Robert, Your concern seems to be correct. The bug has already been reported: https://bugs.launchpad.net/nova/+bug/1284719. # Oops, 1 year old bug... Regards, Makkie On 2015/01/27 3:58, Robert Li (baoli) wrote: Hi, I’m looking at rollback_live_migration_at_destination() in compute/manager.py. If it’s shared storage (such as NFS, is_shared_instance_path is True), it’s not going to be called since _live_migration_cleanup_flags() will return False. Can anyone let me know what’s the reason behind it? So nothing needs to be cleaned up at the destination in such case? Should VIFs be unplugged, to say the least? I’m working on the live migration support with SR-IOV macvtap interfaces. The devices allocated at the destination needs to be freed. thanks, Robert __ 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
[openstack-dev] [Trove] Proposal to add sample configurations of admin_{user, tenant_name, password}
Hello folks, I'd like to propose following small changes to [filter:authtoken] section in default api-paste.ini: +admin_tenant_name = %SERVICE_TENANT_NAME% +admin_user = %SERVICE_USER% +admin_password = %SERVICE_PASSWORD% I created a new ticket [1] about this. Some of core OpenStack components have them in api-paste.ini or configs. This is also mentioned by Thomas Goirand in [2], and he says it's troublesome to add them manually. In addition, I think this is mindful of Trove beginners ( I'm one of them! ) who try to set up Trove following install-guide [3]. If there are some comments or samples, it will be helpful. Therefore, I also think it's reasonable to comment above admin_* samples out. Any feedback on this would be appreciated. [1] https://bugs.launchpad.net/trove/+bug/1325482 [2] https://bugs.launchpad.net/trove/+bug/1299332 [3] http://docs.openstack.org/icehouse/install-guide/install/apt/content/trove-install.html Regards, Makkie ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Trove] Idea of sample admin_{user, tenant_name, password} in api-paste.ini instead of admin_token
Hi developers,
If you have a chance it would be great to hear any feedback.
I opened a new ticket about admin_{user,tenant_name,
password}:
https://bugs.launchpad.net/trove/+bug/1299332
In this ticket, I suggest following changes in api-paste.ini:
+admin_tenant_name = %SERVICE_TENANT_NAME%
+admin_user = %SERVICE_USER%
+admin_password = %SERVICE_PASSWORD%
Some of other OpenStack components have them in api-paste.ini as default.
However, Trove doesn't have yet after admin_token was removed by
https://bugs.launchpad.net/trove/+bug/1325482.
Actually, I don't think it's a critical bug. Tests and devstack will
add them automatically.
However, it's important for packaging, and also helpful for Trove
beginners ( like me :-) ) who try to install Trove from source code
following documents.
In addition, this is mentioned by Thomas Goirand in
https://bugs.launchpad.net/trove/+bug/1299332. He is also afraid about
complexity of package validation by Tempest.
Again, please give me feedback if you are interested.
Regards,
Makkie
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
