<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl =
"http://schemas.microsoft.com/repl/" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =
"http://www.passport.com/NameSpace.xsd" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle21 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=015095316-18082009><FONT face=Arial
color=#0000ff size=2>It was sent this morning to the
list</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> spacewalk-list-bounces@redhat.com
[mailto:spacewalk-list-bounces@redhat.com] <B>On Behalf Of </B>Gomes,
Rich<BR><B>Sent:</B> Tuesday, August 18, 2009 12:33 PM<BR><B>To:</B>
spacewalk-list@redhat.com<BR><B>Subject:</B> RE: [Spacewalk-list] Spacewalk
& RHEL question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Evan,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d">
Can you send this to me as well? This sounds exactly like what I am trying to
do.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Thanks,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Rich<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com]
<B>On Behalf Of </B>Frey, Evan<BR><B>Sent:</B> Monday, August 17, 2009 5:18
PM<BR><B>To:</B> spacewalk-list@redhat.com<BR><B>Subject:</B> Re:
[Spacewalk-list] Spacewalk & RHEL question<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Ah, I
misread your email. I thought you were trying to connect 1 client machine to
multiple servers.<BR><BR>All that said I am currently doing exactly what you are
describing. I have it in a two stage setup. I have a box for each architecture
downloading all rpms in subscribed channels and dumping it to a central repo. An
rhnpush script is kicked off that then iterates through the reop and pushes all
the deltas to their corresponding channels. Future development will just pull
down the src rpms and rebuild in each environment. If you want I can send you
the scripts and directions for setup. I've been using it for months with no
issues.</SPAN><o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">:
spacewalk-list-bounces@redhat.com <BR><B>To</B>: spacewalk-list@redhat.com
<BR><B>Sent</B>: Mon Aug 17 16:52:43 2009<BR><B>Subject</B>: RE:
[Spacewalk-list] Spacewalk & RHEL question </SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">The documentation I’ve seen are
mailing list/web postings of people working on scripts to pull RHN packages to
add to Spacewalk (rather than Satellite).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d">----<BR><BR>Jeff Moody<BR>Senior Systems
Engineer<BR> <BR>EVS Corporation<BR>5050 Poplar Avenue ,Suite
1600<BR>Memphis, Tennessee 38157<BR>(901) 259-2387 - 24x7 Helpdesk<BR><BR>(901)
881-0919 - Office<BR>(901) 497-1444 -
Cell<BR>jeff.moody@evscorporation.com</SPAN><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com]
<B>On Behalf Of </B>Frey, Evan<BR><B>Sent:</B> Monday, August 17, 2009 3:51
PM<BR><B>To:</B> spacewalk-list@redhat.com<BR><B>Subject:</B> Re:
[Spacewalk-list] Spacewalk & RHEL question<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Configuration
and management is done on clients that are registered with the
spacewalk/satellite/rhn server. I don't believe that the client supports
registering with multiple servers. I could be wrong but it seems like a
potential package nightmare. If you have seen documentation outlining this,
please post for I would be interested to read up.</SPAN><o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">:
spacewalk-list-bounces@redhat.com <BR><B>To</B>: spacewalk-list@redhat.com
<BR><B>Sent</B>: Mon Aug 17 16:14:34 2009<BR><B>Subject</B>: RE:
[Spacewalk-list] Spacewalk & RHEL question </SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">So, is it impossible to run a
RHEL box that gets its updates from RHN but is configured and monitored by
Spacewalk?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">I have seen some different
documentation on potential methods to sync the RHN packages to Spacewalk, but
feel pretty confident that this is (1) in violation of the spirit of the
Spacewalk project and (2) may invalidate the Red Hat Support agreements that my
company already has in place.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">More than anything, I have yet
to find another product/project with some of the monitoring abilities of
Spacewalk and would like that level of monitoring on our RHEL
servers.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Thanks.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d">----<BR><BR>Jeff Moody<BR>Senior Systems
Engineer<BR> <BR>EVS Corporation<BR>5050 Poplar Avenue ,Suite
1600<BR>Memphis, Tennessee 38157<BR>(901) 259-2387 - 24x7 Helpdesk<BR><BR>(901)
881-0919 - Office<BR>(901) 497-1444 -
Cell<BR>jeff.moody@evscorporation.com</SPAN><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B>From:</B> spacewalk-list-bounces@redhat.com
[mailto:spacewalk-list-bounces@redhat.com] <B>On Behalf Of </B>Frey,
Evan<BR><B>Sent:</B> Monday, August 17, 2009 1:46 PM<BR><B>To:</B>
spacewalk-list@redhat.com<BR><B>Subject:</B> RE: [Spacewalk-list] Spacewalk
& RHEL question<o:p></o:p></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I think (and I may be wrong) that a client can only be
registered to one spacewalk system. When I have accidentally tried to
register a system that was previously registered, an error pops up warning me to
use the --force option to re-register. The force option then unregisters
my client from the original system and registers it to the forced system.
Not sure if it removes it on the spacewalk/satellite server or just from the
client config.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B>From:</B>
spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com]
<B>On Behalf Of </B>Jeff Moody<BR><B>Sent:</B> Monday, August 17, 2009 2:17
PM<BR><B>To:</B> spacewalk-list@redhat.com<BR><B>Subject:</B> [Spacewalk-list]
Spacewalk & RHEL question<o:p></o:p></P>
<P class=MsoNormal>Are there any gotchas I should know about when registering a
RHEL server with Spacewalk?<o:p></o:p></P>
<P class=MsoNormal>Is it possible to use Spacewalk for config management and
monitoring and still pull updates from RHN?<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I would assume that this shouldn’t be an issue if I don’t
have a RHEL channel defined in Spacewalk and the updates should pull from RHN,
but I didn’t know if there was an issue I may run into by having the box
registered to both systems.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">----<BR><BR>Jeff
Moody<BR>Senior Systems Engineer<BR> <BR>EVS Corporation<BR>5050 Poplar
Avenue ,Suite 1600<BR>Memphis, Tennessee 38157<BR>(901) 259-2387 - 24x7
Helpdesk<BR><BR>(901) 881-0919 - Office<BR>(901) 497-1444 -
Cell<BR>jeff.moody@evscorporation.com</SPAN><o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">CONFIDENTIAL:
This e-mail, including its contents and attachments, if any, are confidential.
It is neither an offer to buy or sell, nor a solicitation of an offer to buy or
sell, any securities or any related financial instruments mentioned in it. If
you are not the named recipient please notify the sender and immediately delete
it. You may not disseminate, distribute, or forward this e-mail message or
disclose its contents to anybody else. Unless otherwise indicated, copyright and
any other intellectual property rights in its contents are the sole property of
Mizuho Securities USA Inc.<o:p></o:p></SPAN></P>
<P>E-mail transmission cannot be guaranteed to be secure or error-free. The
sender therefore does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version.<o:p></o:p></P>
<P>Although we routinely screen for viruses, addressees should check this e-mail
and any attachments for viruses. We make no representation or warranty as to the
absence of viruses in this e-mail or any attachments. Please note that to ensure
regulatory compliance and for the protection of our customers and business, we
may monitor and read e-mails sent to and from our server(s). <o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">CONFIDENTIAL:
This e-mail, including its contents and attachments, if any, are confidential.
It is neither an offer to buy or sell, nor a solicitation of an offer to buy or
sell, any securities or any related financial instruments mentioned in it. If
you are not the named recipient please notify the sender and immediately delete
it. You may not disseminate, distribute, or forward this e-mail message or
disclose its contents to anybody else. Unless otherwise indicated, copyright and
any other intellectual property rights in its contents are the sole property of
Mizuho Securities USA Inc.<o:p></o:p></SPAN></P>
<P>E-mail transmission cannot be guaranteed to be secure or error-free. The
sender therefore does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version.<o:p></o:p></P>
<P>Although we routinely screen for viruses, addressees should check this e-mail
and any attachments for viruses. We make no representation or warranty as to the
absence of viruses in this e-mail or any attachments. Please note that to ensure
regulatory compliance and for the protection of our customers and business, we
may monitor and read e-mails sent to and from our server(s). <o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV></DIV></BODY></HTML>