[Spacewalk-devel] PGPORT (regarding queries)
Hi, We have started looking at the queries that need to be tagged. In the initial stages of going through these queries we found a couple of things and some ways we can tag them. Keeping in mind the diversity and complexity of the some of the queries we have divided them into four categories: 1. Queries that need to have minor changes to make them work in postgres. For eg: It could be like adding an as clause for alias names etc. We had a suggestion to tag them with the following comment where ever the changes are necessary: pgsql_c:xxx -- which is postgresql_comment:line number. 2. Queries that need to be rewritten. We had gone through a couple of them as we went along the list and found some queries that had to be rewritten to give an exact result. For eg: queries on system catalogs in oracle do not work in postgres. we would be tagging such queries with the following comment: pgsql_q:xxx -- which is postgresql_query:line number. 3. Incase there are any db changes to accommodate a query using Orafce, such queries would be tagged as: pgsql_orafce:xxx -- which is postgresql_database_change:line number. 4. No changes required to the existing query. Works both on postgres and oracle. pgsql_ora:xxx -- which is works on both postgres and oracle:line number. These are just some initial thoughts and I am sure we will have some additions to it down the road as we unfold some more of them. Do let me know what you think. Regards, Vikram Rai EnterpriseDB ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] PGPORT (regarding queries)
Thanks for sending this out. A couple of questions: * Why did we abandon the tagging using number (1-5) and decide to go with letters/words. This seems more prone to error. * Is the line # relative to the query? Like PGPORT_xx:3 for line #3 in the query? or is it the absolute line # in the file. If the later, I would suggest we don't do this because: 1) grep will give us the file/line#. 2) if lines are inserted during the tagging process or (merging w/ master), the line # will be wrong. See below: Vikram Rai wrote: Hi, We have started looking at the queries that need to be tagged. In the initial stages of going through these queries we found a couple of things and some ways we can tag them. Keeping in mind the diversity and complexity of the some of the queries we have divided them into four categories: 1. Queries that need to have minor changes to make them work in postgres. For eg: It could be like adding an as clause for alias names etc. We had a suggestion to tag them with the following comment where ever the changes are necessary: pgsql_c:xxx -- which is postgresql_comment:line number. Why c? - seems arbitrary or at least I don't get it :) 2. Queries that need to be rewritten. We had gone through a couple of them as we went along the list and found some queries that had to be rewritten to give an exact result. For eg: queries on system catalogs in oracle do not work in postgres. we would be tagging such queries with the following comment: pgsql_q:xxx -- which is postgresql_query:line number. Why q? - seems arbitrary or at least I don't get it :) 3. Incase there are any db changes to accommodate a query using Orafce, such queries would be tagged as: pgsql_orafce:xxx -- which is postgresql_database_change:line number. I'd like to have a convention where we're more specific. In addition to tagging as a #3, and that we *might* leverage orafce, I'd like to tag it with what feature(s) in orafce such as NVL, DECODE(), .. Also, a query might be tagged as a #3 and not leverage orafce but require another compatability measure such as a DB function or procedure. I'd like to account for this. 4. No changes required to the existing query. Works both on postgres and oracle. pgsql_ora:xxx -- which is works on both postgres and oracle:line number. Why ora? - seems arbitrary or at least I don't get it :) These are just some initial thoughts and I am sure we will have some additions to it down the road as we unfold some more of them. Do let me know what you think. Regards, Vikram Rai EnterpriseDB ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] spacewalk and CentOS
hi Guys, Over the next few days were going to have CentOS-5.3 ready for release and I was just wondering if there is anything that might be desirable to get into the distro from the Spacewalk side of things. iirc, there was interest in bringing back the *rhn* support packages which we dropped from 5.X ( since they really have no use in CentOS and we dont want to have $people hitting rhn services ). Is there anything else beyond that, I might be able to do this end to make life for Spacewalk/CentOS users easier at this stage ? -- Karanbir Singh http://www.karan.org/ z00dax#centos-de...@irc.freenode.net ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Automating Oracle-xe Setup
Jan Pazdziora wrote: On Wed, Feb 18, 2009 at 11:30:30AM -0800, Mike McCune wrote: % And the creation of the spacewalk user / permissions? su - oracle -c 'sqlplus / as sysdba' EOS create user spacewalk identified by spacewalk default tablespace users; grant dba to spacewalk; alter system set processes = 400 scope=spfile; alter system set _optimizer_filter_pred_pullup=false scope=spfile; alter system set _optimizer_cost_based_transformation=off scope=spfile; EOS we should consider adding the user creation steps to spacewalk-setup Do you mean spacewalk-setup the package, or spacewalk-setup the file in /usr/bin? The file in /usr/bin :) Mike -- Mike McCune mmccune AT redhat.com Engineering | Portland, OR RHN Satellite | 650.567.9039x79248 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk and CentOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 24 Feb 2009 16:17:36 + Karanbir Singh mail-li...@karan.org wrote: hi Guys, Over the next few days were going to have CentOS-5.3 ready for release and I was just wondering if there is anything that might be desirable to get into the distro from the Spacewalk side of things. iirc, there was interest in bringing back the *rhn* support packages which we dropped from 5.X ( since they really have no use in CentOS and we dont want to have $people hitting rhn services ). Is there anything else beyond that, I might be able to do this end to make life for Spacewalk/CentOS users easier at this stage ? -- Karanbir Singh http://www.karan.org/ z00dax#centos-de...@irc.freenode.net Hi Karanbir, I think there are definitely some packages we would love to get into CentOS 5.3. In a perfect world all of these would be nice to see: http://stahnma.fedorapeople.org/spacewalk-tools/5Server/i386/ But of those there are a few that are more helpful than others, rhnlib, rhn-check, and rhn-setup. (anybody know of others?) I think rhnlib is the one that would need patching to prevent it from doing any querying of RHN hosted. Also big thanks for checking in with us on this, very proactive. :) Cheers, Devan - -- Devan Goodwin dgood...@redhat.com Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmkVvIACgkQAyHWaPV9my4eBgCfUQBmuBigwg2TaeGhseNvxNhg gngAnAq6hRSIGczHjA1V7WAgT4yvmPjQ =ObHJ -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk and CentOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Devan Goodwin wrote: On Tue, 24 Feb 2009 16:17:36 + Karanbir Singh mail-li...@karan.org wrote: hi Guys, Over the next few days were going to have CentOS-5.3 ready for release and I was just wondering if there is anything that might be desirable to get into the distro from the Spacewalk side of things. iirc, there was interest in bringing back the *rhn* support packages which we dropped from 5.X ( since they really have no use in CentOS and we dont want to have $people hitting rhn services ). Is there anything else beyond that, I might be able to do this end to make life for Spacewalk/CentOS users easier at this stage ? -- Karanbir Singh http://www.karan.org/ z00dax#centos-de...@irc.freenode.net Hi Karanbir, I think there are definitely some packages we would love to get into CentOS 5.3. In a perfect world all of these would be nice to see: http://stahnma.fedorapeople.org/spacewalk-tools/5Server/i386/ But of those there are a few that are more helpful than others, rhnlib, rhn-check, and rhn-setup. (anybody know of others?) I think rhnlib is the one that would need patching to prevent it from doing any querying of RHN hosted. Also big thanks for checking in with us on this, very proactive. :) Cheers, Devan Here are the obvious ones from my perspective: rhn-client-tools rhnlib rhnsd yum-rhn-plugin jabberpy osad rhn-custom-info rhn-kickstart rhn-virtualization rhncfg rhnmd rhns-certs-tools This covers most every tool that interacts with Spacewalk/RHN/Satellite/Proxy today on EL5. Thanks. Brandon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFJpGyshwQhj8l1t/cRArfgAJ4gMzT2nyDiA9qKbcaGkz7EqcRCdwCfSDdg qpthMgIawKhViGcEO+MozqY= =fkWr -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] space05 bugs
unaddressed bugs: 37 - http://tinyurl.com/bm3e9y total bugs: 84 - http://tinyurl.com/dx5skq We are planning on going out on March 15th (the Ides of March release). Please have your unaddressed bugs done by no later than March 9th. Sincerely, Spacewalk Nanny -- jesus m. rodriguez| jes...@redhat.com sr. software engineer | irc: zeus rhn satellite spacewalk | 919.754.4413 (w) rhce # 805008586930012| 919.623.0080 (c) +---+ | Those who cannot learn from history | | are doomed to repeat it. | | -- George Santayana | +---+ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] space05 bugs
Is there a tracker for this ?? Jesus M. Rodriguez wrote: unaddressed bugs: 37 - http://tinyurl.com/bm3e9y total bugs: 84 - http://tinyurl.com/dx5skq We are planning on going out on March 15th (the Ides of March release). Please have your unaddressed bugs done by no later than March 9th. Sincerely, Spacewalk Nanny -- jesus m. rodriguez| jes...@redhat.com sr. software engineer | irc: zeus rhn satellite spacewalk | 919.754.4413 (w) rhce # 805008586930012| 919.623.0080 (c) +---+ | Those who cannot learn from history | | are doomed to repeat it. | | -- George Santayana | +---+ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] space05 bugs
n/m .. space05. Sorry Partha Aji wrote: Is there a tracker for this ?? Jesus M. Rodriguez wrote: unaddressed bugs: 37 - http://tinyurl.com/bm3e9y total bugs: 84 - http://tinyurl.com/dx5skq We are planning on going out on March 15th (the Ides of March release). Please have your unaddressed bugs done by no later than March 9th. Sincerely, Spacewalk Nanny -- jesus m. rodriguez| jes...@redhat.com sr. software engineer | irc: zeus rhn satellite spacewalk | 919.754.4413 (w) rhce # 805008586930012| 919.623.0080 (c) +---+ | Those who cannot learn from history | | are doomed to repeat it. | | -- George Santayana | +---+ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] 486982 - fixed ise on software upgrade list
1) why not add a default constructor where you can initialize all of the member variables 2) why didn't we just check for null :) it's not hard for this class to get broken simply by passing in null to the setters. so initializing the Lists to an empty list won't ALWAYS protect you from the ISE. jesus Sent to you by jmrodri via Google Reader: 486982 - fixed ise on software upgrade list via Fedora Hosted Git Repositories - spacewalk.git/rss log by Justin Sherrill jsher...@redhat.com on 2/24/09 486982 - fixed ise on software upgrade list - [DH] java/code/src/com/redhat/rhn/frontend/dto/UpgradablePackageListItem.java Things you can do from here: - Subscribe to Fedora Hosted Git Repositories - spacewalk.git/rss log using Google Reader - Get started using Google Reader to easily keep up with all your favorite sites ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] new build
new build? um that's not very descriptive :) jesus Sent to you by jmrodri via Google Reader: new build via Fedora Hosted Git Repositories - spacewalk.git/rss log by Pradeep Kilambi pkila...@redhat.com on 2/24/09 new build - [DH] java/spacewalk-java.spec Things you can do from here: - Subscribe to Fedora Hosted Git Repositories - spacewalk.git/rss log using Google Reader - Get started using Google Reader to easily keep up with all your favorite sites ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Random cleanup while I was in here. Final is unnecessary for static methods;...
Thanks for the cleanup, and yes final is unnecessary on static methods because you can't override them. jesus Sent to you by jmrodri via Google Reader: Random cleanup while I was in here. Final is unnecessary for static methods; technica... via Fedora Hosted Git Repositories - spacewalk.git/rss log by Jason Dobies jason.dob...@redhat.com on 2/23/09 Random cleanup while I was in here. Final is unnecessary for static methods; technically, they can't be overridden. Added use of generics. - [DH] java/code/src/com/redhat/rhn/manager/rhnset/RhnSetDecl.java Things you can do from here: - Subscribe to Fedora Hosted Git Repositories - spacewalk.git/rss log using Google Reader - Get started using Google Reader to easily keep up with all your favorite sites ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Extracted out the custom name generation so it can be used outside of creati...
reuse? what are you mad? Kidding, great work. jesus Sent to you by jmrodri via Google Reader: Extracted out the custom name generation so it can be used outside of creating a... via Fedora Hosted Git Repositories - spacewalk.git/rss log by Jason Dobies jason.dob...@redhat.com on 2/23/09 Extracted out the custom name generation so it can be used outside of creating a new set (i.e. used to load the set later). - [DH] java/code/src/com/redhat/rhn/manager/rhnset/RhnSetDecl.java Things you can do from here: - Subscribe to Fedora Hosted Git Repositories - spacewalk.git/rss log using Google Reader - Get started using Google Reader to easily keep up with all your favorite sites ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] checkstyle for new license format
Did I miss these in my checkin? jesus Sent to you by jmrodri via Google Reader: checkstyle for new license format via Fedora Hosted Git Repositories - spacewalk.git/rss log by Mike McCune mmcc...@gmail.com on 2/23/09 checkstyle for new license format - [DH] java/code/src/com/redhat/rhn/domain/kickstart/cobbler/CobblerSnippet.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/BaseCobblerSnippetEditAction.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/CobblerSnippetCreateAction.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/CobblerSnippetDeleteAction.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/CobblerSnippetEditAction.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/CobblerSnippetListSetupAction.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/test/CobblerSnippetEditActionTest.java - [DH] java/code/src/com/redhat/rhn/frontend/action/kickstart/cobbler/test/CobblerSnippetListSetupTest.java - [DH] java/code/src/com/redhat/rhn/manager/kickstart/cobbler/BaseCobblerSnippetCommand.java - [DH] java/code/src/com/redhat/rhn/manager/kickstart/cobbler/CobblerSnippetEditCommand.java - [DH] java/code/src/com/redhat/rhn/manager/kickstart/cobbler/CobblerSnippetLister.java - [DH] java/code/src/com/redhat/rhn/manager/kickstart/cobbler/CreateCobblerSnippetCommand.java - [DH] java/code/src/com/redhat/rhn/manager/kickstart/cobbler/DeleteCobblerSnippetCommand.java Things you can do from here: - Subscribe to Fedora Hosted Git Repositories - spacewalk.git/rss log using Google Reader - Get started using Google Reader to easily keep up with all your favorite sites ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk and CentOS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Stahnke wrote: Karanbir Singh mail-li...@karan.org wrote: hi Guys, Over the next few days were going to have CentOS-5.3 ready for release and I was just wondering if there is anything that might be desirable to get into the distro from the Spacewalk side of things. iirc, there was interest in bringing back the *rhn* support packages which we dropped from 5.X ( since they really have no use in CentOS and we dont want to have $people hitting rhn services ). Is there anything else beyond that, I might be able to do this end to make life for Spacewalk/CentOS users easier at this stage ? This is awesome that you want to do this. (I'd like to not have my repo) In a perfect world all of these would be nice to see: http://stahnma.fedorapeople.org/spacewalk-tools/5Server/i386/ But of those there are a few that are more helpful than others, rhnlib, rhn-check, and rhn-setup. (anybody know of others?) I think rhnlib is the one that would need patching to prevent it from doing any querying of RHN hosted. Also big thanks for checking in with us on this, very proactive. :) Also, kudos from me. Here are the obvious ones from my perspective: rhn-client-tools rhnlib rhnsd yum-rhn-plugin jabberpy osad rhn-custom-info rhn-kickstart rhn-virtualization rhncfg rhnmd rhns-certs-tools IMHO, if the RPMS are not shipped in RHEL, they shouldn't be in CentOS. I'd like to see the items in RHEL proper in Centos (patched of course). Keep in mind that RH ships separate RHN Channels or additional packages via other repos too. osad, jabberpy, rhn-kickstart* and rhn-virt* are NOT currently shipped in RHEL. I don't think they should be in Centos. Please ship only the items in RHEL. rhn-client-tools, rhnlib, yum-rhn-plugin. There could be a couple more, but I don't have a RHEL system in front of me. I will check tomorrow at work. Again, I am asking for alignment with RHEL. Outside of that, users can use EPEL for the supplemental packages. (Assuming they eventually all make it in there...and I am working on it with a few SW-Dev people). Michael Stahnke stahnma That's a fine point. So, I have RHEL, but don't have CentOS, so the things I authoritatively know we deal with (many of these may already be in CentOS): RHEL-4 == redhat-rpm-config rhn-applet rhnlib rpm rpmdb-redhat up2date RHEL-5 == createrepo redhat-rpm-config rhn-client-tools rhnlib rhnsd rpm yum yum-metadata-parser yum-rhn-plugin yum-updatesd yum-utils Common to both RHEL versions redhat-rpm-config rhnlib rpm Specific to just the RHN Tools channels in RHN == auto-kickstart jabberpy osad rhn-custom-info rhn-kickstart rhn-virtualization rhncfg rhnmd rhns-certs-tools Thanks. Brandon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFJpMbqhwQhj8l1t/cRApfhAJ4mRQY3TEvOqYU8vszF2HH4kODOhgCfcTH5 SysBI3UeJe8T13WKGc1qPsc= =9zAm -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Automating Oracle-xe Setup
On Tue, Feb 24, 2009 at 11:48:36AM -0800, Mike McCune wrote: su - oracle -c 'sqlplus / as sysdba' EOS create user spacewalk identified by spacewalk default tablespace users; grant dba to spacewalk; alter system set processes = 400 scope=spfile; alter system set _optimizer_filter_pred_pullup=false scope=spfile; alter system set _optimizer_cost_based_transformation=off scope=spfile; EOS we should consider adding the user creation steps to spacewalk-setup Do you mean spacewalk-setup the package, or spacewalk-setup the file in /usr/bin? The file in /usr/bin :) That's what I feared. Ideally, spacewalk-setup (the file, and the Spacewalk/Setup.pm) should how have anything embedded database or XE specific. That spacewalk-setup should receive connect string to use, and that connect string should point to a working, setup database user account. We could do something like oracle-xe-utils or spacewalk-oracle-xe (package) to hold any helper scripts. But we should aim at removing even the last embedded db bits away from spacewalk-setup, not add new ones. I've added the create user spacewalk SQL to https://fedorahosted.org/spacewalk/wiki/OracleXeSetup and I'm actually considering removing the part about http://127.0.0.1:9000/apex from that page, so the list of steps that you need to do on Oracle XE prior to running spacewalk-setup should get pretty short. -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
