date:20120517

Re: Install of Management Node

2012-05-17 Thread Aaron Coburn

Arbin,
I would suggest following the online documentation. Version 2.3 has not been 
released yet, so I would recommend following the instructions located here:

https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+Installation

The documentation assumes that the management node is a RHEL or CentOS server.

Aaron


--
Aaron Coburn
Systems Administrator and Programmer
Academic Technology Services, Amherst College
acob...@amherst.edu






On May 16, 2012, at 8:41 PM, Sanders, Arbin D wrote:

All,

What packages are needed when installing CentOS for the management node? This 
will be my first time installing CentOS from scratch and I would like to know 
how you all install it.

Thanks!

Arbin Darren Sanders

IT Manager – Academic Computing
North Carolina Central University
712 Cecil Street
Suite 3014
Durham, NC 27707
919.530.6307
919.530.5097 (Fax)

For the Latest ITS Updates and Tips Join Us Online

  

CONFIDENTIALITY: This email (including any attachments) may contain 
confidential, proprietary and privileged information, and unauthorized 
disclosure or use is prohibited. If you received this email in error, please 
notify the sender and delete this e-mail from your system.


__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__

Re: MIT licensed source code

2012-05-17 Thread Josh Thompson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, May 16, 2012 10:37:02 AM Kevan Miller wrote:
> On May 11, 2012, at 3:17 PM, Josh Thompson wrote:
> >
> > Kevan,
> >
> > Ugh.  Thanks for looking at this.  I guess it goes to show you can't just
> > trust that another project that says it is MIT licensed is *completely*
> > MIT
> > licensed.  :(  I'll figure out a way to deal with it.  If it works out
> > that
> > bcpowmod.php and str_split.php are not actually needed, can I just remove
> > them?  If so, do I need to document that modification somewhere?
>
> BTW, vcl/trunk/web/.ht-inc/phpseclib/index.html refers to PHP Secure
> Communications Library as LGPL-licensed. Which is contradicted by
> http://phpseclib.sourceforge.net/
>
> It looks like our documentation comes from
> http://phpseclib.sourceforge.net/documentation/ -- I'd check with the
> phpseclib project. Seems to be their reference to LGPL is unintended or
> inconsistent. bcpowmod.php's LGPL license would seem to be a problem with
> this, however…
>
> --kevan

After looking further, there are only two files (AES.php and Rijndael.php)
needed from the phpseclib project, and both of them appear as though they were
written to be able to be included by themselves (i.e. each one contains
information about the author, the project, and the license).  Both files state
that they are MIT licensed and contain that license in them.  Is it normal to
just pull in specific files from another project, or is it better to include
the whole project?

My only other experience in including another open source project in one I
work on is from including the Dojo Toolkit with VCL.  In that case, it seemed
to make the most sense to include the whole thing.

License wise, it seems simplest to just include the two files in the release,
but I just want to make sure we do the right thing in respecting other open
source projects.

Thanks,
Josh
- --
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk+08HIACgkQV/LQcNdtPQN8dgCdF/RaBttxHHuRMjuw73G9Kv34
RjYAnimOHe1R50N532Bgxi+uOjVnkgjv
=PjK8
-END PGP SIGNATURE-

Re: VCL-543 OSX under ESXi 4.1

2012-05-17 Thread Andy Kurth

Hi Jim,
I made a commit to OSX.pm this morning.  I mainly changed the
indentation.  For the most part, the Perl code is indented using tabs.

I also made some minor indentation/spacing changes to the pod sections
so that the output lined up when running pod2text, etc.  These
sections must be indented using spaces.

None of the code functionality should have changed except for possibly
one location.  My editor was complaining about lines 1843/1844 in the
previous revision:
1843: #$command .= " && sed -i '' -e \'s/
1844: //g\' currentimage.txt";

I'm assuming both of these lines should be commented.  I changed it to:
1783: # $command .= " && sed -i '' -e \'s///g\' currentimage.txt";

Please do an 'svn up' and make sure I didn't mess anything up.

Thanks,
Andy

On Wed, Apr 4, 2012 at 3:10 PM, Aaron Peeler  wrote:
> Hi Jim,
>
> Made progress to a point, I wasn't able to get a full blown instance
> going, but I feel my effort was good enough to prove it can be done
> and used. Overall the code looks good and as we move forward, possibly
> in the 2.4 release, I think it would be ideal to put all OS related
> routines in their respective OS modules, like
> notify_via_(wall,msg,oascript), etc.
>
> In the supporting documentation for this on the vcl wiki somewhere, I
> recommend to list known working apple hardware. So far I can say that
> it would work with the Mac Mini 2011 model and your running it on
> MacPro.
>
> I'll work on committing the backend and db components it into trunk on
> your behalf. I think Josh has already committed the php part.
>
> Thanks for the work and sorry it took so long to review it.
>
> Aaron
>
>
> On Wed, Apr 4, 2012 at 7:49 AM, Aaron Peeler  wrote:
>> Thanks Jim.
>>
>> Right, I saw that one also. I've got a 2010 mac mini model which also
>> has the keyboard issue.  Doesn't seem like it's feasible to use the
>> 2010 model. Going to give it one more shot with trying to do a
>> kickstart install off the dvd. It that doesn't work then I'll try to
>> locate a 2011 model.
>>
>> Overall your code looks good and should work - just would like to test it.
>>
>> Aaron
>>
>>
>> On Tue, Apr 3, 2012 at 4:35 PM, James O'Dell  wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> This site gives a walk through installing OSX on a mac mini
>>> using esxi 5. It lists the hardware used, and a link to
>>> vmware's nic driver.
>>>
 http://paraguin.com/2012/01/17/os-x-on-a-mac-mini-with-vmware-esxi-5/
>>>
>>> __Jim
>>>
>>> On 4/3/2012 11:48 AM, Aaron Peeler wrote:
 Hi Daiyu,

 Thanks. Yes those are a couple that I had found.

 Aaron

 On Tue, Apr 3, 2012 at 2:35 PM, Hayashi, Daiyu
  wrote:
> Based on your email I take it that you've read these posts.
>
> http://paraguin.com/2012/01/10/the-mac-mini-vmware-esxi-5-server-part-1-research/
>
> http://tinkertry.com/maczilla-core-i5-mac-mini-esxi-5-0-update-1/
>
>
> Daiyu Hayashi
> Lead Information Technology Consultant
> Mihaylo College of Business and Economics
> Cal State University Fullerton
> 657-278-7347
>
>
>
>
> -Original Message-
> From: Aaron Peeler [mailto:fapee...@ncsu.edu]
> Sent: Tuesday, April 03, 2012 6:28 AM
> To: vcl-dev@incubator.apache.org
> Subject: VCL-543 OSX under ESXi 4.1
>
> Jim,
>
> I'm working on testing the OSX module for inclusion in the next release 
> and run into some questions.
>
> By chance have you tried to use other apple hardware? I've got a  mac 
> mini (2010 mid) model.
>
> The initial issue I've run into is the usb keyboard gets disabled once 
> the vmware kernel is loaded. In searching on a solution for this, I've 
> run across folks stating that there is a missing network adapter as well 
> and that has to added later.
>
> I'm going to attempt to install ESXi on a usb drive and boot the mac mini 
> off of that (hopefully).
>
> So I was wondering if you've installed ESXi (either 4.1 or 5 ) on a mac 
> mini yet?
>
> Thanks,
> Aaron
>
> --
> Aaron Peeler
> Program Manager
> Virtual Computing Lab
> NC State University
>
> All electronic mail messages in connection with State business which are 
> sent to or received by this account are subject to the NC Public Records 
> Law and may be disclosed to third parties.



>>>
>>>
>>> - --
>>> Jim O'Dell
>>> Network Analyst
>>> California State University Fullerton
>>> Email: jod...@fullerton.edu
>>> Phone: (657) 278-2256
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v1.4.9 (MingW32)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAk97XvoACgkQREVHAOnXPYS2wwCg2q31vV+xb5umhvBhvAhEuQ37
>>> grAAoKMTuOrRkgiI2qycV0GwH8l5v9tI
>>> =Kvto
>>> -END PGP SIGNATURE-
>>
>>
>>
>> --
>> Aaron Peeler
>> Program Manager
>> Virtual Computing Lab
>> NC

Re: MIT licensed source code

2012-05-17 Thread Aaron Coburn

Just to ask the obvious Why not just use the openssl library for this? 
Especially since the public and private keys are already being loaded in the 
initGlobals() function. I know that it's interface is not nearly so nice, and 
it doesn't support symmetric encryption for PHP <= 5.3, but here's some code 
that could be dropped in place in utils.php:

function encryptData($data){
global $keys;
if(! $data)
return false;
openssl_public_encrypt(
$data,
$encrypted,
$keys['public']);
return trim(base64_encode($encrypted));
}

function decryptData($data){
global $keys;
if(! $data)
return false;
openssl_private_decrypt(
base64_decode($data),
$decrypted,
$keys['private']);
return trim($decrypted);
}

The other change would require modifying the initGlobals() function so that the 
public/private keys were read earlier in the execution of the function, i.e. 
before trying to decrypt a continuation value.

Aaron



--
Aaron Coburn
Systems Administrator and Programmer
Academic Technology Services, Amherst College
acob...@amherst.edu






On May 17, 2012, at 8:34 AM, Josh Thompson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, May 16, 2012 10:37:02 AM Kevan Miller wrote:
On May 11, 2012, at 3:17 PM, Josh Thompson wrote:

Kevan,

Ugh.  Thanks for looking at this.  I guess it goes to show you can't just
trust that another project that says it is MIT licensed is *completely*
MIT
licensed.  :(  I'll figure out a way to deal with it.  If it works out
that
bcpowmod.php and str_split.php are not actually needed, can I just remove
them?  If so, do I need to document that modification somewhere?

BTW, vcl/trunk/web/.ht-inc/phpseclib/index.html refers to PHP Secure
Communications Library as LGPL-licensed. Which is contradicted by
http://phpseclib.sourceforge.net/

It looks like our documentation comes from
http://phpseclib.sourceforge.net/documentation/ -- I'd check with the
phpseclib project. Seems to be their reference to LGPL is unintended or
inconsistent. bcpowmod.php's LGPL license would seem to be a problem with
this, however…

--kevan

After looking further, there are only two files (AES.php and Rijndael.php)
needed from the phpseclib project, and both of them appear as though they were
written to be able to be included by themselves (i.e. each one contains
information about the author, the project, and the license).  Both files state
that they are MIT licensed and contain that license in them.  Is it normal to
just pull in specific files from another project, or is it better to include
the whole project?

My only other experience in including another open source project in one I
work on is from including the Dojo Toolkit with VCL.  In that case, it seemed
to make the most sense to include the whole thing.

License wise, it seems simplest to just include the two files in the release,
but I just want to make sure we do the right thing in respecting other open
source projects.

Thanks,
Josh
- --
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk+08HIACgkQV/LQcNdtPQN8dgCdF/RaBttxHHuRMjuw73G9Kv34
RjYAnimOHe1R50N532Bgxi+uOjVnkgjv
=PjK8
-END PGP SIGNATURE-

Re: openstack and VCL ?

2012-05-17 Thread Young h Oh

Hi Aaron,

I've been also  working on Openstack plugin for VCL and finished the POC
test on Openstack Essex with Ubuntu 12.04 x64 server.  The reservations
works but there are still some issues on capturing (or snapshot) images in
Openstack Essex. If you can create jira issue, I could post my initial work
in details and share some configuration tips with others. Thank you.

Young Hyun Oh
IBM Tivoli

From:   Cameron Mann 
To: vcl-dev@incubator.apache.org,
Cc: vcl-u...@incubator.apache.org
Date:   04/12/2012 03:39 PM
Subject:Re: openstack and VCL ?

Hi Young,

At the moment we've tested our module with Amazon EC2 and OpenStack's
Cactus release.  Provisioning works, though there's still a few issues that
need resolving.  We're also still deciding the best approach to take with
image capture, especially for Windows images.  We definitely want to get
everyone's thoughts on this once it's open sourced.

It'll be great to get a chance to talk with you at the conference.

Cameron

On Thu, Apr 12, 2012 at 9:55 AM, Young h Oh  wrote:
  Hi Cameron,

  Sounds great. Our team are also interested in implementing the OpenStack
  Provisioning module to VCL at IBM tivioli. The stage here is also in the
  proof of concept and I've tried to build up the test environment now. But
  before I go further, I'd like to know whether you already implemented the
  openstack provisioning module or not. I'd like to avoid any duplicating
  efforts on the same work. If you already finished, please let me know.

  Also, I'll join the ICA CON 2012 and I'm looking forward to your
  presentation. We can discuss more details about your work after it. Thank
  you.

  Young

  Aaron Peeler ---03/29/2012 01:09:50 PM---Great. I'll create a jira issue
  on it to give it an initial home. You should see it come across the

  From: Aaron Peeler 
  To: Cameron Mann ,
  Cc: vcl-u...@incubator.apache.org, vcl-dev@incubator.apache.org
  Date: 03/29/2012 01:09 PM
  Subject: Re: openstack and VCL ?

  Great. I'll create a jira issue on it to give it an initial home. You
  should see it come across the vcl-dev list shortly.

  Thanks again and looking forward to your presentation.

  Aaron

  On Thu, Mar 29, 2012 at 11:08 AM, Cameron Mann 
  wrote:
  > We'd definitely be comfortable with that and should be able to do so
  within
  > the next two or three weeks.
  >
  > Cameron
  >
  >
  > On Wed, Mar 28, 2012 at 11:08 AM, Aaron Peeler 
  > wrote:
  >>
  >> Hi Cameron,
  >>
  >> That's wonderful.
  >>
  >> I understand this is a POC now, but also thats a great point in
  >> development cycle to get more eyes looking at it. Would you be
  >> comfortable (if not now, soon) submitting the work under ASF for
  >> review by the VCL community? Also with that we could work toward
  >> bringing you or your lead on this effort in as a apache vcl committer.
  >>
  >> I look forward to seeing you at ICA CON 2012
  >>
  >> Best Regards,
  >> Aaron
  >>
  >>
  >> On Wed, Mar 28, 2012 at 11:50 AM, Cameron Mann 
  >> wrote:
  >> > Hi Aaron,
  >> >
  >> > One of the things we're working on at Cybera is an EC2 provisioning
  >> > module.
  >> >  We've also done a lot of work with OpenStack and our intent is for
  the
  >> > module not just to work with Amazon EC2 but any cloud that
  implements
  >> > the
  >> > EC2 API, including OpenStack.  Right now it's very much in a proof
  of
  >> > concept state, but our intent is to open source it once some of the
  >> > rough
  >> > edges are smoothed over.
  >> >
  >> > We'll also be presenting a paper at the upcoming ICA CON 2012 on our
  >> > work so
  >> > far.
  >> >
  >> > Cameron
  >> >
  >> >
  >> > On Tue, Mar 27, 2012 at 8:28 AM, Aaron Peeler 
  >> > wrote:
  >> >>
  >> >> Hi Folks,
  >> >>
  >> >> I think Tony from ECU asked about this before.
  >> >>
  >> >> Has anyone worked with openstack http://openstack.org/ ?
  >> >>
  >> >> I think integrating openstack provisioning into the VCL framework
  >> >> would benefit VCL. It could also benefit openstack and their
  current
  >> >> users. From what I understand, Openstack has a large commercial
  base
  >> >> of users and could be a way to expose VCL to more commercial users.
  >> >>
  >> >> Unless I'm wrong, currently openstack doesn't provide a
  self-service
  >> >> interface for users to VDI or clusters, nor does it provide
  bare-metal
  >> >> loads.  VCL with xCAT could provide that for that community in a
  short
  >> >> time-frame.
  >> >>
  >> >> Is there anyone interested in investigating and working on an
  >> >> openstack provisioning module ?  I don't think it will take a huge
  >> >> amount of work, one would need to know openstack and how to add in
  a
  >> >> VCL provisioning module. I'd be willing to assist but would need
  >> >> someone to take the lead on it.
  >> >>
  >> >> Thoughts?
  >> >>
  >> >> I know this is a development question, but also felt this is big
  >> >> enough to include folks on the vcl-user list.
  >> >>
  >

Re: openstack and VCL ?

2012-05-17 Thread Aaron Peeler

Hi Young,

Thanks for the update. This sounds like good progress.

You should be able to create a jira issue using your jira account.

Let me know if you can't and I'll be happy to create one.

Aaron

On Thu, May 17, 2012 at 11:04 AM, Young h Oh  wrote:

> Hi Aaron,
>
> I've been also  working on Openstack plugin for VCL and finished the POC
> test on Openstack Essex with Ubuntu 12.04 x64 server.  The reservations
> works but there are still some issues on capturing (or snapshot) images in
> Openstack Essex. If you can create jira issue, I could post my initial work
> in details and share some configuration tips with others. Thank you.
>
> Young Hyun Oh
> IBM Tivoli
>
> [image: Inactive hide details for Cameron Mann ---04/12/2012 03:39:13
> PM---Hi Young, At the moment we've tested our module with Amazon]Cameron
> Mann ---04/12/2012 03:39:13 PM---Hi Young, At the moment we've tested our
> module with Amazon EC2 and OpenStack's
>
> From: Cameron Mann 
> To: vcl-dev@incubator.apache.org,
> Cc: vcl-u...@incubator.apache.org
> Date: 04/12/2012 03:39 PM
>
> Subject: Re: openstack and VCL ?
> --
>
>
>
> Hi Young,
>
> At the moment we've tested our module with Amazon EC2 and OpenStack's
> Cactus release.  Provisioning works, though there's still a few issues that
> need resolving.  We're also still deciding the best approach to take with
> image capture, especially for Windows images.  We definitely want to get
> everyone's thoughts on this once it's open sourced.
>
> It'll be great to get a chance to talk with you at the conference.
>
> Cameron
>
> On Thu, Apr 12, 2012 at 9:55 AM, Young h Oh 
> <*o...@us.ibm.com*>
> wrote:
>
>Hi Cameron,
>
>Sounds great. Our team are also interested in implementing the
>OpenStack Provisioning module to VCL at IBM tivioli. The stage here is also
>in the proof of concept and I've tried to build up the test environment
>now. But before I go further, I'd like to know whether you already
>implemented the openstack provisioning module or not. I'd like to avoid any
>duplicating efforts on the same work. If you already finished, please let
>me know.
>
>Also, I'll join the ICA CON 2012 and I'm looking forward to your
>presentation. We can discuss more details about your work after it. Thank
>you.
>
>Young
>
>
>Aaron Peeler ---03/29/2012 01:09:50 PM---Great. I'll create a jira
>issue on it to give it an initial home. You should see it come across the
>
>From: Aaron Peeler <*aaron_pee...@ncsu.edu* >
>To: Cameron Mann <*cameron.m...@cybera.ca* >,
>Cc: *vcl-u...@incubator.apache.org* , *
>vcl-dev@incubator.apache.org* 
>Date: 03/29/2012 01:09 PM
>Subject: Re: openstack and VCL ?
>--
>
>
>
>
>Great. I'll create a jira issue on it to give it an initial home. You
>should see it come across the vcl-dev list shortly.
>
>Thanks again and looking forward to your presentation.
>
>Aaron
>
>On Thu, Mar 29, 2012 at 11:08 AM, Cameron Mann <*cameron.m...@cybera.ca
>* > wrote:
>> We'd definitely be comfortable with that and should be able to do so
>within
>> the next two or three weeks.
>>
>> Cameron
>>
>>
>> On Wed, Mar 28, 2012 at 11:08 AM, Aaron Peeler <*
>aaron_pee...@ncsu.edu* >
>> wrote:
>>>
>>> Hi Cameron,
>>>
>>> That's wonderful.
>>>
>>> I understand this is a POC now, but also thats a great point in
>>> development cycle to get more eyes looking at it. Would you be
>>> comfortable (if not now, soon) submitting the work under ASF for
>>> review by the VCL community? Also with that we could work toward
>>> bringing you or your lead on this effort in as a apache vcl
>committer.
>>>
>>> I look forward to seeing you at ICA CON 2012
>>>
>>> Best Regards,
>>> Aaron
>>>
>>>
>>> On Wed, Mar 28, 2012 at 11:50 AM, Cameron Mann <*
>cameron.m...@cybera.ca* >
>>> wrote:
>>> > Hi Aaron,
>>> >
>>> > One of the things we're working on at Cybera is an EC2
>provisioning
>>> > module.
>>> >  We've also done a lot of work with OpenStack and our intent is
>for the
>>> > module not just to work with Amazon EC2 but any cloud that
>implements
>>> > the
>>> > EC2 API, including OpenStack.  Right now it's very much in a
>proof of
>>> > concept state, but our intent is to open source it once some of
>the
>>> > rough
>>> > edges are smoothed over.
>>> >
>>> > We'll also be presenting a paper at the upcoming ICA CON 2012 on
>our
>>> > work so
>>> > far.
>>> >
>>> > Cameron
>>> >
>>> >
>>> > On Tue, Mar 27, 2012 at 8:28 AM, Aaron Peeler <*
>aaron_pee...@ncsu.edu* >
>>> > wrote:
>>> >>
>>> >> Hi Folks,
>>> >>
>>> >> I think Tony from ECU asked about this before.
>>> >>
>>> >> Has anyone worked with openstack 
>

Re: MIT licensed source code

2012-05-17 Thread Kevan Miller

On May 17, 2012, at 8:34 AM, Josh Thompson wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Wednesday, May 16, 2012 10:37:02 AM Kevan Miller wrote:
>> On May 11, 2012, at 3:17 PM, Josh Thompson wrote:
>>> 
>>> Kevan,
>>> 
>>> Ugh.  Thanks for looking at this.  I guess it goes to show you can't just
>>> trust that another project that says it is MIT licensed is *completely*
>>> MIT
>>> licensed.  :(  I'll figure out a way to deal with it.  If it works out
>>> that
>>> bcpowmod.php and str_split.php are not actually needed, can I just remove
>>> them?  If so, do I need to document that modification somewhere?
>> 
>> BTW, vcl/trunk/web/.ht-inc/phpseclib/index.html refers to PHP Secure
>> Communications Library as LGPL-licensed. Which is contradicted by
>> http://phpseclib.sourceforge.net/
>> 
>> It looks like our documentation comes from
>> http://phpseclib.sourceforge.net/documentation/ -- I'd check with the
>> phpseclib project. Seems to be their reference to LGPL is unintended or
>> inconsistent. bcpowmod.php's LGPL license would seem to be a problem with
>> this, however…
>> 
>> --kevan
> 
> After looking further, there are only two files (AES.php and Rijndael.php)
> needed from the phpseclib project, and both of them appear as though they were
> written to be able to be included by themselves (i.e. each one contains
> information about the author, the project, and the license).  Both files state
> that they are MIT licensed and contain that license in them.  Is it normal to
> just pull in specific files from another project, or is it better to include
> the whole project?

First, I should say that all my comments are from a purely procedural nature… 
I'm not making any comments on the function.

It's more "normall" to pull in whole projects. Certainly true when you're pull 
in as dependencies. Advantage is that as fixes are made to original library, 
you pull in as a dependency (and don't have to migrate any source fixes). More 
later...

That doesn't mean that whole projects is "better". Both can be equally correct. 
In this case, only pulling in the two files would seem perfectly fine to me.

Can I please ask that the LGPL files be removed from SVN immediately? Please 
treat this as a -1 on the original svn commit as the commit contains LGPL 
licensed code. Removing the offending files from svn will address my veto.

As a (final?) piece of mentor education, see:

http://www.apache.org/foundation/voting.html#votes-on-code-modification
http://www.apache.org/foundation/voting.html#Veto

> 
> My only other experience in including another open source project in one I
> work on is from including the Dojo Toolkit with VCL.  In that case, it seemed
> to make the most sense to include the whole thing.

Right. So, both techniques are used. Which is most appropriate, depends on the 
situation.

> 
> License wise, it seems simplest to just include the two files in the release,
> but I just want to make sure we do the right thing in respecting other open
> source projects.

In general copying code is less desirable than including released software from 
another project. A description of this practice (with negative connotations) 
would be "forking" (though forking usually refers to an entire project). In 
general, we'd prefer to collaborate with other projects, rather than copy their 
code. 

However, open source gives us the flexibility to choose. And we should feel 
free to choose what best fits the needs of the project -- taking all factors 
into account...

In this case, we should definitely raise the licensing questions that have been 
raised with the phpseclib project (no matter how we resolve the issue). And, by 
the way, perhaps there was a mistake made and those files aren't LGPL -- we may 
learn something...

--kevan

Re: VCL-543 OSX under ESXi 4.1

2012-05-17 Thread James O'Dell

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Andy,

Thanks for the head's up. I'll check on the 'currentimage.txt' lines.

Currently, I've found that there are at least 3 additional subroutines
required for 2.3. I'm in the process of writing the following
subroutines.

'check_connection_on_port'
'get_cpu_core_count'
'enable_firewall_port'

Josh already made a change to the 'requests.php' that I needed.

I'll grap a copy of OSX.pm from the repository, and make sure
to include the indentation/space changes. (I'll also remove
the comments I left to myself.. sry)

__Jim

On 5/17/2012 7:06 AM, Andy Kurth wrote:
> Hi Jim,
> I made a commit to OSX.pm this morning.  I mainly changed the
> indentation.  For the most part, the Perl code is indented using tabs.
> 
> I also made some minor indentation/spacing changes to the pod sections
> so that the output lined up when running pod2text, etc.  These
> sections must be indented using spaces.
> 
> None of the code functionality should have changed except for possibly
> one location.  My editor was complaining about lines 1843/1844 in the
> previous revision:
> 1843: #$command .= " && sed -i '' -e \'s/
> 1844: //g\' currentimage.txt";
> 
> I'm assuming both of these lines should be commented.  I changed it to:
> 1783: #   $command .= " && sed -i '' -e \'s///g\' 
> currentimage.txt";
> 
> Please do an 'svn up' and make sure I didn't mess anything up.
> 
> Thanks,
> Andy
> 
> On Wed, Apr 4, 2012 at 3:10 PM, Aaron Peeler  wrote:
>> Hi Jim,
>>
>> Made progress to a point, I wasn't able to get a full blown instance
>> going, but I feel my effort was good enough to prove it can be done
>> and used. Overall the code looks good and as we move forward, possibly
>> in the 2.4 release, I think it would be ideal to put all OS related
>> routines in their respective OS modules, like
>> notify_via_(wall,msg,oascript), etc.
>>
>> In the supporting documentation for this on the vcl wiki somewhere, I
>> recommend to list known working apple hardware. So far I can say that
>> it would work with the Mac Mini 2011 model and your running it on
>> MacPro.
>>
>> I'll work on committing the backend and db components it into trunk on
>> your behalf. I think Josh has already committed the php part.
>>
>> Thanks for the work and sorry it took so long to review it.
>>
>> Aaron
>>
>>
>> On Wed, Apr 4, 2012 at 7:49 AM, Aaron Peeler  wrote:
>>> Thanks Jim.
>>>
>>> Right, I saw that one also. I've got a 2010 mac mini model which also
>>> has the keyboard issue.  Doesn't seem like it's feasible to use the
>>> 2010 model. Going to give it one more shot with trying to do a
>>> kickstart install off the dvd. It that doesn't work then I'll try to
>>> locate a 2011 model.
>>>
>>> Overall your code looks good and should work - just would like to test it.
>>>
>>> Aaron
>>>
>>>
>>> On Tue, Apr 3, 2012 at 4:35 PM, James O'Dell  wrote:
> This site gives a walk through installing OSX on a mac mini
> using esxi 5. It lists the hardware used, and a link to
> vmware's nic driver.
> 
>> http://paraguin.com/2012/01/17/os-x-on-a-mac-mini-with-vmware-esxi-5/
> 
> __Jim
> 
> On 4/3/2012 11:48 AM, Aaron Peeler wrote:
>> Hi Daiyu,
>>
>> Thanks. Yes those are a couple that I had found.
>>
>> Aaron
>>
>> On Tue, Apr 3, 2012 at 2:35 PM, Hayashi, Daiyu
>>  wrote:
>>> Based on your email I take it that you've read these posts.
>>>
>>> http://paraguin.com/2012/01/10/the-mac-mini-vmware-esxi-5-server-part-1-research/
>>>
>>> http://tinkertry.com/maczilla-core-i5-mac-mini-esxi-5-0-update-1/
>>>
>>>
>>> Daiyu Hayashi
>>> Lead Information Technology Consultant
>>> Mihaylo College of Business and Economics
>>> Cal State University Fullerton
>>> 657-278-7347
>>>
>>>
>>>
>>>
>>> -Original Message-
>>> From: Aaron Peeler [mailto:fapee...@ncsu.edu]
>>> Sent: Tuesday, April 03, 2012 6:28 AM
>>> To: vcl-dev@incubator.apache.org
>>> Subject: VCL-543 OSX under ESXi 4.1
>>>
>>> Jim,
>>>
>>> I'm working on testing the OSX module for inclusion in the next release 
>>> and run into some questions.
>>>
>>> By chance have you tried to use other apple hardware? I've got a  mac 
>>> mini (2010 mid) model.
>>>
>>> The initial issue I've run into is the usb keyboard gets disabled once 
>>> the vmware kernel is loaded. In searching on a solution for this, I've 
>>> run across folks stating that there is a missing network adapter as 
>>> well and that has to added later.
>>>
>>> I'm going to attempt to install ESXi on a usb drive and boot the mac 
>>> mini off of that (hopefully).
>>>
>>> So I was wondering if you've installed ESXi (either 4.1 or 5 ) on a mac 
>>> mini yet?
>>>
>>> Thanks,
>>> Aaron
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State Universi

Re: MIT licensed source code

2012-05-17 Thread Josh Thompson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday, May 17, 2012 11:45:00 AM Kevan Miller wrote:
> On May 17, 2012, at 8:34 AM, Josh Thompson wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Wednesday, May 16, 2012 10:37:02 AM Kevan Miller wrote:
> >> On May 11, 2012, at 3:17 PM, Josh Thompson wrote:
> >>> Kevan,
> >>>
> >>> Ugh.  Thanks for looking at this.  I guess it goes to show you can't
> >>> just
> >>> trust that another project that says it is MIT licensed is *completely*
> >>> MIT
> >>> licensed.  :(  I'll figure out a way to deal with it.  If it works out
> >>> that
> >>> bcpowmod.php and str_split.php are not actually needed, can I just
> >>> remove
> >>> them?  If so, do I need to document that modification somewhere?
> >>
> >> BTW, vcl/trunk/web/.ht-inc/phpseclib/index.html refers to PHP Secure
> >> Communications Library as LGPL-licensed. Which is contradicted by
> >> http://phpseclib.sourceforge.net/
> >>
> >> It looks like our documentation comes from
> >> http://phpseclib.sourceforge.net/documentation/ -- I'd check with the
> >> phpseclib project. Seems to be their reference to LGPL is unintended or
> >> inconsistent. bcpowmod.php's LGPL license would seem to be a problem with
> >> this, however…
> >>
> >> --kevan
> >
> > After looking further, there are only two files (AES.php and Rijndael.php)
> > needed from the phpseclib project, and both of them appear as though they
> > were written to be able to be included by themselves (i.e. each one
> > contains information about the author, the project, and the license).
> > Both files state that they are MIT licensed and contain that license in
> > them.  Is it normal to just pull in specific files from another project,
> > or is it better to include the whole project?
>
> First, I should say that all my comments are from a purely procedural
> nature… I'm not making any comments on the function.
>
> It's more "normall" to pull in whole projects. Certainly true when you're
> pull in as dependencies. Advantage is that as fixes are made to original
> library, you pull in as a dependency (and don't have to migrate any source
> fixes). More later...
>
> That doesn't mean that whole projects is "better". Both can be equally
> correct. In this case, only pulling in the two files would seem perfectly
> fine to me.
>
> Can I please ask that the LGPL files be removed from SVN immediately? Please
> treat this as a -1 on the original svn commit as the commit contains LGPL
> licensed code. Removing the offending files from svn will address my veto.
>
> As a (final?) piece of mentor education, see:
>
> http://www.apache.org/foundation/voting.html#votes-on-code-modification
> http://www.apache.org/foundation/voting.html#Veto
>
> > My only other experience in including another open source project in one I
> > work on is from including the Dojo Toolkit with VCL.  In that case, it
> > seemed to make the most sense to include the whole thing.
>
> Right. So, both techniques are used. Which is most appropriate, depends on
> the situation.
> > License wise, it seems simplest to just include the two files in the
> > release, but I just want to make sure we do the right thing in respecting
> > other open source projects.
>
> In general copying code is less desirable than including released software
> from another project. A description of this practice (with negative
> connotations) would be "forking" (though forking usually refers to an
> entire project). In general, we'd prefer to collaborate with other
> projects, rather than copy their code.
>
> However, open source gives us the flexibility to choose. And we should feel
> free to choose what best fits the needs of the project -- taking all
> factors into account...
>
> In this case, we should definitely raise the licensing questions that have
> been raised with the phpseclib project (no matter how we resolve the
> issue). And, by the way, perhaps there was a mistake made and those files
> aren't LGPL -- we may learn something...
>
> --kevan

Kevan,

Thanks for your thoughts and pointing out the code modification veto process
(I wasn't aware of that).  I removed the offending files and emailed the
project maintainer regarding the discrepancy in licensing.

Josh
- --
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk+1YJEACgkQV/LQcNdtPQMdqwCfVL0kJ7yWds73jEi+Xe4Uo7iu
m/0AnjSIpFn1UjAbDNCIMMsIO0Ew1MVd
=SR3z
-END PGP SIGNATURE-

Re: MIT licensed source code

2012-05-17 Thread Josh Thompson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Aaron,

Good thoughts, and thanks for "asking the obvious".  I vaguely remember
considering using openssl instead of mcrypt when I initially wrote that code.
I think the only reason I decided to use mcrypt was that it was symmetric key
based, making it quite a bit faster.  It probably doesn't introduce enough
delay to really matter, but just doing some tests now, I found using
openssl_public_encrypt/openssl_private_decrypt to be around 15 times slower
than the current code.

If it wasn't for what I see to be a useful exercise in dealing with possibly
incompatible code from another project, I'd go ahead and switch to openssl,
using the symmetric functions if available and the asymmetric ones if not.
For now, I think I'll go ahead and finish working through the issue with
phpseclib.

Josh

On Thursday, May 17, 2012 2:26:55 PM Aaron Coburn wrote:
> Just to ask the obvious Why not just use the openssl library for this?
> Especially since the public and private keys are already being loaded in
> the initGlobals() function. I know that it's interface is not nearly so
> nice, and it doesn't support symmetric encryption for PHP <= 5.3, but
> here's some code that could be dropped in place in utils.php:
>
> function encryptData($data){
> global $keys;
> if(! $data)
> return false;
> openssl_public_encrypt(
> $data,
> $encrypted,
> $keys['public']);
> return trim(base64_encode($encrypted));
> }
>
> function decryptData($data){
> global $keys;
> if(! $data)
> return false;
> openssl_private_decrypt(
> base64_decode($data),
> $decrypted,
> $keys['private']);
> return trim($decrypted);
> }
>
> The other change would require modifying the initGlobals() function so that
> the public/private keys were read earlier in the execution of the function,
> i.e. before trying to decrypt a continuation value.
>
> Aaron
>
>
>
> --
> Aaron Coburn
> Systems Administrator and Programmer
> Academic Technology Services, Amherst College
> acob...@amherst.edu
>
>
>
>
>
>
> On May 17, 2012, at 8:34 AM, Josh Thompson wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday, May 16, 2012 10:37:02 AM Kevan Miller wrote:
> On May 11, 2012, at 3:17 PM, Josh Thompson wrote:
>
> Kevan,
>
> Ugh.  Thanks for looking at this.  I guess it goes to show you can't just
> trust that another project that says it is MIT licensed is *completely*
> MIT
> licensed.  :(  I'll figure out a way to deal with it.  If it works out
> that
> bcpowmod.php and str_split.php are not actually needed, can I just remove
> them?  If so, do I need to document that modification somewhere?
>
> BTW, vcl/trunk/web/.ht-inc/phpseclib/index.html refers to PHP Secure
> Communications Library as LGPL-licensed. Which is contradicted by
> http://phpseclib.sourceforge.net/
>
> It looks like our documentation comes from
> http://phpseclib.sourceforge.net/documentation/ -- I'd check with the
> phpseclib project. Seems to be their reference to LGPL is unintended or
> inconsistent. bcpowmod.php's LGPL license would seem to be a problem with
> this, however…
>
> --kevan
>
> After looking further, there are only two files (AES.php and Rijndael.php)
> needed from the phpseclib project, and both of them appear as though they
> were written to be able to be included by themselves (i.e. each one
> contains information about the author, the project, and the license).  Both
> files state that they are MIT licensed and contain that license in them.
> Is it normal to just pull in specific files from another project, or is it
> better to include the whole project?
>
> My only other experience in including another open source project in one I
> work on is from including the Dojo Toolkit with VCL.  In that case, it
> seemed to make the most sense to include the whole thing.
>
> License wise, it seems simplest to just include the two files in the
> release, but I just want to make sure we do the right thing in respecting
> other open source projects.
>
> Thanks,
> Josh
> - --
> - ---
> Josh Thompson
> VCL Developer
> North Carolina State University
>
> my GPG/PGP key can be found at pgp.mit.edu
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.17 (GNU/Linux)
>
> iEYEARECAAYFAk+08HIACgkQV/LQcNdtPQN8dgCdF/RaBttxHHuRMjuw73G9Kv34
> RjYAnimOHe1R50N532Bgxi+uOjVnkgjv
> =PjK8
> -END PGP SIGNATURE-
- --
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account

Re: MIT licensed source code

2012-05-17 Thread Kevan Miller

On May 17, 2012, at 4:33 PM, Josh Thompson wrote:

> Thanks for your thoughts and pointing out the code modification veto process
> (I wasn't aware of that).  I removed the offending files and emailed the
> project maintainer regarding the discrepancy in licensing.

Cool. Thanks Josh. 

In most projects, Veto's are pretty rare. However, they are an important part 
of the ASF process. 

--kevan

Re: VCL-543 OSX under ESXi 4.1

2012-05-17 Thread James O'Dell

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andy,

The 'currentimage.txt' line you were referring to was originally one
line, and it was commented out.

Chances are, the reason the 'currentimage.txt' line looks weird
is probably due to you looking at it from a windows system.

The original code has the line commented out. The line contains
a 'ctrl-M', which windows is interpreting as a carriage return.
So windows breaks the one line into 2 lines at the carriage return
(aka ctrl-M).

i.e.
Original Linux
> #   # remove carriage returns
> #$command .= " && sed -i '' -e \'s/^M//g\' currentimage.txt";

Window's
> #   # remove carriage returns
> #   $command .= " && sed -i '' -e \'s/
> //g\' currentimage.txt";


I'm thinking the whole mess should be removed to avoid any problems.

I'm sure you already know this, but Windows and Linux text files
terminate lines differently..

Windows = +
Linux/MAC OSX   = 

Hope this helps,

__Jim

On 5/17/2012 7:06 AM, Andy Kurth wrote:
> Hi Jim,
> I made a commit to OSX.pm this morning.  I mainly changed the
> indentation.  For the most part, the Perl code is indented using tabs.
> 
> I also made some minor indentation/spacing changes to the pod sections
> so that the output lined up when running pod2text, etc.  These
> sections must be indented using spaces.
> 
> None of the code functionality should have changed except for possibly
> one location.  My editor was complaining about lines 1843/1844 in the
> previous revision:
> 1843: #$command .= " && sed -i '' -e \'s/
> 1844: //g\' currentimage.txt";
> 
> I'm assuming both of these lines should be commented.  I changed it to:
> 1783: #   $command .= " && sed -i '' -e \'s///g\' 
> currentimage.txt";
> 
> Please do an 'svn up' and make sure I didn't mess anything up.
> 
> Thanks,
> Andy
> 
> On Wed, Apr 4, 2012 at 3:10 PM, Aaron Peeler  wrote:
>> Hi Jim,
>>
>> Made progress to a point, I wasn't able to get a full blown instance
>> going, but I feel my effort was good enough to prove it can be done
>> and used. Overall the code looks good and as we move forward, possibly
>> in the 2.4 release, I think it would be ideal to put all OS related
>> routines in their respective OS modules, like
>> notify_via_(wall,msg,oascript), etc.
>>
>> In the supporting documentation for this on the vcl wiki somewhere, I
>> recommend to list known working apple hardware. So far I can say that
>> it would work with the Mac Mini 2011 model and your running it on
>> MacPro.
>>
>> I'll work on committing the backend and db components it into trunk on
>> your behalf. I think Josh has already committed the php part.
>>
>> Thanks for the work and sorry it took so long to review it.
>>
>> Aaron
>>
>>
>> On Wed, Apr 4, 2012 at 7:49 AM, Aaron Peeler  wrote:
>>> Thanks Jim.
>>>
>>> Right, I saw that one also. I've got a 2010 mac mini model which also
>>> has the keyboard issue.  Doesn't seem like it's feasible to use the
>>> 2010 model. Going to give it one more shot with trying to do a
>>> kickstart install off the dvd. It that doesn't work then I'll try to
>>> locate a 2011 model.
>>>
>>> Overall your code looks good and should work - just would like to test it.
>>>
>>> Aaron
>>>
>>>
>>> On Tue, Apr 3, 2012 at 4:35 PM, James O'Dell  wrote:
> This site gives a walk through installing OSX on a mac mini
> using esxi 5. It lists the hardware used, and a link to
> vmware's nic driver.
> 
>> http://paraguin.com/2012/01/17/os-x-on-a-mac-mini-with-vmware-esxi-5/
> 
> __Jim
> 
> On 4/3/2012 11:48 AM, Aaron Peeler wrote:
>> Hi Daiyu,
>>
>> Thanks. Yes those are a couple that I had found.
>>
>> Aaron
>>
>> On Tue, Apr 3, 2012 at 2:35 PM, Hayashi, Daiyu
>>  wrote:
>>> Based on your email I take it that you've read these posts.
>>>
>>> http://paraguin.com/2012/01/10/the-mac-mini-vmware-esxi-5-server-part-1-research/
>>>
>>> http://tinkertry.com/maczilla-core-i5-mac-mini-esxi-5-0-update-1/
>>>
>>>
>>> Daiyu Hayashi
>>> Lead Information Technology Consultant
>>> Mihaylo College of Business and Economics
>>> Cal State University Fullerton
>>> 657-278-7347
>>>
>>>
>>>
>>>
>>> -Original Message-
>>> From: Aaron Peeler [mailto:fapee...@ncsu.edu]
>>> Sent: Tuesday, April 03, 2012 6:28 AM
>>> To: vcl-dev@incubator.apache.org
>>> Subject: VCL-543 OSX under ESXi 4.1
>>>
>>> Jim,
>>>
>>> I'm working on testing the OSX module for inclusion in the next release 
>>> and run into some questions.
>>>
>>> By chance have you tried to use other apple hardware? I've got a  mac 
>>> mini (2010 mid) model.
>>>
>>> The initial issue I've run into is the usb keyboard gets disabled once 
>>> the vmware kernel is loaded. In searching on a solution for this, I've 
>>> run across folks stating that there is a missing network adapter as 
>>> well an

Re: VCL-543 OSX under ESXi 4.1

2012-05-17 Thread Aaron Peeler

Hi Jim,

I have another routine to add to OSX.pm. user_exists. It was mainly
needed for the server reservations.

It's using the id cmd, so it shouldn't need any changes. But since it
wouldn't work for windows, I couldn't put it in the OS.pm module.


=head2 user_exists

 Parameters  :
 Returns :
 Description :

=cut

sub user_exists {
my $self = shift;
if (ref($self) !~ /linux/i) {
notify($ERRORS{'CRITICAL'}, 0, "subroutine was called
as a function, it must be called as a class method");
return;
}

my $management_node_keys = $self->data->get_management_node_keys();
my $computer_node_name   = $self->data->get_computer_node_name();
 # Attempt to get the username from the arguments
# If no argument was supplied, use the user specified in the
DataStructure
my $username = shift;
if (!$username) {
$username = $self->data->get_user_login_id();
}

   notify($ERRORS{'DEBUG'}, 0, "checking if user $username exists on
$computer_node_name");

# Attempt to query the user account
my $query_user_command = "id $username";
my ($query_user_exit_status, $query_user_output) =
$self->execute($query_user_command,1);
   if (grep(/uid/, @$query_user_output)) {
   notify($ERRORS{'DEBUG'}, 0, "user $username exists on
$computer_node_name");
   return 1;
   }
   elsif (grep(/No such user/i, @$query_user_output)) {
   notify($ERRORS{'DEBUG'}, 0, "user $username does not exist on
$computer_node_name");
   return 0;
   }
   elsif (defined($query_user_exit_status)) {

   notify($ERRORS{'WARNING'}, 0, "failed to determine if
user $username exists on $computer_node_name, exit status:
$query_user_exit_status, output:\n@{$query_user_output}");
   return;
   }
   else {
   notify($ERRORS{'WARNING'}, 0, "failed to run ssh
command to determine if user $username exists on
$computer_node_name");
   return;
   }

}





On Thu, May 17, 2012 at 5:26 PM, James O'Dell  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Andy,
>
> The 'currentimage.txt' line you were referring to was originally one
> line, and it was commented out.
>
> Chances are, the reason the 'currentimage.txt' line looks weird
> is probably due to you looking at it from a windows system.
>
> The original code has the line commented out. The line contains
> a 'ctrl-M', which windows is interpreting as a carriage return.
> So windows breaks the one line into 2 lines at the carriage return
> (aka ctrl-M).
>
> i.e.
> Original Linux
>> #       # remove carriage returns
>> #        $command .= " && sed -i '' -e \'s/^M//g\' currentimage.txt";
>
> Window's
>>         #       # remove carriage returns
>>         #               $command .= " && sed -i '' -e \'s/
>> //g\' currentimage.txt";
>
>
> I'm thinking the whole mess should be removed to avoid any problems.
>
> I'm sure you already know this, but Windows and Linux text files
> terminate lines differently..
>
> Windows         = +
> Linux/MAC OSX   = 
>
> Hope this helps,
>
> __Jim
>
> On 5/17/2012 7:06 AM, Andy Kurth wrote:
>> Hi Jim,
>> I made a commit to OSX.pm this morning.  I mainly changed the
>> indentation.  For the most part, the Perl code is indented using tabs.
>>
>> I also made some minor indentation/spacing changes to the pod sections
>> so that the output lined up when running pod2text, etc.  These
>> sections must be indented using spaces.
>>
>> None of the code functionality should have changed except for possibly
>> one location.  My editor was complaining about lines 1843/1844 in the
>> previous revision:
>> 1843: #        $command .= " && sed -i '' -e \'s/
>> 1844: //g\' currentimage.txt";
>>
>> I'm assuming both of these lines should be commented.  I changed it to:
>> 1783: #               $command .= " && sed -i '' -e \'s///g\' 
>> currentimage.txt";
>>
>> Please do an 'svn up' and make sure I didn't mess anything up.
>>
>> Thanks,
>> Andy
>>
>> On Wed, Apr 4, 2012 at 3:10 PM, Aaron Peeler  wrote:
>>> Hi Jim,
>>>
>>> Made progress to a point, I wasn't able to get a full blown instance
>>> going, but I feel my effort was good enough to prove it can be done
>>> and used. Overall the code looks good and as we move forward, possibly
>>> in the 2.4 release, I think it would be ideal to put all OS related
>>> routines in their respective OS modules, like
>>> notify_via_(wall,msg,oascript), etc.
>>>
>>> In the supporting documentation for this on the vcl wiki somewhere, I
>>> recommend to list known working apple hardware. So far I can say that
>>> it would work with the Mac Mini 2011 model and your running it on
>>> MacPro.
>>>
>>> I'll work on committing the backend and db components it into trunk on
>>> your behalf. I think Josh has already committed the php part.
>>>
>>> Thanks for the work and sorry it took so long to review it.
>>>
>>> Aaro

Re: Install of Management Node

Re: MIT licensed source code

Re: VCL-543 OSX under ESXi 4.1

Re: MIT licensed source code

Re: openstack and VCL ?

Re: openstack and VCL ?

Re: MIT licensed source code

Re: VCL-543 OSX under ESXi 4.1

Re: MIT licensed source code

Re: MIT licensed source code

Re: MIT licensed source code

Re: VCL-543 OSX under ESXi 4.1

Re: VCL-543 OSX under ESXi 4.1

13 matches

Site Navigation

Mail list logo

Footer information