BECO What happened since April followed by Our plans What happened since April Quick reminder of the original plan CO 3 What we did Release of version 100 Training Support ID: 815735
Download The PPT/PDF document "FESA S. Deghaye for the FESA team" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
FESA
S.
Deghaye for the FESA team
BE/CO
Slide2What happened since April?
followed by “Our
plans”
Slide3What happened since April
Quick reminder of the original plan (CO
3
)
What we did:
Release of version 1.0.0
Training
Support
Preparation and release of version 1.1.0
RDA3 integration
Slide4FESA strategic planning ’13
(CO
3
approved version)
Main goal in LS1:
migrate as many FESA
2.10 classes
as
possible
to
FESA 3
Major milestones in 2013
Feb: FESA3 v0.9 for early adopters (~20 classes)
1
st
of July: FESA3 v1.0 released for 32 & 64 bits
Sep: Stop
new
FESA2 developments
Oct: FESA3 v2.0-RC with
RDA3 for early adopters
Dec: FESA3 v2.0 with RDA3 as main release
Slide5That was the plan…
… and what we actually did was…
Slide6Release of version 1.0.0
As agreed in C03 –
development
version for the
01-07-2013
Delivered on time but known missing features
(e.g. timing domain data) =>
1.1.0 needed
Dependencies: RDA2, new timing (
TimDT
)
Support for Linux 32 and 64 bits only
Slide7Training
Two courses available:
FESA Basics
(2 days): basic FESA +
dev
environment
FESA Advanced
(1 day) more advanced FESA features
12 persons per session in the CTC
So far:
5 sessions for Basics
(~60
persons)
3 sessions (
4
th
mid-Oct
) for Advanced
(~36
persons)
Slide8Support
Support organised (
r
ota - 1 week each)
430+ support requests/information requests
Wide range
- from
design to debug, from simple C++ problem to complex FESA behaviour
+/-
16 issues a week
!
Takes
more than 1
FTE
Slide9Version 1.1.0
Version
1.1.0
released the
12
th
of September
Impacted all parts (model, DB, code gen, C++, plug-in)
Contains many fixes/improvements e.g.:
Timing domain data support
The
rolling buffer has been improved and some side-effects have been fixed.
Added C++ methods
to ease
migration
Improved
release
procedure (e.g.
archi
info)
Improved Controls
TestBed
integration for better overall quality
…
Slide10RDA3 integration
Close contact with CMW team
Involved in all the discussions
Involved in the interim reports
Very good collaboration from FESA
PoV
August
Study how the RDA2 integration is done
First
tests and prototypes with RDA3
Result: running
both RDA 2
& 3
in FESA 3 but no
connection
between RDA 3 and FESA
Slide11Our Plans
for the rest of the year and early next year
Slide12Our plans - Main strategic goals
Continue
migration to FESA 3
Support & Training
Limit new
features
RDA 3 integrations
V2.0.0-EA
*
with missing
features ASAP
V2.0.0 before the dry
runs
Support ACCOR
Installations, dry runs…
*
Early Adopters
Slide13RDA3
Important change
Affects:
C++ Framework
Code generation
Very different
API
more
than a simple drop-in
replacement
i
t’s C++ and XSLT…
Slide14RDA3 – the plan
Integration (since
9
th
of S
eptember)
Get scalars on simple class (custom code only)
Get
scalars
on simple class (generated code)
Get other types (array 1D, 2D)
Set scalars, array 1D & 2D (custom and generated code)
Subscription (USER only
)
Navigator (RDA3 Java client)
Support for non-user selector (waiting
for Timing
)
FESA 3 class as a RDA3 client
(waiting for CMW)
FESA 3 V2.0.0-EA
(early adopters)
Breaking news !!!
Geneva 30-09-2013, 14:15
A successful get (actually 10 of them) was done on a FESA 3 class using RDA 3.
Slide15RDA3 – the risks
Planning
risk
We know what and who
We don’t know the
technical problems awaiting
E.g. RDA3 namespaces (aliases, migration tool) ?!?
Early-Adopter version ASAP but not before end of October
Technical risk
Bugs & sub-optimal
impl
. of the FESA3-RDA3 glue
Careful validation of the FESA server part (functional & non-functional)
Slide16ACCOR – Installations & d
ry runs
Migration of operational devices from
GM
&
FESA 2 to FESA 3
first
tests with Steen &
co
this
week
Navigator
for operational FECs (S. Jackson
)
Ensure that FESA 3 can be used in dry runs
E
xpert support to diagnose/fix problems on the fly during the dry runs
Move of FESA
3 devices from one class version to another (manual intervention so far
)
Slide17Major milestones
FESA 3 version
2.0.0-EA
end of October
FESA 3 version
1.2.0
with latest improvements and fixes
before version 2.0.0 before the
end of the year
FESA 3 version
2.0.0 early next year
Changelog
of version 2.0.0 is nothing
but
RDA3
Version
2.0.0 hard deadline
is
1 week before the Linac2 dry-run
(Steen, Daniel Calcoen, Richard Scrivens)
Keep
the
two branches
alive until
mid-14
(the longer the more expensive and error-prone)
Slide18Operational deployment of RDA3
FESA User guidelines
User releases his class with FESA 1.x (
a.b.c
)
User moves
to
FESA 2.0
User releases new version
(
d.e.f
)
User moves
devices from
a.b.c
to the
d.e.f
, rebuilds
and
reboots the
FEC.
User tests
I
f
rollback
is needed,
reverse point 4
Slide19Dry run
Dry run
FESA3/RDA3 fall-back solution
FESA 3
V 1.X
FESA 3
V 2.X
FESA
Class A
Dates are for illustrative purpose
only
0
3
1
FEC
XYZ
2
RDA3 only
Bug-fix release
1 week min
deploy
deploy
01-Dec
01-Feb
01-May
= release