Re: [DISCUSS] Graduation - Prepare Board Resolution

2012-05-31 Thread Andy Kurth
>> On Fri, May 18, 2012 at 10:06 AM, Andy Kurth  wrote:
>>> I have created a Confluence page which we can use to work out the
>>> board resolution:
>>> https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution
>>>
>>> Once we are comfortable with the resolution, one of the PPMC members
>>> will propose it on the general incubator list.  The areas we need to
>>> work on are in bold.  We need to define the project description and
>>> scope.  I wrote this as "dynamically provisioning and brokering remote
>>> access to compute resources".  Thoughts?
>
> I'm not sure I would not really understand the scope of VCL from that 
> statement.

I agree more should be added.  I kept it short since the example
resolutions suggested on the graduation guide page are very short and
general:
ofbiz: "open-source software related to enterprise automation"

Can we just use the description then?:
"open-source software related to a modular cloud computing platform
which dynamically provisions and brokers remote access to compute
resources"

I have updated the wiki to include this text and also added Alan to
the list of members:
https://cwiki.apache.org/confluence/display/VCL/Graduation+Board+Resolution

I haven't seen a tally message for the chairperson vote.  Once the
vote is closed I'll add my name to the page.

-Andy


Re: [DISCUSS] Graduation - Prepare Board Resolution

2012-05-31 Thread Henry Schaffer
>...
 will propose it on the general incubator list.  The areas we need to
 work on are in bold.  We need to define the project description and
 scope.  I wrote this as "dynamically provisioning and brokering remote
 access to compute resources".  Thoughts?
>>
>> I'm not sure I would not really understand the scope of VCL from that 
>> statement.
>
> I agree more should be added.  I kept it short since the example
> resolutions suggested on the graduation guide page are very short and
> general:
> ofbiz: "open-source software related to enterprise automation"
>
> Can we just use the description then?:
> "open-source software related to a modular cloud computing platform
> which dynamically provisions and brokers remote access to compute
> resources"

  I think this is reasonable - but have a *minor* quibble -

  The bulk of what the VCL does (auth/auth, reservations, image
storage, image loading, ...) seems to me to be fall under the
"provisions" concept - but "brokers" seems to be getting equal
emphasis even though it is an added capability. It's an important
added capability, but perhaps this slight revision might help:

 "open-source software related to a modular cloud computing platform
which dynamically provisions (and brokers) remote access to compute
resources"

--henry

>...


Re: [DISCUSS] Graduation - Prepare Board Resolution

2012-05-31 Thread Aaron Coburn
>> ...
> will propose it on the general incubator list.  The areas we need to
> work on are in bold.  We need to define the project description and
> scope.  I wrote this as "dynamically provisioning and brokering remote
> access to compute resources".  Thoughts?
>>> 
>>> I'm not sure I would not really understand the scope of VCL from that 
>>> statement.
>> 
>> I agree more should be added.  I kept it short since the example
>> resolutions suggested on the graduation guide page are very short and
>> general:
>> ofbiz: "open-source software related to enterprise automation"
>> 
>> Can we just use the description then?:
>> "open-source software related to a modular cloud computing platform
>> which dynamically provisions and brokers remote access to compute
>> resources"
> 
>  I think this is reasonable - but have a *minor* quibble -
> 
>  The bulk of what the VCL does (auth/auth, reservations, image
> storage, image loading, ...) seems to me to be fall under the
> "provisions" concept - but "brokers" seems to be getting equal
> emphasis even though it is an added capability. It's an important
> added capability, but perhaps this slight revision might help:

I don't have a strong opinion about this, but I have always understood 
"provisioning" to relate to the infrastructure for image storage, capture and 
loading while "brokering" relates to connecting the virtualization or blade 
back-end to a user's request, which would include such things as 
authentication, authorization, reservations, scheduling, etc. I think the two 
are pretty equal in importance.

Just my $0.02

-Aaron C


> "open-source software related to a modular cloud computing platform
> which dynamically provisions (and brokers) remote access to compute
> resources"
> 
> --henry
> 
>> ...



smime.p7s
Description: S/MIME cryptographic signature


Re: [DISCUSS] Graduation - Prepare Board Resolution

2012-05-31 Thread Andy Kurth
On Thu, May 31, 2012 at 11:03 AM, Aaron Coburn  wrote:
>>> ...
>> will propose it on the general incubator list.  The areas we need to
>> work on are in bold.  We need to define the project description and
>> scope.  I wrote this as "dynamically provisioning and brokering remote
>> access to compute resources".  Thoughts?

 I'm not sure I would not really understand the scope of VCL from that 
 statement.
>>>
>>> I agree more should be added.  I kept it short since the example
>>> resolutions suggested on the graduation guide page are very short and
>>> general:
>>> ofbiz: "open-source software related to enterprise automation"
>>>
>>> Can we just use the description then?:
>>> "open-source software related to a modular cloud computing platform
>>> which dynamically provisions and brokers remote access to compute
>>> resources"
>>
>>  I think this is reasonable - but have a *minor* quibble -
>>
>>  The bulk of what the VCL does (auth/auth, reservations, image
>> storage, image loading, ...) seems to me to be fall under the
>> "provisions" concept - but "brokers" seems to be getting equal
>> emphasis even though it is an added capability. It's an important
>> added capability, but perhaps this slight revision might help:
>
> I don't have a strong opinion about this, but I have always understood 
> "provisioning" to relate to the infrastructure for image storage, capture and 
> loading while "brokering" relates to connecting the virtualization or blade 
> back-end to a user's request, which would include such things as 
> authentication, authorization, reservations, scheduling, etc. I think the two 
> are pretty equal in importance.
>
> Just my $0.02
>
> -Aaron C

That's what I was thinking.
-Andy


Re: Multiple issues with install_perl_libs.pl

2012-05-31 Thread Dmitri Chebotarov
Michael

I think these settings worked for me (edited install_perl_libs.pl):

- hardcoded URL:

my $epel_url = 
"http://mirror.utexas.edu/epel/6/x86_64/epel-release-6-7.noarch.rpm";

- changed tar_verbosity:

"tar_verbosity" => "0"

If you are installing manually, check ~/.cpan/CPAN/MyConfig.pm for 
'tar_verbosity' => q[0],

Thanks.

--
Thank you,

Dmitri Chebotarov
Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175
Fax: (703) 993-3404


On Thursday, May 31, 2012 at 14:58 , Michael Jinks wrote:

> I'm starting over trying to install VCL. I'm on a RHEL-6 machine, using
> the only release of VCL I could find (2.2.1), and I'm up to the point
> where I'm trying to run:
> 
> /usr/local/vcl/bin/install_perl_libs.pl (http://install_perl_libs.pl)
> 
> That ends with:
> 
> [...]
> WARNING: failed to install the following components:
> EPEL
> Perl module: Object::InsideOut
> Perl module: RPC::XML
> 
> The EPEL issue seems to be an old URL. I was able to work around it by
> doing "yum install epel-release". After a brief search I couldn't find
> a better URL to feed to rpm; I see that download.fedora.redhat.com 
> (http://download.fedora.redhat.com) is
> defunct, but substituting the new host name, "dl.fedoraproject.org 
> (http://dl.fedoraproject.org)",
> yields a 404.
> 
> I see in the docs that the RPC::XML problem is a known issue, but when I
> try to install manually by calling cpan directly, I hit the problem
> described here:
> 
> http://tinyurl.com/c2gjrrf [mail-archives.apache.org 
> (http://mail-archives.apache.org)]
> 
> That thread suggests that the bug should be fixed as of February, but
> this is a fresh download of the VCL package from a couple of days ago.
> Any chance the old bug leaked back in? Or is there a newer release that
> I wasn't able to get from the VCL download site?
> 
> Thanks,
> -m
> 
> -- 
> Michael Jinks :: mji...@uchicago.edu (mailto:mji...@uchicago.edu)
> University of Chicago IT Services
> 
>