[Spacewalk-devel] Informal Devel Environment Survey
paji at redhat.com
Sat Jan 24 00:09:28 EST 2009
My setup involves the following
1) Workstation with Fedora on it. This workstation has eclipse +
sudo yum install ant-nodeps junit ant-junit java-1.6.0-openjdk-devel
sudo rpm -Uvh
it also has a checkout of the spacewalk git repo.
The checkout directory has the code directory listed in /etc/exports to
make it available across systems for NFS mount.
It also has a Vmware Server running on it with a Rhel 5 VM.
2) The Rhel 5 VM has Spacewalk setup from the
https://fedorahosted.org/spacewalk/wiki/HowToInstall instructions ..
I then go to
I skip the git checkoout part and instead mount the directory exported
from fedora.., I follow every other step formt he development
Idea is to do the development + compilation using the Eclipse IDE on
Fedora and runtime with ant/tomcat5/apache etc on Rhel 5 where a
'spacewalk-like' environemnt is present.
Trick is to maintain the same directory structure + user permission
(including same UID + GIDs) information across both machines..
so for example if the git directory is in
/opt/sw/spacewalk on fedora it is the same in rhel 5 ..
if my UID is XXX on fedora, there must be a user with the same name and
name UID in rhel 5.
I would think a similar setup could work for Fedora/Centos combination
This is a fairly complicated setup but i like the separation between
development and runtime environment..
Travis Camechis wrote:
> Sounds like a good idea. I think another useful think would to have people
> describe how they setup there environment. It would be good to see how
> people streamline there development and testing. One thing Im wondering is
> how people do a lot of there testing. It looks like testing a lot of the
> features could involve rebuilding VMS a lot and running the test ( not for
> sure since I haven't actually used the product yet ).
> Currently I set up my Development box on a CentOs workstation. I setup a
> NFS mount so I could mount my checkout on my F10 laptop. I also plan on
> installing a couple VMS on the Centos machine to act as test clients. I
> currently have one installed so far.
> On Fri, Jan 23, 2009 at 8:06 PM, Jesus M. Rodriguez <jmrodri at gmail.com>wrote:
>> On Fri, Jan 23, 2009 at 12:27 PM, Michael DeHaan <mdehaan at redhat.com>
>>> Jesus M. Rodriguez wrote:
>>>> On Thu, Jan 22, 2009 at 3:03 PM, Coe, Colin C. (Unix Engineer)
>>>> <Colin.Coe at woodside.com.au> wrote:
>>>>> I've found that doing the steps under 'Deploying Development Schema'
>>>>> doesn't work (for me anyway) and ends up needing to redo the dev
>>>>> Also, I'd like to see
>>>>> fleshed out a lot more.
>>>> Anything in particular? I'd be happy to update it.
>>>> Spacewalk-devel mailing list
>>>> Spacewalk-devel at redhat.com
>>> Could the dev-environment be more appliancey?
>>> How about a shell-script/recipe to automate environment setup, or
>>> a kickstart for installation of a dev-environment in a virtual machine
>>> just the virt-install command
>>> and kickstart, you should be good to go)?
>>> One problem is grabbing the Oracle bits, for now, so that may have to be
>>> one-off, but everything else, perhaps...
>> The appliance idea is a decent one, and worth adding to the list of dev
>> I personally use a virt guest to do my development in. I wouldn't want the
>> appliance to be the only way of dev setup.
>> A great idea though.
>> Spacewalk-devel mailing list
>> Spacewalk-devel at redhat.com
> Spacewalk-devel mailing list
> Spacewalk-devel at redhat.com
More information about the Spacewalk-devel