Details:
by Jose Manimala
Can you define this for me:
A xen guest to run a test instance of the TurboGears voting
application along with a db backend.
1. whats xen guest
IRC will be a problem becaus my college has banned IRC. but i can mail
you. everything seems fine. i am yet to set up python on my comp. can
you point me to an rpm or a guide to its install.
--
Jose M Manimala
S6 Computer science and engineering
Rajagiri School Of Engineering And Technology
Ph: +919846367850
http://www.jmm-blog.co.nr
GPGkeyID: 98FF52D2
17 years
Hello
by Jose Manimala
Hey,
my name is jose m manimala. I am a server
administrator and a web programmar and have good knowledge of web
technologies(jsp,php,asp,soap,ajax). Hoping i could be of help with
web server administartion and web technologies. I run a fedora core 6
machine with tomcat and apache running on it. Have also experience
with linux kernel compiling and shell scripts.... Hope i can be of
help.
i am doing my graduate studies in cochin, India.
cheers
--
Jose M Manimala
S6 Computer science and engineering
Rajagiri School Of Engineering And Technology
Ph: +919846367850
http://www.jmm-blog.co.nr
17 years
Software in infrastructure vs repositories
by Rahul Sundaram
Hi
Has Fedora Infrastructure team consider a rule not to deploy any
proprietary software and not even any software that is not available in
the official Fedora repository? That would make things easier for
ensuring good packaging, maintenance and licensing.
Rahul
17 years
App3 unreachable
by Paulo Santos
Hi guys,
Looks like app3 is pingable but we are unable to ssh into it. Same goes if
you telnet to port80 to test http connectivity.
>From what i know both app3 and app4 should be reachable, since they are
hosting mirrormanager, is this correct ?
[santosp@bastion ~]$ telnet app3 80
Trying 10.8.34.61...
telnet: connect to address 10.8.34.61: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
[santosp@bastion ~]$ ssh -v app3
OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to app3 [10.8.34.61] port 22.
debug1: Connection established.
debug1: identity file /home/fedora/santosp/.ssh/identity type -1
debug1: identity file /home/fedora/santosp/.ssh/id_rsa type -1
debug1: identity file /home/fedora/santosp/.ssh/id_dsa type -1
(stalls until timeout)
Thanks,
Paulo
17 years
report_mirror traceback
by Andreas Kupfer
Hi,
I get the following traceback on Ubuntu LTS:
kupfer@ftp-a:~$ ./report_mirror -c ./report_mirror.conf
Traceback (most recent call last):
File "./report_mirror", line 240, in ?
main()
File "./report_mirror", line 236, in main
print server.checkin(base64.urlsafe_b64encode(bz2.compress(p)))
File "/usr/lib/python2.4/xmlrpclib.py", line 1096, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request
verbose=self.__verbose
File "/usr/lib/python2.4/xmlrpclib.py", line 1147, in request
return self._parse_response(h.getfile(), sock)
File "/usr/lib/python2.4/xmlrpclib.py", line 1286, in _parse_response
return u.close()
File "/usr/lib/python2.4/xmlrpclib.py", line 744, in close
raise Fault(**self._stack[0])
xmlrpclib.Fault: <Fault 1: 'HostCategoryDir() did not get expected keyword
argument directoryID'>
Yours,
Andreas aka ScottyTM
--
*"NO CARRIER" - A Naval Aviator's worst nightmare!*
17 years
Distributing static content
by Mike McGrath
Over the last couple of weeks we've been using puppet to distribute
static content across some of our application servers and proxy servers.
Static content might include the new static webpage or an application
like our accounts system.
This has proved to be a bit of an issue. Puppet wasn't really designed
to do this and as such puts a noticeable load on the boxes while running
as well as causing longer runs. Puppet works for this but we're
currently into it managing thousands of files and initial deploys take a
long time :) In the past we'd discussed moving some things (like
turbogears apps) around using rpms. We can do that with tg pretty
easily. But what about other static content, images, things like that?
This needs to be scriptable from start to finish, here's the options as
I see them:
1. Straight nfs mount (boo)
2. nfs mount to cron copy the files
3. recursive wget to an http store somewhere
4. rsync via ssh keys or rsync server (I'm currently leaning towards this)
5. Figure out how to make puppet more efficient with large numbers of files.
We've got a whole pool of sysadmins on this list. How do you deal with
these issues in your current environments?
-Mike
17 years
bodhi
by Luke Macken
So we're less than a week away from F7, so why not completely change the
way updates are pushed? :)
We're going to use mash[0] to compose our updates repo instead of managing
it by hand. This removes the burden of multilib, repo-cleaning, and
dep closure checking from bodhi.
This means that we need to change the push process to be something like:
- Move all submitted builds from
dist-f7-updates-candidate to dist-f7-updates-testing in Koji
- Run mash
- Add/remove appropriate updates from updateinfo.xml and insert it
into all of the repodata
- Sync out to wallace, which will sync to the mirrors
In theory, this should do the trick.
The roadmap[1] to 1.0 should be fairly accurate now. So what we have
left, aside from the new push process mentioned above, is:
- ACLs. We need to make sure that all updates are submitted by the
appropriate {,co-}maintainers.
- Package signing stuff. Jesse pointed me to the sign_unsigned tool[2]
that we could potentially integrate with to help do this.
I won't be able to start hacking on this until monday, as I am graduating
tomorrow and then moving on Sunday, so any help would be appreciated :)
luke
[0]: http://git.fedoraproject.org/?p=hosted/mash;a=summary
[1]: https://hosted.fedoraproject.org/projects/bodhi/roadmap
[2]: http://git.fedoraproject.org/?p=fedora/releng;a=blob_plain;f=scripts/sign...
17 years
RFR: svn.fedoraproject.org instance for Certificate System
by Margaret Lum
> _Project Sponsor_
> Name: Red Hat
> Wiki Name: http://pki-svn.fedora.redhat.com/wiki/Main_Page
> Infrastructure Sponsor: Red Hat
> Owners/Contacts @ Red Hat: Thomas Kwan, Matt Harmsen, Steve Parkinson,
> Margaret Lum
>
> _Project Info_
> Project Name: Certificate System
> Target Audience: folks interested in Open Source PKI software
> Expiration Date (required): indefinite
> Description/Summary: This project is an enterprise-class Open Source
> Certificate System for Linux, supporting certificate management, key
> archival, OCSP support and smartcard life-cycle management.
> Project plan (Detailed) and Goals: Review documentation here:
> http://pki-svn.fedora.redhat.com/wiki/Documentation.
>
> _Specific resources needed_:
> We require an svn.fedoraproject.org instance for the following
> repositories:
> idm/pki
> idm/fortitude
>
> _Additional Info_
> Please contact me further for enabling the ACLs on each repository.
> Initially, I would like these to be CLOSED to non-redhat.com domains,
> while we start importing code into the repository. Also, must I
> submit RFRs for code imports, or can I import these directly?
>
>
17 years
