GNU/Linux and opensource news gathered
«  février 2018
lundi mardi mercredi jeudi vendredi samedi dimanche
29 30 31 1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 1 2 3 4
retour à la date courante

Aujourd'hui 4 nouvelles :

  • From Crisis to Resilience: Strengthening Critical Caribbean Internet Infrastructure, par Bevil Wooding, 1er février 2018

    jeudi 1er février 2018 :: Team ARIN :: RSS
    In 2017, six hurricanes traversed the Caribbean. Ten Caribbean countries, most in the ARIN region, were directly impacted by the most dangerous of these, Hurricanes Irma and Maria.  Communications infrastructure in the affected territories took a severe hit, with the islands of Barbuda and Dominica being taken completely offline. Weakness in telecoms networks, deficiencies in regulatory policy and the scarcity of skilled technical personnel were all exposed by the storms, and especially in the critical stage of recovery and relief. Drawing from the experience, the Caribbean is now taking steps to ensure that its networks and critical Internet infrastructure are more robust and more resilient.

    Caribbean Crisis in Context

    The frequency and intensity of the 2017 storms represent a worrying escalation of climate-based catastrophe. It is also profoundly challenging the historic constraints of economy, infrastructure and human capacity that define small states in the region.
    By some estimates, relief and recovery efforts alone could cost upwards of US$150 billion.  Given the high cost of recovery, and the already high debt to GDP burden carried by most Caribbean territories, the region’s capacity to rebound diminishes each year.  Consequently, the Caribbean enters each hurricane season with more fragile communications infrastructure than the year before.

    Focus on Network Resilience

    The failure of Caribbean communications networks was a particularly worrying consequence of the recent storms. However, the increasing threat of severe weather events also highlights the urgent need to improve the region’s communications infrastructure.
    Thankfully, regional organizations like the Caribbean Telecommunications Union (CTU) and the volunteer-based, non-profit Caribbean Network Operators Group (CaribNOG), are focusing special attention on strengthening Caribbean network resilience.  They have found solid support from Internet organizations such as Packet Clearing House (PCH) and those of us here at ARIN because of our strong interest and history in supporting critical Internet infrastructure in the region.
    The CTU has empaneled a special Commission for Caribbean Network Resilience to critically examine the region’s communications vulnerabilities and come up with recommendations for more resilient infrastructure, technologies and methods. There is strong support for the Commission from the industry, including IBM, Cisco, and Intel, as well as inter-governmental organizations like the World Bank and Organization of American States, as it works to develop actionable recommendations for regional governments, regulators and communications ministries. It is hoped that these recommendations, expected before the start of the 2018 hurricane season, will help strengthen local and regional network infrastructure and spur the creation of more autonomous networks in the region.
    CaribNOG is developing special software applications to address disaster preparedness and response. It is also designing technical workshops targeting network operators and computer engineers to help with the proliferation of autonomous networks and strengthening of critical Internet infrastructure in the Caribbean. The CTU and CaribNOG are collaborating to help support capacity building efforts targeting the Caribbean’s technical community, policy makers and regulators.
    We are working closely with the CTU and CaribNOG to help support capacity building efforts targeting the Caribbean’s technical community. Our ARIN in the Caribbean initiative is a key part of this support. We have planned a series of outreach events targeting countries in the ARIN region. We are also supporting the Commission for Caribbean Network Resilience in the development of specific recommendations for regional governments, regulators and communications ministries to strengthen their network infrastructure and build more autonomous networks in the region.
    The scale of the devastation wrought by this season’s hurricanes is unprecedented in recent Caribbean communications history. However, the Caribbean’s challenge is not only climate-change fueled hurricanes, but in the longer term, on other equally damaging implications such as sea-level rise, coral bleaching, drought, and other consequences of earth’s changing climate patterns.
    Now, there is an unprecedented commitment to work collaboratively to strengthen network resilience in the region. There is also new resolve to ensure that the Caribbean is better prepared for whatever the future brings.

    The post From Crisis to Resilience: Strengthening Critical Caribbean Internet Infrastructure appeared first on Team ARIN. Lire la suite Bevil Wooding
  • Skype now available as a snap for Linux users, par Canonical, 1er février 2018

    jeudi 1er février 2018 :: Ubuntu - news, usn :: RSS

    Skype snap widens availability in the Linux community with easy install and automatic updates
    London, UK – 1st February 2018 – Canonical, the company behind Ubuntu, announces today that Skype is now available as a snap, the universal Linux app packaging format.  Available as of todaythe release means that Skype can deliver its communication service to a wider range of Linux users, including millions on Ubuntu.
    Skype is used by millions of users globally to make free video and voice calls, send files, video and instant messages and to share both special occasions and everyday moments with the people who matter most.
    Skype has turned to snaps to ensure its users on Linux, are automatically delivered to its latest version upon release. And with snaps’ roll-back feature, whereby applications can revert back to the previous working version in the event of a bug, Skype’s developers can ensure a seamless user experience.
    The Skype snap will work natively on all Linux distributions that support snaps, including Linux Mint, Manjaro, Debian, Arch Linux, OpenSUSE, Solus, and Ubuntu. This Skype desktop application is compatible across the wide range of Linux platforms, opening it up to an increased range of devices and to millions of users.
    “Skype has been enabling the world’s conversations for over ten years,” said Jonáš Tajrych, Senior Software Engineer at Skype, Microsoft. “We want to be able to deliver the same high quality experience on Linux as we do on other platforms. Snaps allow us to do just that, by giving us the ability to push the latest features straight to our users, no matter what device or distribution they happen to use.”
    “We’re delighted to welcome Skype to the snaps ecosystem,” said Jamie Bennett, VP of Engineering, Devices & IoT at Canonical. “Skype, and the ever growing number of snaps it joins, looks to put the Linux user first, allowing them to enjoy the latest versions upon release and provide a wider range of applications for users to choose from.”
    Snaps are containerised software packages, designed to work securely within any Linux environment across desktop, the cloud and IoT devices. Thousands of snaps have been launched since 2016, with its appeal coming from the automatic updates and roll-back features, plus security benefits, allowing greater flexibility for developers on the one hand, and a more seamless experience for users on the other.
    Skype is available to download as a snap by clicking here or running snap install –classic skype.
    About Canonical
    Canonical is the company behind Ubuntu, the leading OS for cloud operations. Most public cloud workloads use Ubuntu, as do most new smart gateways, switches, self-driving cars and advanced robots. Canonical provides enterprise support and services for commercial users of Ubuntu. Established in 2004, Canonical is a privately held company.
      Lire la suite Canonical
  • Externally exposing a LXD-based Kubernetes service, par Canonical, 1er février 2018

    jeudi 1er février 2018 :: Ubuntu - news, usn :: RSS
    This article originally appeared on Rye Terrell’s blog

    So you’ve conjured up a Kubernetes cluster on top of LXD on your dev box. Cool. You’ve created a deployment, you’ve got a service directing traffic to it, and you can query it from your box. Sweet. Time to demo this to your boss!
    “Hey boss,” starts your email, “check it out — I’ve got our product running in a k8s cluster! Just click here to see it for yourself: https://…”
    Oops, what IP do you send your boss? You can’t use the internal LXD container IP. You can’t use the IP of your dev box, no traffic is going to reach the relevant container. Damn. What to do?
    There’s actually a few ways to solve this. Here, I’ll cover an iptables one-liner that will forward traffic on a particular port to the proper container.
    Let’s make sure we’re on the same page. First, I’ll create a “hello-world” deployment:
    $ kubectl run hello-world --replicas=2 --labels="run=load-balancer-example" --port=8080

    Then I’ll create an associated service (with type NodePort, since I want to expose it externally):
    $ kubectl expose deployment hello-world --type=NodePort --name=example-service

    Now we should be in roughly the same place. Let’s grab the NodePort for our service:
    $ kubectl describe services example-service
    Name:                     example-service
    Namespace:                default
    Labels:                   run=load-balancer-example
    Annotations:              <none>
    Selector:                 run=load-balancer-example
    Type:                     NodePort
    Port:                     <unset>  8080/TCP
    TargetPort:               8080/TCP
    NodePort:                 <unset>  30386/TCP
    Endpoints:                <none>
    Session Affinity:         None
    External Traffic Policy:  Cluster
    Events:                   <none>

    And find one of the nodes it’s running on:
    $ kubectl get pods --selector="run=load-balancer-example" --output=wide
    NAME                          READY     STATUS    RESTARTS   AGE       IP           NODE
    hello-world-58f9949f8-2cqw7   1/1       Running   0          1h     juju-2282c0-7
    hello-world-58f9949f8-k5zvl   1/1       Running   0          1h   juju-2282c0-3

    Next we’ll need to find the IP address associated with that node:
    $ lxc info juju-2282c0-3 | grep eth0
    eth0: inet vethV8TI50

    Finally, using the node IP and the NodePort information we just collected, we’ll set up an iptables rule (note that the port 8080 is the port I’ll expose on my host):
    iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 8080 -j DNAT --to-destination

    Feel free to use iptables-save and iptables-persistent to allow your new rule to survive a reboot.
    Now we can test it out from another host (note that is the IP of my host):
    $ curl
    Hello Kubernetes!

    Great! Alright, go finish that email.

    Want to know more?

    On February 7th, technical lead Stephane Graber will be presenting a webinar for Ubuntu Product Month that will dive into how LXD works, what it does, how it can be used in the enterprise, and even provide an opportunity for Q&A.
    Register For Webinar Lire la suite Canonical
  • Snapcraft Summit summary – day 2, par Kyle Fazzari, 1er février 2018

    jeudi 1er février 2018 :: Ubuntu - news, usn :: RSS

    The second day of Snapcraft Summits tend to be particularly productive as all the participants get more familiar with each other, and this one is no exception. In addition to developers from CircleCI, Electron, Microsoft, Plex, and Slack, today saw the addition of our friends from ROSHub joining us to hack on their snaps.
    Snapcraft recently (in v2.37) gained the ability to patch ELF files in classic snaps to have an rpath to load its libraries instead of relying on LD_LIBRARY_PATH. Some of the participants here ran into an issue with this new feature where they needed to set rpaths themselves, and Snapcraft overwrote whatever they did while patching. In a thrilling show of tactile force, Sergio Schvezov cranked out a fix for Snapcraft.
    Snapcraft uses Click for its command-line interface. Click requires a locale to be set, and raises an ugly error if it’s not. Unfortunately, this is often the case in some of the environments that run snapcraft, e.g. CI systems that spin up a Docker container to build and push a snap. A few participants hit this, and it was pointed out to be a terrible experience, so Kyle Fazzari whipped up a feature that fell back to C.UTF-8 if it was available. It was reviewed and available in the edge channel before the room could blink.
    In a similar vein, there were a number of issues discovered with the Snapcraft docker images, and Kyle devoted some time to making them shine with an eye toward rewriting the CircleCI tutorial to be much simpler.
    There has been some interest in adding a Kotlin plugin to Snapcraft. We finally have the skills and experience together in the same room to make it happen, so Leo Arias devoted a good chunk of time to working on his first Kotlin snap: ktlint.
    Leo also worked with James Henstridge to make a plan for integrating with Gnome Builder. The idea is to start with fairly basic integration to gauge interest before undertaking the more in-depth Snapcraft work required. Lire la suite Kyle Fazzari