- Edge-computing - lists.opendev.org

Next Tuesday's (November 19) weekly call is cancelled
by Ildiko Vancsa 15 Nov '19

15 Nov '19

Hi, As a few people from the group will be at Kubecon next week we are cancelling the weekly call for next Tuesday. The next call will be on __November 26 at 1500 UTC__. For more information and agenda please see the wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Thanks, Ildikó

1 0

Call for Paper: [Computers]: Special Issue "Simulation, Imaging and Modelling for Biomedical Systems" (Scopus, ESCI, 50% discount, Deadline Approaching)
by Blink Yu 14 Nov '19

14 Nov '19

[Apologies if you receive multiple copies of this message] ==================================== Special Issue "Simulation, Imaging and Modelling for Biomedical Systems" Deadline for manuscript submissions: 15 December 2019 Guest Editor: Dr. Elena Casiraghi and Dr. Barbara Barricelli Department of Computer Science; Università degli Studi di Milano, Italy Website: https://www.mdpi.com/journal/computers/special_issues/SIM_BS ===================================== Dear Colleagues, Over the past decades, a continuous increase in computational power, together with substantial advances in the digital image processing and pattern recognition fields, has motivated the development of computer-aided diagnostic (CAD) systems, augmented and virtual reality applications for surgical planning and simulation, and digital-twin applications for healthcare. Thanks to their effective, precise, and repeatable results, validated CAD systems are nowadays exploited as a valid aid during diagnostic procedures. Surgical simulation applications have become an essential part of surgical procedures as well as training, while research on the development of digital-twin applications in healthcare is continuously increasing, to deliver significant societal and health benefits. Similar important advances in the field of microscopy image analysis have been motivated by the advent of digital microscopes producing high-resolution digital images. Indeed, in the past thirty years the development of computerized systems that have helped pathologists in their analysis of images obtained by fluorescence, histochemical, and immunohistochemical labeling has become a main research focus for computer scientists and clinicians. State-of-the-art automatic microscopy image analysis systems automatically identify biological structures of interest and then try to reproduce the evaluation and quantification performed by expert pathologists and clinicians. These tools are much appreciated in the field for their potential to minimize the inherent subjectivity of manual analysis and to largely reduce the workload of clinicians via high-throughput analysis. This Special Issue intends to provide a comprehensive overview of recent, theoretical, and/or practical advances and new trends in biomedical/microscopy image enhancement and analysis, vision modelling, and general physiological models applied to biomedical/microscopy image processing and advanced visualization methods and devices, and to discuss their applications in the biological and medical fields. Keywords: BioMedical/microscopy image enhancement Biomedical/microscopy image quality assessment Biomedical/microscopy image analysis Computational approaches for citology and histology Computer-aided diagnosis Neuro imaging BioMedical/microscopy image databases Machine learning and artificial intelligence Image segmentation, registration, and fusion Interventional imaging systems Image-guided interventions and surgery Surgical and interventional simulation systems Interventional tracking and navigation Surgical planning and simulation Surgical visualization and mixed, augmented and virtual reality Digital twins and end-user development in biomedicine Interventional software and user interfaces Physiological models Dr. Elena Casiraghi Dr. Barbara Barricelli Guest Editors -- Mr. Blink Yu Managing Editor E-Mail: blink.yu(a)mdpi.com Skype: live:c91693ac8277e1f0 -- MDPI Wuhan Office No.6 Jingan Road, 430064 Wuhan, China MDPI Postfach, CH-4020 Basel, Switzerland http://www.mdpi.com -- Disclaimer: MDPI recognizes the importance of data privacy and protection. We treat personal data in line with the General Data Protection Regulation (GDPR) and with what the community expects of us. The information contained in this message is confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this message in error, please notify me and delete this message from your system. You may not copy this message in its entirety or in part, or disclose its contents to anyone.

1 0

Meeting is on for this Tuesday (November 12)
by Ildiko Vancsa 12 Nov '19

12 Nov '19

Hi, As I need to update the calendar invites it is a quick heads up that we will have an attempt to have a meeting this week to recap the discussions happened at the Open Infrastructure Summit in Shanghai last week. As we have KubeCon happening next week which may also affect attendance of our weekly call I’m hoping that this week and next week we can spread the information and then keep on working on items onwards. Dial in info and agenda is here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Thanks, Ildikó

1 0

Joint sessions on Thursday at the PTG
by Ildiko Vancsa 07 Nov '19

07 Nov '19

Hi, It is a friendly reminder that we have two joint sessions at the PTG today: * meeting with the Neutron team today at 12:00pm in room 431 * meeting with the Cinder team at 1:30pm at table Austin Edge PTG etherpad: https://etherpad.openstack.org/p/PVG-ECG-PTG Thanks, Ildikó

1 0

Cyborg joint session on Wednesday (November 6) at the Shanghai PTG
by Ildiko Vancsa 05 Nov '19

05 Nov '19

Hi, Just a quick heads up that we are planning a joint session with the Cyborg project tomorrow (November 6) at 4pm at the Cyborg table (Diablo) at the PTG (https://www.openstack.org/ptg/) The objective for the discussion is to kick off the collaboration between the edge group and the Cyborg project to make sure we have a good awareness on both sides around how acceleration devices are leveraged on the edge and what we need to do to make sure the infrastructure services support the needs. Edge group PTG etherpad: https://etherpad.openstack.org/p/PVG-ECG-PTG Thanks, Ildikó

1 0

PTG cross-project session scheduling and plans
by Ildiko Vancsa 30 Oct '19

30 Oct '19

Hi, As a few people from the group are already on the road and had to skip the meeting today I’m dropping this mail as a reminder to the PTG planning. We have a few cross-project slots that are currently scheduled for Thursday, namely: * Neutron - Thursday 12:00pm - 12:30pm * Cinder - 1:30pm - A few more cross-project sessions scheduled for Friday * Ironic - Friday 1:30pm - * Airship - some time in the afternoon, check right after lunch Beyond the above you can find the currently planned topics here: https://etherpad.openstack.org/p/PVG-ECG-PTG Please reply to this thread asap if any of the cross-project sessions are colliding with other activities. Please add comments to the etherpad or reply to this thread with further questions or comments. Thanks, Ildikó

2 4

Edge call is on now
by Ildiko Vancsa 15 Oct '19

15 Oct '19

Zoom is fixed. :) https://zoom.us/j/879678938 Thanks, Ildikó

2 1

StarlingX's Use of Keystone for Kubernetes Authentication
by Waines, Greg 12 Oct '19

12 Oct '19

Hey Colleen, Ildiko asked me to summarize StarlingX’s experiences with using Keystone in STX R2.0 . Specifically summarize StarlingX’s experiences with using Keystone for Kubernetes API Authentication and Docker Registry Authentication. Greg. Background: In STX 1.0 * StarlingX managed a Baremetal OpenStack Cloud, * All the OpenStack Services, e.g. neutron, nova, cinder, etc. ... including StarlingX itself, used Keystone to authenticate, In STX 2.0 * StarlingX changed to manage a Baremetal Kubernetes Cluster, with a Containerized OpenStack Cloud running on top of Kubernetes. * The solution is now layered * StarlingX Kubernetes * Keystone * StarlingX ... authenticating with the Platform Keystone * Kubernetes ... authenticating with the Platform Keystone (intent ... but abandoned) * Docker Registry ... authenticating with the Platform Keystone * OPTIONAL Containerized OpenStack * Keystone, * Nova, Neutron, Glance, Cinder, Horizon, Heat * ... all authenticating with the OpenStack Keystone * Barbican, Telemetry (Ceilometer, Panko, Gnocchi, Aodh), Ironic * ... all authenticating with the OpenStack Keystone Use of Keystone in “StarlingX Kubernetes”: * Ironically we were using Keystone for authentication of a Baremetal Kubernetes Cluster * Normally this would be done for a Kubernetes Cluster running on top of OpenStack * i.e. the Kubernetes Cluster using services of the underlying cloud provider * e.g. using the cloud provider’s authentication services, load balancing services, storage services, etc. * ( This doesn’t have any relevance to this discussion ... just thought I’d point it out. ) * StarlingX Services authenticating with Keystone * No issues ... did it in STX 1.0 ... so no changes required. * Docker Registry authenticating with Keystone * This link: https://docs.docker.com/registry/spec/auth/token/ describes how Docker Registry token authentication works * The Authentication/Authorization Service in the above link’s diagram, MUST be a JSON Web Token Server supporting OAUTH2 interface to docker, * Docker provides an EXAMPLE of such a Token Server in its github: https://github.com/docker/distribution/tree/master/contrib/token-server , which can be copied and updated to handle your preferred authn/z backend. * Docker guy we spoke to was kind of surprised someone hadn’t done this already for keystone. * So StarlingX started with this example and built a JSON Web Token Server supporting OAUTH2 interface to docker and with a backend talking to Keystone * Located here: https://opendev.org/starlingx/containers/src/branch/master/registry-token-s… * ... we are still doing this currently. * Kubernetes API authenticating with Keystone * So we were using the Keystone Authentication and Authorization Webhooks and the Client-Keystone-Auth defined here: https://github.com/kubernetes/cloud-provider-openstack * I presented this solution in this presentation at the DENVER OPENSTACK SUMMIT https://www.dropbox.com/s/gnyf3mtyf5janq1/KubernetesMultiTenancyWithKeyston… * See slides 6,7,8 * This did not work out-of-the box circa early-2019, we had to fix the following issues: * Had to add Authentication to Armada (upstreamed) * StarlingX used Armada to manage set of helm charts for openstack * Armada did NOT support kubernetes authentication * StarlingX team added it and upstreamed it * Had to fix lock feature for Authentication in Armada (upstreamed) * After previous upstream commit to support authentication in armada, * A commit went in to Armada to support locking (for atomic transactions I think), and the commit forgot to take into account authentication, * StarlingX team fixed this commit upstream. * Had issues with expiring tokens with the client-keystone-auth * I believe that the client-auth-plugin was using a cached keystone client that was holding on to tokens that eventually expired * We put in some workaround for this ... can’t remember details. * Eventually we “generally” had this working ... except for a specific but-easily-repeatable use case, where the system would hang or fail in client-keystone-auth (being called from the StarlingX systemInventory process) * It was a path in the client-keystone-auth, where the code was trying to refresh the token in the kubernetes client, * Investigation suggested that the client-keystone-auth was not compatible with our version of eventlet(0.18.4) ... which is a few years old, * There was no way to update the token through “proper” methods. Attempting to delete the client caused the code to mysteriously freeze. If you tried to set the client to none on 1 line then set it to a new client in another line, the code would freeze as you try to set the client to none. * we managed to get it to work by digging through the internals of the client and setting a new token that way, but this was somewhat of a hack. * Since eventlet was used everywhere and we were getting close to STX 2.0 release date, we felt like it was too much risk to try and upversion it. * So, we abandoned the “Kubernetes API authentication with Keystone” work. * StarlingX Roadmap wrt Kubernetes API Authentication * Given our struggles in getting Keystone working ... a little uneasy in picking it up again, * Also Authentication requirements from StarlingX 2.0 Users of the Kubernetes Layer only, are asking for things like: * OpenID Connect (OIDC, OAuth2) type authentication, * LDAP * SAML * Integration with specific authentication platforms like: * GitHub, * LinkedIn, * Azure, * Windows Active Directory * I suspect many of these would require development in Keystone to support. * Whereas there are other existing opensource solutions that can provide that now. Greg.

2 1

PTG planning - ACTION NEEDED
by Ildiko Vancsa 10 Oct '19

10 Oct '19

Hi, I’m reaching out with a friendly reminder that it is time now to prepare for the upcoming PTG (https://www.openstack.org/ptg/) which will be held in Shanghai, November 6-8. The Edge Computing Group session is scheduled for all day Friday (November 8). We have time to discuss items that are more relevant for the working group’s activities as well as organizing cross-project sessions. I created an etherpad which has a few items there already: https://etherpad.openstack.org/p/PVG-ECG-PTG Please add ‘+1’s next to the items you are interested in discussing as well as comments or new items to talk about. We will continue the planning on the next weekly call next Tuesday (October 15). It is crucial to identify projects to have sessions with to make sure we get a chance to schedule the collaborative sessions. Please let me know if you have any questions. Thanks and Best Regards, Ildikó

1 0

FW: [ironic] FFE: Add idrac HW type Redfish virtual media boot interface
by David.Paterson＠dell.com 24 Sep '19

24 Sep '19

My associate wasn't getting much traction with this FFE and I know this group expressed interest in this feature. Please take a look and review and +1 if possible. Thanks, dp From: Pioso, Richard Sent: Monday, September 23, 2019 8:09 PM To: 'openstack-discuss(a)lists.openstack.org' Subject: [ironic] FFE: Add idrac HW type Redfish virtual media boot interface Hi, I request a late feature freeze exception (FFE) for https://review.opendev.org/#/c/672498/ -- "Add Redfish vmedia boot interface to idrac HW type". There is high demand from operators for this feature. They would be delighted if it were included in Train. We believe it is a low risk change, because of the following: 1) It affects only the idrac hardware type. 2) The highest priority boot interfaces supported by the idrac hardware type remain so. 'ipxe' and 'pxe' continue to have the highest priority, and the new 'idrac-redfish-virtual-media' has the lowest priority. The new order from highest to lowest priority is 'ipxe', 'pxe', and 'idrac-redfish-virtual-media'. 3) The new interface is based on and almost entirely leverages an already merged interface implementation, 'redfish-virtual-media'. [1] Please let me know if you have any concerns or questions. Thank you for your consideration. Rick [1] https://review.opendev.org/#/c/638453/

1 0