Hi,
I am working on deploying images to bare-metal machines using nova bare-metal.
My datacenter has 2 types of hw models, IBM and Dell. In existing
implementation, if I want to deploy image on specified type of hw model, I need
to setup 2 baremetal compute nodes, one for container of IBM
-
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: Monday, June 30, 2014 12:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Taurus Cheung
Subject: Re: [openstack-dev] [nova][baremetal] Scheduling baremetal deployment
on different hw model
Firstly, use
Hi,
I am working on deploying images to bare-metal machines using nova bare-metal.
After deployment, I would like to deprovision (disconnect) bare-metal nodes
from OpenStack controller/compute, so these bare-metal nodes can run standalone.
A typical scenario is that I have a workstation with
I am working on deploying images to bare-metal machines using nova bare-metal.
So far working well.
I know Ironic is under rapid development. Could I know the current status of
Ironic and the suitable time to shift from nova baremetal to Ironic?
Regards,
Taurus
Hi
I am working on deploying images to bare-metal machines using nova bare-metal.
In current architecture, disk images are kept at /var/lib/nova/instances after
the image is written (by dd) to the hard disk of bare-metal machines. But these
disk images file are no longer needed.
Does nova
Hi,
I am working on deploying images to bare-metal machines using nova bare-metal.
In current design, some files like hostname, network config file and meta.json
are injected into the image before writing to bare-metal machines. Can we
control which items to be injected into the image?
Hi,
I am working on deploying images to bare-metal machines using nova bare-metal.
In existing implementation in nova-baremetal-deploy-helper.py, there's only 1
worker to write image to bare-metal machines. If there is a number of
bare-metal instances to deploy, they need to queue up and wait
Hi,
I am working on deploying images to bare-metal machines using nova bare-metal.
In current design, nova bare-metal would first write a partition layout of root
partition and swap partition, then write the image to root partition. It seems
that the logic assumes there's no partition table
