[Apologies if you got multiple copies of this invitation]
The Sixth (IEEE*) International Conference on Software Defined Systems
(SDS-2019)
Rome, Italy. June 10-13, 2019
http://emergingtechnet.org/SDS2019/
(*Technically Co-Sponsored by IEEE Italy Section)
*Call for Papers:*
Next generation cloud systems will require a paradigm shift in how they are
constructed and managed. Conventional control and management platforms are
facing considerable challenges regarding flexibility, dependability and
security that next generation systems will require. The cloud computing
paradigm has gone part of the way towards alleviating some of the problems
associated with resource allocation, utilization and managements (e.g., via
elasticity). However, many of the elements of a well-designed cloud
environment remain “stiff” and hard to modify and adapt in an integrated
fashion. This includes underlying networking topologies, many aspects of
the user control over IaaS, PaaS or SaaS layers when such is needed,
construction of XaaS services, provenance and meta-data collection, and so
on. In many situations the problem may be because service abstraction is
inadequate. Software Defined Systems (SDS) are systems that have added
software components which help abstract actual IT equipment and other
layers. One classical example, of course, are hypervisors. Such separation
provides a great opportunity for system administrators to more easily
construct and managing their systems through flexible software layers.
Software Defined Systems include Software Defined Networking (SDN),
Software Defined Storage, Software Defined Servers (Virtualization),
Software Defined Datacenters (SDD), Software Defined Security (SDSec), and
ultimately Software Defined Clouds (SDCloud) to name a few possibilities.
Individual solutions and seamless integration of these abstractions remains
in many respects a challenge. After the high success of the previous
editions (SDS'2014, SDS'2015, SDS'2016, SDS'2017 and SDS'2018), The sixth
International conference on Software Defined Systems 2019 (SDS'2019) will
continue to be a forum for scientists, researchers, students, and
practitioners to present their latest research results, ideas, and
developments in the area of software defined systems – both components and
their integration - and by implication advancement of next generation
clouds.
SDS 2019 aims to investigate the opportunities and in all aspects of
Software Defined Systems. In addition, it seeks for novel contributions
that help mitigating SDS challenges. That is, the objective of SDS 2019 is
to provide a forum for scientists, engineers, and researchers to discuss
and exchange new ideas, novel results and experience on all aspects of
Software Defined Systems.
Researchers are encouraged to submit original research contributions in all
major areas, which include, but not limited to:
* Software Defined Systems support for Cloud Computing.
* Software Defined Networking (SDN).
* SDN concepts, architecture, and APIs.
* Network Virtualization
* SDN and OpenFlow protocol
* Software Defined Radio
* Cognitive Radio Networks.
* Access Control models in SDN.
* Software Defined Storage.
* Storage Automation and Abstraction.
* Policy-driven storage provisioning.
* Software Defined Servers and Virtualization.
* Software Defined Datacenters.
* Software Defined Security o Security policies automation.
* Self-management systems.
* Autonomic Computing techniques.
* Real-time load prediction model to optimize the user satisfaction.
* Software Defined Systems Scalability.
* Software Defined Systems optimization.
* Software tools and frameworks to support SDS.
* Software Defined Systems challenges and opportunities
* Software Defined Systems surveys.
* Social engineering, insider threats system for SDS.
* Incident Handling and Penetration Testing with SDS.
* Software Defined Systems support if IoT.
* Security protocols in SDS.
* Security and privacy of mobile SDS based cloud computing
* Service-oriented architectures, service portability andP2P
* Network virtualization and cloud-based radio access networks
*Submission*
Papers selected for presentation will appear in the SDS Proceedings, which
will be submitted to IEEE Xplore for inclusion. Papers must be 8 pages in
IEEE format, 10pt font using the IEEE 8.5" x 11" two-column format, single
space, A4 format. All papers should be in PDF format, and submitted
electronically at Paper Submission Link. A full paper must not exceed the
stated length (including all figures, tables and references).
Submitted papers must present original unpublished research that is not
currently under review for any other conference or journal. Papers not
following these guidelines may be rejected without review. Also submissions
received after the due date, exceeding length limit, or not appropriately
structured may also not be considered. Authors may contact the Program
Chair for further information or clarification.
*Important Dates:*
Submission Date: 15 January 2019
Notification to Authors: 1 April 2019
Camera Ready Submission: 20 April 2019
Please send any inquiry on SDS 2019 to the Emerging Tech. Network Team at:
emergingtechnetwork(a)gmail.com
Reminder: Technical Advice IRC meeting again **Wednesday at 4-5 pm UTC AND
11-12 pm UTC** on #wikimedia-tech.
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Currently the codes for uncaught exceptions include the class name, for
example "internal_api_error_ReadOnlyError", or
"internal_api_error_DBQueryError", or possibly something like
"internal_api_error_MediaWiki\Namespace\FooBarException". As you can see in
that last example, that can get rather ugly and complicates recent attempts
to verify that all error codes use a restricted character set.
Thus, we are deprecating these error codes. In the future all such errors
will use the code "internal_api_error". The date for that change has not
yet been set.
If a client for some reason needs to see the class of the uncaught
exception, this is available in a new 'errorclass' data property in the API
error. This will be returned beginning in 1.33.0-wmf.8 or later, see
https://www.mediawiki.org/wiki/MediaWiki_1.33/Roadmap for a schedule. Note
that database errors will report the actual class, such as
"MediaWiki\rdbms\DBQueryError", rather than the old unprefixed name that
had been being maintained for backwards compatibility.
Clients relying on specific internal error codes or detecting internal
errors by looking for a "internal_api_error_" prefix should be updated to
recognize "internal_api_error" and to use 'errorclass' in preference to
using any class name that might be present in the error code.
In JSON format with errorformat=bc, an internal error might look something
like this:
{
"error": {
"code": "internal_api_error_InvalidArgumentException",
"info": "[61e9f71eedbe401f17d41dd2] Exception caught: Testing",
"errorclass": "InvalidArgumentException",
"trace": "InvalidArgumentException at ..."
},
"servedby": "hostname"
}
With modern errorformats, it might look like this:
{
"errors": [
{
"code": "internal_api_error_InvalidArgumentException",
"text": "[61e9f71eedbe401f17d41dd2] Exception caught: Testing",
"data": {
"errorclass": "InvalidArgumentException"
}
}
],
"trace": "InvalidArgumentException at ...",
"servedby": "hostname"
}
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
_______________________________________________
Mediawiki-api-announce mailing list
Mediawiki-api-announce(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce
Reminder: Technical Advice IRC meeting again **Wednesday 4-5 pm UTC** on
#wikimedia-tech.
Question can be asked in English & German.
The Technical Advice IRC Meeting is a weekly support event for volunteer
developers. Every Wednesday, two full-time developers are available to help
you with all your questions about Mediawiki, gadgets, tools and more! This
can be anything from "how to get started" over "who would be the best
contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
ToolsDB will be undergoing maintenance and updates, Tuesday, November 27th at 1730 UTC to 1800 UTC.
Actual outage times should be fairly brief, but during this time the database will be taken offline and the system rebooted. Due to the expected brief nature of the outage and the fact that some tables are not replicated (see https://wikitech.wikimedia.org/wiki/Help:Toolforge/Database#ToolsDB_Backups… <https://wikitech.wikimedia.org/wiki/Help:Toolforge/Database#ToolsDB_Backups…>), we are not planning on failing over to the replica at this time.
Brooke Storm
Operations Engineer
Wikimedia Cloud Services
bstorm(a)wikimedia.org <mailto:bstorm@wikimedia.org>
IRC: bstorm_
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hi,
next Tuesday, 2018-11-27 @ 17:30UTC we will reboot the
labnet1001.eqiad.wmnet server for maintenance and security updates.
This server provides virtual networking services for CloudVPS in the
main deployment (the old one, different from the eqiad1 deployment).
We won't be doing any failover prior to the reboot for operative reasons
(we measured the failover downtime is longer than the actual reboot time).
The impact of this brief reboot downtime will be:
* all VMs in the main CloudVPS deployment won't have network connectivity
* ongoing network connections (downloads, uploads) will fail and will
have to be restarted
* cross connectivity between VM instances in the main and eqiad1
deployment won't be possible
Thanks for your understanding, and let us know any issues you may find
after the reboot next week.
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hi,
next Tuesday 2018-11-20 at 17:30 UTC we will be rebooting the OSM
database (part of our data services) for maintenance and security updates.
In concrete the labstore1006.eqiad.wmnet (osmdb.eqiad.wmnet) server will
be rebooted. The other server in the cluster, labstore1007.eqiad.wmnet
has been rebooted already, but we won't be doing any pre-failover for
operative reasons.
Apologies in advance for any inconvenience, and please let us know any
issue you may find after these operations.
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hello!
I need to shut down the tools-dev host in order to move it to a
different server. The downtime will be brief, but in the meantime I
recommend people move their work to a different bastion (e.g.
tools-login.wmflabs.org) in order to avoid interruption.
This will happen on or near 15:00 UTC on Tuesday, 2018-11-20. I'll also
send alerts to sessions on the bastion prior to the shutdown.
-Andrew
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Reminder: Technical Advice IRC meeting again **Wednesday 4-5 pm UTC** on
#wikimedia-tech.
Question can be asked in English & German.
The Technical Advice IRC Meeting is a weekly support event for volunteer
developers. Every Wednesday, two full-time developers are available to help
you with all your questions about Mediawiki, gadgets, tools and more! This
can be anything from "how to get started" over "who would be the best
contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Next monday 2018-11-19 we will be rebooting several Cloud VPS
infrastructure servers [0] for maintenance and security updates.
This is just a simple reboot of servers and we don't expect any outage
or major interruptions, but some services may be down briefly:
* Horizon and Wikitech may misbehave
* instance creation/deletion/shutdown, etc
* CI tests may stop running
Apologies in advance for any inconvenience, and please let us know any
issue you may find after these operations.
[0] cloudcontrol1003, cloudservices1003, labcontrol1001, labservices1001
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce