<div dir="ltr">still a question in line. <div>Thanks.<br><div class="gmail_extra"><br><div class="gmail_quote">2016-01-08 21:53 GMT+08:00 Andrew Laski <span dir="ltr"><<a href="mailto:andrew@lascii.com" target="_blank">andrew@lascii.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 01/08/16 at 12:33pm, John Garbutt wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On 8 January 2016 at 08:17, 少合冯 <<a href="mailto:lvmxhster@gmail.com" target="_blank">lvmxhster@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi, all<br>
<br>
Now I'm working on the migrations list/show API.<br>
The new api defines migrations is a sub-collection of an instance.<br>
GET v2.1/tenant_id/servers/server-id/migrations/migration-id<br>
<br>
I need to support the new cell API to get a migration of a specified<br>
instance.<br>
get_migration_by_instance_and_id<br>
<br>
I read up the nova cell doc.<br>
<a href="http://docs.openstack.org/developer/nova/cells.html" rel="noreferrer" target="_blank">http://docs.openstack.org/developer/nova/cells.html</a><br>
<br>
It tells us that, the migrations table will be API-level.<br>
The instances table is Cell-level.<br>
So does that means that we can do live migration cross cells?<br>
</blockquote>
<br>
In sort, you can't currently live-migrate between cells.<br>
<br>
So there is the current cells v1. When using cells v1 you will never<br>
be able to move between cells. In addition, when using nova-network,<br>
network assumptions generally mean IPs can't move between cells.<br>
</blockquote>
<br></span>
Assuming a global network the limitation is just within Nova. There is no mechanism for moving instance data from one cell database to another. And it's not something that will be added since v1 is in a freeze.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
In cells v2, we were talking about ways that could happen. Its still<br>
hard, because you would need to copy the instance record between one<br>
cell database to another, with the API understanding how the move is<br>
going. Complexity best avoided, if possible.<br>
</blockquote>
<br></span>
Cells v2 makes some architecture choices that will make it easier to accomplish this. But it's not necessary to have for cells v2 so it's not likely to be in place initially.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
And also this will affect my code.<br>
If the migrations is API-level, so I do not need a cell name to get the<br>
migrations info from DB.<br>
<br>
Or I need to get the cell name by the specified instance, and then get the<br>
migrations info by _TargetedMessage.<br>
</blockquote>
<br>
Afraid I don't have enough context from the rest of your email to<br>
answer these questions.<br>
</blockquote>
<br></span>
I'm not entirely clear on the question either, but if the migration is in the api level database then you do not need a cell name to get the migration from the db. The cell name is only used to route a request to a cell database.<br></blockquote><div><br></div><div>still puzzle the current nova code.</div><div><a href="https://github.com/openstack/nova/blob/master/nova/cells/messaging.py#L1668">https://github.com/openstack/nova/blob/master/nova/cells/messaging.py#L1668</a> </div><div><a href="https://github.com/openstack/nova/blob/master/nova/cells/messaging.py#L1330">https://github.com/openstack/nova/blob/master/nova/cells/messaging.py#L1330</a><br></div><div><br></div><div>why <span style="color:rgb(121,93,163);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;font-size:12px;line-height:16.8px;white-space:pre;background-color:rgb(248,238,199)">get_migrations </span>in the above link still need to route a request to a cell database, or broadcast to all cell database? </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Thanks,<br>
John<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</blockquote></div><br></div></div></div>