Testing oVirt...
-
@obsolesce said in Testing oVirt...:
@hobbit666 said in Testing oVirt...:
I've loosey been reading the posts on this but what is oVirt? Is it just a management thing for KVM or is it and KVM based hypervisor in it's self?
It's a cloud infrastructure software, I'd call it a cloud stack but there's a product named that... it's a competitor of OpenStack or Apache's CloudStack.
It's not a cloud, nor a stack. It's only one layer of a virtualization management "stack". The stacks include the storage, storage management, virtualization management, cloud components, etc. This is only the one piece. It lacks the pieces necessary to be cloud (autoprovisioning and API based access.)
-
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
@hobbit666 said in Testing oVirt...:
I've loosey been reading the posts on this but what is oVirt? Is it just a management thing for KVM or is it and KVM based hypervisor in it's self?
It's a cloud infrastructure software, I'd call it a cloud stack but there's a product named that... it's a competitor of OpenStack or Apache's CloudStack.
It's not a cloud, nor a stack. It's only one layer of a virtualization management "stack". The stacks include the storage, storage management, virtualization management, cloud components, etc. This is only the one piece. It lacks the pieces necessary to be cloud (autoprovisioning and API based access.)
It does have API based access and just because autoprovisioning isn't ready to go out of the box, doesn't mean it can't. You can easily create scripts that autoprovision resources and for example, VPSs using the API.
-
@scottalanmiller said in Testing oVirt...:
It's not a cloud, nor a stack. It's only one layer of a virtualization management "stack".
I'll agree to this.
-
@obsolesce said in Testing oVirt...:
It does have API based access and just because autoprovisioning isn't ready to go out of the box, doesn't mean it can't. You can easily create scripts that autoprovision resources and for example, VPSs using the API.
I looked up the API and it looked like it was just for monitoring. They have a full provisioning API now?
-
@obsolesce said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
@hobbit666 said in Testing oVirt...:
I've loosey been reading the posts on this but what is oVirt? Is it just a management thing for KVM or is it and KVM based hypervisor in it's self?
It's a cloud infrastructure software, I'd call it a cloud stack but there's a product named that... it's a competitor of OpenStack or Apache's CloudStack.
It's not a cloud, nor a stack. It's only one layer of a virtualization management "stack". The stacks include the storage, storage management, virtualization management, cloud components, etc. This is only the one piece. It lacks the pieces necessary to be cloud (autoprovisioning and API based access.)
It does have API based access and just because autoprovisioning isn't ready to go out of the box, doesn't mean it can't. You can easily create scripts that autoprovision resources and for example, VPSs using the API.
Sure, all virtualization can be used to build cloud. But until you've built the cloud, what you have isn't cloud yet. Like Xen or KVM can be the power behind a cloud deployment. So can oVirt. But until the other pieces are there, they are still just building blocks, not the whole themselves.
-
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
@hobbit666 said in Testing oVirt...:
I've loosey been reading the posts on this but what is oVirt? Is it just a management thing for KVM or is it and KVM based hypervisor in it's self?
It's a cloud infrastructure software, I'd call it a cloud stack but there's a product named that... it's a competitor of OpenStack or Apache's CloudStack.
It's not a cloud, nor a stack. It's only one layer of a virtualization management "stack". The stacks include the storage, storage management, virtualization management, cloud components, etc. This is only the one piece. It lacks the pieces necessary to be cloud (autoprovisioning and API based access.)
It does have API based access and just because autoprovisioning isn't ready to go out of the box, doesn't mean it can't. You can easily create scripts that autoprovision resources and for example, VPSs using the API.
Sure, all virtualization can be used to build cloud. But until you've built the cloud, what you have isn't cloud yet. Like Xen or KVM can be the power behind a cloud deployment. So can oVirt. But until the other pieces are there, they are still just building blocks, not the whole themselves.
I've only used and tested it in the context of being a cloud stack. Perhaps I'd be better off then with an actual cloud stack.
Thanks for the clarification.
-
@obsolesce said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
@hobbit666 said in Testing oVirt...:
I've loosey been reading the posts on this but what is oVirt? Is it just a management thing for KVM or is it and KVM based hypervisor in it's self?
It's a cloud infrastructure software, I'd call it a cloud stack but there's a product named that... it's a competitor of OpenStack or Apache's CloudStack.
It's not a cloud, nor a stack. It's only one layer of a virtualization management "stack". The stacks include the storage, storage management, virtualization management, cloud components, etc. This is only the one piece. It lacks the pieces necessary to be cloud (autoprovisioning and API based access.)
It does have API based access and just because autoprovisioning isn't ready to go out of the box, doesn't mean it can't. You can easily create scripts that autoprovision resources and for example, VPSs using the API.
Sure, all virtualization can be used to build cloud. But until you've built the cloud, what you have isn't cloud yet. Like Xen or KVM can be the power behind a cloud deployment. So can oVirt. But until the other pieces are there, they are still just building blocks, not the whole themselves.
I've only used and tested it in the context of being a cloud stack. Perhaps I'd be better off then with an actual cloud stack.
Thanks for the clarification.
What cloud system did you use it as a part of?
-
@scottalanmiller said in Testing oVirt...:
@obsolesce said in Testing oVirt...:
It does have API based access and just because autoprovisioning isn't ready to go out of the box, doesn't mean it can't. You can easily create scripts that autoprovision resources and for example, VPSs using the API.
I looked up the API and it looked like it was just for monitoring. They have a full provisioning API now?
Yeah. I think they've had it for quite a while.
-
All the previous screenshots were from the Admin portal.
This is from the VM portal:
-
From the VM portal, create vm:
-
@fateknollogee Are you using this in production or lab?
Can't wait for 4.2.7!
-
@aaronstuder said in Testing oVirt...:
@fateknollogee Are you using this in production or lab?
Can't wait for 4.2.7!
Lab for now.
Hoping for production once I'm comfortable! -
@aaronstuder said in Testing oVirt...:
@fateknollogee Are you using this in production or lab?
Can't wait for 4.2.7!
In the next couple of weeks, I'm going to tear down the lab & do a 100% rebuild....all oVirt
-
@fateknollogee What's your lab look like?
-
@aaronstuder said in Testing oVirt...:
@fateknollogee What's your lab look like?
Just server hardware or networking gear also?
-
@fateknollogee All of it!
-
@aaronstuder said in Testing oVirt...:
@fateknollogee All of it!
Internet:
FIOS: 150/150Firewall/Router:
Meraki MX 84Switches:
1x Meraki MS320P-24
3x Meraki MS220-48
2x Mellanox SX6036NICs:
Mellanox ConnectX-3 (to be used w 56Gbe)
Mellanox ConnectX-4 (to be used for 100Gbe)
Intel 10GbeServers:
2x SuperMicro 2027TR-HTRF
2x SuperMicro SC216E16-R1200
3x SuperMicro 5018D-FN4T
2x SuperMicro SYS1028-WTRTUPS:
1x Eaton 5PX3000RT2U
2x Eaton 5PX EBM72 -
@fateknollogee Super Jeally
-
@fateknollogee said in Testing oVirt...:
In the next release (which will 4.2.7), you'll be able to deploy a single node install from Cockpit UI.
But not on Fedora
No Fedora support
Regretfully, Fedora is not supported anymore, and RPMs for it are not provided. These are still built for the master branch, so users that want to test them, can use the nightly snapshot. At this point, we only try to fix problems specific to Fedora if they affect developers. For some of the work to be done to restore support for Fedora, see also tracker bug 1460625. -
@aaronstuder said in Testing oVirt...:
@fateknollogee said in Testing oVirt...:
In the next release (which will 4.2.7), you'll be able to deploy a single node install from Cockpit UI.
But not on Fedora
No Fedora support
Regretfully, Fedora is not supported anymore, and RPMs for it are not provided. These are still built for the master branch, so users that want to test them, can use the nightly snapshot. At this point, we only try to fix problems specific to Fedora if they affect developers. For some of the work to be done to restore support for Fedora, see also tracker bug 1460625.oVirt Node 4.3 will have Fedora.
