Hallo Aeolus community.
As a follow up to previous debates on Broker concept, I have put together some code and put in on github here: https://github.com/martinpovolny/broker
There's some basic configuration management implemented and a very limited deltacloud driver.
Read the tests to see what can be done at this stage.
Regards,
On Thu May 2 08:30:13 2013, Martin Povolny wrote:
Hallo Aeolus community.
As a follow up to previous debates on Broker concept, I have put together some code and put in on github here: https://github.com/martinpovolny/broker
There's some basic configuration management implemented and a very limited deltacloud driver.
I didn't get a chance to poke around much at the code yet, but wanted to interject a random idea that popped into my head.
Given some of our recent interest in OpenStack, I was just poking around their documentation, and I found http://docs.openstack.org/grizzly/openstack-compute/admin/content/selecting-... listing all the hypervisors supported.
I noticed that it has one for VMware, which seemed odd to me since I viewed it more as a "competitor" to OpenStack then a hypervisor you'd run things on. They have one for bare metal, too, and I started wondering if it would make sense to write a "hypervisor" layer for a cloud provider.
Then I realized... What would really be cool would be a cloud broker layer. (Though their ComputerFilter seems somewhat germane.) It could make cloud-bursting really easy, but you could probably do more -- all the other benefits of a cloud broker.
I know that this is not what you're describing, and I'm not suggesting you should change it. I just thought this could be an interesting application of this cloud broker, and a way to get it integrated into something with a larger backing. Take it with a grain of salt.
-- Matt
On Thu, May 02, 2013 at 05:13:18PM -0400, Matt Wagner wrote:
On Thu May 2 08:30:13 2013, Martin Povolny wrote:
Hallo Aeolus community.
As a follow up to previous debates on Broker concept, I have put together some code and put in on github here: https://github.com/martinpovolny/broker
There's some basic configuration management implemented and a very limited deltacloud driver.
I didn't get a chance to poke around much at the code yet, but wanted to interject a random idea that popped into my head.
Given some of our recent interest in OpenStack, I was just poking around their documentation, and I found http://docs.openstack.org/grizzly/openstack-compute/admin/content/selecting-... listing all the hypervisors supported.
I noticed that it has one for VMware, which seemed odd to me since I viewed it more as a "competitor" to OpenStack then a hypervisor you'd run things on. They have one for bare metal, too, and I started wondering if it would make sense to write a "hypervisor" layer for a cloud provider.
Sure but they probably don't want all their eggs in one basked so they sort-of-support OpenStack running on their product.
Then I realized... What would really be cool would be a cloud broker layer. (Though their ComputerFilter seems somewhat germane.) It could make cloud-bursting really easy, but you could probably do more -- all the other benefits of a cloud broker.
There could be some value in having a broker on top of OpenStack as a way to choose between private OpenStack instance and some public OpenStack offerings or more private OpenStacks based on various criteria.
But I don't know enough of OpenStack to have an opinion yet. I have seen that there are some availability zones in OpenStack and also Heat might be doing someting like that already. I have downloaded a book on OpenStack to learn more...
I know that this is not what you're describing, and I'm not suggesting you should change it. I just thought this could be an interesting application of this cloud broker, and a way to get it integrated into something with a larger backing. Take it with a grain of salt.
-- Matt
aeolus-devel@lists.fedorahosted.org