You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by Adrian Cole <ad...@jclouds.org> on 2011/02/06 21:13:02 UTC
isolated runurl testing
Hi, guys.
I'm sure that there's been discussion about this, but I wanted to call
attention to something. Implementing WHIRR-124 was pretty tough due to
needing changes to runurl scripts. In WHIRR-124, provider keys are now
different, and these are hard-coded in the runurl scripts. I don't even
know where the version control is for these scripts. I'd like to be able
to change my local copy of hadoop's post-configure and not have to worry
about who's using the public s3 bucket at the time, and I'd like to push
changes to runurl scripts as a part of a patch.
How close are we to being able to isolate tests to only use files or code in
a local checkout of svn?
Cheers,
-Adrian
Re: isolated runurl testing
Posted by Adrian Cole <ad...@jclouds.org>.
Thanks. I think I'll just do this as a part of WHIRR-124
-a
On Sun, Feb 6, 2011 at 9:58 PM, Tom White <to...@cloudera.com> wrote:
> On Sun, Feb 6, 2011 at 9:53 PM, Adrian Cole <ad...@jclouds.org> wrote:
> > Thanks, Tom.
> >
> > Is it possible to update all of the whirr runurl scripts that reference
> the
> > provider "ec2" to also accept "aws-ec2" ? This will buy a little time,
> and
> > allow 124 to not have ugly hacks :)
>
> This sounds fine to me. Can you open a JIRA, or just do it as a part
> of WHIRR-124?
>
> >
> > -A
> >
> > On Sun, Feb 6, 2011 at 9:43 PM, Tom White <to...@gmail.com> wrote:
> >
> >> Hi Adrian,
> >>
> >> This is a known problem, and I'd like to remove the default dependency
> >> on S3 for hosting scripts. There's a proposal on
> >> https://issues.apache.org/jira/browse/WHIRR-225 for how to migrate
> >> away from this. Please let us know your thoughts!
> >>
> >> In the meantime, you can set the whirr.run-url-base property to point
> >> to another S3 bucket (or any webserver) to host a variant of the
> >> scripts for testing/customization.
> >>
> >> Cheers,
> >> Tom
> >>
> >> On Sun, Feb 6, 2011 at 12:13 PM, Adrian Cole <ad...@jclouds.org>
> wrote:
> >> > Hi, guys.
> >> >
> >> > I'm sure that there's been discussion about this, but I wanted to call
> >> > attention to something. Implementing WHIRR-124 was pretty tough due
> to
> >> > needing changes to runurl scripts. In WHIRR-124, provider keys are
> now
> >> > different, and these are hard-coded in the runurl scripts. I don't
> even
> >> > know where the version control is for these scripts. I'd like to be
> >> able
> >> > to change my local copy of hadoop's post-configure and not have to
> worry
> >> > about who's using the public s3 bucket at the time, and I'd like to
> push
> >> > changes to runurl scripts as a part of a patch.
> >> >
> >> > How close are we to being able to isolate tests to only use files or
> code
> >> in
> >> > a local checkout of svn?
> >> >
> >> > Cheers,
> >> > -Adrian
> >> >
> >>
> >
>
Re: isolated runurl testing
Posted by Tom White <to...@cloudera.com>.
On Sun, Feb 6, 2011 at 9:53 PM, Adrian Cole <ad...@jclouds.org> wrote:
> Thanks, Tom.
>
> Is it possible to update all of the whirr runurl scripts that reference the
> provider "ec2" to also accept "aws-ec2" ? This will buy a little time, and
> allow 124 to not have ugly hacks :)
This sounds fine to me. Can you open a JIRA, or just do it as a part
of WHIRR-124?
>
> -A
>
> On Sun, Feb 6, 2011 at 9:43 PM, Tom White <to...@gmail.com> wrote:
>
>> Hi Adrian,
>>
>> This is a known problem, and I'd like to remove the default dependency
>> on S3 for hosting scripts. There's a proposal on
>> https://issues.apache.org/jira/browse/WHIRR-225 for how to migrate
>> away from this. Please let us know your thoughts!
>>
>> In the meantime, you can set the whirr.run-url-base property to point
>> to another S3 bucket (or any webserver) to host a variant of the
>> scripts for testing/customization.
>>
>> Cheers,
>> Tom
>>
>> On Sun, Feb 6, 2011 at 12:13 PM, Adrian Cole <ad...@jclouds.org> wrote:
>> > Hi, guys.
>> >
>> > I'm sure that there's been discussion about this, but I wanted to call
>> > attention to something. Implementing WHIRR-124 was pretty tough due to
>> > needing changes to runurl scripts. In WHIRR-124, provider keys are now
>> > different, and these are hard-coded in the runurl scripts. I don't even
>> > know where the version control is for these scripts. I'd like to be
>> able
>> > to change my local copy of hadoop's post-configure and not have to worry
>> > about who's using the public s3 bucket at the time, and I'd like to push
>> > changes to runurl scripts as a part of a patch.
>> >
>> > How close are we to being able to isolate tests to only use files or code
>> in
>> > a local checkout of svn?
>> >
>> > Cheers,
>> > -Adrian
>> >
>>
>
Re: isolated runurl testing
Posted by Adrian Cole <ad...@jclouds.org>.
Thanks, Tom.
Is it possible to update all of the whirr runurl scripts that reference the
provider "ec2" to also accept "aws-ec2" ? This will buy a little time, and
allow 124 to not have ugly hacks :)
-A
On Sun, Feb 6, 2011 at 9:43 PM, Tom White <to...@gmail.com> wrote:
> Hi Adrian,
>
> This is a known problem, and I'd like to remove the default dependency
> on S3 for hosting scripts. There's a proposal on
> https://issues.apache.org/jira/browse/WHIRR-225 for how to migrate
> away from this. Please let us know your thoughts!
>
> In the meantime, you can set the whirr.run-url-base property to point
> to another S3 bucket (or any webserver) to host a variant of the
> scripts for testing/customization.
>
> Cheers,
> Tom
>
> On Sun, Feb 6, 2011 at 12:13 PM, Adrian Cole <ad...@jclouds.org> wrote:
> > Hi, guys.
> >
> > I'm sure that there's been discussion about this, but I wanted to call
> > attention to something. Implementing WHIRR-124 was pretty tough due to
> > needing changes to runurl scripts. In WHIRR-124, provider keys are now
> > different, and these are hard-coded in the runurl scripts. I don't even
> > know where the version control is for these scripts. I'd like to be
> able
> > to change my local copy of hadoop's post-configure and not have to worry
> > about who's using the public s3 bucket at the time, and I'd like to push
> > changes to runurl scripts as a part of a patch.
> >
> > How close are we to being able to isolate tests to only use files or code
> in
> > a local checkout of svn?
> >
> > Cheers,
> > -Adrian
> >
>
Re: isolated runurl testing
Posted by Tom White <to...@gmail.com>.
Hi Adrian,
This is a known problem, and I'd like to remove the default dependency
on S3 for hosting scripts. There's a proposal on
https://issues.apache.org/jira/browse/WHIRR-225 for how to migrate
away from this. Please let us know your thoughts!
In the meantime, you can set the whirr.run-url-base property to point
to another S3 bucket (or any webserver) to host a variant of the
scripts for testing/customization.
Cheers,
Tom
On Sun, Feb 6, 2011 at 12:13 PM, Adrian Cole <ad...@jclouds.org> wrote:
> Hi, guys.
>
> I'm sure that there's been discussion about this, but I wanted to call
> attention to something. Implementing WHIRR-124 was pretty tough due to
> needing changes to runurl scripts. In WHIRR-124, provider keys are now
> different, and these are hard-coded in the runurl scripts. I don't even
> know where the version control is for these scripts. I'd like to be able
> to change my local copy of hadoop's post-configure and not have to worry
> about who's using the public s3 bucket at the time, and I'd like to push
> changes to runurl scripts as a part of a patch.
>
> How close are we to being able to isolate tests to only use files or code in
> a local checkout of svn?
>
> Cheers,
> -Adrian
>