Greeting,
I have some questions on the force_config_drive configuration options
and hope get some hints.
a) Why do we want this? Per my understanding, if the user want to use
the config drive, they need specify it in the nova boot. Or is it
because possibly user have no idea of the
On Tue, 2014-02-25 at 10:45 +, John Garbutt wrote:
>
> As a heads up, the overheads of DB calls turned out to dwarf any
> algorithmic improvements I managed. There will clearly be some RPC
> overhead, but it didn't stand out as much as the DB issue.
>
> The move to conductor work should certa
On Tue, 2014-02-25 at 03:05 +, Liuji (Jeremy) wrote:
> Now that USB devices are used so widely in private/hybrid cloud like
> used as USB key, and there are no technical issues in libvirt/qemu.
> I think it a valuable feature in openstack.
USB key is an interesting scenario. I assume the USB k
On Mon, 2014-02-24 at 04:10 +, Liuji (Jeremy) wrote:
> I have found a BP about USB device passthrough in
> https://blueprints.launchpad.net/nova/+spec/host-usb-passthrough.
> I have also read the latest nova code and make sure it doesn't support
> USB passthrough by now.
>
> Are there any pro
On Mon, 2014-02-17 at 06:43 +, Gouzongmei wrote:
> Hello,
>
>
>
> In current PCI passthrough implementation, a pci device is only
> allowed to be assigned to a instance while the instance is being
> created, it is not allowed to be assigned or removed from the instance
> while the instance
On Fri, 2014-02-14 at 10:22 +0100, Sylvain Bauza wrote:
> Instead of limitating the consumed bandwidth by proposiong a
> configuration flag (yet another one, and which default value to be
> set ?), I would propose to only decrease the niceness of the process
> itself, so that other processes would
On Fri, 2014-02-14 at 15:29 +, sahid wrote:
> Greetings,
>
> I would like to add a new filter based on the load averages.
>
> This filter will use the command uptime and will provides an option to choice
> a
> period between 1, 5, and 15 minutes and an option to choice the max load
> average
On Mon, 2014-01-27 at 21:14 +, Jani, Nrupal wrote:
> Hi,
>
>
>
> There are two possibilities for the hybrid compute nodes
>
> - In the first case, a compute node has two NICs, one SRIOV
> NIC & the other NIC for the VirtIO
>
> - In the 2nd case, Compute node has only one
On Mon, 2014-01-27 at 22:31 +0100, Ian Wells wrote:
> In any case, as discussed in the meeting, this is an optimisation and
> not something we have to solve in the initial release, because:
>
+1 for this. We should keep it as future enhancement effort.
--jyh
_
On Mon, 2014-01-27 at 14:58 +, Robert Li (baoli) wrote:
> Hi Folks,
>
>
> In today's meeting, we discussed a scheduler issue for SRIOV. The
> basic requirement is for coexistence of the following compute nodes in
> a cloud:
> -- SRIOV only compute nodes
> -- non-SRIOV only compute
On Fri, 2014-01-17 at 22:30 +, Robert Li (baoli) wrote:
> Yunhong,
>
> I'm hoping that these comments can be directly addressed:
> a practical deployment scenario that requires arbitrary
> attributes.
I'm just strongly against to support only one attributes (your PCI
group) for scheduli
On Thu, 2014-01-16 at 00:22 +0800, Jay Lau wrote:
> Greeting,
>
> In compute/manager.py, there is a periodic task named as
> update_available_resource(), it will update resource for each compute
> periodically.
>
> @periodic_task.periodic_task
> def update_available_resource(self, context):
On Fri, 2014-01-17 at 09:39 -0800, Vishvananda Ishaya wrote:
>
> On Jan 16, 2014, at 9:41 PM, Jiang, Yunhong
> wrote:
>
> > I noticed the BP has been approved, but I really want to understand
> > more on the reason, can anyone provide me some hints?
> >
> > In the BP, it states that “For resiz
On Thu, 2014-01-16 at 01:28 +0100, Ian Wells wrote:
> To clarify a couple of Robert's points, since we had a conversation
> earlier:
> On 15 January 2014 23:47, Robert Li (baoli) wrote:
> --- do we agree that BDF address (or device id, whatever
> you call it), and node id should
On Wed, 2013-11-27 at 11:41 -0600, Chris Friesen wrote:
> On 11/26/2013 07:48 PM, Vijay Venkatachalam wrote:
> > Hi,
> >
> > Is there a way for the VM to identify that it is
> > getting booted in OpenStack?
> >
> > As said in the below mail, once the VM knows it is
On Wed, 2013-11-27 at 01:48 +, Vijay Venkatachalam wrote:
> Hi,
>
> Is there a way for the VM to identify that it is
> getting booted in OpenStack?
>
> As said in the below mail, once the VM knows it is
> booting in OpenStack it will alter the boot sequence.
>
On Wed, 2013-11-27 at 12:38 +, Day, Phil wrote:
> Doesn’t this mean that you can’t deploy Icehouse (3.0) code into a
> Havana system but leave the RPC version pinned at Havana until all of
> the code has been updated ?
I think it's because this change is for computer manager, not for
conduct
On Tue, 2013-11-19 at 12:52 +, Daniel P. Berrange wrote:
> On Wed, Nov 13, 2013 at 02:46:06PM +0200, Tuomas Paappanen wrote:
> > Hi all,
> >
> > I would like to hear your thoughts about core pinning in Openstack.
> > Currently nova(with qemu-kvm) supports usage of cpu set of PCPUs
> > what can
On Mon, 2013-11-18 at 15:32 -0800, Joe Gordon wrote:
>
>
>
> On Mon, Nov 18, 2013 at 4:08 PM, yunhong jiang
> wrote:
> On Mon, 2013-11-18 at 14:09 -0800, Joe Gordon wrote:
> >
> > Phil Day discussed this at the summit and I have f
On Fri, 2013-11-15 at 22:42 +, Jiang, Yunhong wrote:
> I have no particular part thus any part that need help is ok for me.
>
> My own purpose is to support dynamic resource claim to support live migration
> to instance with hardware allocated. For instance with device assigned (PCI
> device
On Mon, 2013-11-18 at 14:09 -0800, Joe Gordon wrote:
>
> Phil Day discussed this at the summit and I have finally gotten around
> to posting a POC of this.
>
> https://review.openstack.org/#/c/57053/
Hi, Joe, why you think the DB is not exact state in your followed commit
message? I think the D
On Mon, 2013-11-18 at 10:18 -0500, Andrew Laski wrote:
> On 11/15/13 at 04:01pm, yunhong jiang wrote:
> >On Fri, 2013-11-15 at 17:19 -0500, Andrew Laski wrote:
> >If yes, would it be possible to create a special task_state as IDLE, to
> >distinguish it better? When
On Fri, 2013-11-15 at 17:19 -0500, Andrew Laski wrote:
> On 11/15/13 at 07:30am, Dan Smith wrote:
> >> You're not missing anything. But I think that's a bug, or at least an
> >> unexpected change in behaviour from how it used to work. If you follow
> >> instance_update() in nova.db.sqlalchemy.api
23 matches
Mail list logo