Die CeBIT sieht sich mit ihrem Leitthema rund um den digitalen Wandel auf Kurs. Vor allem die Technologienation Japan als diesjähriges Partnerland gilt als Trumpf. Und die CeBIT-Stadt Hannover lässt sich vom Leitthema inspirieren.
Quelle: Heise Tech News
In case you missed it, this week we’re celebrating #Docker’s 4th Birthday with meetups all over the world (check out #dockerbday on twitter). This feels like the right time to look back at the past 4 years and reflect on what makes the Docker Community so unique and vibrant: people, values, mentorship and learning opportunities. You can read our own Jérôme Petazzoni’s blog post for a more technical retrospective.
Managing an open source project at that scale and preserving a healthy community doesn’t come without challenges. Last year, Arnaud Porterie wrote a very interesting 3-part series blog post on open source at Docker covering the different challenges associated with the People, the Process and the Tooling and Automation. The most important aspect of all being the people.
Respect, fairness and openness are essential values required to create a welcoming environment for professionals and hobbyists alike. In that spirit, we’ve launched a scholarship program and partnerships in an attempt to improve opportunities for underrepresented groups in the tech industry while helping the Docker Community become more diverse. If you’re interested in this topic, we’re fortunate enough to have Austin area high school student Kate Hirschfeld presenting at DockerCon on Diversity in the face of adversity.
But what really makes the Docker community so special is all of the passionate contributors who work tremendously hard to submit pull requests, file GitHub issues, organize meetups, give talks at conferences, write blog posts or record Docker tips videos.
Leadership, mentorship, contribution and collaboration play a massive role in the development of the Docker Community and container ecosystem. Through the organization of the Docker Mentor Week last year or a Docker Mentor Summit at DockerCon 2017, we’re always trying to emulate the community and encourage more advanced users to share their knowledge with newcomers.
A great example of leadership and mentorship in the Docker Community is Docker Captain Alex Ellis. We could not write a blog post on #PiDay without mentioning Alex and the awesome work he does around Docker and Raspberry Pi. In addition to sharing his knowledge through blog posts and videos, Alex is actively inspiring and mentoring younger folks such as Finnian Anderson. Alex’s support and advocacy got Finnian invited to DockerCon 2017 to give a demo of a Raspberry Pi-driven hardware gauge to monitor a Docker Swarm in real time.
If you’re pumped about all the things you learn and all the people you meet at Docker events, you’re going to love what we have planned for you at this year’s DockerCon! We’re giving everyone at DockerCon access to a tool called #MobyMingle to connect with people who share the same Docker use cases, topic of interests or hack ideas, or even your favorite TV shows. So no matter where you’re traveling from or how many people you know before the conference, we will make sure you end up feeling at home!
Register for DockerCon 2017
Docker turns 4 – our take on what makes the docker community so vibrant and unique #dockerbdayClick To Tweet
The post Docker Turns 4: Thank you Docker Community! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Neue Anwendungen bringen einen stetig steigenden Datenaustausch. Ein Stadtnetzbetreiber mit einem FTTH-Netz meint deshalb, dass 250 MBit/s nicht das Ende sein können. (Glasfaser, Open Access)
Quelle: Golem
Das Mehrspieler-Actionspiel Quake Champions soll an das schnelle Gameplay von Quake 3 Arena anknüpfen – und auch als kostenlose Version erscheinen. Die Closed Beta soll innerhalb der nächsten vier Wochen starten.
Quelle: Heise Tech News
In case you missed it, this week we’re celebrating #Docker’s 4th Birthday with meetup celebrations all over the world (check out #dockerbday on twitter). This feels like the right time to look back at the past 4 years and reflect on what makes the Docker Community so unique and vibrant: people, values, mentorship and learning opportunities. You can read our own Jérôme Petazzoni’s blog post for a more technical retrospective.
Managing an open source project at that scale and preserving a healthy community doesn’t come without challenges. Last year, Arnaud Porterie wrote a very interesting 3-part series blog post on open source at Docker covering the different challenges associated with the People, the Process and the Tooling and Automation. The most important aspect of all being the people.
Respect, fairness and openness are essential values required to create a welcoming environment for professionals and hobbyists alike. In that spirit, we’ve launched a scholarship program and partnerships in an attempt to improve opportunities for underrepresented groups in the tech industry while helping the Docker Community become more diverse. If you’re interested in this topic, we’re fortunate enough to have Austin area high school student Kate Hirschfeld presenting at DockerCon on Diversity in the face of adversity.
But what really makes the Docker community so special is all of the passionate contributors who work tremendously hard to submit pull requests, file GitHub issues, organize meetups, give talks at conferences, write blog posts or record Docker tips videos.
Leadership, mentorship, contribution and collaboration play a massive role in the development of the Docker Community and container ecosystem. Through the organization of the Docker Mentor Week last year or a Docker Mentor Summit at DockerCon 2017, we’re always trying to emulate the community and encourage more advanced users to share their knowledge with newcomers.
A great example of leadership and mentorship in the Docker Community is Docker Captain Alex Ellis. We could not write a blog post on Pi Day without mentioning Alex and the awesome work he does around Docker and Raspberry Pi. In addition to sharing his knowledge through blog posts and videos, Alex is actively inspiring and mentoring younger folks such as Finnian Anderson. Alex’s support and advocacy got Finnian invited to DockerCon 2017 to give a demo of a Raspberry Pi-driven hardware gauge to monitor a Docker Swarm in real time.
If you’re pumped about all the things you learn and all the people you meet at Docker events, you’re going to love what we have planned for you at this year’s DockerCon! We’re giving everyone at DockerCon access to a tool called #MobyMingle to connect with people who share the same Docker use cases, topic of interests or hack ideas, or even your favorite TV shows. So no matter where you’re traveling from or how many people you know before the conference, we will make sure you end up feeling at home!
Register for DockerCon 2017
Docker turns 4 – our take on what makes the docker community vibrant and unique dockerbday…Click To Tweet
The post Docker Turns 4: Mentorship, Pi, Moby Mingle and Moar appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Wie bereits im Jahr 2015 gibt es erneut Gerüchte darüber, dass Citrix verkauft werden soll. Das Unternehmen steht unter dem Druck eines Hedgefonds und hat deshalb auch schon Firmenteile veräußert. (Citrix, Dell)
Quelle: Golem
Die Toilette der Zukunft ist intelligent und digital vernetzt – zumindest wenn es nach Hersteller Duravit geht. Der Hersteller ein WC, dass via App auf Wunsch vollautomatisch den Urin des Nutzers analysieren soll.
Quelle: Heise Tech News
Mit Teams hat Microsoft einen neuen Dienst für Office 365 vorgestellt. Es handelt sich um einen digitalen Arbeitsplatz zum Vernetzen von Mitarbeitern. Neben der zentralen Chat-Funktion bietet die Anwendung ebenfalls Videokonferenzen.
Quelle: Heise Tech News
Portability is the key concept of interoperability. When systems are interoperable, we can move around code and processes between different infrastructure and platforms with minimal concern about the layers below. In the past, I’ve described this as a “black box” approach where users only care about the APIs and are blind to the implementation details. Ideally, APIs provide a perfect abstraction so that different implementations of the API are completely equal.
Sadly, even small implementation differences can break API interoperability.
That means that when users of open software install it, configuration choices for their environment or technology stack may cause the software to behave slightly differently and break interoperability. In another common case, the pace of innovation creates problems. New features being introduced can also change behaviors that make it difficult to interoperate between versions. While these issues may not impact the single user’s experience, they have profound impacts across the community.
Without interoperability, it’s difficult to build ecosystems and share best practices.
Ecosystem and shared practices are a significant part of the user value for large, complex open platforms like OpenStack, Cloud Foundry and Kubernetes. The ecosystem ensures that people build products on top of the platform that furthers the platforms’ relevance and utility. Shared practices help control the cost of operating the platforms by allowing the community to benefit from communal operational experience.
We can drive interoperability with architectural work that drives consistent behaviors or add APIs to discover useful variations. Communities need to be reasonably opinionated to reduce variations. When variation is required—such as when different SDN layers or container runtime engines—then projects should maintain clear APIs to abstract implementations.
There are also interoperability tasks within the work to maintain a project. This work takes the form of maintaining and applying compliance tests to running systems such as OpenStack DefCore/Refstack work championed by IBM and others. It also means enforcing parity between development, test and production environments. Interoperability breaks down quickly when developer and continuous integration environments are very different from production deployments.
But the primary driver for interoperability is users demanding it.
Users and operators can put significant pressure on project leaders and vendors to ensure that the platforms are interoperable. That means rewarding vendors who take on time to work on the type of work I described in addition to adding features. It also means rewarding vendors who help drive operational improvements in a shared way. Those actions encourage shared best practices.
If you like these ideas, please subscribe to my blog, RobHirschfeld.com where I explore site reliability engineering, DevOps and open hybrid infrastructure challenges. And join me at my session at Interconnect 2017: Open cloud architecture: Think you can out-innovate the best of the rest?
The post How open communities can hurt, and help, interoperability appeared first on #Cloud computing news.
Quelle: Thoughts on Cloud
Cloud Foundry on Azure keeps getting better.
We now support the use of Azure Blob Storage and Managed Disks with Cloud Foundry.
These enhancements come on the heels of the launch of Pivotal Cloud Foundry on Azure and a series of Azure Service Broker releases. We continue to invest in deeper integration of Azure’s enterprise grade services with the open source Cloud Foundry platform.
Here’s how to get started with these new capabilities!
1.Use Azure Blob Storage for the Cloud Foundry Cloud Controller Blobstore
The Cloud Controller blobstore is a critical data store. Buildpacks, droplets, packages, and resource pools are all hosted this way. Operators can now use Azure Blob Storage for this component. Consequently,they will enjoy greater availability and scalability. Previously, an NFS server was required.
By default, the blobstore configuration uses the Fog Ruby gem. The Azure team worked with Fog community updating the Fog Azure RM gem to support this new feature.
Check out the Cloud Foundry documentation for background and configuration instructions. The BOSH deployment template (multi-node) is updated, using Azure Blob storage by default. This is also integrated with the upcoming Pivotal Cloud Foundry 1.10 release.
2. Use Azure Managed Disks
The Azure CPI V21 now supports the Azure Managed Disk Service in BOSH.
This simplifies VM/disk deployment and management. It also provides superior scalability, security and reliability.
Operators can choose to create new deployments using managed disks. They can also migrate existing deployments to managed disks. Just make a quick edit to the BOSH manifest file and you’re done! Check the guidance for Using Managed Disks for detailed steps.
This enhancement will be baked into the BOSH and Pivotal Cloud Foundry deployment templates soon. Look for those to be published in the coming months.
We’ve seen tremendous interest in Cloud Foundry running atop Azure. As a result, we are making additional investments. Engineers are working to bring more Azure database services to the Cloud Foundry runtime and service broker. And soon, you'll be able to interact with logs and metrics from your Cloud Foundry apps using Azure OMS. Let us know if you have any suggestions by entering your ideas here.
Quelle: Azure
