Re: [openstack-dev] [TripleO] devtest environment for virtual or true bare metal
Excerpts from Ben Nemec's message of 2014-08-08 22:25:35 +: That sounds essentially correct. Note that all 15 vms aren't used in a normal devtest run, but we create them all anyway because of some difficulties adding new environments in some situations (namely CI, I believe). On 08/05/2014 11:27 AM, LeslieWang wrote: Hi Ben, Thanks for your reply. Actually I'm a little confused by virtual environment. I guess what it means is as below: - 1 Seed VM as deployment starting point. - Both undercloud and overcloud images are loaded into Glance of Seed VM. - 15 VMs are created. 1 for undercloud, 1 for overcloud controller, left 13 are for overcloud compute. - 1 Host machine acts as container for all 15 VMs. It can be separated from Seed VM. - Seed VM communicates with Host machine to create 15 VMs and installed corresponding images. Is it correct? Or can you roughly introduces the topology of the devtest virtual environment. Best RegardsLeslie Wang Yes, im not sure that '15 VMs are created' is entirely correct - we create 15 vm definitions. This does include qcow2 images but these typically start much smaller than their full possible size on disk. The distinction is, as Ben points out, that we do not actually deploy to all of these VMs. In addition to the CI issues, we specify a static number that is large enough for full runs to more correctly emulate a real deployment - typically you have a set number of servers to deploy on which is not directly determined by your deployment requirements. Cheers, Greg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] devtest environment for virtual or true bare metal
That sounds essentially correct. Note that all 15 vms aren't used in a normal devtest run, but we create them all anyway because of some difficulties adding new environments in some situations (namely CI, I believe). On 08/05/2014 11:27 AM, LeslieWang wrote: Hi Ben, Thanks for your reply. Actually I'm a little confused by virtual environment. I guess what it means is as below: - 1 Seed VM as deployment starting point. - Both undercloud and overcloud images are loaded into Glance of Seed VM. - 15 VMs are created. 1 for undercloud, 1 for overcloud controller, left 13 are for overcloud compute. - 1 Host machine acts as container for all 15 VMs. It can be separated from Seed VM. - Seed VM communicates with Host machine to create 15 VMs and installed corresponding images. Is it correct? Or can you roughly introduces the topology of the devtest virtual environment. Best RegardsLeslie Wang ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://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
Re: [openstack-dev] [TripleO] devtest environment for virtual or true bare metal
Hi Ben, Thanks for your reply. Actually I'm a little confused by virtual environment. I guess what it means is as below: - 1 Seed VM as deployment starting point. - Both undercloud and overcloud images are loaded into Glance of Seed VM. - 15 VMs are created. 1 for undercloud, 1 for overcloud controller, left 13 are for overcloud compute. - 1 Host machine acts as container for all 15 VMs. It can be separated from Seed VM. - Seed VM communicates with Host machine to create 15 VMs and installed corresponding images. Is it correct? Or can you roughly introduces the topology of the devtest virtual environment. Best RegardsLeslie Wang ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO] devtest environment for virtual or true bare metal
Dear all,
Looking at devtest pages at TripleO wiki
http://docs.openstack.org/developer/tripleo-incubator/devtest.html. I thought
all variables and configurations of devtest are for true bare-metal because I
see diskimage-builder options of both overcloud and undercloud doesn't include
vm option. But I see this configuration in
tripleo-incubator/scripts/devtest_testenv.sh,
## #. Set the default bare metal power manager. By default devtest uses
##nova.virt.baremetal.virtual_power_driver.VirtualPowerManager to
##support a fully virtualized TripleO test environment. You may
##optionally customize this setting if you are using real baremetal
##hardware with the devtest scripts. This setting controls the
##power manager used in both the seed VM and undercloud for Nova Baremetal.
##::
POWER_MANAGER=${POWER_MANAGER:-'nova.virt.baremetal.virtual_power_driver.VirtualPowerManager'}
Thus, seems like all setting are for virtual environment, not for true bare
metal. So I'm a little confused. Can anyone help clarify it? And what is the
right configure of POWER_MANAGER if using real bare metal hardware?
Best RegardsLeslie___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] devtest environment for virtual or true bare metal
On 08/04/2014 09:46 AM, LeslieWang wrote:
Dear all,
Looking at devtest pages at TripleO wiki
http://docs.openstack.org/developer/tripleo-incubator/devtest.html. I thought
all variables and configurations of devtest are for true bare-metal because I
see diskimage-builder options of both overcloud and undercloud doesn't
include vm option. But I see this configuration in
tripleo-incubator/scripts/devtest_testenv.sh,
## #. Set the default bare metal power manager. By default devtest uses
##nova.virt.baremetal.virtual_power_driver.VirtualPowerManager to
##support a fully virtualized TripleO test environment. You may
##optionally customize this setting if you are using real baremetal
##hardware with the devtest scripts. This setting controls the
##power manager used in both the seed VM and undercloud for Nova
Baremetal.
##::
POWER_MANAGER=${POWER_MANAGER:-'nova.virt.baremetal.virtual_power_driver.VirtualPowerManager'}
Thus, seems like all setting are for virtual environment, not for true bare
metal. So I'm a little confused. Can anyone help clarify it? And what is the
right configure of POWER_MANAGER if using real bare metal hardware?
Best RegardsLeslie
Devtest defaults to a virtual environment because that's what most
people working with it have available. We try to stay as close to the
baremetal use case as possible though, which is why the vm element isn't
included in image builds. The images are built to be deployed to
baremetal, and the virtual deployment just uses the VirtualPowerManager
to do that.
The correct power manager to use for real baremetal is going to depend
on the hardware you have available. You'll have to look through the
available power managers and decide which is appropriate for you.
-Ben
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://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
