From: Remo Andreoli <Remo.Andreoli@santannapisa.it>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RT-Cloud 2024 - The third International Workshop on Real-Time Cloud Systems (Extended submission deadline: 16th May)
Date: Sun, 12 May 2024 04:07:35 +0000 [thread overview]
Message-ID: <DB6PR03MB31092BFEA07904C3570F5E20E7E12@DB6PR03MB3109.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <DB6PR03MB310998EFF51082D702A82C92E7E12@DB6PR03MB3109.eurprd03.prod.outlook.com>
--------------------------------------------------------------------------------
The third International Workshop on
Real-Time Cloud Systems
(RT-Cloud 2024)
www.ecrts.org/rt-cloud-2024/
--------------------------------------------------------------------------------
While most cloud services operate on a best-effort basis and provide no
timing guarantees, there is a growing interest in cloud technologies for
industrial and critical applications. Edge computing is a recent paradigm
that brings processing and storage resources closer to the user. As a
result, it provides benefits such as low latency and high bandwidth while
still providing the benefits of cloud computing, making it lucrative for
low-latency, real-time / safety-critical applications. However, a higher
degree of determinism is desired for cloud and edge technologies to be
fully embraced by the real-time / safety-critical industry. This calls
for new techniques and methodologies to design predictable and reliable
cloud/edge technologies and applications.
The 3rd International Workshop on Real-Time Cloud Systems (RT-Cloud) aims
to bring together industrial and academic researchers and become a forum
for discussing topics (including ideas, open and upcoming challenges, use
cases, initiatives, calls to action, and projects, regulations and
standards, future research directions, etc.) related to real-time cloud/
edge/fog computing and virtualization techniques. This year, the workshop
will have a focus on industrial cloud use cases. The workshop also
welcomes short and full papers that consider:
- New technologies, innovative approaches/ideas, including work-in-progress
- Open problems and upcoming challenges
- Regulations and standards
- Demos and tutorials, especially, for open-source projects
- Call to actions
- Experimental reports on existing technologies, including negative ones
Original full and short papers on all aspects of real-time/safety-critical
cloud/edge/fog and virtualization are welcome. Researchers are encouraged
(but not limited) to submit papers regarding the following:
1. Use cases and applications for RT-cloud
- Use of cloud computing principles to improve performance/safety/
security in existing real-time systems/use cases
- Real-time cloud and edge applications
-- Industrial use cases and requirements
-- Experiments and experiences with RT-cloud
-- Real-time / safety-critical applications as a cloud-based service
-- Real-time extension to existing cloud-computing technologies
-- Decomposition between the edge, fog, and cloud
2. Virtualization and cloud computing technologies/models for RT-cloud
- Development Operations (DevOps) for RT-cloud
- Deterministic hypervisors and cloud execution environments, including
containers and WASM
- Real-time Saas, Paas, Iaas, and XaaS (anything as a service model)
- Execution and deployment models for RT-Cloud, including
serverless computing
- Microservices Architectures for real-time system
- Modeling of network and cloud, execution stacks, and applications
- Adaptive SLAs for RT-cloud
3. Resource management (including monitoring, scheduling) and
orchestration for RT-cloud
-- Predictable orchestration and cloud operation
-- Tools and techniques for resource sharing and isolation
-- End-to-end resource management and scheduling in edge-cloud continuum
-- Co-scheduling of virtual network and compute resources
-- Edge-cloud-IoT continuum and interaction/interfacing
-- QoS mechanisms and isolation guarantees
-- Autonomous monitoring systems
4. Safety and Security for RT-cloud
- Assurance in RT-cloud, deterministic scaling, fail-over, migration, etc.
- Trusted RT-Cloud/edge environment
-- Considering security and privacy together with safety
--------------------------------------------------------------------------------
IMPORTANT DATES
Submission deadline: May 16, 2024 (AoE)
Notification of Acceptance: June 6, 2024
RT-Cloud Workshop: July 9, 2024
ECRTS 2024: July 9-12, 2024
--------------------------------------------------------------------------------
SUBMISSION INSTRUCTIONS
Manuscripts must present original work. They must be written in English,
using the IEEE format, and submitted through easychair. There are no strict
rules about the number of pages, but the recommended length for full papers
is 6 to 8 pages, and for short papers is 3-4 pages.
Submission link: https://easychair.org/conferences/?conf=rtcloud2024
All submissions will be reviewed by the technical program committee members,
and accepted papers will be included in the workshop proceedings, which will
be available online on the workshop website. Papers will not be assigned a
DOI to enable authors to submit a full/extended paper later on to a
conference or a journal. For every accepted paper, at least one author is
expected to register for the workshop and present the paper.
--------------------------------------------------------------------------------
WORKSHOP CHAIRS
- Johan Eker (Lund University/Ericsson)
- Luca Abeni (Scuola Superiore Sant'Anna - luca.abeni@santannapisa.it)
- Gautam Gala (University of Kaiserslautern-Landau - gala@eit.uni-kl.de)
PUBLICITY CHAIR
- Remo Andreoli (Scuola Superiore Sant'Anna - remo.andreoli@santannapisa.it)
parent reply other threads:[~2024-05-12 4:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DB6PR03MB310998EFF51082D702A82C92E7E12@DB6PR03MB3109.eurprd03.prod.outlook.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB6PR03MB31092BFEA07904C3570F5E20E7E12@DB6PR03MB3109.eurprd03.prod.outlook.com \
--to=remo.andreoli@santannapisa.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).