[rhos-list] Optimizing IT: Red Hat Virtual Event

Wed Dec 5 23:24:44 UTC 2012

-----Original Message-----
From: Steve Loranz [mailto:sloranz at redhat.com] 
Sent: Wednesday, December 05, 2012 5:34 PM
To: Heron, Rodrique (CTR) WDC31
Cc: Perry Myers; daniel at dumdan.com; rhos-list at redhat.com; Ohad Levy; Ian McLeod; John R. Dunning; Angus Salkeld; Steven Hardy; Zane Bitter
Subject: Re: [rhos-list] Optimizing IT: Red Hat Virtual Event

> If anyone got a work script that uses OZ to build, then push images into Glance, please share.

This is exactly what imagefactory will do for you.

Please realize that imagefactory is plugin based. Our current OS plugins pretty much just wrap Oz. The Cloud plugins take the resulting OS images and manage whatever needs to be done to prepare them for and push them to the cloud. If all you want is Openstack, then only install the Openstack cloud plugin. This was done precisely to decouple different areas of the code and make it easier for developers focused on a specific OS or a specific cloud to work on supporting that OS or cloud. For the user it allows imagefactory to be as focused or as flexible as needed.

-steve

Steve/Ian

Thanks for the pointers, I did look into Image Factory. But decided to use OZ because I wasn't sure if Image Factory was Aelous and I did not want aleous. Is there another source for information on using Image Factory the way you describe.

I was looking at: http://www.aeolusproject.org/imagefactory.html

On Dec 5, 2012, at 3:58 PM, "Heron, Rodrique  (CTR)      WDC31" <Rodrique.Heron at cigna.com> wrote:

> 
> -----Original Message-----
> From: Perry Myers [mailto:pmyers at redhat.com]
> Sent: Wednesday, December 05, 2012 3:28 PM
> To: Heron, Rodrique (CTR) WDC31
> Cc: daniel at dumdan.com; rhos-list at redhat.com; Ohad Levy; Ian McLeod; 
> Steve Loranz; John R. Dunning; Angus Salkeld; Steven Hardy; Zane 
> Bitter
> Subject: Re: [rhos-list] Optimizing IT: Red Hat Virtual Event
> 
> Hi Rodrique and Daniel,
> 
> On 12/05/2012 02:08 PM, Heron, Rodrique (CTR) WDC31 wrote:
>> I missed the event.
> 
> It's actually just recorded presentations, and they are available for 90 days I believe.  So you may still be able to register for the event and listen to the presentations for a while.
> 
>> I am using Foreman, and it would be nice to use Foreman to build images and push them to glance. 
> 
> Right, so today Foreman just takes images that already exist and what you're looking for is a feature enhancement to Foreman that would integrate with something like Image Factory or Oz to build new VM images from source media and then push those images into Glance.  Do I have that right?
> 
> You are exactly right. I would be happy with just using OZ alone to build images and using some other tool to push those images into Glance. I believe fog can do this, I know Foreman uses fog to talk to Openstack, ovirt etc.. If anyone got a work script that uses OZ to build, then push images into Glance, please share.
> 
>> -
>> Rodrique Heron
>> 
>> -----Original Message-----
>> From: rhos-list-bounces at redhat.com
>> [mailto:rhos-list-bounces at redhat.com] On Behalf Of Daniel Dumitriu
>> Sent: Wednesday, December 05, 2012 1:54 PM
>> To: Perry Myers
>> Cc: rhos-list at redhat.com
>> Subject: Re: [rhos-list] Optimizing IT: Red Hat Virtual Event
>> 
>> This is just a repeat of the comment/question I left in "The Lounge" of the Event:
> 
> Apologies for not being in the lounge today to take the questions live.
> I had another commitment and couldn't attend.
> 
>> ==
>> Thanks, Perry, for the OpenStack presentation.
>> Inciting, to say the least.
>> Question: At various points, you did mention "Heat" as an upstream 
>> project. Could you be more specific on the provisioning side of 
>> things ?
> 
> It's a service similar to Cloud Formations in Amazon AWS.  It provides the ability to define a template that describes multiple VMs working in concert.  So you would define a template with 1 or more VM definitions, and then tell Heat to launch that template.  Heat then uses the OpenStack Nova APIs to launch the VMs in the proper order, waiting for things like dependencies in one VM before launching the 2nd.
> 
> I've included some of the Heat folks on this thread.  I'm sure they 
> can do better justice to your question than I could :)
> 
>> It would be interesting, for example, to see what could happen if 
>> "Foreman" would be used to "provision the Cloud". Especially for a 
>> "private hybrid cloud" that includes both VMs and hardware servers.
> 
> Foreman could definitely be used for both bare metal server 
> provisioning for OpenStack core services and Compute Nodes while also 
> being used to provision the VMs that will be in the cloud.  I thought 
> that Ohad (Foreman creator/maintainer) had done some integration work 
> (or maybe it was just planned) to better integrate Foreman w/ 
> OpenStack from a guest provisioning perspective (using Fog as an 
> abstraction layer I think)
> 
> Ohad, any additional thoughts here?
> 
> Perry
> 
> ----------------------------------------------------------------------
> -------- CONFIDENTIALITY NOTICE: If you have received this email in 
> error, please immediately notify the sender by e-mail at the address 
> shown.
> This email transmission may contain confidential information.  This 
> information is intended only for the use of the individual(s) or 
> entity to whom it is intended even if addressed incorrectly.  Please 
> delete it from your files if you are not the intended recipient.  
> Thank you for your compliance.  Copyright (c) 2012 Cigna 
> ======================================================================
> ========
> 

------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: If you have received this email in error,
please immediately notify the sender by e-mail at the address shown.  
This email transmission may contain confidential information.  This 
information is intended only for the use of the individual(s) or entity to 
whom it is intended even if addressed incorrectly.  Please delete it from 
your files if you are not the intended recipient.  Thank you for your 
compliance.  Copyright (c) 2012 Cigna
==============================================================================