[Spacewalk-list] Cloning channel from script

Waldirio Manhães Pinheiro waldirio at gmail.com
Fri May 29 05:02:09 UTC 2015


Hello All

Darryl, my recommendation is use spacewalk-clone-by-date, you have two
ways, the first one is define all parameters in a single line "beautiful",
the second and I really prefer, is create a template, you will execute the
command spacewalk-clone-by-date using the flag -m

###
-m --sample-config
Generate a sample configuration file
###

So you will define all that you would like in your channels (base, child,
dates, etc) and execute the command again with flag -c

###
-c FILE, --config=FILE
Configuration file holding parameters, see --sample-config for an
example.Any command-line parameters override those in specified config file.
###

Enjoy

Take Care

______________
Atenciosamente
Waldirio
msn: waldirio at gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html

On Wed, May 13, 2015 at 11:24 AM, Matt Micene <matt.micene at dlt.com> wrote:

>  That’s the expected behavior of the spacewalk-create-channel tool as far
> as I can tell.  The tool reads files in /usr/share/rhn/channel_data to
> determine the RPM list that was create at issue date of a particular
> release (RHEL 6 Update 6 for example).  The tool will only work on channels
> that were on the distribution ISO and it looks like there’s some hidden
> syntactic sugar as well (from my local testing).  So you get only the
> package published at the time of release, no updates.
>
>
>
> If you want to clone a channel and all the errata, you’re probably better
> off looking at spacewalk-clone-by-date.  You can provide a date to clone
> errata up to, and you can clone channels that aren’t part of the ISO (like
> rhn-tools).
>
>
>
> The syntax is pretty simple spacewalk-clone-by-date –l RHT-channel
> my-channel –d DATE is the basics, and you can automate it with a config
> file (-m will print a sample file).  I wrote about using the tool for
> work:   http://blogs.dlt.com/content-workflow-rhn-satellite/
>
>
>
> HTH,
>
> Matt
>
>
>
>
>
> Matt Micene
>
> DLT Solutions
>
> Solution Architect
>
> RHCA# 100-002-435
>
> Direct 703-773-1195
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Darryl Baker
> *Sent:* Tuesday, May 12, 2015 3:24 PM
>
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Cloning channel from script
>
>
>
> I’ve been playing a bit with the spacewalk-create-channel command. Two
> things I’ve noticed:
>
>
>
> You must specify the update level and there is no way that I can find to
> just select the “latest update.”
>
>
>
> Then once I make the clone the GUI shows no errata in the new channel
> whereas when I make the clone through the RHSS console the channel has a
> list of them.
>
>
>
> I would like to just say the latest update and see the errata attached to
> the clone. Anyone have any thoughts?
>
>
>
> Regards,
>
>
>
> Darryl
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Darryl Baker
> *Sent:* Tuesday, May 12, 2015 9:12 AM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Cloning channel from script
>
>
>
> I’m only doing a few hundred machines at the moment but we are growing
> fast. Scripts to modify the channels systems are using as well as making
> the channel clones would be great. Thank you for offering. If You would
> post the collection to GitHub, please.
>
>
>
>
>
> Regards,
>
>
>
> Darryl
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [
> mailto:spacewalk-list-bounces at redhat.com
> <spacewalk-list-bounces at redhat.com>] *On Behalf Of *Franky Van Liedekerke
> *Sent:* Tuesday, May 12, 2015 1:04 AM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Cloning channel from script
>
>
>
> I have several perl scripts that do all that: create new cloned channels,
> subscribe servers to the new channels, update kickstart profiles and
> activation keys.
> Even a extra web interface in php and perl crontab to manage the patching
> of thousands of servers via spacewalk.
> If interested, I can put them on github ...
>
> Franky
>
> Darryl Baker <darryl.baker at texturacorp.com> schreef op 11 mei 2015
> 17:08:53 CEST:
>
> I’m using Red Hat Satellite 5.7. Each month I clone the distribution
> channels so I can have sets of machines at the identical patch level and
> those patches can be worked through the testing cycle before being applied
> in production. Currently I am doing this manually through the GUI. A
> mindless, time consuming thing. I would like to set up scripts to do this
> for me. Any clues on how to do this will be much appreciated.
>
>
>
>
>
>
>
> Regards,
>
>
>
> *Darryl Baker*
>
> Textura Corporation
>
> Linux Engineer Application Support
>
> 1405 Lake Cook Road
>
> Deerfield, Illinois 60015
>
> Office Phone - 847-235-8467
>
> Email – darryl.baker at texturacorp.com
>
> [image: Image removed by sender. cid:05DC2306-1083-4864-A07C-DE5DA45A6302]
>
>
>
> ------------------------------
>
>
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20150529/50e74a7d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 468 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20150529/50e74a7d/attachment.jpg>


More information about the Spacewalk-list mailing list