Project

General

Profile

Task #2166

Jenkins: CentOS 7 slave

Added by Junxiao Shi about 4 years ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Category:
Build
Target version:
Start date:
Due date:
% Done:

40%

Estimated time:
3.00 h

Description

Deploy CentOS 7 x86_64 slaves.

Collect the list of packages needed by projects, so that the deployment can be repeated.


Related issues

Has duplicate NFD - Task #4610: Make CentOS 7 an official (CI-tested) platformIn Progress

History

#1 Updated by Lan Wang about 4 years ago

  • Assignee changed from Lan Wang to Ashlesh Gawande

#2 Updated by Ashlesh Gawande about 4 years ago

  • % Done changed from 0 to 50

Installed Virtual Machines and configured Networking and ssh.

#3 Updated by Alex Afanasyev about 4 years ago

Ashlesh, how do you managing images? Just in plain virtualbox?

I have suggestion to invest time into building vagrant images and use puppet as a configuration management. It would still be virtualbox, but this would allow simpler instantiation and management of vms. Moreover, others would be able to easily instantiate VM that is used for testing.

#4 Updated by Ashlesh Gawande about 4 years ago

Yes I am using VirtualBox command line to make VMs. Right now I just made three VMs. How do I build vagrant images?

#5 Updated by Alex Afanasyev about 4 years ago

I have limited knowledge about vagrant, as I basically just started learning. Some tutorial is available at https://docs.vagrantup.com/v2/boxes.html.

I can only say that creating "box" in vagrant is straightforward and simple. Most likely, you will be able to reuse the virtualbox image you already created.


Another piece that I briefly mentioned is Puppet. I have not used it at all, but a lot of projects use it for management purposes. So we need to investigate how it can help us.

#6 Updated by Ashlesh Gawande about 4 years ago

  • Status changed from New to In Progress

#7 Updated by Ashlesh Gawande about 4 years ago

Alright I have installed all dependencies on the three machines. Now should I install a puppet agent on them and make a Vagrant base box?

#8 Updated by Lan Wang about 4 years ago

go ahead if you know how to do those.

#9 Updated by Ashlesh Gawande about 4 years ago

Hi Alex

I am confused about installing puppet server. Should I just install puppet agent on each machine and you will install and configure a server or should I install and configure a puppet server?

#10 Updated by Alex Afanasyev about 4 years ago

I'm not sure. I don't really know what puppet is and how to use it. You can install agents on VMs and then try to figure out how to use them (and then tell us).

#11 Updated by Alex Afanasyev about 4 years ago

And, just in case. It is optional. If it is too complicated to use / there are no clear benefits, then don't spend too much time on it.

#12 Updated by Ashlesh Gawande about 4 years ago

  • % Done changed from 50 to 100

I am sorry I forgot to update here. I have abandoned the puppet installation. The machines can be logged in at:

I have vagrant boxes ready, which can be used to repeat deployment. Where do I upload them to?

#13 Updated by Alex Afanasyev about 4 years ago

You can try to upload them to vagrant cloud (https://vagrantcloud.com). I haven't done it before, but they have some documentation about it.

#14 Updated by Alex Afanasyev about 4 years ago

CentOS and Fedora required additional tweaking of /etc/sudoers: default config requires tty to run sudo, which prevents jenkins script to do any meaningful task.

See http://unix.stackexchange.com/questions/122616/why-do-i-need-a-tty-to-run-sudo-if-i-can-sudo-without-a-password

#15 Updated by Alex Afanasyev about 4 years ago

Also failed and also most likely because of limited memory:

#16 Updated by Ashlesh Gawande about 4 years ago

I disabled requiretty for jenkins user.

#17 Updated by Alex Afanasyev about 4 years ago

Still failing at random places. http://jenkins.named-data.net/job/ndn-cxx/OS=CentOS7/1696/consoleFull

I have no idea what is going on and how to fix that... There is almost 2Gb free space available plus 2Gb of swap (which is not used).

#18 Updated by Junxiao Shi over 3 years ago

  • Status changed from In Progress to Closed

#19 Updated by Junxiao Shi 9 months ago

  • Status changed from Closed to New
  • Assignee deleted (Ashlesh Gawande)
  • Target version changed from v0.3 to v0.7
  • % Done changed from 100 to 0

As discussed in 20180409 NFD call, we should reactivate CentOS7 slaves.

#20 Updated by Davide Pesavento 9 months ago

  • Subject changed from Jenkins: CentOS 7.0 slave to Jenkins: CentOS 7 slave
  • Description updated (diff)

#21 Updated by Davide Pesavento 4 months ago

  • Status changed from New to In Progress
  • Assignee set to Md Ashiqur Rahman

#22 Updated by Davide Pesavento 4 months ago

  • Has duplicate Task #4610: Make CentOS 7 an official (CI-tested) platform added

#23 Updated by Davide Pesavento 4 months ago

  • % Done changed from 0 to 40

CentOS-7-64bit has been enabled for ndn-cxx.

#24 Updated by Junxiao Shi about 1 month ago

I notice that both CentOS 7 slaves are deployed on the same site. One needs to be moved to fulfill resiliency requirements and prevent downtime due to single site failure.

Also available in: Atom PDF