Re: [Spacewalk-devel] SatOps: A Ruby script SOE manipulation tool
Just checked you sent it to the list too. Thanks - Original Message - > From: "Aurelien Gouny" > To: "Gilles Dubreuil" > Cc: spacewalk-devel@redhat.com > Sent: Thursday, July 19, 2012 3:40:13 PM > Subject: Re: SatOps: A Ruby script SOE manipulation tool > > The correct URL is https://github.com/SatOps/SatOps > > > > > > > > Gilles Dubreuil > 19 July 2012 2:15 PM > > The SatOps is a Ruby script using the Satellite XML/RPC API to > export/import content, partially or entirely - well as much as > possible. > > From an architecture viewpoint, the SatOps allows to scale up RHN > Satellite/Spacewalk topologies such as having a Master reference and > synchronising Slaves. > This has proven very useful for keeping DR Satellite content aligned > and avoid the "swivel chair syndrome". > > For instance maintaining one SOE definition set across Production > master and DR slave RHN Satellites in active/active mode. > > The SatOps has been in production for months at several "big" > organisations sites using RHN Satellite for managing thousands of > RHEL servers. > > For more details, please check out https://github.com/SatOps/SatOp > > > > -- > Aurelien Gouny Email: aurel...@redhat.com > Red Hat Asia-Pacific Phone: +61 2 8923 2835 > Level 35 - 100 Miller Street Mobile: +61 432 146 000 > North Sydney NSW 2060, Australia GnuPG Key ID: 0x53E08904 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] SatOps: A Ruby script SOE manipulation tool
Damn! I fix it... - Original Message - > From: "Aurelien Gouny" > To: "Gilles Dubreuil" > Cc: spacewalk-devel@redhat.com > Sent: Thursday, July 19, 2012 3:40:13 PM > Subject: Re: SatOps: A Ruby script SOE manipulation tool > > The correct URL is https://github.com/SatOps/SatOps > > > > > > > > Gilles Dubreuil > 19 July 2012 2:15 PM > > The SatOps is a Ruby script using the Satellite XML/RPC API to > export/import content, partially or entirely - well as much as > possible. > > From an architecture viewpoint, the SatOps allows to scale up RHN > Satellite/Spacewalk topologies such as having a Master reference and > synchronising Slaves. > This has proven very useful for keeping DR Satellite content aligned > and avoid the "swivel chair syndrome". > > For instance maintaining one SOE definition set across Production > master and DR slave RHN Satellites in active/active mode. > > The SatOps has been in production for months at several "big" > organisations sites using RHN Satellite for managing thousands of > RHEL servers. > > For more details, please check out https://github.com/SatOps/SatOp > > > > -- > Aurelien Gouny Email: aurel...@redhat.com > Red Hat Asia-Pacific Phone: +61 2 8923 2835 > Level 35 - 100 Miller Street Mobile: +61 432 146 000 > North Sydney NSW 2060, Australia GnuPG Key ID: 0x53E08904 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] cobbler 2.2 version
On 07/19/2012 03:39 PM, Franky Van Liedekerke wrote: > Hi all, > > in this thread: > https://www.redhat.com/archives/spacewalk-devel/2012-July/msg00045.html > I saw people saying that cobbler version 2.2 has issues working together > with spacewalk 1.7 > However: I had the EPEL activated when I upgraded from 1.6 to 1.7, and > cobbler updated as well, so now I'm currently running cobbler 2.2.1 > together with Spacewalk 1.7, and no issues so far By any change you forgot to switch your SELinux Enforcing mode? >(apart from the fact > that I needed to regenerate the kickstart profiles, but a small script > resolved that just fine). > Is this something that I now should be worried about when upgrading to > 1.8 in the future? Since cobbler 2.2.3 is also out, but I'm now holding > back on updating that part ... > > Franky > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel -- Simon Lukasik ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] systemd services for rhnsd and osad
On 07/19/2012 04:46 PM, Franky Van Liedekerke wrote: But in RHEL6, "systemctl" is not present as a command, "service" should still be used (systemd is not present in rhel6). Or am I misreading this? Yes, you are correct. Systemd is not present on RHEL6. I have it incorrect there. -- Miroslav Suchy Red Hat Systems Management Engineering ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] [PATCH] systemd services for rhnsd and osad
On 2012-07-19 16:30, Miroslav Suchý wrote:
I done that some weeks ago, while traveling by train.
I did not have time to test it thoroughly, and I will probably have
no time for that in future. So I'm posting it here.
Decide yourself, if you want to merge it, or leave it for somebody
else who will work on systemd integration.
I just looked at this patch and saw this:
+%if 0%{?fedora} || 0%{?rhel} > 5
+/bin/systemctl stop rhnsd >/dev/null 2>&1
+%else
+service rhnsd stop >/dev/null 2>&1
+%endif
According to me this means: if it is fedora or the redhat major
version>5 then use 'systemctl' to stop the service, otherwise use
'service'.
But in RHEL6, "systemctl" is not present as a command, "service" should
still be used (systemd is not present in rhel6).
Or am I misreading this?
Franky
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] [PATCH] systemd services for rhnsd and osad
I done that some weeks ago, while traveling by train.
I did not have time to test it thoroughly, and I will probably have no
time for that in future. So I'm posting it here.
Decide yourself, if you want to merge it, or leave it for somebody else
who will work on systemd integration.
--
Miroslav Suchý
Red Hat Satellite Engineering
>From 1e9dcfd8016d85888c02d44d50a611f0987f6090 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Miroslav=20Such=C3=BD?=
Date: Fri, 15 Jun 2012 11:46:44 +0200
Subject: [PATCH 1/3] implement rhnsd.service for systemd
---
client/rhel/rhnsd/rhnsd.service | 11 +++
client/rhel/rhnsd/rhnsd.spec| 30 +++---
2 files changed, 38 insertions(+), 3 deletions(-)
create mode 100644 client/rhel/rhnsd/rhnsd.service
diff --git a/client/rhel/rhnsd/rhnsd.service b/client/rhel/rhnsd/rhnsd.service
new file mode 100644
index 000..14b3e3b
--- /dev/null
+++ b/client/rhel/rhnsd/rhnsd.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=Red Hat Network Server daemon
+After=syslog.target network.target auditd.service
+
+[Service]
+PIDFile=/var/run/rhnsd.pid
+ExecStart=/usr/sbin/rhnsd
+ExecReload=/bin/kill -HUP $MAINPID
+
+[Install]
+WantedBy=multi-user.target
diff --git a/client/rhel/rhnsd/rhnsd.spec b/client/rhel/rhnsd/rhnsd.spec
index 5c9d4c0..711b188 100644
--- a/client/rhel/rhnsd/rhnsd.spec
+++ b/client/rhel/rhnsd/rhnsd.spec
@@ -4,7 +4,7 @@ Group: System Environment/Base
Source0: https://fedorahosted.org/releases/s/p/spacewalk/%{name}-%{version}.tar.gz
URL: https://fedorahosted.org/spacewalk
Name: rhnsd
-Version: 4.9.15
+Version: 5.0.0
Release: 1%{?dist}
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
@@ -15,6 +15,13 @@ Requires: rhn-check >= 0.0.8
Requires(post): aaa_base
Requires(preun): aaa_base
BuildRequires: sysconfig
+%elsif 0%{?fedora} || 0%{?rhel} > 5
+Requires(post): chkconfig
+Requires(preun): chkconfig
+Requires(post): systemd-sysv
+Requires(preun): systemd-sysv
+Requires(post): systemd-units
+Requires(preun): systemd-units
%else
Requires(post): chkconfig
Requires(preun): chkconfig
@@ -41,6 +48,11 @@ make -f Makefile.rhnsd install VERSION=%{version}-%{release} PREFIX=$RPM_BUILD_R
%if 0%{?suse_version}
install -m 0755 rhnsd.init.SUSE $RPM_BUILD_ROOT/%{_initrddir}/rhnsd
%endif
+%if 0%{?fedora} || 0%{?rhel} > 5
+rm $RPM_BUILD_ROOT/%{_initrddir}/rhnsd
+mkdir -p $RPM_BUILD_ROOT/%{_unitdir}
+install -m 0644 rhnsd.service $RPM_BUILD_ROOT/%{_unitdir}/
+%endif
%find_lang %{name}
@@ -50,14 +62,22 @@ install -m 0755 rhnsd.init.SUSE $RPM_BUILD_ROOT/%{_initrddir}/rhnsd
%preun
if [ $1 = 0 ] ; then
-/etc/rc.d/init.d/rhnsd stop >/dev/null 2>&1
+%if 0%{?fedora} || 0%{?rhel} > 5
+/bin/systemctl stop rhnsd >/dev/null 2>&1
+%else
+service rhnsd stop >/dev/null 2>&1
+%endif
/sbin/chkconfig --del rhnsd
fi
%postun
if [ "$1" -ge "1" ]; then
-/etc/rc.d/init.d/rhnsd condrestart >/dev/null 2>&1 || :
+%if 0%{?fedora} || 0%{?rhel} > 5
+/bin/systemctl condrestart rhnsd >/dev/null 2>&1 || :
+%else
+service rhnsd condrestart >/dev/null 2>&1 || :
+%endif
fi
%clean
@@ -68,7 +88,11 @@ rm -fr $RPM_BUILD_ROOT
%dir %{_sysconfdir}/sysconfig/rhn
%config(noreplace) %{_sysconfdir}/sysconfig/rhn/rhnsd
%{_sbindir}/rhnsd
+%if 0%{?fedora} || 0%{?rhel} > 5
+%{_unitdir}/rhnsd.service
+%else
%{_initrddir}/rhnsd
+%endif
%{_mandir}/man8/rhnsd.8*
%doc LICENSE
--
1.7.10.4
>From b7bef2628996765fc0e67412bfefe772dd5ae30f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Miroslav=20Such=C3=BD?=
Date: Sun, 17 Jun 2012 17:16:57 +0200
Subject: [PATCH 2/3] implement osad.service for systemd
---
client/tools/osad/osad.service | 11 +++
client/tools/osad/osad.spec| 31 ---
2 files changed, 35 insertions(+), 7 deletions(-)
create mode 100644 client/tools/osad/osad.service
diff --git a/client/tools/osad/osad.service b/client/tools/osad/osad.service
new file mode 100644
index 000..5597571
--- /dev/null
+++ b/client/tools/osad/osad.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=OSAD daemon
+After=syslog.target network.target
+
+[Service]
+EnvironmentFile=-/etc/sysconfig/osad
+PIDFile=/var/run/osad.pid
+ExecStart=/usr/sbin/osad --pid-file $PIDFile
+
+[Install]
+WantedBy=multi-user.target
diff --git a/client/tools/osad/osad.spec b/client/tools/osad/osad.spec
index cba0768..dd74885 100644
--- a/client/tools/osad/osad.spec
+++ b/client/tools/osad/osad.spec
@@ -16,7 +16,7 @@ Group: System Environment/Daemons
License: GPLv2
URL: https://fedorahosted.org/spacewalk
Source0: https://fedorahosted.org/releases/s/p/spacewalk/%{name}-%{version}.tar.gz
-Version: 5.10.44
+Version: 5.11.0
Release: 1%{?dist}
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
@@ -35,17 +35,24 @@ Requires: PyXML
%endif
Conflicts: osa-dispatcher < %{version}-%{release}
Conflicts: osa-dispatcher > %{version}-%{release}
-%if !0%{?suse
[Spacewalk-devel] cobbler 2.2 version
Hi all, in this thread: https://www.redhat.com/archives/spacewalk-devel/2012-July/msg00045.html I saw people saying that cobbler version 2.2 has issues working together with spacewalk 1.7 However: I had the EPEL activated when I upgraded from 1.6 to 1.7, and cobbler updated as well, so now I'm currently running cobbler 2.2.1 together with Spacewalk 1.7, and no issues so far (apart from the fact that I needed to regenerate the kickstart profiles, but a small script resolved that just fine). Is this something that I now should be worried about when upgrading to 1.8 in the future? Since cobbler 2.2.3 is also out, but I'm now holding back on updating that part ... Franky ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] API Ruby scripts example
* Gilles Dubreuil [Jul 18. 2012 08:55]: > Thinking about adding Ruby script examples for Spacewalk API documentation. > Some people (Red Hat customers) have asked how to use Ruby to communicate > with the Spacewalk/RHN Satellite API. > > So what about having Ruby examples along the Perl and Python API ones? > > Files examples are available at: > > http://people.redhat.com/gdubreui/spacewalk-ruby Great, thanks ! Just for completeness, I played around with Ruby and the Spacewalk API as well a couple of months ago: https://github.com/kkaempf/ruby-spacewalk Enjoy ! Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] View services and partitions
Hello list, I would like to add two functionnalities to Spacewalk (without any idea on an approx date) but would like to check with you if it's OK. 1) Add a page on System to manages services on the clients, with 2 views: a) Something like the output of chkconfig command (dunnon how to get this from python!), and being able to modify the configuration b) Planify start/stop/restart of the services (interface to service command) 2) Have the soft partitionning of the client in the web ui Now, my questions. First, do you agree this would be interesting features? Now on an architecture point of view: - should it be an additional client package or integrated in the actual code? - on the server, should it be new web pages or integrated in existing ones? - If you have any advices, I'll take them with great pleasure! Thanks in advance, Pierre ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] View services and partitions
I want to add services configuration for 2 reasons: - being able to update a rpm AND schedule a service restart - being able to see the actual configuration of the server For the second point, yes, I was talking about disk partitionning. Something like df-h about of /etc/fstab content nicely presented. 2012/7/19 Patrick Hurrelmann : > On 19.07.2012 09:13, Pierre Casenove wrote: >> Hello list, >> I would like to add two functionnalities to Spacewalk (without any >> idea on an approx date) but would like to check with you if it's OK. >> 1) Add a page on System to manages services on the clients, with 2 views: >> a) Something like the output of chkconfig command (dunnon how to get >> this from python!), and being able to modify the configuration >> b) Planify start/stop/restart of the services (interface to service command) >> 2) Have the soft partitionning of the client in the web ui >> >> Now, my questions. >> First, do you agree this would be interesting features? >> Now on an architecture point of view: >> - should it be an additional client package or integrated in the actual code? >> - on the server, should it be new web pages or integrated in existing ones? >> - If you have any advices, I'll take them with great pleasure! >> >> Thanks in advance, >> >> Pierre > > Hi Pierre, > > personally I like this idea. On the other hand one could argue that such > functionality does not belong inside SW. But as rpms are pushed and > services get updated this would be very handy if these functionalities > are connected. > E.g. > update rpm A with service Ad. Schedule update _and_ restart of service. > install rpm B with service Bd. Schedule install _and_ activate service > > But you you please elaborate point 2? Are you speaking of disk > partitioning or am I getting this wrong? > > Regards > Patrick > > -- > Lobster LOGsuite GmbH, Hauptstraße 67, D-82327 Tutzing > > HRB 178831, Amtsgericht München > Geschäftsführer: Dr. Martin Fischer, Rolf Henrich > > ___ > 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] View services and partitions
On 19.07.2012 09:13, Pierre Casenove wrote: > Hello list, > I would like to add two functionnalities to Spacewalk (without any > idea on an approx date) but would like to check with you if it's OK. > 1) Add a page on System to manages services on the clients, with 2 views: > a) Something like the output of chkconfig command (dunnon how to get > this from python!), and being able to modify the configuration > b) Planify start/stop/restart of the services (interface to service command) > 2) Have the soft partitionning of the client in the web ui > > Now, my questions. > First, do you agree this would be interesting features? > Now on an architecture point of view: > - should it be an additional client package or integrated in the actual code? > - on the server, should it be new web pages or integrated in existing ones? > - If you have any advices, I'll take them with great pleasure! > > Thanks in advance, > > Pierre Hi Pierre, personally I like this idea. On the other hand one could argue that such functionality does not belong inside SW. But as rpms are pushed and services get updated this would be very handy if these functionalities are connected. E.g. update rpm A with service Ad. Schedule update _and_ restart of service. install rpm B with service Bd. Schedule install _and_ activate service But you you please elaborate point 2? Are you speaking of disk partitioning or am I getting this wrong? Regards Patrick -- Lobster LOGsuite GmbH, Hauptstraße 67, D-82327 Tutzing HRB 178831, Amtsgericht München Geschäftsführer: Dr. Martin Fischer, Rolf Henrich ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
