| Table of Contents | ||
|---|---|---|
|
...
Micro-segmentation is done with L3 overlay networking, which in turn is controlled by Warren SDN. Requirements for NICs can be found from the following link: https://conflu.warren.oye.io/display/WARP/Warren + Hardware + Requirements
Do we need a specific network switch (brand and model)?
...
Yes, and not only can, but is highly advisable! Otherwise high reliability markers for Warren cannot be guaranteed. All networking devices should have redundancy if the purpose of particular usage of Warren is public service provisioning.
Are Controller Nodes needed on every physical location (when you have multiple DC or On-Premises locations where you run VM and Contained Nodes)?
In general, yes. There can be some exceptions considered, when a particular location has some specific purpose, thus, having for example, a reduced set of Warren components installed. Still, for the sake of reliability, there should be at least 1 control node present.
What are the options for storage systems other than CEPH?
Although, the production grade option is at the moment only CEPH, local storage (inside hosts) with ZFS and iSCSI connected shared enterprise storage options are at the moment in development. Analysis and preparation, integrating StorPool distributed storage systems have been completed and development could start, when demand for commercial, more stable and feature-rich CEPH counterpart occurs.
Are there migration tools available from by example VMware or Hyper-V to Warren.io platform?
There are specific procedures for such migration, that are basically described here: https://superuser.openstack.org/articles/how-to-migrate-from-vmware-and-hyper-v-to-openstack/
Openstack is pretty similar to Warren in terms of virtualization tools. By no means can such a process be described as a trivial one and such migration has a significant chance to fail when current platform-specific features are in use for end-user applications.