+1
A reference case is that, in an operating system like Linux, hardware drivers
only abstract hardware devices into
manageable resources with standard interfaces. Then the kernel takes the job to
allocate resources, map and
schedule workload onto them, and so on.
In OpenStack, projects for res
[Nova][Cinder] Feature about volume delete
protection
On 6 March 2014 08:50, zhangyu (AI) wrote:
> It seems to be an interesting idea. In fact, a China-based public
> IaaS, QingCloud, has provided a similar feature to their virtual
> servers. Within 2 hours after a virtual server i
This is TRULY a constructive suggestion. Time and again people have good ideas,
but fail to
make them high-quality BPs, even being familiar with code base. The major
reason lies in lacking
of design experiences. Such a Gerrit-based design iteration will make the
design and decision
process more
protection
On Thu, Mar 6, 2014 at 9:13 PM, John Garbutt
mailto:j...@johngarbutt.com>> wrote:
On 6 March 2014 08:50, zhangyu (AI)
mailto:zhangy...@huawei.com>> wrote:
> It seems to be an interesting idea. In fact, a China-based public IaaS,
> QingCloud, has provided a similar
It seems to be an interesting idea. In fact, a China-based public IaaS,
QingCloud, has provided a similar feature
to their virtual servers. Within 2 hours after a virtual server is deleted, the
server owner can decide whether
or not to cancel this deletion and re-cycle that "deleted" virtual serv
Agree. Snapshot seems to be a nature solution for it.
-Original Message-
From: Joe Gordon [mailto:joe.gord...@gmail.com]
Sent: Tuesday, March 04, 2014 11:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Luohao (brian)
Subject: Re: [openstack-dev] [nova][cinder] n
bry...@us.ibm.com>
All the world's a stage and most of us are desperately unrehearsed.
-- Sean O'Casey
--------
From:"zhangyu (AI)" mailto:zhangy...@huawei.com>
] [Cinder] [Nova]Do you think volume force delete
operation should not apply to the volume being used?
I thinkforce delete = nova detach volume,then cinder delete volume
Volume status in db shoud be modified after nova detach volume.
Thanks!
From: zhangyu (AI) [mailto:zhangy
If I understand your question correctly, the case you describe should be like
the following:
Assume we have created both an instance and a volume, then we try to attach
that volume to the instance.
Before that operation is completed (the status of the volume is "attaching"
now), for whatever r
Sure, hard-coding seems weird…
However, a global configuration here dominates all domains. It might be a
little too strong in cases in which we want to apply various configurations to
different domains.
Could we add any new attributes in the info for creating a domain for this? Or
any other su
10 matches
Mail list logo
