Re: migration of services from linode server to phx2 lab

2015-06-16 Thread Michael Scherer
Le mardi 16 juin 2015 à 03:38 -0400, Eyal Edri a écrit :
 
 - Original Message -
  From: Karsten Wade kw...@redhat.com
  To: infra@ovirt.org
  Sent: Tuesday, June 16, 2015 6:29:04 AM
  Subject: Re: migration of services from linode server to phx2 lab
  
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
  
  Hi,
  
  Between myself (original linode01.ovirt.org admin) and Michael (misc,
  aka knower-of-stuff), what can we do to get us off this Linode
  instance? From what I can tell, at least Mailman is running from there.
  
  If we still need service failover, can we switch to another Red
  Hat-provided service such as an OpenShift or OpenStack instance?
 
 Hi Karsten,
 I know this has been taking for too long, but unfortunately there are many 
 reasons
 and obstacles that prevented us from moving, which i'll explain below,
 while there is a risk right now of moving services to PHX, but i think we can 
 try.
 
 Blocking items:
  - were missing more hypervisors to the production DC ( we finally got them 
 installed last week, and are now in final stages of bringing them up)
  - storage issue - currently NFS storage is quite slow, we are testing moving 
 to a mixed mode of local + nfs for the jenkins slaves,
though might be that the production service won't get 
 affected too much - worth a try.
  - lack of monitoring for servers, which might add risk if we hit an issue.
 
 there are some other issues, but not blocking imo.
 
 Here is what needs to be done (per service to migrate off linode), and we'd 
 appreciate any help given.
 1. create new VM on production DC in PHX (assign dns/ip/etc.. )
 2. create puppet manifests to manage that vm, so it will be easy to reproduce 
 it and maintain it
 3. install the relevant software on it (for e.g mailman/ircbot/etc...)
 4. test to see it works
 5. do the actual migration (downtime of existing service, and bringing up the 
 new one)

So, last time I did look, the puppet setup was a bit unfinished rather
overkill ( using r10k to deploy count as overkill when you do not have
stage/prod/qa, at least for me ). Did stuff changed, or should first
some effort be made to fix/automate/improve the puppet setup ?


-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS



signature.asc
Description: This is a digitally signed message part
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


migration of services from linode server to phx2 lab

2015-04-28 Thread Eyal Edri
Hi,

We're finally able to start migrating services from linode01 to a production 
VMs on the phx lab. [1]
I'd like to go over all the services and decide which ones we want to migrate 
and what else exists on linode:

Dns entries: resources.ovirt.org, lists.ovirt.org
Services:
   mailman 
   ovirt irc bot 
   spamassin   
   postfix ( aliases for ovirt.org )
   package repositories
   mirrorlist

Storage:
   gerrit backups (still there?)
   download for rpm and code (repos)


For each we should decide if we're migrating or just installing a new server 
with new configuration
on phx. optimally we'd like to do it with relevant puppet classes per service.

Please share your thoughts about each service and feel free to volunteer and 
help our with migrating
one of these.


[1] hopefully we'll also have the ilos working by next week, so another reason 
to migrate.

-- 
Eyal Edri
oVirt infra team
irc: eedri

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


Re: migration of services from linode server to phx2 lab

2015-04-28 Thread David Caro
On 04/28, Eyal Edri wrote:
 Hi,
 
 We're finally able to start migrating services from linode01 to a production 
 VMs on the phx lab. [1]
 I'd like to go over all the services and decide which ones we want to migrate 
 and what else exists on linode:
 
 Dns entries: resources.ovirt.org, lists.ovirt.org
 Services:
mailman 

I'm not familiar with mailman, so for me it might be the most complicated
(email usually is also very sensitive to ip changes)

ovirt irc bot 

This might be the simplest

spamassin   
postfix ( aliases for ovirt.org )
package repositories

fairly simple to move too, but careful with all the release crons and setups
around the publishers

mirrorlist

the mirrorlist is just a basic cgi script, also easy to move

 
 Storage:
gerrit backups (still there?)

this was migrated to jenkins.ovirt.org due to space issues iirc

download for rpm and code (repos)

the code is on gerrit itself

 
 
 For each we should decide if we're migrating or just installing a new server 
 with new configuration
 on phx. optimally we'd like to do it with relevant puppet classes per service.
 
 Please share your thoughts about each service and feel free to volunteer and 
 help our with migrating
 one of these.
 
 
 [1] hopefully we'll also have the ilos working by next week, so another 
 reason to migrate.
 
 -- 
 Eyal Edri
 oVirt infra team
 irc: eedri
 
 ___
 Infra mailing list
 Infra@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/infra

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization RD

Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605


pgp5q4SmT8jFn.pgp
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra