Can we run ESXi on top of OpenStack? - openstack

I want to install ESXi on top of Openstack. Is that possible? If yes, Is there any glance image available for ESX? or Can we import any raw disk which has ESXi installed in it?

OpenStack is a Cloud platform or toolkit that orchestrates various technologies such as storage, networking and compute, including hypervisors. ESXi is a hypervisor but not a Cloud platform or toolkit. The VMware products that most directly map to OpenStack is not vSphere or ESXi, but vCloud Automation Center and vCloud Director.
In fact, OpenStack does not have it's own hypervisor but manages different hypervisors, such as
KVM,
Xen,
Hyper-V, &
ESXi.
Source: Ask Openstack
This Image should give you an idea as to what ESXi is to OpenStack
Unlike Linux kernel based hypervisors, such as KVM, vSphere with OpenStack requires the VM instances to be hosted on an ESXi server distinct from a Nova compute node, which must run on some flavor of Linux.
In contrast, VM instances running on KVM can be hosted directly on a Nova compute node.
Although a single OpenStack installation can support multiple hypervisors, each compute node will support only one hypervisor.
So any multi-hypervisor OpenStack Cloud requires at least one compute node for each hypervisor type.
Currently, the ESXDriver has a limit of one ESXi host per Nova
compute service.
Source: Blog

VMware ESXi (formerly ESX) is an enterprise-class, type-1 hypervisor
developed by VMware for deploying and serving virtual computers. As a
type-1 hypervisor, ESXi is not a software application that one
installs in an operating system (OS); instead, it includes and
integrates vital OS components, such as a kernel.[2]
ref: https://en.wikipedia.org/wiki/VMware_ESXi
As ESXi is a type 1 hypervisor, you cannot deploy it on top of kvm or another supported hypervisor of OpenStack.

Related

How to map VM to internal network?

I have a Dell's Machine with High on Resources like (32 GB RAM, 24 cores of CPU and 5 TB of Disk Space).
I have installed Openstack(devstack) on this Machine which has Ubuntu installed on it and has IP address 10.10.1.3.
This machine is in our local network , means i can ssh directly to this big machine from my laptop if i am in same network.
Now i have created a virtual machine instance using openstack and it has Ubuntu on it and it has IP address 10.10.0.3.
Now i want to access this virtual machine directly from my laptop like i access the big machine.
Any solution for this?
If your vm (let's call it "instance") is on a internal network (tenant/project network) what you need is a FIP (floating IP) from your external network so you can assign that FIP to your openstack instance. Also ensure your security groups allow ssh to your vm !.
I have some questions here so I can help you a better way:
Do you have an external network already created (flat or vlan based) ?.
The vm is using a tenant/project internal (gre/vxlan) network ?
Did you create a router in your tenant, which is using the external network for external access ?.
The aforementioned router is already connected to your internal network ?.

Cloudify 3.3 - Use of existing network (no Floating IP)

we want to configure a Cloudify Manager into an OpenStack project in which there is only an external network (named public_net), with public IP addresses.
In other words, each Cloudify VM (both Manager and Application) should be attached to the external net (no Floating IP).
The Cloudify CLI, on the other hand, was created out of OpenStack.
How should we configure the OpenStack plugin to implement this scenario?
The Cloudify manager if bootstrapped with the Openstack blueprint will be configured to two networks:
The network that it can connect to the OpenStack API (external network)
A management network that it will create.
If you want to use the external network for the management network, you should change the blueprint so it will have this network as an external resource (external_resource: true) and set the name of the network to public_net.
your blueprint will look like this:
management_network:
type: cloudify.openstack.nodes.Network
properties:
use_external_resource: true
resource_id: public_net
openstack_config: *openstack_configuration

PCI passthrough strategy in Docker or oVirt

We have to deploy a test system where a Docker container or a VM (oVirt 3.5) shares up to 4x 10GB network cards with other containers/VMs.
So far we are using just oVirt for this purpose but we would like to shift to a Dockerized system to save some resources on the machines.
Does anybody have some experience or suggestion?
Docker containers are really just processes; it can run them each in a separate network namespace (the default) or let them use the host's network directly (--net=host).
If running in a separate network namespace then they won't have any access to the host's network cards; in the default config (--net=bridge) they are NAT networked via a Linux bridge, so if that matches your requirements, you're away.
Link to Docker docs on networking

Configuring openstack for a in-house test cloud

We're currently looking to migrate an old and buggy eucalyptus cloud to openstack. We have ~15 machines that are all on the same office-internal network. The instances get their network configuration from an external (not eucalyptus) DHCP server. We run both linux and windows images. The cloud is used exclusively for platform testing from Jenkins.
Looking into openstack, it seems that out of the three supported networking modes, none really fit our environment. What we are looking for is something like an "unmanaged mode" where openstack launches an instance that is hooked up to eth0 interface on the instances' compute node and which will receive its network configuration from the external DHCP on boot. I.e. the VM's, guest hosts and clients (jenkins) are all on the same network, managed by an external DHCP server.
Is a scenario like this possible to set up in OpenStack?
It's not commonly used, but the Networking setup that will fit your needs the best is FlatNetworking (not FlatDHCPNetworking). There isn't stellar documentation on configuring that setup to work through your environment, and some pieces (like the nova-metadata service) may be a bit tricky to manage with it, but that should accomplish allowing you to run an OpenStack cloud with an external DHCP provider.
I wrote up the wiki page http://wiki.openstack.org/UnderstandingFlatNetworking some time ago to explain the setup of the various networks and how they operate with regards to NICs on hosting systems. FlatNetworking is effectively the same as FlatDHCPNetworking except that OpenStack doesn't try and run the DHCP service for you.
Note that with this mode, all the VM instances will be on the same network with your OpenStack infrastructure - there's no separation of networks at all.

Software version of network switch for VMs

I have hosted two images (both 2003 servers) from my VMServer. Including my desktop (xp-pro) there are three host.
I would like to connect them in a network (local LAN) without a physical switch.
Is there any software switch so that I can run in my desktop OS and let images use that interface to get IP automatically so that I can access Images from desktop OS?
Well you could use dynamips (+ GNS3), but just use VMware's virtual infrastructure:
http://www.virtualizationadmin.com/articles-tutorials/vmware-esx-and-vsphere-articles/installation-deployment/vmware-understanding-virtual-switch.html
i.e. You need to upgrade to at least ESX, now it's vSphere.
edit: Oh you really are on very basics of using a virtual machine: just use bridged networking:
http://www.vmware.com/support/ws55/doc/ws_net_configurations_bridged.html

Resources