://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Qin Zhao
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
not quite sure if we can model it in Nova, and let the user to
create snapshot chain via Nova api. Has it been discussed in design session
or mail group? Anybody know that?
On Tue, Feb 25, 2014 at 6:40 PM, John Garbutt j...@johngarbutt.com wrote:
On 25 February 2014 09:27, Qin Zhao chaoc
be something worthwhile discussing at the up
and coming summit.
Thanks
Gary
From: Qin Zhao chaoc...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Tuesday, February 25, 2014 2:05 PM
To: OpenStack Development Mailing
://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
--
Qin Zhao
instance will be preferred sometimes. Creating a new instance will be
another story.
On Wed, Mar 5, 2014 at 3:20 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Tue, Mar 4, 2014 at 1:06 AM, Qin Zhao chaoc...@gmail.com wrote:
I think the current snapshot implementation can be a solution
, 2014 at 6:21 PM, Qin Zhao chaoc...@gmail.com wrote:
Hi Joe, my meaning is that cloud users may not hope to create new
instances
or new images, because those actions may require additional approval and
additional charging. Or, due to instance/image quota limits, they can
not do
Gordon joe.gord...@gmail.com wrote:
On Wed, Mar 5, 2014 at 8:59 AM, Qin Zhao chaoc...@gmail.com wrote:
Hi Joe,
If we assume the user is willing to create a new instance, the workflow
you
are saying is exactly correct. However, what I am assuming is that the
user
is NOT willing to create
AM, Qin Zhao chaoc...@gmail.com wrote:
Hi Joe,
For example, I used to use a private cloud system, which will calculate
charge bi-weekly. and it charging formula looks like Total_charge =
Instance_number*C1 + Total_instance_duration*C2 + Image_number*C3 +
Volume_number*C4. Those Instance
. ;)
Best,
-jay
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Qin Zhao
___
OpenStack-dev mailing list
OpenStack
with adding the functionality in a
way that is generic (not hypervisor-specific).
Best,
-jay
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Qin Zhao
/cgi-bin/mailman/listinfo/openstack-dev
--
Qin Zhao
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Dear stackers,
FYI. Eventually I report this problem to libguestfs. A workaround has been
included into libguestfs code to fix it. Thanks for your supporting!
https://bugzilla.redhat.com/show_bug.cgi?id=1123007
On Sat, Jun 7, 2014 at 3:27 AM, Qin Zhao chaoc...@gmail.com wrote:
Yuriy,
And I
, and eventlet. The
situation is a little complicated. Is there any expert who can help me to
look for a solution? I will appreciate for your help!
--
Qin Zhao
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
of each compute node can do the
calculation according to its settings (or its calculation method, if it is
pluggable), so that resource usage behavior can be specified to meet the
unique requirement.
--
Qin Zhao
___
OpenStack-dev mailing list
OpenStack-dev
://bugs.python.org/issue7213*
On Wed, Jun 4, 2014 at 10:41 PM, Qin Zhao chaoc...@gmail.com wrote:
Hi Zhu Zhu,
Thank you for reading my diagram! I need to clarify that this problem
does not occur during data injection. Before creating the ISO, the driver
code will extend the disk. Libguestfs
://bugs.python.org/issue7213*
On Wed, Jun 4, 2014 at 10:41 PM, Qin Zhao chaoc...@gmail.com wrote:
Hi Zhu Zhu,
Thank you for reading my diagram! I need to clarify that this problem
does not occur during data injection. Before creating the ISO, the driver
code will extend the disk. Libguestfs is invoked
.
On Thu, Jun 5, 2014 at 7:21 PM, Qin Zhao chaoc...@gmail.com wrote:
Hi Yuriy,
Thanks for reading my bug! You are right. Python 3.3 or 3.4 should not
have this issue, since they have can secure the file descriptor. Before
OpenStack move to Python 3, we may still need a solution. Calling
libguestfs
Yuriy,
And I think if we use proxy object of multiprocessing, the green thread
will not switch during we call libguestfs. Is that correct?
On Fri, Jun 6, 2014 at 2:44 AM, Qin Zhao chaoc...@gmail.com wrote:
Hi Yuriy,
I read multiprocessing source code just now. Now I feel it may not solve
Agree with Sean. A short error name in response body would be better for
applications who consume OpenStack. To my understand, the
X-OpenStack-Error-Help-URI proposed by jpipes will be a uri to error
resolution method. Usually, a consumer application needn't to load its
content.
On Feb 3, 2015
19 matches
Mail list logo
