[Spacewalk-devel] Audit feature merged to master

2009-08-05 Thread Mike McCune

I just pushed the code for Joshua Roys's Audit feature.

With the install of the latest spacewalk-java RPMs you should see a new 
Audit tab at the top of the GUI with a few subsequent pages contained 
within.


More info on getting the feature running here:

http://www.stl.gtri.gatech.edu/jroys/

Joshua, would you consider adding a guide to our wiki here:

https://fedorahosted.org/spacewalk/

on how to get Audit going?

Thanks again for the contribution!
Mike
--
Mike McCune
mmccune AT redhat.com
Engineering   | Portland, OR
RHN Satellite | 650.254.4248

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


[Spacewalk-devel] Spacewalk 0.6 code freeze: Thursday, Aug 6 @ noon EDT

2009-08-05 Thread John Matthews

It's that time again, time to get yet another release of Spacewalk out
the door. Thursday, Aug 6 @ noon EDT will be code freeze.

There are 30 bugs (lot's of tracking bugs) that still need punting
or fixing. Please take a look at your bug lists:

   http://tinyurl.com/kspjsl

We will start building the packages around 2pm EDT. The hope is to
have the packages signed and put into the QA repo by 4pm on Thursday.

Our target is to go LIVE on Friday August 7th, by 5pm EDT.

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] [PATCH/RFC/WIP] manage symlinks in config management

2009-08-05 Thread Pradeep Kilambi

On 08/04/2009 03:53 PM, Joshua Roys wrote:

Hello all,

Attached is a patch that lets you play around with symlinks through 
the config management interface (rhbz#428190).  It's a bit of a hack 
in the sense that it asks you to put the target of the symlink in the 
file contents.  Also, a few things are unfinished or don't do what is 
expected with this patch.


Things to do/fix:
- asking for a diff dereferences the symlink.  move the code from 
transaction.py to file_utils.py/process?
- integrate with deploy/rollback.  pretend symlinks are files in 
transaction.py?  necessary with symlinks?

- hide the owner:group/mode fields?  always root:root/0777?
- when you click on "Symbolic link" in the web interface, hide the 
"File Contents" box and have a "Destination" input field appear?
- on the Channel overview page, the incorrect count of files appears. 
where is this number calculated from?  (how does it get into 
ConfigChannelDto.java?)


Anyone have some advice on the last one?  Or any suggestions on the 
other ones, too.


Thanks,

Joshua Roys



I'll go ahead and take this for review as well. But I vote to include 
this for 0.7 as its already too late for inclusion into spacewalk-0.6 at 
this point.


Thanks,
~ Prad







___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel



--
--
Pradeep Kilambi
Senior Software Engineer
RHN Satellite Engineering
Phone: +1 919 754 4285
RHCE # 805008680430554


___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Re: [Spacewalk-devel] [PATCH] selinux config file management fixes

2009-08-05 Thread Pradeep Kilambi

On 08/04/2009 03:53 PM, Joshua Roys wrote:

Hello all,

Attached is a patch to fix a few issues found in some more thorough 
testing.


Thanks,

Joshua Roys


Patch applied.

Thanks,
~ Prad





___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel



--
--
Pradeep Kilambi
Senior Software Engineer
RHN Satellite Engineering
Phone: +1 919 754 4285
RHCE # 805008680430554


___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Re: [Spacewalk-devel] Keeping up with "rawhide"

2009-08-05 Thread Devan Goodwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 5 Aug 2009 13:47:27 -0400 (EDT)
Greg DeKoenigsberg  wrote:

> On Wed, 5 Aug 2009, Marcus Moeller wrote:
> 
> >> Is it better to be pulling stuff straight out of git, or is it
> >> better to be using some combination of the 0.6/rawhide RPM nightly
> >> builds at miroslav.suchy.cz?
> >
> > I personally prefer nightly builds.
> 
> Yes, that's the conclusion I'm coming to as well.

Me too, someday I think we should change the devel setup to include
instructions on following the devel repo + building their own test
packages to try code.

> 
> > Maybe there should be some update notes on major changes (like
> > jabber backend change or schema enhancements) available in a
> > ChangeLog form on the wiki.
> 
> Like, for instance, the changes between 0.5 and 0.6 -- have the
> release notes for 0.6 been sent out?  A quick google of "spacewalk
> 0.6 release notes" returns nothing useful.

No release notes out yet, but when we build new rpms the changelog is
updated to include the first line of every commit message included. (or
that the package maintainer felt like leaving in)

Cheers,

Devan

- -- 
  Devan Goodwin 
  Software Engineer Spacewalk / RHN Satellite
  Halifax, Canada   650.567.9039x79267
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkp50McACgkQAyHWaPV9my7RLACg6V5XaVK2fgMNg7FqNdXlXrk2
lSoAnjUO6jf+gHm4GnV2jT8zW0Yg659D
=LOWc
-END PGP SIGNATURE-

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Keeping up with "rawhide"

2009-08-05 Thread Greg DeKoenigsberg

On Wed, 5 Aug 2009, Marcus Moeller wrote:

Is it better to be pulling stuff straight out of git, or is it better 
to be using some combination of the 0.6/rawhide RPM nightly builds at 
miroslav.suchy.cz?


I personally prefer nightly builds.


Yes, that's the conclusion I'm coming to as well.

Maybe there should be some update notes on major changes (like jabber 
backend change or schema enhancements) available in a ChangeLog form on 
the wiki.


Like, for instance, the changes between 0.5 and 0.6 -- have the release 
notes for 0.6 been sent out?  A quick google of "spacewalk 0.6 release 
notes" returns nothing useful.


--g

--
Computer Science professors should be teaching open source.
Help make it happen.   Visit http://teachingopensource.org.

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Keeping up with "rawhide"

2009-08-05 Thread Marcus Moeller
Dear Greg.

> So for those of us following along at home, what's the best way of keeping
> up with the latest changes to the Spacewalk codebase?
>
> Is it better to be pulling stuff straight out of git, or is it better to be
> using some combination of the 0.6/rawhide RPM nightly builds at
> miroslav.suchy.cz?

I personally prefer nightly builds.

Maybe there should be some update notes on major changes (like jabber
backend change or schema enhancements) available in a ChangeLog form
on the wiki.

Best Regards
Marcus

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


[Spacewalk-devel] Keeping up with "rawhide"

2009-08-05 Thread Greg DeKoenigsberg


So for those of us following along at home, what's the best way of keeping 
up with the latest changes to the Spacewalk codebase?


Is it better to be pulling stuff straight out of git, or is it better to 
be using some combination of the 0.6/rawhide RPM nightly builds at 
miroslav.suchy.cz?


--g

--
Computer Science professors should be teaching open source.
Help make it happen.   Visit http://teachingopensource.org.

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] 0.6 Ready for Testing

2009-08-05 Thread Devan Goodwin
On Wed Aug 05/2009 @  9:08:P +0200 asdasd, Miroslav Suchý wrote:
> So little explanation:
> This step means that we have schema definition which we can feed to  
> PostgreSQL. That mean definition of tables, procedures, indexes...
> In fact - using tool chameleon we are able to create PosgresSQL schema  
> from Oracle schema anytime we want.
> So DB population during spacewalk-setup should happened without error (I  
> mean this one single step, the script will likely die on something else  
> even before this one step).
> And what is still remaining:
> - ask in spacewalk-setup which backend you wanna use
> - make sure that java, python and perl will load PosgreSQL driver when  
> you choose Pg.
> - make sure that SQL queries in code is compatible with PosgreSQL (there  
>  will be for sure with BLOBs handling).
> - write Pg support for db utilites (like db-control)
> - make performance tests with Pg.
> - and probably something else I do not realize right now.
>
>
> -- 
> Miroslav Suchy
> Red Hat Satellite Engineering

The others mostly clarified but just to add some additional info these
were also included in this merge:

 - ask in spacewalk-setup which backend you wanna use
 - make sure that java, python and perl will load PosgreSQL driver when  
   you choose Pg.

While things have gone backwards a little in the rush to cleanup the
post-merge code, spacewalk-setup should come very close to completing
against PostgreSQL.

Cheers,

Devan


pgp8EeVzqaK6y.pgp
Description: PGP signature
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Re: [Spacewalk-devel] 0.6 Ready for Testing

2009-08-05 Thread Miroslav Suchý

Michael Stahnke wrote:

Perhaps you could explain this a little more.  When I read that the
Postgres Merge happend, I assumed that meant Postgres functionality.
Also, in reading Cliff's notes for Spacewalk 0.6, it looked like
Postgres support was in there.  Am I just mis-reading things, or is
there more to it?  I am sure it's a very significant effort for the
whole process, I just want to be sure I understand where it's at.


So little explanation:
This step means that we have schema definition which we can feed to 
PostgreSQL. That mean definition of tables, procedures, indexes...
In fact - using tool chameleon we are able to create PosgresSQL schema 
from Oracle schema anytime we want.
So DB population during spacewalk-setup should happened without error (I 
mean this one single step, the script will likely die on something else 
even before this one step).

And what is still remaining:
- ask in spacewalk-setup which backend you wanna use
- make sure that java, python and perl will load PosgreSQL driver when 
you choose Pg.
- make sure that SQL queries in code is compatible with PosgreSQL (there 
 will be for sure with BLOBs handling).

- write Pg support for db utilites (like db-control)
- make performance tests with Pg.
- and probably something else I do not realize right now.


--
Miroslav Suchy
Red Hat Satellite Engineering

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel