Difference: ACSWorkshop2014GroupExercise (6 vs. 7)

Revision 72014-09-06 - JorgeIbsen

Line: 1 to 1
 
META TOPICPARENT name="ACSTrainingCourse"

Group Exercises

Line: 7 to 7
 

General Setup

Course virtual machine

Changed:
<
<		To run the SL5 vmware virtual machine SL5 (32 bits) containing the ACS release 2014.2 you'll need the latest version of vmware player (linux, windows), vmware workstation (linux, windows) or vmware fusion (mac). To reduce the load on the host machine, each machine is running at user level 3 (no graphical environment). Your host environment should be able to open xterms and ssh connections to the guest OS.
>
>		To run the CentOS5 vmware virtual machine (32 bits) containing the ACS release 2014.2 you'll need the latest version of vmware player (linux, windows), vmware workstation (linux, windows) or vmware fusion (mac). To reduce the load on the host machine, you may choose to run at user level 3 (no graphical environment). In this case, your host environment should be able to open an xterm and ssh connections to the guest OS.
 

Network

The network is configured to assign a fix IP address to each virtual machine. The course virtual machines will be named:
Changed:
<
<
  • dba
  • ins
  • tel
  • sch
  • its

and each machine will have the following users:

  • tel
  • ins
  • sch
  • dba
  • its

Group Exercise #1: Setting up an ACS work environment

Before you begin

>
>
  • database
  • instrument
  • telescope
  • scheduler
  • integration

Instructions to change the hostname of your virtual machine can be found in this article: CentOS name change. To facilitate name resolution, the hosts file in your virtual box should include an entry for each virtual machine used during the course: 

# virtual machine <vm_name>
192.168.1.XXX   <vm_name>.<domain> <vm_name>

alma unix group

An alma unix group with GID 335 should be created in your environment. This is strictly speaking just a convention, but since many scripts may make reference to this group, having it may make life simpler. If you don't have it, simple add it using the groupadd command: 
# /usr/sbin/groupadd -g 335 alma

Users

The following unix users will be used in the course during the development:
  • its: for integration
  • teamt: telescope development
  • teami: instrument development
  • teams: scheduler development
  • teamd: database development

Add them to your machine using the =useradd+ command: 

# /usr/sbin/useradd -m -g alma -s /bin/bash -d /home/<user> <user>

Before you begin

 
  1. Check that your machine is booting correctly and getting a fix IP address
  2. Check that almamgr account exits and that you can login to it
  3. Check that the /alma/ACS-2014.2/ directory exists and is populated
  4. Check that your development account is using a bash shell
    • Simply run echo $SHELL and check that the output reads /bin/bash
Added:
>
>
  1. Create the course users in your virtual machine.
    • Use the same UIDs across the virtual machines to make the global configuration consistent

Group Exercise #1: Setting up an ACS work environment

 

Setting up the ACS environment variables

Changed:
<
<
  1. Login as the main user assign to your machine (f.i. tel)
>
>
  1. Login as the main user assign to your machine (f.i. teamt)
 
  1. Create a .acs directory
Changed:
<
<
    • cp -r /alma/ACS-2014.2/ACSSW/config/.acs $HOME
>
>
[user@host]$ cp -r /alma/ACS-2014.2/ACSSW/config/.acs $HOME
 
  1. Source the ACS bash profile
    • add the following lines to your $HOME/.bashrc file
Added:
>
>		# setting up INTROOT
  export INTROOT=$HOME/introot
Added:
>
>		# sourcing ACS environment variables
  source .acs/.bash_profile.acs
  1. Logout and login your account and open an xterm. The prompt should read
Changed:
<
<		 your_user>
>
>		user>
 

Starting/stopping ACS services and running the tools

  1. Start the ACS Command Center typing acscommandcenter at the command line
Line: 52 to 74
 
    • aragornContainer (Python)
  1. You can use the ACS Command Center or alternatively the following command lines:
Changed:
<
<		 acsStartContainer - acsStopContainer
>
>		user> acsStartContainer - user> acsStopContainer
 
  1. Start the tools from the Tools menu. Object Explorer and Logging Client in particular. Alternatively you can start the tools from the command line with the following commands: objexp, jlog
  2. Activate and deactivate ACS components from the object explorer
Line: 62 to 84
 

Group Exercise #2: Setting up a development environment

Setting up the your local git repository

Git is used as the source code repository. Below are the elementary working commands. A more complete git commands reference is here. Before you start you need to define your git user name (same as development account) and e-mail:
Changed:
<
<
  • git-config --global user.name $USER
  • git-config --global user.email $USER@$HOSTNAME
>
>
user> git-config --global user.name $USER
user> git-config --global user.email $USER@$HOSTNAME
 

Cloning the course repository

There is a central git repository at the integration server. You will clone that repository and do all further changes locally by issuing:
Changed:
<
<
  • git clone ssh://integration/opt/git/los.git
>
>
user> git clone ssh://its@integration/opt/git/los.git
 

Pulling from the repository to get updates

You can get the latests updates for your local repository from the central server:
Changed:
<
<
  • git pull
>
>
user> git pull
 

Pushing to the repository to provide your updates

To commit changes to your local repository:
Changed:
<
<
  • git add [changed files]
  • git commit
>
>
user> git add [changed files]
user> git commit
 And to push your changes back to the central server (and make them available to others):
Changed:
<
<
  • git push
>
>
user> git push
 If you are not sure you can always check the change status:
Changed:
<
<
  • git status

Setting up your INTROOT area

>
>		 user> git status

Setting up your INTROOT area

 Create an integration root area for your personal account (INTROOT) by issuing the following commands:
Changed:
<
<		 rm –rf $INTROOT getTemplateForDirectory INTROOT $INTROOT
>
>		user> rm –rf $INTROOT user> getTemplateForDirectory INTROOT $INTROOT
 

Setting up your your first software module

Documentation about tools and module structure: ALMA Software Development Tools and Integration Procedures. Create a new module using the getTemplate command:
Changed:
<
<
  • cd ~/
  • getTemplate -> directoryStructure -> create WS_MODROOT area ->
>
>
user> cd ~/<local repository>
user> getTemplate
and navigate the text menu as follows:
  • directoryStructure -> create WS_MODROOT area ->
 Inside the ICD module, run make all to compile the IDL files and generate all stubs and skeletons.
Changed:
<
<		 
  •  cd ~/<local repository>/ICD/src; make clean all install 
  •  cd ˜/<local repository>/<module name>/src; make clean all install
>
>
user> cd ~/<local repository>/ICD/src; 
user> make clean all install 
user> cd ˜/<local repository>/<module name>/src
user> make clean all install
 
Changed:
<
<

Group Exercise #N: LOS Development

>
>

Group Exercise #3: LOS Development

 

Assignments

The suggested development teams composition is:
  • Database (C++):
Line: 102 to 144
 
  • Telescope (C++):
  • Integration: Jorge, Tomás

First Day

Added:
>
>		The task for the first day is to implement a first empty component in C++ that compiles correctly, setting up the CDB and run a manual test using a python simple client. Progress will be measured as follows:
  • 30% C++ component code successfully compiling
  • 60% Test CDB configured and ability to use the object explorer to activate/deactivate the component
  • 100% Run a python simple client script to activate/deactivate to the component
 

Second Day

Changed:
<
<

Group Exercise #N: LOS Integration

Third Day

>
>		The tasks for the second day are to create a first automatic component test, a first system commit, running the test against an integrated test CDB, and incrementally adding functionality. The progress will be measured periodically against the following metric:
  • 30% First integration with at least manual tests
  • 60% Core per-component functionality ready
  • 100% Run of integrated system at the end of the day

Group Exercise #4: LOS Integration

The task for the third day is to add errors and logging to each component and fully integrate the system to run an automatic observation. Progress metrics are:
  • 30% Logging and Error handling coding
  • 60% Integrated test before lunch to , identifying key critical route
  • 100% Successful end-to-end automatic observation

TODO list

Who What Status
NN Something Question
 

Conclusions and Final Remarks

-- Jorge Ibsen - 2014-08-22 \ No newline at end of file

View topic | History: r17 < r16 < r15 < r14 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback